Buy or build: when an off-the-shelf CRM is the right answer

We sell both. We have a ready-made CRM, and we build custom software. That should make this article suspect, so let us be straight about it: most businesses that ask us for a custom CRM should not buy one, and we tell them so.

Here is how to work out which side of the line you are on, before you spend anything.

Start with what off-the-shelf actually gets wrong

Not what it lacks. What it gets wrong.

Most people who say “it does not fit our business” mean the software asks them to work in a slightly different order than they do today. That is not a reason to build. Software you buy has been shaped by thousands of businesses, and quite often the different order is better than the one that grew by accident in your office.

The test that matters: can you name the two screens it gets wrong, and say what it costs you every week?

“Our technicians have to write the meter reading on paper and someone retypes it in the evening, which takes an hour a day and we still get numbers wrong” is a reason to build something. “It feels clunky” is not.

If you can put a number on it — hours, mistakes, jobs lost — custom is worth pricing. If you cannot, you will spend a few lakh to end up with something that feels different rather than something that works better.

Three questions that settle it

Is your process genuinely unusual, or just yours?

Both are real, but only one justifies the cost. A CCTV installer quoting for a site, scheduling a fitter, and raising an AMC renewal a year later is doing something thousands of other firms do. A business that rents equipment by the hour, tracks which unit went where, and bills on return is doing something most CRMs have never heard of.

How many people will actually use it?

Under five, off-the-shelf almost always wins. The subscription is smaller than the maintenance bill on something custom, and you inherit every improvement the vendor makes without paying for it.

Above fifteen or twenty, the arithmetic turns. Per-user pricing starts to look like a monthly salary, and the process you are bending to fit is being bent by twenty people at once.

Who will own it in three years?

This is the question nobody asks and everybody regrets. Custom software is a thing you own, and things you own need looking after. Servers need patching, libraries go out of date, the phone number that was fine in 2026 needs to be an email in 2028. If there is no plan and no budget for that, you are not buying software, you are buying a future problem.

The option most people miss

It is not a choice between two things. There is a third, and it is usually the right answer for a business of twenty or thirty people:

Buy the ordinary part. Build the one piece that is actually yours.

Use a normal CRM for leads, follow-ups and quotations, because there is nothing special about how your business does those. Then build the single screen or the single integration that the market does not serve — the rental tracker, the meter-reading app for the field team, the bridge that pushes finished jobs into Tally the way your accountant wants them.

You get the thing you needed for a fraction of a full build, and the boring nine-tenths stays somebody else’s problem to maintain.

A short honest summary

• Buy if you are under five users, if your complaint is about feel rather than cost, or if you cannot name what you would do differently.
• Build if you can put a weekly number on what the gap costs you, if the process really is unusual, and if you have a budget for keeping it alive.
• Both if the answer is “most of it is normal, but this one thing is killing us” — which, in our experience, it usually is.