Key takeaways
- Most businesses should buy. We say that as a company that builds CRMs.
- Two conditions justify building: per-seat cost at your headcount, and a process no product expresses.
- "Nobody uses our CRM" is nearly always a configuration problem, not a platform problem.
- Migration costs data quality and adoption — it needs a stronger reason than frustration.
- Whichever you choose, lead capture from every channel into one pipeline matters more than the platform.
Start from the assumption that you should buy
We build custom CRMs, and our honest advice to most businesses asking this question is to buy one. Off-the-shelf CRM is a mature category. The products are good, they are maintained for you, they integrate with everything, and they cost a fraction of a build in year one.
The reason to read further is that the exceptions are real and identifiable, and businesses in those situations frequently spend years fighting a product that was never going to fit.
The two conditions that justify building
Per-seat cost has become a real number. CRM pricing is typically per user per month. That is excellent value at ten users and a significant recurring cost at two hundred, particularly when many of those users need read access rather than the full product. A build has a large one-off cost and near-zero marginal cost per user, so there is a headcount at which the arithmetic reverses. Work out where that point is for you rather than assuming it.
Your sales process genuinely does not fit. Not "we would prefer different stage names" — that is configuration. This means a structure the product cannot express: quoting logic tied to a live production schedule, multi-party deals where several organisations own different parts of one opportunity, or approval chains that depend on data the CRM does not hold.
If neither applies, buy. Building because you dislike the interface is an expensive way to change an interface.
The problem that looks like a platform problem and is not
"Our sales team will not use the CRM" is the most common reason businesses consider replacing one, and it is almost never solved by replacing it. The cause is usually that the CRM asks the salesperson for information that benefits everyone except the salesperson.
If a rep must fill twelve fields to log a call and gets nothing back that helps them sell, they will not do it, and no amount of mandate changes that. The fix is to cut required fields to what the rep genuinely benefits from, automate everything derivable — call logs, email activity, source attribution — and make the reporting a by-product of the work rather than a tax on it.
Do this before migrating. If you move platforms without fixing it, you will have the same adoption problem on a new system, plus a data migration.
What building actually costs
The build itself is the visible cost and usually not the largest one. Data migration from spreadsheets or an existing system is consistently underestimated, because real CRM data is messier than anyone expects — duplicates, inconsistent formats, records nobody can identify.
Then there is ongoing maintenance. A custom CRM does not update itself, and integrations break when the systems at the other end change. Budget for a support arrangement rather than assuming the system is finished at launch.
And there is the integration surface. Off-the-shelf CRMs come with hundreds of prebuilt connectors. A custom build gets exactly the ones you commission, so list what you need to connect to before deciding.
What matters more than the build-or-buy answer
Getting every lead into one pipeline with its source attached. Website forms, Google and Meta lead adverts, WhatsApp, inbound calls and email enquiries all need to arrive in the same place, tagged with where they came from. Without that you cannot calculate cost per qualified lead by channel, which means you are optimising ad spend blind.
And speed of follow-up. Response time is one of the more reliable predictors of conversion, and a lead sitting unassigned overnight has usually already spoken to a competitor. Automatic assignment and a response-time alert are worth more than most feature differences between platforms.
Frequently asked questions
- When does a custom CRM become cheaper than a subscription?
- It depends on your seat count and per-user pricing, so it is worth doing the arithmetic rather than guessing. The point arrives sooner if many of your users need only read or light access, since you pay full price per seat for them on most products.
- Our team will not use the CRM we have. Will a new one fix it?
- Usually not. Adoption fails when the CRM asks reps for information that helps everyone but them. Cut the required fields, automate what can be derived, and make reporting a by-product of the work. Fix that before migrating, or you will carry the problem across.
- Can you integrate our CRM with WhatsApp and ad platforms?
- Yes — Meta and Google lead forms, website forms, WhatsApp and inbound calls can all route into one pipeline with the source attached. That attribution is what makes cost-per-qualified-lead reporting possible.
- How long does a custom CRM build take?
- Typically four to ten weeks depending on how many integrations are in scope and how clean the existing data is. Data migration is consistently the part that takes longer than expected.
- What happens to our data if we stop working with you?
- It is yours, on your infrastructure, and you receive the repository and deployment configuration. That independence is one of the main reasons to build rather than subscribe.
Work with us on this
We start every engagement with a written scope after a free discovery call.