Loading
Loading
Processes & use cases · 24 flows
Not a feature list — 24 documented workflows showing every action, surface, outcome, and status. Evaluate by process, not by checkbox.
Vehicle lifecycle
The Automotive Workshop Operating System (AWOS) maps every customer moment from first contact to retention — so software follows how workshops actually earn margin.
Phone, web, walk-in, or fleet enquiry captured as a real person + vehicle need.
First-class CRM record — not free text on a paper job card.
Rego, VIN, history, and ownership linked so the next visit is faster.
Slot, service type, and capacity intent before the bay is blocked.
Booking becomes a repair order; board WIP starts counting.
DVI findings with severity create evidence, not opinions.
Priced lines for recommended work — ARO lives or dies here.
Line-level authorisation; variations cannot silently expand scope.
Reserve, order, receive — bays stop becoming parking lots for missing parts.
Clock time on the job so efficiency is coached, not guessed.
Repair with domain-enforced stage transitions and blockers visible.
GST tax invoice from approved lines — money path, not a second spreadsheet.
Record payment / pay-link path; AR and cash visibility for owners.
Vehicle out with history written for the next service conversation.
Follow-up, deferred work recovery, and next-service reminders.
Featured processes
Start here if you're evaluating whether the software fits your operation.
Service advisor · front of house
Every delayed or messy intake creates rework: wrong vehicle, missing phone number, or an RO that never hits the board. Intake is where car count and data quality are either protected or destroyed.
Authorisation · margin protection
Shops lose money two ways: unapproved work that becomes write-offs, and weak ARO because recommended work was never decided. Line state is the control plane.
Technician · efficiency
Techs should spend cognitive load on diagnosis and repair — not hunting the same screens advisors use for AR. My Day + timers + DVI keep the floor fast. Stall-risk is a waiting-on-parts overlay, not a new RO status.
Use case library
Each card opens a full stage sequence: action, why it exists, surface, outcome, and a live demo capture where available.
26 processes
Service advisor · front of house
LiveEvery delayed or messy intake creates rework: wrong vehicle, missing phone number, or an RO that never hits the board. Intake is where car count and data quality are either protected or destroyed.
Capacity · CX · car count
LiveMissed calls and voicemail are silent car-count killers. A public book URL (and optional iframe) captures intent when the shop is under a car — then check-in converts the appointment into board WIP.
Workshop manager · floor control
LiveWIP only improves when stages mean the same thing to advisors, techs, and owners. Domain-enforced transitions stop “just move it to ready” shortcuts that hide missing parts or unapproved work.
Technician · trust · ARO
LivePhoto-backed (and structured) findings raise approval rates and cut “I didn’t authorise that” disputes. The system must connect inspection → estimate → customer decision without retyping.
Authorisation · margin protection
LiveShops lose money two ways: unapproved work that becomes write-offs, and weak ARO because recommended work was never decided. Line state is the control plane.
Parts · purchasing · throughput
LiveAuthorised work without parts is fake progress. Reserve on approve, raise POs, and receive goods so stage AWAITING_PARTS means something operationally true.
Technician · efficiency
LiveTechs should spend cognitive load on diagnosis and repair — not hunting the same screens advisors use for AR. My Day + timers + DVI keep the floor fast. Stall-risk is a waiting-on-parts overlay, not a new RO status.
Money path · cash
LiveRe-keying approved work into a separate invoicing tool is how lines get lost and disputes start. Operational invoices should birth from authorised scope; books of record stay in Xero/MYOB — export is Dry-run today with a gated live push path, not Connected theatre.
Owner · profit theory
LiveThin-margin independents die on invisible waste: unapproved work, idle bays, unbilled labour, late AR. Dashboards only help when formulas are honest and tied to board reality.
Customer experience
LiveCustomers will not create another password to approve brakes. Token links deliver line decisions, audit trails, and faster bay release.
PLG · time-to-value
LiveSoftware that needs a consultant to open a job will lose independents. Day 0 should create a tenant, an owner, a bay, and a path to the board — then deepen configuration.
People · enablement
LiveHires fail when everyone sits through the owner tour. Each role gets a 10–20 minute first win, screenshot pins, and a competence list. The in-app checklist stays the Day-0 contract for owners.
Evaluation · trust
LiveBuyers regret tools that look great in an owner demo and collapse for technicians. Seeded multi-role accounts make evaluation honest.
Money · CX · AR
PartialUS leaders package text-to-pay tightly. Workshop Wrench ships payment records and pay URLs on invoices, portal pay path, and Stripe Checkout that is Stub without keys and live when configured — never Connected theatre by default.
Revenue recovery · Parts/Advisor
Live+Declined or deferred estimate lines are not lost — they sit in a time-aware queue. When the vehicle returns, everything the customer said no to is surfaced automatically.
Groups · Scale
Live+Independent groups need HQ visibility: open jobs, AR, and stock movement between locations. Workshop Wrench ships multi-location KPIs and stock transfer when locations are seeded — honest Live+ depth, not a full franchise ERP.
Parts · multi-loc
LiveMissing parts park cars. When another location has stock, a transfer beats a rush order. Workshop Wrench records inter-location transfers against on-hand quantities.
B2B · Partial
PartialFleet customers need purchase-order rules and threshold checks before work expands. Workshop Wrench ships fleet account fields and check APIs/UI as a Partial shell — not a branded fleet portal or insurer network.
Admin · Partial
PartialWarranty work needs status and history even when insurers are still email-driven. Workshop Wrench provides a warranty claims entity and UI as a Partial shell — not a live insurer integration.
Bookings · Live
LiveAdvisors live in calendar apps. Workshop Wrench exports bookings as ICS so diary visibility extends beyond the app — Live export, not a claim of full Google two-way sync.
Tech · PWA · Live+
Live+Technicians still need evidence when the network blips. Workshop Wrench queues DVI finding media offline (IndexedDB) and syncs when connectivity returns — Live+ depth, not a claim of full offline ERP.
Switch · Partial
PartialMigration is the hidden cost of shop software. Workshop Wrench provides an import path for operational data — Partial honesty: design-partner quality, not a certified MechanicDesk/Shopmonkey one-click claim.
Process Studio · Partial
PartialProcess Studio direction: templates, rules, and simulate-first automation so shops encode SOPs without silent financial side effects. Status is Partial — simulate exists; full authoring durability still expands.
Trust · meta process
LiveLogo 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.
Parts Exchange · Buyer
LiveWorkshop buyer searches Parts Exchange for a part, reviews listings from verified wreckers, and sends an RFQ — without leaving the Workshop Wrench platform.
Customer experience · Portal
Live+Customers approve, decline, or defer estimate lines via a mobile-friendly portal link. Trust mode classifies each line as Urgent / Advisory / Cosmetic — customers decide with context, not just a price.
Operating model
Buyers do not purchase feature grids — they purchase fewer missed cars, higher ARO, faster bay turns, and cleaner cash collection. Documenting every use case with rationale and stages makes evaluation honest, improves SEO topical depth, and keeps product, e2e, and marketing on the same spine (15 lifecycle stages).
SEO keyword landings
Dedicated landings for high-intent phrases — each points into the matching process for depth.