CRMs with sales forecasting

HubSpot sells the sales half of its platform as a product in its own right, and the reason it appears on so many shortlists is the bottom of the range rather than the top. The free tools are not a trial: contact management, a deal pipeline, email tracking and a mailbox integration cost nothing and keep working, within a documented ceiling of two users and a thousand contacts. For a one- or two-person business running on a spreadsheet, that is a real answer rather than a lead magnet.

What the free tier buys is a path, and the path gets steep. Starter is US$7 per seat per month billed annually. Professional is US$90, and carries a required one-time onboarding fee of US$1,500 before you can use it, with Enterprise asking US$3,500 on the same basis. Those fees are published, but they turn a subscription into a project budget.

The catch is that setup and eventual cost pull in opposite directions. Getting started has almost no friction, but the tier most growing teams land on cannot be switched on without buying onboarding first, which turns a per-seat decision into a procurement one. What you get for staying is depth: custom objects, forecasting and automation higher up, a large catalogue of integrations, and a public API.

Pipedrive is built around one idea carried further than most: a sales pipeline is a board, and everything else is subordinate to moving cards across it. That focus is why the cheapest plan feels usable rather than crippled. You get leads, deals, contacts and a calendar in one workspace, and you can bring your existing records in from a spreadsheet or another system without paying more.

The cost of that focus appears on the second tier. Full mailbox sync, workflow automation and forecast reports are all held back to Growth, which more than doubles the per-seat price. A team that wants its email in the CRM — which is most teams — is not really choosing the entry plan, and it is worth pricing the tier you will actually end up on.

Scale headroom is the quiet strength: an administrator gets role-based access and a change record, and no ceiling on records is published anywhere. What holds up well is the surrounding infrastructure. The API is documented endpoint by endpoint and readable before you buy, the catalogue of integrations is genuinely large, and pricing is published in full at every tier rather than hidden behind a form. Data control is ordinary rather than bad: a published privacy notice and a separate processing agreement, but no choice of where your records are handled.

Odoo draws its free line somewhere nobody else does. Rather than capping users or records, it gives you one application at no cost for an unlimited number of people. If the application you pick is the CRM, a company of forty can run its pipeline on Odoo Online without paying anything, which is a genuinely different offer from the two-user free tiers elsewhere in this field.

Above that, pricing is per user for all applications together: EUR 19.90 a month on yearly billing for Standard, or EUR 29.90 for Custom, which adds on-premise deployment, the Studio builder, multi-company support and an external API. The core is open source, so self-hosting is a real route and the data can sit on machines you control.

On value that is hard to argue with: an unlimited-user CRM at no cost. The catch is that the free tier is a doorway rather than a destination. The moment a second app is useful — invoicing, helpdesk, projects, all of which sit right there — the price becomes per user for everything, and the step is deliberate. There is also the configuration burden that comes with any suite: this is more product than a small sales team needs, and making it fit takes work that a single-purpose CRM does not ask for.

Freshsales is the sales half of a company whose reputation was built on helpdesk software, and it is priced like a product being used to open a door. Growth costs US$9 a seat each month on yearly terms, which buys a working pipeline with contact management and email, a rate more typical of a single-purpose tool than of a product with a large vendor behind it.

What sits above it is substantial. Pro at US$39 and Enterprise at US$59 add sequences, territory management, deeper reporting and the administrative controls a larger team needs, and the whole thing carries the integration surface of a vendor with several other products to connect to.

The thing to weigh is the add-on model. Branded documents cost US$19 a seat, and the AI agent is billed by session at US$49 per hundred, so the published rate is not the whole invoice for a team that wants either. The step from Growth to Pro is also steep — more than four times the rate — and the capabilities most growing teams reach for sit on the far side of it.

Capsule is one of the few entries here that seems entirely comfortable being small. There is a contact database, a sales pipeline and a task list, and the product does not spend much effort persuading you it is a platform. For a business of two or three people that mainly needs to stop losing track of conversations, that restraint is the feature.

The free tier is unusually honest about what it is. Two users, two hundred and fifty contacts, five custom fields and one pipeline — small numbers, but they include connecting a Gmail or Outlook account, which is the thing free plans in this category normally hold back. Moving to Starter at US$18 per seat raises the contact ceiling to thirty thousand and adds a shared mailbox, email templates and direct integrations.

The cost of that restraint is that depth arrives late. Workflow automation, multiple pipelines, project boards, access controls and the reporting that produces a forecast all begin at Growth, at US$36 per seat, and above Advanced at US$54 there is nowhere further to go. The tier descriptions are refreshingly specific about who each plan is for — one to five employees, then small businesses with sales teams — which makes choosing between them a shorter conversation than usual.

