What a custom CRM costs to build in the UK, the four cases where it beats Salesforce or HubSpot, and the ones where buying off the shelf wins.
A custom CRM in the UK costs roughly £40,000 to £120,000 to build and from £12,000 a year to maintain (an ongoing-development retainer from £1,000 a month), plus hosting. A licensed platform can cost less on day one and, for a 40-person team at list prices, costs more over five years — but the money is rarely what should decide it, and most companies asking this question are better off buying off the shelf.
Here is a case where the circumstances justified a custom build. A global luxury goods brand we have worked with had no unified view of its customers across European markets. Each country office had, over years, independently adopted its own e-commerce platform and its own point-of-sale tooling, and staff were tracking customer relationships in spreadsheets in the absence of any real CRM. A regional headquarters had already built a custom solution for its home market, but it was not reusable elsewhere. The result was duplicate customer records, no visibility of a customer’s history across boutique, web and repair-service touchpoints, and frontline staff with reporting needs an enterprise ERP system could not realistically serve.
The team had already evaluated enterprise CRM platforms and rejected them — not on capability, but on fit: licensing costs scaled with features they would never use, and off-the-shelf platforms move on their own release timeline, not the business’s. The organisation preferred to pay more up front for a system it could shape than to commit to ongoing licensing for one it could not.
What a licensed CRM actually costs
Before comparing anything, it is worth being precise about the other column, because per-seat pricing is where most of these comparisons go wrong:
Salesforce Sales Cloud — UK list prices per user per month: Starter Suite £20, Pro Suite £80, Core £156, Advanced £316 and Max £440; Core and above are billed annually (Salesforce UK pricing).
HubSpot Sales Hub — Starter from $20, Professional from $100 and Enterprise from $150 per seat per month, published in US dollars, plus a one-off onboarding fee of $1,500 for Professional and $3,500 for Enterprise (HubSpot product and services catalogue).
For a 40-person team that is £38,400 to £74,880 a year in licences alone at Salesforce UK list prices (Pro Suite, 40 × £80 × 12, up to Core, 40 × £156 × 12). HubSpot Sales Hub Professional is $48,000 a year for 40 seats (40 × $100 × 12) plus the $1,500 onboarding fee; because HubSpot prices in dollars we have kept it out of the five-year table below. All list prices are as of October 2026. Two caveats in both directions: list is not what a company with 40 seats actually pays, because vendors discount at that size and how much is a negotiation rather than a published figure; and list is not the whole bill either, because sandboxes, storage, integration platform seats and the premium support tier are all priced separately.
The five-year arithmetic
For the same 40-person sales and service team, over five years:
| Licensed platform | Custom build | |
|---|---|---|
| Year 1 | £38,400–£74,880 licences + £30,000 configuration | £85,000 build + £2,000–£4,000 hosting |
| Years 2–5 | £38,400–£74,880 a year + £10,000 a year of changes | £24,000 a year maintenance retainer (example: £2,000 a month) + £2,000–£4,000 a year hosting |
| Five-year total | £262,000–£444,000 | £191,000–£201,000 |
Licence lines are Salesforce UK list prices for 40 seats as of October 2026, before discount and before VAT: the low end is Pro Suite, the high end Core. The maintenance line assumes an ongoing development and support retainer of £2,000 a month (our retainers start from £1,000 a month); it is optional, and a team that runs the system in-house would replace it with its own staff cost. Only the custom column carries a hosting line, because running the software is part of what a licence buys. The bottom of that band is a real configuration at list price — two application instances, a managed database with a standby, backups and a staging environment, around £2,100 a year; the top of the band is our estimate, allowing for larger instances, longer backup and log retention and some headroom. Neither column includes the internal product owner a build needs and a licence does not.
At 40 seats the build is still the cheaper column over five years when you compare like for like: £191,000 against £262,000 at the low end (Pro Suite), and £201,000 against £444,000 at the high end (Core). On that basis the crossover falls between year one and year two. The retainer is the swing factor, though: it starts from £1,000 a month and has no fixed ceiling, so a custom build on a £4,000-a-month retainer (about £297,000 over five years) would cost more than a Pro Suite licence (£262,000). So the result depends on which licence tier you would really buy and how much ongoing development you would really commission. That is not the same as saying build. The licensed column is a known quantity you can walk away from at any renewal; the custom column is a delivery risk, a hiring commitment and a product you now own. What the arithmetic does say is that "it will be cheaper to buy" stops being automatically true somewhere around this size.
The licensed column is also the only one that grows with headcount. At 15 seats it is a third of the size and a build almost never pays back; at 200 seats it is five times the size and nothing else in the comparison matters much. Between those two points the deciding factor is not cost but fit.
The four cases where custom genuinely wins
Your process is the product. If how you qualify, price or schedule is a competitive advantage, forcing it into someone else’s object model degrades the thing you compete on. Bending Salesforce far enough to fit is its own expensive project — with the licences still payable.
The CRM is not really a CRM. Field service scheduling, clinical case management, logistics dispatch, lending workflows. Products sold as "CRM with an industry pack" often deliver a rough fit and an implementation partner on a day rate for the rest.
Data residency or regulatory constraints. Where records must live in specific infrastructure, or be auditable in ways a vendor cannot evidence, custom is sometimes the only route that passes review.
Licence cost scales with the wrong thing. If you need 300 occasional users — drivers, technicians, part-time staff — per-seat pricing punishes you for a usage pattern the vendor did not design for.
We build bespoke CRMs around your sales and service process, connected to your email, accounts and website. First release in 6–8 weeks; developers from £49/hour.
The cases where custom loses, and people build anyway
"The vendor’s UI is ugly." A build is an expensive redesign.
"We want to own our data." You already do. Export it.
"Our sales team is unusual." Almost every sales team believes this. Most are a pipeline with custom field names.
"It will be cheaper." Only past a scale most teams never reach — and only if someone maintains it, which is a permanent cost, not a project.
What actually drives the build cost
Custom CRM development cost is not one number, and the variation between two builds of the same nominal scope comes down to five things:
| Driver | Effect |
|---|---|
| Number of integrations | The largest single factor. Every system you must stay in sync with adds weeks to the build and maintenance for as long as it exists |
| Migration from the current CRM | Rarely under two weeks; dirty data can double it |
| Permissions model | "Everyone sees everything" is cheap; regional, role-based, record-level rules are not |
| Reporting | Ten fixed reports are trivial; a report builder is its own product |
| Mobile use | An offline-capable mobile client can add 40% to the whole build |
The middle route most people miss
You do not have to choose the whole thing. A licensed CRM for the standard parts — contacts, pipeline, email — with a custom application for the process that is genuinely yours, the two talking over an API. You pay licences only for the users who need them, and you build only the part that would never have fitted. It is less satisfying than a single system, and it is usually the right answer.
Before you decide
Write down the ten things your current setup stops you doing. If eight of them are configuration, buy. If eight of them are shape — your data does not fit, your process does not fit, your users do not fit — then a custom CRM is worth costing properly.
If you get to that point, our CRM development page sets out how we build these systems, and our bespoke software development page covers how we scope and price this kind of project. Where the real problem turns out to be the system underneath rather than the CRM on top, when to rebuild and when to refactor is the more useful question. And if the honest answer is that Salesforce fits after all, that is a much cheaper conclusion to reach before the build than during it.
Frequently asked questions
How much does a custom CRM cost in the UK?
A full CRM for a sales and service team is roughly £40,000 to £120,000 to build (a first release that replaces spreadsheets for one team can start from £10,000 as an MVP), then from £12,000 a year for an ongoing-development retainer (from £1,000 a month) and £2,000 to £4,000 a year for hosting. The retainer is optional: a team that runs the system in-house replaces it with its own staff cost.
Is a custom CRM cheaper than Salesforce?
Only past a certain size. For a 40-person team over five years, our worked example comes to £191,000–£201,000 for a custom build (assuming a £2,000-a-month retainer) against £262,000–£444,000 for Salesforce Sales Cloud at UK list prices (Pro Suite to Core, October 2026, before discount). At 15 seats a build almost never pays back. Between those points, fit matters more than cost.
How long does it take to build a custom CRM?
A first release usually takes 6 to 8 weeks after a Discovery phase, and the system then grows in releases. Migration from your current CRM rarely takes under two weeks and dirty data can double it; each integration adds time to the build.
What makes a custom CRM more expensive?
Five things: the number of integrations (the largest single factor), data migration, a role- or record-level permissions model, a self-service report builder instead of fixed reports, and an offline-capable mobile client, which can add 40% to the whole build.
When should you not build a custom CRM?
When the reasons are an ugly vendor UI, wanting to own your data (you already can export it), a belief that your sales team is unusual, or an assumption that it will be cheaper at your size. Often the better answer is a licensed CRM for contacts, pipeline and email plus a small custom application for the process that is genuinely yours.
Alexander Bessudnov
Alexander is an accomplished Chief Product Owner with a proven track record of leading successful product development initiatives at Magora. With a passion for innovation and a keen understanding of market trends, Alexander plays a pivotal role in shaping Magora's product strategy and ensuring the delivery of cutting-edge solutions to clients.
LinkedIn