Why Modern Businesses Need a Custom CRM

Nobody decides to outgrow their CRM. It happens gradually, and by the time it is obvious, the workarounds have become the process.

This article is about the symptoms rather than the sales pitch. If you recognise four or five of them, the question is worth asking. If you recognise one, it almost certainly is not — and we would rather you spent the money on something else.

The seven signs you have outgrown your CRM

1. There is a spreadsheet nobody will admit to

Somewhere in your business is a spreadsheet that holds something the CRM cannot. Someone maintains it. It has become load-bearing — if that person leaves, a process breaks — and it exists precisely because the software would not bend to the way the work actually happens.

One spreadsheet is normal. Three is a signal. The tell is not the spreadsheet itself but that nobody has raised it, because everyone has quietly accepted the system does not fit.

2. You are paying for tiers you do not use

Per-seat pricing works well at small scale and badly at growth. The upgrade path is rarely proportional: you need one feature, and it sits two tiers up, so you pay for forty things to get it.

Add up your annual licence cost, then divide it by the number of features your team touches weekly. Most businesses have never done this calculation and are mildly alarmed by the answer.

3. Reporting happens in a spreadsheet, not the CRM

If someone exports to CSV every month to produce the numbers the board actually looks at, your CRM is a data store rather than a management tool. That export is also where errors enter, because it is manual and nobody checks it twice.

4. Onboarding a new starter takes a week of caveats

Listen to how a new employee is trained. If a significant part is "ignore that field", "we use this one for something else", or "you have to do it in this order or it breaks", the software is being used against its own design. Every one of those caveats is a small permanent tax on everybody who joins.

5. Two systems disagree and nobody knows which is right

When your CRM and your finance system hold different numbers for the same customer, the real cost is not the discrepancy. It is that people stop trusting both, and start keeping their own records — which is how you end up back at point one.

6. A consultant has already tried to fix it

If you have paid someone to configure, customise or extend an off-the-shelf CRM and it still does not fit, that is meaningful evidence. You have tested the cheaper hypothesis and it failed. Doing it again with a different consultant usually produces the same result at the same price.

7. Compliance questions cannot be answered quickly

A subject access request arrives. How long does it take to find everything you hold on that person and export it? If the honest answer is days and involves several people, that is a process risk sitting quietly in the background until the day it is not quiet.

What custom actually changes

The software fits the process instead of the other way round. Adding your fiftieth user costs nothing. Reporting comes from the system rather than from an export. Data lives where you choose, which makes compliance questions answerable.

What it does not change: someone still has to own the system. Custom software with no internal owner decays faster than a licensed product, because there is no vendor quietly maintaining it in the background. This is the single most common reason a custom build disappoints, and it has nothing to do with the code.

When the answer is no

We turn this work down regularly, and these are the reasons why.

• Under ten users with a standard sales process. Pipedrive and HubSpot are good products. At that size the licence will cost less than the build for years.
• You need it working next month. Discovery and process mapping alone take 2 to 3 weeks, and a build compressed below the time needed to understand the process produces software nobody uses.
• The process is still changing weekly. Encoding an unstable process in software means paying to rebuild the same feature repeatedly. Let it settle first.
• Nobody internally will own it. Covered above, and worth repeating because it is the one people dismiss.

How to test the decision before spending anything

Three things, none of which require a supplier.

Write the process down. Not the version in the handbook — the version that actually happens, including the exceptions people handle by habit. If two colleagues write it independently and the versions differ, you have found the real problem, and it may not be software.

Cost the current arrangement honestly. Licences, plus the consultant hours, plus a fair estimate of the time spent moving data between systems. That last number is invisible on every invoice and is usually the largest.

Model three years, not one. Custom loses on year one and wins later, or it does not win at all. If per-seat costs are flat and headcount is flat, the case is weak — and you should not let anyone tell you otherwise.

Realistic timelines

For most UK SMEs a bespoke CRM runs 8 to 16 weeks from signed brief to launch: 2 to 3 weeks of discovery and process mapping, 6 to 10 weeks of build in sprints, then 2 to 3 weeks of user testing and training. The variable is rarely the engineering. It is how quickly your team can agree on what the process is.

If you want a second opinion on whether any of this applies to you, we do a free scoping call and you keep the process map whether or not you go ahead. More detail on how we approach these builds is on our CRM and HRM development page, and if the answer turns out to be a web application rather than a CRM, that is covered under custom web app development.

Either way, tell us what is actually going wrong and we will give you an honest read, including when the honest read is that you do not need us.