Custom CRM vs Subscription CRM: When Per-Seat Pricing Stops Making Sense

Plenty of businesses should be on a subscription CRM. If you have four staff, a simple pipeline and no unusual requirements, paying a monthly fee for something maintained by someone else is the sensible choice, and anyone telling you otherwise is selling.

But there is a point where the maths flips. Here is how to work out whether you have reached it.

What subscription CRMs are genuinely good at

Credit where it's due. A subscription CRM gives you something working this afternoon with no build time. Someone else handles maintenance, security patching and uptime. There is a large ecosystem of connectors. If it breaks there is a support line. And if it turns out to be wrong for you, you can leave without having spent a build budget.

Those are real advantages and they matter most when you're small, moving fast, and still working out what your process even is.

The four signs the maths has flipped

1. You're paying for tiers, not features

The tell is when you upgrade a plan to unlock one thing. You needed custom reporting, or a second pipeline, or an extra integration, and to get it you moved everyone in the business onto a higher tier. You are now paying more per person for a feature one person uses.

This is how these platforms are designed to work — the features most likely to be needed by a growing business are placed just above the plan most growing businesses are on. It's good business for them. It's an increasing cost for you with no matching increase in value.

2. Your process lives outside the CRM

Look at how work actually gets done. If the CRM holds the contact record but the real state of a job lives in a spreadsheet, a shared inbox and someone's head, the CRM isn't running your business. It's an address book you're paying a subscription for.

This happens when the system can't represent how you actually work, so people build the workaround. The workaround becomes the process. And the workaround has no permissions, no audit trail, no backup and no reporting.

3. Every new hire costs money before they've done anything

Per-seat pricing means growth is directly taxed. On a custom build, the eleventh user costs nothing. On a per-seat subscription, they cost the same as the first — forever. If you're planning to grow the team meaningfully, model that cost out five years and see what it does to the comparison.

4. You're paying for data you can't get at

Ask a simple question: can you get a live report of the three numbers you check most, without exporting to a spreadsheet? If reporting sits behind an upgrade, or if the answer involves someone rebuilding a spreadsheet every Monday, you're paying to store data you can't use.

The honest signs you should stay put

To be fair about it, here is when a custom build is the wrong call:

• Your process is still changing every few months. Building a custom system around a process you haven't settled is expensive. Settle it first.
• The standard product genuinely fits. If you're using most of what you pay for and nobody is working around it, leave it alone.
• You have no one to own it. A custom system needs someone in the business who owns it, even lightly. Not a developer — just someone responsible.
• The subscription cost is genuinely small relative to your revenue. If it's a rounding error, your attention is better spent elsewhere.

What actually changes with a custom build

The software matches the business. Your stages are your stages. Your fields use your words. Nobody is translating between how the business works and how the software thinks.

Cost stops scaling with headcount. You pay to build it and to host it. Adding people doesn't add licence cost.

You own the data and the infrastructure. Hosted in your region, in accounts in your business's name. No migration project required if you ever change developers.

Changes are a conversation, not a feature request. New service line, new region, new process — the system gets updated. You're not waiting on a roadmap or being told to upgrade.

The comparison people get wrong

Almost everyone compares a build price to a monthly fee. That's comparing a total to an instalment, and it always makes the subscription look cheaper.

The right comparison is five years of total cost of ownership on both sides. Subscription side: monthly fee times 60, plus per-seat growth, plus the tier upgrade you'll be pushed into, plus paid connectors, plus configuration consulting, plus the annual increases. Custom side: the build, plus hosting, plus a maintenance allowance.

Then add the workaround cost to the subscription side, because it's real. Ten minutes a day of manual re-entry across eight people is more than 300 hours a year.

Run those two numbers honestly. Sometimes the subscription still wins, and when it does you should stay on it.

A middle path worth considering

It isn't always all or nothing. Some businesses keep a subscription CRM for the standard sales pipeline and build a custom system for the operational part it can't handle — the scheduling, compliance or delivery workflow that is specific to their industry.

That's often the cheapest sensible answer: keep the commodity part commodity, build the part that's actually yours.

If you want to work out which side of the line your business sits on, book a discovery call. If a subscription is genuinely the right answer for you, we'll tell you that.