Build or Buy: When a Custom CRM Is Worth It
Off-the-shelf wins more often than agencies admit. Here are the four situations where it genuinely does not.
· 2 min read · Business
In short: An agency that builds software has an obvious incentive to tell you to build software. So: for most businesses, most of the time, buying is the right answer. Here is how to tell whether you are the exception.
The comparison people get wrong
The usual comparison is a subscription against a build cost. Twenty users at a monthly fee versus a one-off project — and over three years the build looks competitive.
That comparison is missing the second half. Custom software has a running cost too: hosting, security updates, fixing what breaks when a dependency changes, and someone available when it stops working at month-end. Ignore it and you will be unpleasantly surprised in year two.
Compare like with like: subscription plus configuration time, against build plus maintenance plus the risk of the person who built it being unavailable.
Four cases where custom genuinely wins
- Your process is the business. If how you quote, schedule or price is a real competitive advantage, bending it to fit a generic tool throws away the thing you are good at.
- The off-the-shelf options need so much customisation they stop being off the shelf. Once you are paying for a platform plus a consultant to reshape it, you have the cost of custom with none of the control.
- Per-user pricing has become absurd. Some businesses need fifty occasional users. Subscription models price for fifty daily users. The maths can flip hard.
- It must join systems that do not want to be joined. When the real need is to sit between a supplier feed, an accounting package and a delivery partner, you are building integration software, and no CRM is that.
The trap in the middle
The worst outcome is the middle path: buy a platform, then customise it heavily. You inherit the platform's constraints and its upgrade cycle, plus a layer of custom work that breaks every time the vendor ships a change — and which only one consultant understands.
If a tool needs more than configuration, that is a signal to look harder at either a different tool or a real build, not to start modifying.
A cheaper way to find out
Before committing to either, map the handful of things your team does every day. Not everything — the five actions that happen most. Then test a bought tool against those five, with real data, for two weeks.
Most of the time it fits and you have saved a large sum. When it does not fit, you will know exactly which five things to build, which is a far better brief than "we need a CRM".
We build custom software and we tell clients to buy instead when that is the right answer. If you want a straight opinion on your situation, book a call.