Short Answer
If your sales process looks like most sales processes, buy. HubSpot, Pipedrive, and their competitors encode decades of standard pipeline practice, and for a contact-deal-stage-close motion they are hard to beat at the price. Build when your revenue does not move through a standard pipeline: when “a sale” involves site visits, quotes with engineering input, recurring contracts, compliance steps, or data from operational systems a generic CRM has never heard of. The businesses unhappiest with their CRM are almost never using a bad product. They are using a good product built for someone else’s process.
The Case for Buying
Off-the-shelf CRMs are mature, polished, and immediately available. The mobile apps work. The email integration works. Reporting dashboards, sequence tools, and a marketplace of add-ons come included. For a small team running a conventional pipeline, £15 to £50 per user per month buys an enormous amount of finished software.
There is also organisational wisdom baked in. Stages, follow-up cadences, deal probability: the defaults teach a young sales operation how selling is usually structured. Plenty of businesses become better at sales simply by adopting the discipline a CRM imposes.
Where Buying Goes Wrong
The trouble starts when your process and the product’s model disagree.
A trades business quoting from site surveys does not have “deals moving through stages”. It has enquiries, visits, quotes, revisions, and jobs, each with its own information and paperwork. Forcing that into pipeline stages produces a CRM full of half-true records that the team quietly stops updating.
Per-seat pricing punishes the businesses where everyone touches customers. If your fitters, your office manager, and your accountant all need to see customer records, you are paying sales-tool prices for people who never sell.
And the CRM island problem: customer data lives in the CRM, job data lives in the job system, financial data lives in the accounts package, and every question that spans two of them becomes an export-and-spreadsheet exercise. The add-on marketplace papers over some gaps. It rarely closes the ones that matter, because the gaps are specific to you.
The Case for Building
A custom CRM models your actual objects: surveys, quotes, contracts, renewals, whatever your revenue really consists of. Everyone who needs access has it, without a per-seat meter running. It connects natively to your operational systems, so “customer” means one record everywhere, not four records in four tools that disagree about the phone number.
Cost behaves differently too. A build is a capital cost followed by modest upkeep, against a subscription that rises with team size forever. On a five-year view, a growing team frequently pays more in seats than a focused build would have cost.
Fairness requires the other column. A custom CRM starts from zero: the polish, the mobile app, and the integrations that come free with HubSpot all have to be specified and built if you need them. Building a worse copy of Pipedrive is a real failure mode, and it happens to businesses that build before understanding why the product did not fit.
How to Decide
Describe your path from first contact to money in the bank, in your own words, without using the word “pipeline”. If what you described maps cleanly onto contacts, deals, and stages, buy the product and take the polish. If your description is full of objects and steps no CRM vendor’s demo has ever shown, that mismatch is what you would be paying for, month after month, in workarounds and abandoned records.
How We Approach This
CRM-shaped builds sit inside our custom software development work, usually as part of a wider operational system rather than a standalone contact list, with admin systems and API integrations connecting sales records to the job, billing, and reporting data around them. When a prospect’s process is genuinely standard we say buy, and have done so more than once, because a build they did not need would come back on us. If you want that judgement applied to your process, tell us how you sell. The general version of this trade-off is covered in custom software vs off the shelf, and if your CRM frustration is really a visibility problem, dashboard vs report may be the more relevant read.
