How Much Does a Bespoke CRM Cost?

Most software agencies won't give you a straight answer to this question. Ask what a bespoke CRM costs and you'll get a contact form, a “let's hop on a call,” or a range so wide it tells you nothing. So here are real numbers.

Our own pricing, stated plainly: a focused bespoke CRM — one clear problem, one integration, real reporting — starts from €25,000 and takes two to four weeks. A full platform build, with multiple pipelines, live integrations into the tools you already run, role-based access and reporting your board will actually trust, starts from €42,000 across eight to sixteen weeks. Multi-entity systems with compliance obligations — SSO, audit trails, data separation between entities — start at €150,000 and go up from there depending on scope.

Those are our numbers, for the work we do. The wider market is broader than that, and it's worth explaining why — because if you go out and get quotes, you'll see figures that look nothing alike, and almost none of the people giving them will tell you what's actually driving the difference.

Why published CRM prices vary by a factor of fifty

Search for “bespoke CRM cost” and you'll find quotes from £2,000 to £250,000. Both figures are honest. They just describe two completely different things.

At the bottom of the market, £2,000–£15,000 buys a single-team tool: one pipeline, contacts, activity history, one automation rule, built by a competent freelancer in three to four weeks. If you run a five-person sales team and your process is genuinely simple, that may be all you need.

At the top of the market, you're paying for a regulated platform: multi-entity data separation, evidence for SOC 2 or ISO 27001, single sign-on, an analytics warehouse, audit logging on every write. That's six to eighteen months of engineering plus a security review, and the price reflects it.

The trap is assuming you're buying the first when your actual requirements describe the second. Compliance needs have a habit of surfacing around month three — a client asks for an audit trail, a regulator asks for data separation — and retrofitting that into a system that was never built for it costs far more than building it in from day one. This is the single most common way a CRM project blows its budget: not bad estimating, but a scope that was never actually the scope you thought you were buying.

Typical UK and EU bands in 2026

Nobody quotes what comes after launch, and it's the line people forget. A maintained production system — security patching, dependency updates, bug fixes, small enhancements — runs £1,500–£5,000 a month. Lighter systems cost £200–£500 a month plus hosting. Nothing runs on nothing.

It's worth budgeting for this before you sign off on a build price, not after. A system with no maintenance plan doesn't stay still — dependencies go out of date, the platforms it integrates with change their APIs without warning, and small requests from your own team pile up until someone has to do them anyway. Treat the monthly figure as part of the real cost of ownership, not an optional extra you can decide about later.

What actually drives the number up

The scope bands above only get you so far, because two projects in the same band can cost very differently once you get into the detail. Five things move a CRM quote more than anything else, roughly in this order:

1. 1

   Integrations. One clean, documented REST API is a matter of days. A legacy system with a SOAP endpoint, no sandbox environment and a vendor with a three-week response time is a month of work you cannot compress by adding more people. This is the single biggest driver of a quote moving.

2. 2

   Permissions. “Everyone sees everything” is close to free. Role-based access is a moderate lift. Row-level rules — this partner sees only their own introductions, this advisor only their own book, this administrator sees everything except commission figures — touch every query in the system and every test you write against it.

3. 3

   Data migration. Four thousand contacts from a spreadsheet is a scripted afternoon. Twelve years of records spread across three systems, where the same client exists under four different spellings, is its own budget line. Assume your data is worse than you think it is.

4. 4

   Reporting. Listing records back to a user is cheap. Trustworthy aggregate reporting across time periods and multiple entities is not — especially once someone asks why last quarter's number changed after a record was edited two weeks later.

5. 5

   Compliance. GDPR retention and erasure, audit trails, KYC and AML checks — in financial services, these shape the data model from day one. They are not something you bolt on once the system is built.

When you should buy instead of build

Given all of that, the honest next question isn't “how much,” it's “should we build this at all.” We turn down CRM work regularly, and we'd rather tell you that up front than take on a project we don't believe in.

Buy off-the-shelf if your sales process looks like most companies'. Salesforce and HubSpot encode decades of standard sales practice — if a conventional pipeline fits how you sell, you will not out-engineer them for the price. Buy if you need something running next week; nothing bespoke ships that fast, properly. And buy if you have no one internally who will own the system — without a technical owner, a bespoke platform turns into an expensive liability within a year.

Build when the standard model actively fights how you work. The clearest signal we see is a sales team maintaining shadow spreadsheets alongside a CRM they're already paying for — that's a business telling you, in practice, that the tool doesn't fit. Introducer and partner networks, multi-entity advisory structures, revenue-share arrangements and regulated onboarding all break generic pipelines in ways that adding a few custom fields never fixes.

Build, too, once the licence economics turn against you. Ten users on Sales Cloud costs roughly £8,600 a year in licences alone, plus £15,000–£50,000 to implement and £10,000–£30,000 a year in ongoing admin — call it £150,000–£350,000 over five years. A bespoke equivalent runs £40,000–£80,000 to build plus £5,000–£15,000 a year to run, or £65,000–£155,000 over the same period. The crossover is real, but it arrives later than vendors selling against it will tell you, and it only holds if you actually have internal ownership of the system.

None of this is an argument that bespoke is always better — most of the time, it isn't. It's an argument for running the comparison honestly, against your actual process, rather than accepting whichever answer the person in front of you is selling.

How to get a quote you can trust

Whether you end up buying off-the-shelf or building bespoke, the same four questions separate a quote you can trust from one that will surprise you halfway through:

• —

  Insist on a fixed scope and a fixed number before a line of code is written. If a supplier won't commit to both, the uncertainty becomes your risk the moment it turns into a change request in month three.

• —

  Ask what you'll actually see in week two. The right answer is working software you can click through, not a status report or a slide deck.

• —

  Ask who owns the code, and where it runs. The answer should be you — your repository, your infrastructure — not a black box on someone else's account that you lose access to if the relationship ends.

• —

  Ask what support costs after launch, in writing. A build price with no maintenance number attached is only half a quote.

If you've read this far and you're still not sure which side of that line you're on, that's normal — it usually takes a real scoping conversation to know for certain. BlockLabs scopes, prices and builds bespoke CRM systems for firms whose processes don't fit the standard model — see how we approach CRM development.

Frequently asked questions