Custom CRM vs off-the-shelf CRM: how to decide before you spend money

Most businesses should buy a CRM. The ones that should not usually have a core record that is not a deal, people who must not see each other's data, or documents and consent that are part of the work. A real student-recruitment platform shows what that looks like.

14 November 2026/8 min read

The short answer: buy an off-the-shelf CRM when your sales process looks broadly like everyone else's. Consider a custom CRM when the thing you manage is not really a "deal", when people who share the system must not see each other's data, or when the CRM has to do the operational work itself (documents, consent, partner terms) rather than just record that it happened somewhere else.

Most companies should use an existing CRM, and I would rather say so in the first conversation than six months into a build. This article is the test I use, with a live system as the worked example.

What an off-the-shelf CRM does well

A good CRM product gives you contacts, companies, a deal pipeline, email and calendar sync, reporting and a long list of integrations on the first day, with a vendor who keeps it secure and running. You pay per user per month and never think about servers.

If your business sells something, follows up, and closes or loses, that is exactly the shape these products are built around. Configure the stages, import the contacts, train the team. A custom build will not beat that on cost or speed, and it should not try.

Five signs you have outgrown it

The pressure to go custom rarely comes from missing features. It comes from the shape of the work not matching the shape of the product.

1. Your core record is not a deal. A CRM is organised around a contact moving through a pipeline once. If one person, property or case moves through many processes at the same time, each with its own stage, documents and outcome, you end up modelling it with workarounds: duplicate contacts, custom objects, naming conventions that only one person understands.

2. People in the same system must not see each other's data. "Sales can see deals" is easy. "This partner sees only their own clients, this manager sees their team plus files shared with them, and nobody sees another partner's commercial terms" is where configuration gets fragile, because one wrong sharing rule exposes a competitor's data. How I structure role-based access covers why this has to be enforced on the server.

3. Documents and consent are part of the process. If a document is evidence (a passport, a signed agreement, a certificate) with rules about who may use it, reuse it and delete it, a file attached to a contact is not enough.

4. Outside people work inside the system. Agents, partners, students or clients who need their own login, their own view and a short list of things they are allowed to do are a portal, and portals are where off-the-shelf licensing and permission models get expensive.

5. Your stages and rules keep changing, and you need to own them. If the business changes its process every intake or every season, you need the stages to be data you control, not a ticket to a vendor or a consultant.

One of these is normally a configuration problem. Three or more usually means the product is being bent into something it was not designed to be.

A real example: student recruitment at London School of Excellence

London School of Excellence places international and UK-domiciled students onto university courses through a network of independent recruitment agents. The platform that runs it is a custom CRM in everything but name. I took it over in April 2026, so I can describe what it has to do, and what had to change to make it trustworthy; the original decision to build rather than buy was made before my time and is not something I can speak for.

What it has to hold maps almost exactly onto the five signs:

What the business needs	How the platform handles it
One student, many applications	A single student record with a permanent ID sits behind every application that student makes, so details are entered and checked once
Three roles that see different things	Head office sees every application; a regional manager sees their own files plus those shared with them; an agent sees only their own students and applications
Partners whose terms must stay private	Each agent's commission ladder is excluded from every query unless explicitly requested, so it cannot leak through a screen nobody checked
Documents as evidence	A verified passport belongs to the student and is referenced by each application, so it is uploaded once and cannot be deleted while an application still uses it
Consent from people with no account	Students sign the data-protection agreement through a public link; re-issuing it archives the earlier signature with the exact wording that was agreed to
A pipeline the business controls	Application stages are records an administrator manages, so a new stage needs no deployment
Notifications that respect permissions	Every notification is re-checked against the recipient's access, so nobody is alerted about a record they cannot open

It also carries a course catalogue of 140 universities and 2,324 courses (read from the live system in November 2026), agent onboarding as its own ten-stage pipeline, tasks and weekly reporting, and email threaded onto the application it belongs to. The client reports that more than 500 people use it.

Several of those rows were not true when I took the system over. The student's details lived inside each application, so a second application created a second copy of the same person. The list of applications was scoped by an ID the browser sent, so an agent who left it out received every application in the business. Fixing those on a system in daily use, during live intakes, was most of the work, and is written up in the case study.

That is the honest lesson of a custom CRM: you get exactly the rules you need, and you are responsible for every one of them being right.

What custom really costs

The build is the visible cost. These are the ones that decide whether it was worth it:

Ownership. Someone has to be accountable for the system for years: fixes, changes, security, and the next intake that needs a new rule.
Testing. Rules that only exist in your system are only protected by your tests. The London School of Excellence platform is guarded by 1,879 automated tests (repository audit, September 2026), and the access rules are the reason most of them exist.
Change on live data. A system the business runs on has no maintenance window. Changes have to be additive, reversible and migrated with dry runs.
Knowledge. If one person understands the system and they leave, you own a liability. Documentation and a clean structure are part of the build, not extras.

None of this is a reason not to build. It is the price to compare against licences, workarounds and the hours your team spends keeping a product in line with how you actually work.

The middle path most businesses should try first

Before replacing a CRM, try narrowing the problem:

Keep the CRM for what it is good at, usually contacts, email and the sales pipeline.
Build only the part that is genuinely yours, such as a partner portal, a document and consent flow, or a commission calculator.
Connect the two so nobody types the same thing twice.

This often costs less than either extreme. It stops working when the custom part and the CRM need to share the same record and the same permissions. That is the situation the London School of Excellence platform is in: students, applications, documents and agent access all hang off one record.

Questions to answer before you decide

What is the one record your business revolves around, and does it move through one process or several at once?
Who must never see what? Write the actual sentences, with names of roles.
Which documents are evidence, and what are the rules for reusing and deleting them?
Who outside your company needs to log in, and what may they do?
How often do your stages and rules change, and who decides?
Who will own the system in three years?

If the answers are short, buy a product. If they take a page, that page is the beginning of a specification. Custom CRM & workflow systems describes how I approach that work, and the property and investment CRM and case management platform are two more examples of where the line fell.

Common questions

Is a custom CRM more expensive than an off-the-shelf CRM?

At the start, almost always, because you pay to build what a product already has. It can cost less over time only when licence fees, workarounds and manual effort cost more than owning a system, which is worth working out with your own numbers before deciding.