Walk into a well-run shop and count the systems nobody calls software.
- A comeback tracker: a spreadsheet, updated nightly.
- A daily numbers dashboard: a Sheets file fed by nightly exports from the shop management system.
- A follow-up autotexter: an automation duct-taped to the phone system.
- A tech hours board: a whiteboard by the parts counter.
- An advisor-tech pairing tracker: kept by hand for over a year.
- An RO hygiene audit: a nightly hunt for missing parts cost.
Half of it lives on paper. Half of it is bolted onto the shop management system with exports and duct tape. All of it is real: field-tested, load-bearing, running the business every day.
That's the part the software industry keeps missing. The question was never whether shop owners would build. They already build. The question is why the building is stuck at the duct-tape stage.
The gap
The software you buy can't keep up, and it isn't the vendor's fault. The core system runs on one roadmap for every shop; your request goes in a queue. Meanwhile AI put customization one prompt away, and your appetite moved. The core system is good rails. It was never built to let 281,000 shops each run their own playbook on top.
So the playbooks live where they've always lived: in a spreadsheet, on a whiteboard, in the one advisor's head. The best system in your shop can't leave your shop. And the shop across town is rebuilding the same thing from scratch, by hand.
What comes next
The problem becomes the prompt. The workaround becomes the system. The system becomes software. Shop owners are already doing it, 300 hours at a time, on six duct-taped tools.
What's missing isn't the will to build. It's the infrastructure: a place where a shop-built system gets form, gets installed on the stack the next shop already runs, and travels with its builder's name on it.
That's what we're building. The manifesto says why.
Build what the work reveals.