Off-the-Shelf CRM or Custom? How to Decide Before You Spend

Every business that reaches a certain size has the same argument. Someone says we should just buy something. Someone else says nothing off the shelf fits how we work. Both are right, which is why the argument never resolves on opinion alone.

I build custom systems for a living, so treat my answer with appropriate suspicion. It is still this: buy first, build only when buying has actually failed.

The short answer

If a ready-made tool does 80% of what you need and you can live with the other 20%, buy it. Build when the 20% is the part your business competes on, or when the subscription maths has quietly turned against you.

Question one: is this how you win, or just how you cope?

Every business has processes that are genuinely theirs and processes that are simply admin.

Payroll is admin. Buy it. Nobody ever won a customer because their payroll was bespoke.

But a taxi dispatch platform decides which driver gets which ride, and that logic is the business. That is why white-label dispatch systems like Yelowsoft exist as products in their own right rather than as spreadsheets.

Ask honestly which side your process falls on. Most fall on the admin side, and that is fine.

Question two: what does the workaround actually cost?

Teams underestimate this enormously because the cost is spread thin.

Add it up properly: fifteen minutes a day, per person, re-entering something the tool cannot hold. Across six people that is roughly ninety hours a year. Now compare that to a build.

The answer sometimes still favours the ready-made tool. But at least you have compared real numbers instead of a licence fee against a project quote.

Question three: how many people, and for how long?

Per-seat pricing is cheap at five users and painful at forty. A custom system costs a lot once and very little afterwards.

The crossover is usually somewhere between year two and year four. If you are a school running 100-plus modules across attendance, fees and parent communication (the shape of an ERP like Campus on Click) per-seat subscriptions for every teacher stop making sense fairly quickly.

If you are three people and might be three people in two years, buy.

Question four: does your data have somewhere to go?

Some systems exist because the data has nowhere else to live. An IoT platform pulling live readings off equipment, like Rigseye, is not a CRM problem with a CRM answer. Nothing off the shelf is going to ingest your specific devices.

When the input is unusual, the tool usually has to be too.

The honest middle path

Most of the time the right answer is neither extreme:

• Buy the boring parts. Accounting, email, payroll, storage.
• Build the one thing that is yours. The job board, the dispatch logic, the parent portal.
• Connect them. A custom system that talks to your existing accounting tool is far cheaper than one that replaces it.

That is what NICS Nexus is: one platform for how that team actually runs its days, not a replacement for every tool they own.

Signs you are not ready to build

• You cannot describe your current process without saying "it depends who does it".
• The main driver is that the current tool is ugly.
• Nobody internally will own the project once it launches.

Any of those, and a build will produce an expensive version of the confusion you already have.

What it costs

A custom CRM or internal tool is a logins-and-roles project. The estimator gives a range in a minute, and SaaS, CRM and ERP work sets out what is involved.

If you are in the middle of this argument, send me a WhatsApp with the tool you are currently fighting and the part it will not do. Quite often the answer is a different off-the-shelf tool, or a small integration, and I would rather say that than take on a build you do not need.