Demonstration
One repair order, start to finish.
Intake to delivered, on the founder's own test shop: the actual screens BayStacker showed, in the order the repair happened — not a mockup.
1 · Intake
A complaint becomes an intake.
VIN, customer, phone, complaint and four arrival photos. Create intake stays unavailable until every one of them is on the form — the screen names exactly what is still missing.
2 · Diagnosis
The case reads what is recorded, not what is assumed.
The evidence ladder on RO LAT-WO-2026-00193's own case: symptom and root cause on file, observed behaviour and codes still open. Nothing on this list is checked until it is actually recorded.
3 · Repair
Removal, build and reinstall, each one timestamped.
The same repair order’s road test log: three inputs, each with the person who completed it and the minute it happened, not a single "repair complete" checkbox.
4 · Money
The invoice, and the honest line about paying it.
Paid in full, balance $0.00 — and the shop’s own payout state shown beside it rather than assumed. A shop with no connected payout account is told so where the invoice is sent, not left to find out from a declined card.
5 · Delivered
Intake, diagnosis, repair, verification — then closeout.
The same repair order’s overview, at the end: all four phases marked done, and the vehicle itself marked Closeout · Delivered. Nothing on this page was staged for the screenshot; it is the record the repair actually left behind.
Proof
First shop stories coming.
This walkthrough runs on the founder's own test shop, not a customer's. There is no shop story here yet — when a shop that has actually used BayStacker agrees to have theirs told, it replaces this paragraph, and not before.
See it on your own last rework.
A walkthrough runs Analysis A on a job that already came back — the shop brings the job, not the other way round.