An established repair shop, decades of loyal customers, and a filing system that still ends in a handwritten slip. GarageHub is purpose-built Windows software that replaces the paper — without losing a single thing the shop already knows.
This is not a startup with a blank page. It is a working shop with thirty-five years of customers — people the owner knows by name, cars he has serviced twice a decade since the nineties — and all of that history lives in a system built for the fuel pumps next door, not for the garage.
So the front counter does it twice: look the customer up in the old software, then write the work order out by hand. Every repair a customer declined — the brake job they'd think about, the leak they'd get to next month — goes onto that slip and then, in practice, nowhere.
That framed everything: an import that can't lose a record, a search that answers before the customer finishes talking, and repair documentation that would still make sense to a lawyer, an accountant or a new hire in a decade's time.
Plate and state, VIN, name, phone. Candidates explain why they matched, and a person always confirms before anything is filled in.
Arrival, vehicle, odometer, and the customer's concern in their own words — kept separate from what the technician later finds.
Versioned estimates that freeze when issued, and a record of exactly what the customer agreed to — including the parts they turned down.
A statement of charges that cannot claim a figure nobody authorized, printed as a document reproducible years later.
Deferred repairs become tracked follow-ups on a schedule, with coded mail so the shop learns which reminders actually brought the car back.
Encrypted backups and a recovery path proven by drill: the machine is deliberately destroyed, and the shop comes back from a file and a key.
Delivered in slices, each one ending with something the owner could run and complain about. That loop mattered more than any plan: the most valuable feedback in the whole project came from thirty seconds of real use at a counter, not from a specification.
The software is built and runs end to end — a customer walks in, and a printed statement comes out the other side. What remains is the careful part: professional review of the customer-facing paperwork, an independent security review, and a pilot on copied data before a single real record moves. That order is deliberate.
Built for one shop, with the ambition that it fits others like it. Details of the system itself stay private while it is in development.
Talk about a build like this