A CRM shaped like your business, not a sales pipeline
Generic CRMs are built for a sales team moving deals through stages. If your business runs on jobs, bookings, files or service history, you're forcing your process into someone else's shape.
Most CRM software was designed around one process: a salesperson moving an opportunity through a pipeline to a close. If that is your business, use one of the established products - they are mature, cheap and good at it.
A great many businesses don't work that way. A tuning shop tracks vehicles, stages, files and repeat customers. A field service company tracks jobs, engineers, locations and parts. A studio tracks projects, milestones and deliverables. In all of those, a pipeline CRM becomes something you maintain alongside the real process rather than something that runs it - and a system nobody updates is worse than no system, because now your data is wrong as well as incomplete.
RampDesk exists because of exactly this problem. It is our own garage management software, and it is built around vehicles, stages and bookings rather than deals.
Signs a generic CRM is not working
The symptoms are consistent across industries, and they all come back to the same root cause: the system doesn't model the thing your business is actually about.
A spreadsheet runs alongside it
The CRM holds contacts, but the real work is tracked somewhere else because the CRM cannot represent it.
Nobody updates it
Keeping it current is extra work rather than a side effect of doing the job, so it drifts out of date and stops being trusted.
Custom fields everywhere
Twenty custom fields bolted onto a contact record is a sign the underlying model is wrong for you.
You pay per seat for viewers
People who only need to look something up are costing you a full licence each.
Customers cannot see anything
Every status question comes to your team by phone or email because there is nowhere for a customer to look.
What a custom CRM actually contains
The point is that the central object is the thing your business is about - a vehicle, a job, a property, a case - rather than a deal. Everything else hangs off that.
The right central record
Whatever your business actually revolves around, with the fields and states that genuinely apply to it.
Stages that match reality
Your real workflow, with the rules about what can move where, rather than a generic funnel.
Quoting and pricing
Your pricing logic encoded, so quotes are consistent regardless of who produces them.
Bookings and scheduling
Capacity, availability and assignment built in rather than tracked separately in a calendar.
Documents and files
Attached to the record they belong to, with history, rather than living in an email thread.
Automated communication
Confirmations, reminders and status updates sent without anyone remembering to send them.
Reporting that answers your questions
The specific numbers you actually run the business on, not a dashboard of generic metrics.
Roles and permissions
Who can see and change what, including limited access for people who only need to look.
Client portals: stop being a lookup service
A surprising proportion of most service businesses' inbound contact is customers asking for information you already have: what stage is my job at, when is my appointment, can I have that invoice again, here is the document you asked for.
Every one of those is a person on your team stopping what they are doing to look something up. A portal turns that into self-service, which is faster for the customer and removes an entire category of interruption for you. It also creates a record - a customer who can see the status is a customer who is not forming their own theory about it.
Status without asking
Where the job is, what happens next, when it is expected.
Documents in one place
Quotes, invoices, certificates and reports available whenever they need them, not re-sent on request.
Upload and submission
Customers send you what you need through a route that actually attaches it to the right record.
Booking and rescheduling
Within rules you set, so the diary manages itself instead of generating phone calls.
History
Everything that has happened before, which for repeat customers is most of the value.
Migrating off what you have now
This is the part that stops most CRM replacements, and it is a legitimate fear - the data in your current system is messy, incomplete and load-bearing.
We handle it as its own phase rather than an afterthought. Data comes across in a rehearsed migration that is run and checked more than once before anything goes live, with a period where both systems are readable so nobody is cut off from history. We would rather spend longer on migration than have a team lose trust in a new system in its first fortnight because a record they needed wasn't there.
Deliverables
Every engagement includes these as standard, not as line items to negotiate.
- A data model built around what your business is actually about
- Your real workflow stages and the rules that govern them
- Quoting, booking and document handling where relevant
- A customer-facing portal with role-based access
- A rehearsed data migration from your current system
- Full export of your own data, on demand, in a usable format
Where we have done this
RampDesk
Garages don't run a sales pipeline. They run vehicles through stages. RampDesk is the software we built because nothing off the shelf models that.
Read the case studyNearOps
Service businesses run their bookings, dispatch, payments and payouts through NearOps under their own brand. Matching engineers to jobs by coverage area rather than a radius is the part that turned out to be hard.
Read the case studyWhat would this actually take?
Flip the ones that are true. The more that are, the bigger the thing worth building - and the more of it we have already built for someone else.
Nothing flipped yet
Turn on whichever statements are true for your business. The verdict updates as you go.
This is a rough guide, not a quote. The only way to know properly is to map the process, which is what discovery is for.
Questions people actually ask
Why build a CRM instead of using Salesforce or HubSpot?
If you run a sales pipeline, don't build one - those products are mature and cheap and will beat anything custom. Building makes sense when your business revolves around something other than deals: vehicles, jobs, properties, cases. Forcing that into a pipeline model produces a system nobody updates, and an out-of-date CRM is worse than none because your data is now actively wrong.
How do you migrate data from our current CRM?
As its own phase with its own budget, not as an afterthought in the final week. We extract, clean and map the data, then rehearse the migration and check the results before anything goes live - usually more than once. We also keep the old system readable for a period so nobody is cut off from history while they are still learning the new one.
Can customers have their own login?
Yes, and it is usually where the fastest return comes from. A portal where customers can see job status, download their documents, upload what you've asked for and book within your rules removes an entire category of interruption from your team's day - most of which is people asking for information you already hold.
What does a custom CRM cost to run?
Hosting and database for a system of this kind is typically modest and doesn't scale per seat, which is often the main saving against a per-user licence - especially if you have people who only need to look things up. The honest comparison is total cost over three to five years including the licences you would drop and the manual work you would stop doing.
Do you have an example of a CRM you've built?
RampDesk, which is our own product rather than a client project. It is garage management software built around vehicles, stages, bookings and discount codes rather than a sales pipeline, and it runs live every day. Because we operate it ourselves we deal with the support, the edge cases and the consequences of our own design decisions.
Where to go next
Custom Software
Most businesses outgrow their tools long before they replace them. Custom software is what you build when the spreadsheet, the shared inbox and three subscriptions have quietly become the process.
Websites with Built-in Software
Most business websites are a brochure with a contact form. The ones that earn their keep let the customer do something - book, get a price, look something up, check a status.
Software for Automotive and ECU Tuning Businesses
We know this industry well enough to have built our own products in it. RampDesk is our garage management software, used for tuning and remap work as well as servicing and MOTs. The Tuning File Portal automates file handling. This is not a vertical we picked off a list.
Tell us what is slowing you down
A short conversation is usually enough for us to tell you what it would take to fix it, and what it would cost you to leave it alone.