Custom CRM vs off-the-shelf: how to decide

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.

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 to the 'lead → opportunity → closed' model these platforms were built around.

When that's the case, off-the-shelf CRM software creates a hidden cost that rarely shows up in ROI calculations: the cost of bending your process to fit the software, rather than having software that fits your process.

When off-the-shelf is the right choice:

Your sales process is reasonably standard. You're selling a defined product or service, tracking a pipeline, sending proposals and managing a customer relationship through recognisable stages. You have budget for licences at scale and want to benefit from continuous product investment. You need integrations with a large ecosystem of other tools — marketing platforms, accounting software, support systems.

In these cases, configuring an existing platform is almost always faster and cheaper than building something from scratch.

When bespoke makes more sense:

Your process has stages, data fields or logic that don't exist in the off-the-shelf model and can't be adequately approximated. You're paying for modules and features you will never use. Your team is consistently working around the system rather than in it — using spreadsheets alongside the CRM because the CRM doesn't quite capture what they need. You're in a regulated sector where data handling requirements create constraints that generic platforms don't accommodate well.

The economics often look different from the outside. A bespoke system has a higher upfront cost but no per-user licensing fees. Over three to five years, for a team of ten or more users, the maths often favours bespoke — especially when you factor in the cost of ongoing workarounds.

The question to ask:

Can your process be adequately represented in the standard model, with acceptable customisation? If the answer is yes, configure rather than build. If the answer is no — if you're looking at months of painful configuration, extensive custom development on top of a platform, and users who will struggle to use the end result — the case for building the right thing from scratch becomes much stronger.

This isn't a question you should answer alone. It requires someone who understands both your operation and the technical options — and who isn't trying to sell you a specific product.