Salesflare is built on a complaint rather than a feature list: sales people do not maintain a CRM, so a CRM that depends on being maintained is a CRM full of stale records. Its answer is to construct the history automatically from the mailbox and calendar you already use, so the contact, the company and the thread of what was said are there without anyone typing them.

The pricing is straightforward and published in both dollars and euros. Growth is US$29 a user a month on an annual plan and Pro is US$49; paying monthly makes those US$39 and US$64. Forecasting and a documented migration path come with the subscription instead of being sold beside it.

The cost is that automatic is not the same as complete, and the model suits some sales motions far better than others. A relationship-led business with long threads gets a rich record for free; a high-volume outbound team working from lists gets much less from the automation and still pays for it. There is also no free plan, and the lead-search credits that fill in missing addresses are sold separately from the seat.

OnePageCRM is built on an argument about behaviour rather than about features. Every contact record carries a next action — one thing, with a date — and the interface is a queue of those actions rather than a board of deals. If your problem is that follow-ups quietly stop happening, the product is designed to make that failure visible.

On setup and value it is among the easier decisions here. Pricing starts at US$9.95 per user per month, records are unlimited, and the vendor states there are no paid add-ons, so the figure on the pricing page is the figure on the invoice. Email sync, click-to-call, workflow automation, forecasting and a published API are all part of it rather than upsells.

The tradeoff is the method itself. A product with an opinion this strong is excellent when the opinion matches how you work and irritating when it does not — a team running long, multi-stakeholder deals with no single obvious next step will spend its time fighting the queue. The pipeline tooling is also lighter than the products aimed at larger sales teams, which is a consequence of the same design choice rather than an oversight.

NetHunt belongs to the small group of products that answer the CRM adoption problem by refusing to be a separate place. It renders inside Gmail, so records, pipelines and the correspondence that produced them share one window, and nobody has to be persuaded to log in anywhere new.

What distinguishes it from lighter tools in the same space is structure. This is a real record model with fields, views and pipelines rather than a clever arrangement of labels, and the entry tiers are listed at US$24 and US$34 a seat, with month-to-month rates of US$30 and US$42.

The thing to weigh is the top half of the price list. Business and Business Plus show monthly rates of US$60 and US$84 but are quoted rather than published for annual billing, so a growing team cannot price its own future without a conversation. And like every Gmail-native product, the dependency is absolute: there is no version of this for a company running Microsoft, which settles the question before any feature comparison begins.

Flowlu is only partly a CRM. It is a business-operations tool for service companies, and the pipeline sits alongside project management, task tracking, invoicing and basic finance, on the theory that in an agency or a consultancy these are all views of one job rather than four systems.

The pricing is remarkable for what is included. There is a free tier, and the paid plans are US$6 and US$11 per user per month on yearly billing — which is a low rate for a product carrying project management, invoicing and finance alongside the pipeline.

The value case is the strongest thing about it — very little else asks so little for so much surface. The downside is the arithmetic of breadth. Nothing at this price is deep, and a company that mainly needs a sales CRM will find the pipeline module competent rather than considered, with the design attention spread across modules it may never open. The right way to read Flowlu is as an operations tool that happens to include a CRM, not as a CRM that happens to include invoicing.

Salesforce Starter exists because the company's main products cannot be bought the way small businesses buy software. It is packaged as a suite with sales, service and email in one place, published at US$25 per user per month, and — unusually for this vendor — you can sign up for it without a conversation. There is a free suite beneath it as well.

What that buys is a foothold in the largest ecosystem in the category. The partner network, the integration catalogue and the availability of people who already know the platform are all without equal here, and none of that goes away as the business grows.

The thing to weigh is what happens next. The published price carries a note that transaction fees apply, so the seat rate is not the whole cost, and everything above Starter returns to the sales-led model the rest of the vendor's range uses — quoted, negotiated and frequently partner-implemented. Starter is a genuine self-serve product; it is also the last rung on this ladder that behaves like one.

Krayin is an open-source CRM built on Laravel, and that framework choice is most of its argument. Extending a CRM usually means learning the vendor's own extension model; here it means writing PHP in a framework that a very large number of working developers already use, against a codebase you can read in full.

What follows from that is data control of the strongest kind available: records on hardware you own, with no third party holding a copy. There is no licence cost, the application runs on infrastructure you provide, and customer records never leave machines you own. For a development shop that wants a CRM shaped precisely to a process, starting from readable code in a familiar framework is a shorter path than configuring somebody else's product.

The cost is everything a vendor normally absorbs. No hosted plan is published, so provisioning, updates, backups and security are yours from the first day. It is also younger and less proven than the established open-source projects in this field, with a smaller community and less accumulated documentation, which matters most at exactly the moment something breaks.