Outgrown your CRM: rebuild, replace or extend?

Declared bias: we are an AI consultancy and we build custom systems, including CRMs. So every price on this page is the vendor’s own published UK list price, read on 21 September 2026 and linked at the bottom, and the seat counts are labelled as our assumption.

At a glance

• Salesforce’s published UK Sales Cloud list runs £20 to £440 per user per month. At Core and 25 users that is £140,400 over three years.
• The deciding sign is not cost. It is the spreadsheet kept beside the CRM.
• Most “we have outgrown it” conversations turn out to be about reporting, which is the cheapest thing on this page to fix.
• The migration is the project. History, attachments and five years of custom fields are what does not transfer.
• Settle it with one week of testing: one representative deal, one awkward exception, and no spend.

Which six signs say you have outgrown your CRM?

Six, in the order they usually appear.

1. A spreadsheet appears beside it. Somebody keeps a separate sheet because the CRM cannot hold something the business needs.
2. Reporting requires an export. The data is in there and the view a director wants takes half a day to produce.
3. The same fact is typed twice. Into the CRM, and again into the accounting package, the scheduler or a document.
4. Exceptions leave the system. Routine deals run inside it and the awkward, valuable ones run by email.
5. You are paying full seats for people who only look. Light-touch users on full licences.
6. New process changes are quoted as consultancy. Every small change needs a partner and a statement of work.

The one that decides it is the first. That spreadsheet is the exact shape of the gap: somebody has already specified the missing system, for free, in the plainest possible format. Read it before you talk to any supplier. If the sheet has forty rows and four columns, you have a small problem. If it has become the place the business runs from, you have a large one.

When is keeping Salesforce or HubSpot the right answer?

More often than a supplier of custom software will say, so here it is plainly.

Keep the product when the pipeline is standard and the only friction is reporting. Keep it when your team is growing fast and the process will look different in a year. Keep it when the integrations you rely on exist as supported connectors and would have to be written by hand otherwise. Keep it when nobody internally can own a system, because a build with no owner decays faster than a licence does.

And keep it when your real objection is the invoice. Building software to avoid a subscription is nearly always the most expensive way to avoid a subscription. The cheaper route is a seat audit and a conversation with your account manager before renewal.

Products also carry things that are easy to undervalue: security patching somebody else funds, a roadmap, a support line, and a large pool of people who already know the tool. A build gives you control and takes those back.

What does outgrown usually mean in a mid-sized business?

In a business of £1m to £50m turnover it almost never means the CRM cannot hold the contacts. It means one of three things, and they have very different prices.

Reporting. The commonest by a distance. The information exists, the view does not. This is often solvable inside the product, or with a small reporting layer that reads from it, for a fraction of a rebuild.

Process shape. Your work does not move through stages the way the product assumes. A contracts manager at a construction firm does not have a linear pipeline; they have a job that exists in five states at once. That is a real mismatch and it is where a build starts to make sense.

The middle of the business. The CRM holds the sale and the accounting package holds the invoice, and everything in between, which is delivery, lives in email and one person’s head. This is the most valuable gap and the one least likely to be fixed by swapping one product for another.

Diagnose which of the three you have before deciding anything. Route one is cheap, route two is a bounded build, route three is the one worth real money.

What is the real three-year bill, at published list prices?

Most comparison pages assert a five-year cost with invented seat counts. Here it is with the vendor’s own published numbers, read today, and our assumptions stated.

Salesforce Sales Cloud edition	Published UK list, per user per month	25 users, 36 months
Starter Suite	£20	£18,000
Pro Suite	£80	£72,000
Core	£156	£140,400
Advanced	£316	£284,400
Max	£440	£396,000

All billed annually, per Salesforce’s own UK pricing page. The seat count of 25 is ours, and the table scales linearly, so halve it for 12 or double it for 50. None of this includes implementation, integration work, or the partner day rates that usually accompany the upper three rows.

Against that, published UK bands for building: Unity Bridge puts a focused custom CRM at £20,000 to £50,000 over two to four months, a multi-module system at £50,000 to £100,000 over four to eight months, and an enterprise build at £100,000 to £250,000 and above. Add a run rate: Square Root publishes hosting at £200 to £2,000 a month and maintenance at 15 to 25 per cent of build cost a year.

Read the two together fairly. At Starter or Pro editions with a small team, a build does not compete and should not be attempted. At Core and above with twenty-five or more seats, the three-year numbers converge, and at that point the decision stops being arithmetic and becomes the eight-factor question in the build-versus-buy guide linked below.

One thing the table cannot show: you will probably not turn all of it off. Most builds replace part of the stack, and the residual licence keeps running.

Extend, replace or rebuild: three routes, three risks

Extend. Keep the CRM, build the missing piece beside it, connect the two. Lowest cost, fastest, and reversible. The risk is that you accumulate several extensions over three years and end up maintaining a system you never decided to build.

Replace. Move to a different product that fits better. Moderate cost, and the risk is that you pay the entire migration price for a fit that is better but not different in kind. Ask what specifically will be true in the new product that is not true now, in one sentence, before starting.

Rebuild. Commission a system shaped around your process. Highest cost and highest ceiling. The risk is that you freeze your current way of working into software, including the parts that were accidents. Rebuild only after the process has been read properly, never as a way of avoiding that work.

Side by side

Extend, replace or rebuild: three routes, three risks

Whichever you choose, the migration is the project. Ask the one question on each route first.

	ExtendKeep it, build the missing piece	ReplaceA better-fitting product	RebuildShaped around your process
