Bespoke CRM or off-the-shelf: a UK SME decision guide
Off-the-shelf CRM wins on day one: cheap to start, instant, proven. Bespoke wins when your process is the product: it costs once, fits exactly, and never charges per user. The honest decision method is to price both over five years, count the workflows you would have to abandon to fit the package, and be suspicious of anyone whose answer never varies. Ours does: most small teams should buy off the shelf, and we say so.
Somewhere around the fifteenth employee, every business has the CRM conversation. It usually starts with a spreadsheet that has become load-bearing and ends with somebody asking the question this note answers: do we subscribe to something, or build our own?
The honest answer most consultancies will not give you: it depends, the dependency is measurable, and most small teams should buy off the shelf. Here is the measurement.
The two prices, stated honestly
Off-the-shelf pricing is a meter. Mainstream CRM tools price per user per month, typically in the tens of pounds at the tiers a growing SME actually needs. The arithmetic is the point, not any particular vendor: fifteen people on an illustrative £30 per user per month is £5,400 a year, £27,000 over five years, rising with every hire and every “that feature is on the next tier up” conversation. You stop paying, it stops working.
Bespoke pricing is a lump. A system built around your process costs real money once, plus modest hosting and aftercare. There is no per-user line: the sixteenth employee costs nothing. Five years later the system is an asset you own, not a subscription you survived. The risk sits at the front instead: scope it badly and the lump grows.
Neither price is dishonest. They are different shapes, and the five-year view, not the first invoice, is where they can be compared like for like.
The real decision: whose process is it?
Price matters less than fit, and fit comes down to one question: is the process the CRM must support yours, or everyone’s?
A standard sales pipeline, leads in, deals through stages, invoices out, is everyone’s process. The packages have refined it across millions of users, and pretending your version is special is expensive vanity. Buy the tool, take the discipline it imposes as a free consultancy, and spend your money elsewhere.
The opposite case is the business whose workflow is the competitive advantage: the hire firm whose quoting logic nobody else has, the manufacturer whose job costing took twenty years to get right, the distributor whose customers stay because the service model is peculiar and brilliant. Forcing that through a package means abandoning the peculiarity, and the peculiarity was the point. That is when bespoke stops being a luxury and becomes the cheaper option that merely looks dearer.
Scoring your own case
| Question | Points towards off-the-shelf | Points towards bespoke |
|---|---|---|
| Could a competitor run their sales on your process unchanged? | Yes | No, ours is genuinely different |
| How many spreadsheet workarounds orbit the current tool? | None to two | The workarounds are the job |
| Headcount using it in five years | A handful | Twenty plus, where the meter compounds |
| Integrations needed (stock, accounts, website, couriers) | The package lists them | The connections are the value |
| Who must own the data and the logic? | Renting is fine | Ownership matters: compliance, sale of the business, sheer independence |
Three or more in the right-hand column and the conversation is worth having. Fewer, and the honest advice is a subscription and a tidy import; we will say so, without charge, because a mis-sold bespoke system is a reputation we cannot afford.
The middle path nobody advertises
Plenty of businesses need eighty per cent package and twenty per cent peculiar. The pragmatic answer is often both: a mainstream tool for the standard pipeline, plus a small bespoke layer for the peculiar part, integrated rather than fought. It is unglamorous, it is cheaper than either extreme done badly, and it is on the table in every scoping conversation.
The same scoping discipline applies as everywhere else on this site: a written specification and a fixed price before any code, working software shown as it grows, your team piloting it alongside the old way until it has earned trust. The method is described under Bespoke Systems, and if the system you are replacing is itself an old one, the Legacy Rescue pages cover that exit too.
Start with the spreadsheet count. If you have stopped being embarrassed by it, it is time.