Loading
Trust · meta process
LiveRead integration badges like a buyer who has been burned
Logo walls lie. This process teaches how Workshop Wrench labels integrations — matching API catalog truth — so evaluation is fair against MechanicDesk, Workshop Software, Shopmonkey, and Tekmetric packaging.
Primary persona: Owner / IT evaluator
The problem
What breaks without this process
Buyers sign contracts on “Connected” logos that are actually salesware.
Why it matters
Rationale — profit, risk, and shop floor truth
- 01
AU day-one bar is Xero + parts + SMS + pay-link — each with honest status.
- 02
US QBO/PartsTech are later, not day-one theatre.
- 03
OpenAPI Live is a real alternative to 70 fake connectors.
Proof from the live demo
Real UI — not a pitch mockup
Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.
live demo capture
Stage sequence
Step-by-step use case
Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.
- 01
Open integrations hub
Action
Read Live / Stub / Dry-run / Planned legend.
Why this stage
Shared vocabulary with the product catalog.
Surface: /integrationsOutcome: Legend understood - 02
Check money adapters
Action
Xero Dry-run · Stripe Stub|live by key · SMS mock|Twilio · AU parts shell connected:false.
Why this stage
These are the AU competitive objections.
Surface: Integration pagesOutcome: Honest shortlist - 03
Prove in demo settings
Action
Login demo → Settings integrations strip + Swagger catalog.
Why this stage
Marketing must match API status.
Surface: Settings /docsOutcome: Trust - 04
Plan elevates
Action
Only flip Connected/Live after STATUS + e2e evidence.
Why this stage
Prevents marketing outrunning product.
Surface: Program boardOutcome: Safe GTM
Related search intent
- workshop software integrations
- Xero dry run honesty
- shop software API