Off-the-shelf CRM vs custom: how to actually decide
Most businesses should use an off-the-shelf CRM. This is written by a company that builds custom ones, so take that as meaning something.
The established CRM products are mature, cheap relative to what they do, and extremely good at the thing they were designed for. If that thing is what you need, building your own is an expensive way to end up with something worse.
But a large number of businesses are not doing that thing, and they discover it slowly and expensively. This is an attempt to help you work out which group you're in before you spend money either way.
What a standard CRM is actually built for
Nearly every mainstream CRM models the same process: a salesperson moves an opportunity through stages toward a close, with a value and a probability attached. Everything else - contacts, activities, reporting, forecasting - hangs off that central idea.
If your business genuinely works that way, these products are excellent and you should use one. The question is whether your business is about deals, or about something else.
The test: what is your central record?
Ask what the fundamental unit of your business is - the thing you would naturally list if someone asked what you're currently working on.
| Your business is about | Standard CRM fit | Why |
|---|---|---|
| Deals and opportunities | Excellent | Exactly what the product models |
| Vehicles | Poor | History belongs to the vehicle, which outlives the customer |
| Jobs at locations | Poor | Scheduling, travel and capacity are central, not incidental |
| Projects with milestones | Mixed | Workable, but project tools usually fit better |
| Cases or matters | Poor | Compliance, documents and history dominate |
| Properties or assets | Poor | The asset persists across many customer relationships |
| Subscriptions or accounts | Good | Close enough to the deal model to work |
If your central record is not a deal, you're going to be bending a pipeline into a shape it wasn't designed for. That is possible, and lots of businesses do it. It just has a cost that accumulates quietly.
The symptoms of a bad fit
You don't usually discover this through analysis. You discover it through these:
- A spreadsheet runs alongside the CRM because the CRM cannot represent the real work.
- The contact record has fifteen or twenty custom fields bolted onto it.
- Nobody updates it reliably, because updating it is extra work rather than a by-product of doing the job.
- You're paying a full seat licence for people who only ever look things up.
- Reporting requires exporting to a spreadsheet, every time.
- New staff are told "we don't really use that bit".
Two or three of those is friction. Five or six means the system is not running your business and has become a thing you maintain alongside it.
The middle option most people skip
It is not a binary. Between "use the standard product" and "build a whole CRM" there is an option that suits a lot of businesses: keep the off-the-shelf system for what it is good at, and build the specific piece it cannot do.
A tuning shop might keep a standard system for marketing contact and build a vehicle-and-stage tracker. A field service business might keep its accounts package and build the scheduling and job capture. Integration between them is a solved problem when both sides have an API.
This is frequently the best value answer and it is under-recommended, largely because it is less profitable for whoever is advising you - including, in fairness, us.
Running the numbers honestly
Compare total cost over three to five years, not build price against monthly fee, and include the things that don't appear on either invoice.
| Off-the-shelf | Custom | |
|---|---|---|
| Up-front | Low - setup and configuration | Significant - discovery, design, build |
| Monthly | Per seat, rises as you grow | Hosting only, largely flat |
| Customisation | Limited, sometimes a paid add-on | Whatever you need |
| Workaround cost | Real but invisible - manual steps, parallel spreadsheets | Minimal if scoped properly |
| Maintenance | Included | Yours to budget for |
| If you stop paying | Access ends | It keeps running |
| Time to value | Days | Weeks to months |
The line that changes the answer most often is workaround cost. It never appears on an invoice, so it gets left out - but two people spending an hour a day on manual steps the CRM forces on them is a substantial annual figure, and it is the whole reason the comparison is not as lopsided as it first looks.
How we ended up building our own
RampDesk exists because of exactly this decision. Tuning businesses kept running a spreadsheet alongside whatever CRM they had, because the CRM understood customers and the business ran on vehicles. No amount of custom fields fixed that, because the underlying model was wrong.
So the record at the centre of RampDesk is the vehicle, with customers attached to it rather than the other way round. That one decision made everything downstream - history, stages, quoting, repeat work - straightforward, where in a pipeline CRM every one of them is a workaround.
That is the whole test, really. If the thing at the centre of the software is not the thing at the centre of your business, you'll feel it every day.