We Build the Desk Your Shop Actually Runs On
Not a seat you rent. A system built around the way your business takes the call, quotes the work, gets the yes and gets paid. We run our own auto shop on one. We have built five more for other people.
Every screen on this site is a real desk we built, photographed with invented customers.
A Safe Does Not Have a License Plate
Shop software is written for one trade and sold to twelve. Underneath, it believes a job hangs off a car. So it asks for a plate or a VIN before it will let the work close.
A locksmith rekeys a cafe door. There is no plate. A safe has no VIN. On off the shelf software that is not an inconvenience, it is a shop that cannot close its own jobs.
In the system we build, one line decides this. It is set per trade. For a locksmith the answer is no, and a lock gets identified by its keyway, its brand or the line the technician wrote instead.
hasPlate: false, trimLabel: "Keyway", // KW1, SC1 - it decides what blanks the van carries colourLabel: "Finish", thing: "lock", // not "vehicle", not "property", not "site"
src/domain/trade.ts, the locksmith row
That is what a custom CRM is. Not a nicer color scheme on the same assumptions. The assumptions themselves, written for your trade.
Three Ways Bought Software Stops Working
It Does Not Know Your Words
Your screens say vehicle when you fix doors. Your technician looks for a field that is not there and writes it in the notes, so nobody can ever search it again. The words on a screen are not decoration. They decide what gets recorded and what gets lost.
You Pay Forever and Own Nothing
Per seat, per month, priced on how many people you hired. Texting is an upgrade. The data is theirs and the export is a spreadsheet. Five years in you have paid for a system twice over and you cannot take it with you.
The One Thing That Makes You Money Is the Thing It Will Not Do
Every shop has one. The pre purchase inspection. The two level master key. The fleet account billed monthly. It is the reason customers pick you, and it is the thing you are doing in a notebook because the software has no room for it.
One Line, From the Phone Ringing to the Money In
Every business that runs on jobs has the same railway underneath it. The trades differ. The line does not.
The call
A call comes in and nobody picks up. The desk texts back before they have finished dialing your competitor.
The lead
Name, number, address, what is wrong. Landed on a board, attributed to the site or the ad that earned it.
The quote
Priced off your own rates. Sent as one page the customer reads on a phone.
The yes
One signature that agrees the price and gives permission to do the work. Asking twice is how a job ends up half approved.
The day
On a board with a real date. An approval is not a booking, because the bay still has to be free.
The work
Photographed as it happens. The inspection, the part number, the before and after.
The money
Invoiced from the lines already on the job. Paid by card, and the payment is what closes it.
Any one of those steps can be the whole reason you are losing money, and it is never the same step twice.
What Happens Between a Missed Call and a Text Back
This runs in every stack above. Only the boxes change. It is worth reading once because the money is in the timing, not the technology.
A call comes in and nobody picks up
The tracking number records it. The number itself is the attribution, so you know whether the caller came from your site, a map listing or an ad.
A poller notices, or a webhook fires
Either the provider tells us, or we ask every minute. Asking is less elegant and it is the one that still works when their webhook is down.
The system checks who this is
Matched on a phone number stored one way, in one place. Doing that five different ways is how one person becomes four customers.
It decides whether to answer at all
Is it inside your hours. Have we already texted them today. Is a real person already replying in that thread. Has this customer asked us to stop.
The text goes out
Under your number, in your words, saying something a human would say. Forty four seconds is the target, because the caller is still deciding.
The reply lands on a board
Not in somebody's personal phone. In the shop's book, where the next person on shift can see it.
Every one of those six steps is a place we have seen a shop lose a job. The fourth is the one that gets built last and matters most, because software that texts a customer at eleven at night costs you the customer it was trying to catch.
Read From the Database, on 15 September 2026
Every number on this site carries the day it was read. A number with no date is one nobody can check.
jobs run through the desk we built for our own shop
technicians working on it across nine states
calls and texts it handled in the first half of September
trades it has its own vocabulary for, from cars to safes
Four Stacks We Build On
There is no best stack. There is one that fits the size of the business, what it can spend a month, and how strange its work is.
The Full Build
What our own shop runs on. A business with real volume, work that no product on the market models correctly, and a reason to own the thing outright.
$20 to $80 a month to run, plus texting and card fees on what you use.
Static Front, Managed Back
The one most small shops should start on. A business that needs a real database and real logins, and does not yet need a server of its own.
$0 to $25 a month until you are past the free tiers.
Assembled From Tools
Live this week, and it has a ceiling. A business that needs something working on Friday, or one testing whether a process is even right before paying to build it.
$50 to $400 a month, and it climbs with every person you hire.
The Framework Build
When the public site and the app are one thing. A business whose marketing site, customer portal and internal tool should be a single product, or one that expects to hire developers.
$20 to $150 a month at small scale, more once traffic is real.
Asked Before Anybody Signs Anything
What does a custom CRM cost?
Can you just fix the software we already have?
How long before we can stop using our old system?
What happens to the customers and history we already have?
Do we have to change how we work?
Tell Us What Your Shop Does That the Software Will Not
That one thing is usually the whole conversation. Write it in a sentence and we will tell you honestly whether it needs a custom build or a better setup of something you already pay for.