The Doctrine
Generic SaaS sells you a tool. Customizable SaaS sells you a tool with knobs. PSaaS sells you a tool that becomes yours.
This is what the Hub is.
The Inversion
For forty years, software told shops how to run. Tritech designed a work-order screen in 2008 and bike shops have been adapting their Tuesday mornings to it ever since. Lightspeed decided what an "inventory category" was and shops bent their language to match. The customer worked around the software.
The Hub reverses this. The software adapts to the shop. Permanently. Indefinitely. At zero marginal cost.
Everything in this bible — every schema convention, every audit rule, every design choice — exists in service of that one fact.
Why Now
Reprogrammable software has been a fantasy for small businesses for as long as software has existed. Four constraints kept it impossible:
- Owners couldn't program.
- Programmers cost $150/hour.
- Changes broke the system.
- Vendors wouldn't allow it.
AI removes the first three. Single-tenant architecture removes the fourth. What's left as the only constraint is the shop's ability to articulate what it wants — a constraint the shop can actually push on, unlike the vendor roadmap, which it cannot.
The Compound Effect
A shop on Lightspeed for three years has Lightspeed.
A shop on the Hub for three years has a thousand small adaptations specific to how that shop runs. Year one: work orders show the customer's last three visits because James asked for it on a Tuesday. Year two: a youth-race-team module nobody else has, because James started a team. Year three: when a customer walks in with a bike, the screen pulls up the bike's history and the rider's training mileage, because Robbie wanted it.
Each change is small. The accumulated fit is unmatchable.
Three years in, no competitor can sell into that shop. The software at the shop has become the shop's software. Switching costs aren't contract terms. They are the lived shape of the tool.
What This Means Operationally
Every feature request, every walkthrough reaction, every "could it also do X" — these are not noise to be triaged against a roadmap. They are the product itself, being built one shop at a time. The roadmap is the substrate (see The Substrate Line). The features are the customer's.
The doctrine, in one sentence:
The software stops being something the shop buys and starts being something the shop owns, in the deepest sense — shaped by their hands, fit to their floor, indistinguishable over time from their way of doing business.