We build custom CRMs, so you would expect us to tell you to build one. We will not, because most of the time the right answer is to buy one. This piece is about the minority of cases where that stops being true, and how to recognise them before you have spent three years bending a tool to fit.
When off-the-shelf is the right answer
If your sales process looks like most sales processes, buy the tool. A pipeline of deals, a few stages, contacts and companies, email and calendar sync, some reporting. HubSpot, Pipedrive, Zoho and their competitors do this well, cost very little at small scale, and come with onboarding, integrations and a support desk. A custom build cannot beat that on day one, and should not try.
The same goes if your process is still changing. A CRM you can reconfigure in an afternoon is exactly what you want while you are working out how you sell.
Where the cracks appear
The problems start when the CRM has to hold more than a pipeline, because what you sell is not a simple deal. Three patterns come up again and again.
The object the CRM does not have. A van-hire business sells contracts tied to vehicles. A storage facility sells units tied to a building. A training company sells cohorts tied to dates. Generic CRMs have deals, contacts and companies, and everything else has to be bolted on with custom objects, which is where the fit starts to fail and the price tier jumps.
The process that lives outside it. Applications, credit checks, document collection, approvals, onboarding: the work between "they said yes" and "they are a customer". Most CRMs stop at the signature, so the rest ends up in email threads and a spreadsheet, and the CRM is only half the truth.
The per-seat bill. Off-the-shelf pricing is per user per month, and the features you need tend to sit in the higher tiers. A ten-person business on a mid-tier plan can be paying several thousand pounds a year, rising every time someone joins. That is fine while the tool is doing the job; it stops being fine once your team is working around it.
What a custom CRM actually is
It is worth being precise, because the phrase sounds grander than the thing. A custom CRM is a system that holds *your* objects (contracts, vehicles, units, whatever you actually sell), with *your* pipeline stages and *your* rules for what happens at each one, and that carries the customer from first enquiry all the way through onboarding without a handoff to email. It usually includes the parts of the process that generic CRMs leave out, because that is the whole point of building it.
What it is not: a clone of HubSpot. You do not need the marketing suite, the chatbot or the four hundred integrations. You need the twenty things your team does every day to work without workarounds.
The honest cost comparison
Off-the-shelf: low upfront, rising monthly, plus the hidden cost of the workarounds and the second system you keep alongside it. Custom: a one-off build, typically a few weeks for a focused CRM, then a small monthly fee for hosting and support, or a monthly fee that covers everything if you would rather hire it than own it. The crossover point is usually somewhere between two and three years, earlier if your team is growing or your plan tier is high, and the custom system is doing more work for the money because it covers the whole process.
Which one are you?
Buy if your process is standard, still changing, or the CRM is used by a small sales team for a straightforward pipeline. Build if the thing you sell is not a "deal", if the real work happens after the signature, or if you are paying for tiers you only need for one feature. And if you are not sure, it costs nothing to find out: bring your current setup to a free mapping session and we will tell you which side you are on, including when the answer is to keep what you have.