RampDesk: a CRM built around vehicles, not deals
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.
What this is
RampDesk is our own software product. It is commercial garage management software that other businesses in the motor trade pay to use, and it is also the system our own tuning operation runs on every day. That second part is unusual and it matters: we're our own most demanding customer, so a bad decision costs us before it costs anyone else.
It exists because the generic options all model the same thing - a salesperson moving a deal through a funnel - while a tuning shop is tracking a vehicle through a sequence of technical stages, often across repeat visits over years.
Five businesses pay for it today. That is a deliberately early-stage number and we would rather state it than dress it up, but the data behind it is not small: one of those businesses alone holds more than 90,000 contacts and vehicles in the system. Carrying that much history without becoming slow or unusable is a different engineering problem from holding a few hundred records.
We built it, we run it, and we support it. That last part matters more than it sounds: operating your own product means you live with every design decision you made, and you find out quickly which ones were wrong.
- Product design and the underlying data model
- Full application build, front end and back end
- Infrastructure, deployment and monitoring
- Ongoing development, support and operation
The problem with a pipeline
A generic CRM wants to know what stage a deal is at and how likely it is to close. A tuning business wants to know which vehicle is on which ramp, what stage its map is at, what was done to it last time it came in, which file version is current, and whether the customer has an outstanding quote.
You can force that into a pipeline CRM with enough custom fields, and plenty of businesses have tried. What you end up with is a system that technically holds the data but doesn't understand it, so it cannot enforce any rules, cannot report on anything useful, and becomes one more thing to update rather than the thing that runs the shop. In practice a spreadsheet appears alongside it within a month, and that spreadsheet becomes the real system.
What we built instead
The central record in RampDesk is the vehicle, with the customer attached to it rather than the other way round - because in this industry a vehicle can outlast a keeper, and its history is the valuable thing.
Vehicle-first data model
History, specification and previous work follow the vehicle, so a returning car arrives with everything already known about it.
Stages that match the workshop
The real sequence a job moves through, with rules about what can move where and what has to be complete first.
Quoting
Pricing logic built in, so a quote is consistent whoever produces it and doesn't depend on who is on the desk that day.
Bookings
Diary and capacity as part of the same system, rather than a separate calendar that has to be kept in sync manually.
Discount codes
Promotional codes with rules and tracking, so campaigns can be run and measured rather than guessed at.
Customer communication
Confirmations and status updates that go out automatically instead of depending on someone remembering.
Not one tool - a suite
RampDesk is described as a CRM because that is the nearest single word, but it is closer to an operating system for a workshop. Each module is a product in its own right, and shops adopt them at different speeds: most start with the diary or quoting and add the rest as they trust it.
That modularity is deliberate. A business can replace one painful part of its process without a wholesale migration, which is the single biggest reason CRM replacements fail.
Vehicles and history
The central record, carrying specification, previous work and files across repeat visits and changes of owner.
Workshop stages
The real job sequence, with rules about what can move where and what has to be complete first.
Quoting
Pricing logic encoded, so a quote is the same number whoever produces it.
Bookings and diary
Capacity, durations and assignment in the same system as the work itself.
Discount codes
Promotions with rules and tracking, so campaigns can be measured rather than guessed at.
Customer communication
Confirmations, reminders and status updates that go without anyone remembering.
File handling
Originals and modified files stored against the vehicle, with version history.
Reporting
The specific numbers a tuning business runs on, current, without anyone building a spreadsheet.
What running it has taught us
Operating a product is a different discipline from delivering one. You cannot hand over and move on - you get the support messages, the edge cases, the consequences of a schema decision made eight months earlier.
The most useful lesson has been about adoption. Features that made the software more capable but added a step to a daily task were consistently ignored. The ones that got used were the ones that removed a step. That has changed how we scope client work: we now look much harder at what a new feature costs the person using it, not just what it adds.
Why this matters if you're hiring us
Most agencies can show you work they delivered. Fewer can show you something they still run, where they carry the consequences of their own decisions rather than handing them to someone else at launch.
RampDesk is why we're confident talking about migration, support load, edge cases and the unglamorous parts of software that only show up in year two. We're not describing them from a methodology document.
What is in it
- Vehicle-first CRM with full service history
- Workshop stage tracking with transition rules
- Quoting engine with built-in pricing logic
- Booking and capacity management
- Discount codes with rules and reporting
- Automated customer notifications
Where to go next
CRMs & Client Portals
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.
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.
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.
In development · Automated ECU file serviceTuning File Portal
A tuning file service is a queue of skilled manual work where a mistake can damage an engine. It is the hardest kind of process to automate, and the most valuable.
Want something like this?
Tell us what your business runs on and where it hurts. We'll tell you what it would take to build something similar for you.