Custom CRM vs HubSpot or Salesforce: When Bespoke Actually Wins
Build a custom CRM when your core entities are not contacts and deals — they are bookings, jobs, cases, properties or patients — or when per-seat licensing is scaling faster than the business. Otherwise configure HubSpot, Salesforce or Pipedrive, which will be faster, cheaper and better supported.
Most businesses asking about a custom CRM should not build one, and an agency that says otherwise without asking what your entities are is selling rather than advising. The packaged CRMs are genuinely excellent at the pipeline model, and reproducing that from scratch is expensive and pointless.
- If your process fits a pipeline with custom fields, configure. The debate ends there.
- Build when the entities are wrong, not when the labels are.
- Compare on three-year cost at projected headcount, not on sticker price.
- Adoption decides success more often than features do.
The three situations where building wins
- 1. Your entities genuinely are not contacts and deals. A travel agency has bookings with supplier components and deposit schedules. A surveyor has jobs with sites and reports. Forcing those into a deal record means the real data ends up in a spreadsheet beside the CRM, which is the worst of both.
- 2. Per-seat licensing is outrunning the business. At ten seats this is noise. At eighty, on an enterprise tier, the three-year number frequently exceeds a bespoke build — and that comparison is the one worth running before anything else.
- 3. The data cannot sit with a third party. Genuine regulatory or contractual constraints, not a general preference. This is rarer than people claim but real when it applies.
What you give up by building
| Packaged CRM | Custom build |
|---|---|
| Running next month | Months before it is live |
| Thousands of integrations | You build the ones you need |
| Mature mobile apps | Another thing to build |
| Someone else handles updates | You own it forever |
| Hire people who know it | Everyone needs training |
| Pipeline model you must fit | A model that matches your business |
The hybrid most people miss
Keeping a packaged CRM for marketing and pipeline, and building only the operational system your business actually runs on, is frequently the right answer and rarely proposed. Marketing automation is a solved problem that nobody should rebuild. Your booking, job or case management is not, and that is where the custom work earns its money.
Frequently asked questions
How much does a custom CRM cost?
Typically £30,000–£80,000 for a focused one, £70,000–£150,000 with several integrations and complex permissions. Set that against three years of per-seat licensing at your projected headcount, including the tiers you will be pushed onto as you grow.
Can we customise Salesforce instead?
Up to a point, and heavy customisation of any packaged CRM eventually costs more than it saves — you end up paying licence fees for a platform you have substantially rewritten, with upgrade risk on top. If the customisation is fighting the data model rather than extending it, that is the signal.
What usually goes wrong?
Adoption. A CRM nobody updates is worse than none, because decisions get made on data that looks current. Build around how the team already works and migrate enough history to be useful on day one.
Do we have to choose immediately?
No, and starting on a packaged CRM is often the better route even if you expect to build later. It teaches you what you actually need, and that specification is worth more than a year of workshops.
We build custom CRMs — including TravelCRM, our own — and will say plainly when configuring an existing one is the better answer.