What it looks like	example-deal-approvals.xlsxSheet DealDiscount approved by FennerSam, 22 Oct Flagged: CalderNobody yetFlagged Kept beside the CRM: it names the missing piece	Migration checklist2 of 4 Done: Export contacts and deals Done: Map the old fields to the new product To do: Re-create the approval workaround To do: Retrain the sales team	Document Process note: how a deal really moves Rep drafts the proposal in Word. Finance director approves any discount over 10 per cent. Order goes to operations by email. Read this before anything is built.
Cost	In its favour: Lowest, and fastest	Mixed: Moderate, plus the migration	Against it: Highest
Ceiling	Mixed: Bounded by the CRM	Mixed: Better, not different in kind	In its favour: Highest
The risk	Extensions pile into a system nobody chose	The whole migration for a modest gain	Freezing today's accidents into software
Ask first	Which piece is missing?	What will be true that is not now?	Has the process been read properly?
The verdict	Wins most often at £1m to £50m	Only with a one-sentence reason	Only after the process is read

in its favour mixed against it

In practice, extend wins most often in this turnover band and rebuild wins when route three of the previous section is the real problem.

Why is the migration the project?

Because the software is the predictable half and the data is not. Building a system to a defined process is estimable work. Moving five years of accumulated reality into it is not, until somebody tries.

What tends not to survive: attachments and the context they sat in, email threads logged against records, audit history, custom fields added by people who have since left, and anything held in the vendor’s own format rather than as data. What tends to survive: contacts, companies, and the structured fields somebody designed deliberately.

Three practical steps. Ask your current vendor, in writing, exactly what a full export contains. Take that export now, before you need it, and look at it. And decide explicitly what you are not migrating, because “everything” is not a migration plan, it is a way of discovering the cost in month four.

Run this test before you decide

One week, no spend, and it settles most of the argument.

Take one representative deal from start to delivery, and one awkward exception from the last month. Follow both through every system they touch. Count the number of times the same fact is typed. Note every point where somebody waits for somebody else. Then write, in one paragraph, what would have to exist for both of those to run without a workaround.

If you can write that paragraph, you have a specification and you are ready to get quotes. If you cannot, no supplier can give you a meaningful price, and the next step is reading the process rather than buying anything.

What we run ourselves, and what it produces

We run a custom CRM of our own rather than a licensed one, so the trade-offs on this page are ones we live with rather than ones we have read about. We are not going to present that as evidence, because you cannot open it and check it.

What you can open is the wider system around it. Every system we run is drawn on Inside AGMM, department by department, with the receipts for what publishes and what runs. None of it is a claim about your CRM. It shows the standard we hold a delivered system to. What we cannot show you yet is listed on our evidence page.

The same standard applies to a CRM extension. Every figure on a sales report should trace back to a record somebody can open. Every handover from sales to delivery should leave a note the next person can read. If a report cannot show its working, the system has moved the argument, not ended it.

What does it cost to find out?

The 30-minute fit call is free and nothing is purchased on it. If the question deserves a proper read, the AI Constraint Audit is a fixed £2,000 over fourteen days, in three sixty-minute working sessions with the founders who would scope any build. It finds constraints, weak points and opportunities to save or earn serious money, and it ends in four documents you own outright. A more extensive audit always follows, and it is included in any build proposal.

The fee is not credited against a build. That is precisely what lets the recommendation be “keep Salesforce and fix the reporting”, which is a real outcome and not a rhetorical one. What we build, and the conditions under which we will take it on, are on custom CRM development, and the wider service sits under custom builds.

When do we tell people not to rebuild?

When the problem is reporting. Fix the reporting. It is a fraction of the cost and it resolves the complaint in most cases.

When the seat count is small. Below roughly fifteen users on a mid-tier edition, the arithmetic does not support a build and no amount of enthusiasm changes it.

When the sales process is about to change, because of a new market, a new product line or an acquisition. Wait until the shape settles.

When nobody can be named as the owner. A CRM without an owner reverts to spreadsheets whether it is licensed or built.

And when the plain answer is that two departments disagree about who owns the customer. That is a management decision, and buying software to avoid making it is expensive.

What this does not apply to

This is written for UK businesses of roughly £1m to £50m turnover with between about ten and a hundred people in the system: an operations director at a 40-person distributor, a contracts manager at a construction firm, a finance lead at a clinic group.

It does not apply to sole traders or very small teams, for whom a product is almost always right. It does not cover enterprise CRM estates with existing integration platforms and formal architecture governance. It does not cover regulated record-keeping in financial services or healthcare, which adds requirements beyond this page. And the three-year table is an illustration built on a stated seat assumption, not a quote.

When we are the wrong choice

If you want the whole estate replaced in one project, we will propose the smallest useful first version instead, and some buyers find that a disappointing answer.

If the decision has already been made and you want a supplier to execute it, an audit that might disagree is not what you are buying.

If your current system fits and the complaint is the renewal price, negotiate. We will say so on the call and it will cost you nothing.

If there is no owner, no supplier can supply one.

Sources

Read on 21 September 2026.

• Salesforce UK, Sales Cloud pricing. Starter Suite £20, Pro Suite £80, Core £156, Advanced £316, Max £440 per user per month, billed annually.
• Unity Bridge Solutions, custom CRM development UK. Focused CRM £20,000 to £50,000 over two to four months; multi-module £50,000 to £100,000 over four to eight months; enterprise £100,000 to £250,000 and above.
• Square Root, cost to develop software in the UK. Cloud infrastructure £200 to £2,000 a month; maintenance and support 15 to 25 per cent annually.
• Monday.com pricing. Basic £8 per seat per month billed annually, quoted here as an example of low-cost seat pricing for light users.

Related reading

• Custom software or off-the-shelf: how to decide
• How much does custom software cost in the UK?
• What business process automation costs in the UK