Salesforce, HubSpot and Pipedrive are excellent products. They have vast feature sets, large user communities, extensive integrations and competitive pricing at scale. For a business with a straightforward sales pipeline, they're probably the right choice — and anyone who tells you otherwise is selling something.
The problem is that many businesses don't have a straightforward sales pipeline. They have renewals, compliance steps, site visits, multi-stakeholder approvals, complex pricing rules or service delivery processes that don't map cleanly onto the 'lead → opportunity → closed' model these platforms were built around.
When that's the case, off-the-shelf CRM creates a hidden cost that rarely shows up in the licence quote: the cost of bending your process to fit the software, rather than having software that fits your process.
The workaround audit
Before comparing prices, run a workaround audit on whatever you're using now or trialling. Count the spreadsheets kept alongside the system 'just in case'. Count the fields your team deliberately fills with placeholder text because the real answer doesn't fit the options. Count the steps in your actual process that happen outside the CRM entirely — in inboxes, notebooks and hallway conversations.
Every workaround is a process requirement the tool doesn't meet. A few are normal. A dozen means the tool is wrong, no matter how good its feature list looks.
When off-the-shelf is the right choice
Your sales process is reasonably standard. You're selling a defined product or service through recognisable stages. You have budget for licences at scale and want continuous product investment. You need the ecosystem — marketing platforms, accounting software, support tools that already integrate.
In these cases, configuring an existing platform is almost always faster and cheaper than building from scratch. Take this option seriously: the graveyard of software projects is full of bespoke builds that should have been a well-configured HubSpot.
When bespoke makes more sense
Your process has stages, data structures or logic that can't be adequately approximated — think a counselling service tracking referrals, assessments, counsellor allocation and case closure, or a utilities consultancy managing sites, suppliers and renewal windows rather than 'deals'. You're paying for modules you'll never use while missing the three features you actually need. Your team works around the system more than in it. Or you're in a regulated sector where data handling constraints rule generic platforms out.
Run the five-year maths
Licence comparisons are usually quoted monthly per user, which flatters off-the-shelf. The real comparison is total cost over three to five years. Fifteen users on a mid-tier platform at £40–£80 per user per month is £36,000–£72,000 in licences alone — before implementation consultancy, add-ons, the integration work every platform needs, and the staff time absorbed by workarounds.
A bespoke system has a higher upfront cost — typically £20,000 and up for a real operational platform — but no per-seat licences, no features you don't use, and no compromises where it matters. For a team of ten or more over five years, the totals are often surprisingly close, and the bespoke system fits the whole time.
There's a third option nobody mentions
Platform core with a bespoke layer on top. Keep Salesforce or HubSpot doing what it's good at — contacts, pipeline, email — and build the part that's genuinely yours: the portal, the operational workflow, the reporting view your team actually uses. This hybrid is frequently the right answer for businesses in the grey zone, and it's the option platform consultants rarely volunteer because it ends at a smaller invoice.
The question that decides it
Can your process be represented in the standard model with acceptable customisation? If yes — configure, don't build. If the honest answer is no — if you're looking at months of painful configuration, custom objects fighting the data model, and users who'll need training to tolerate it — the case for building the right thing is already made.
This isn't a question to answer alone, and it isn't a question to ask a Salesforce partner. It needs someone who understands your operation and the technical options — and who isn't paid more for one answer than the other.