Skip to content
Workshop Wrench
Compare · 2026-08Process-first

Compare shop software the way shops actually run

Feature grids hide the truth. Buyers lose money on weak booking, invisible WIP, unauthorised work, missing parts, late AR, and KPIs nobody trusts. Wrench strengths today: Process Studio path (design), open API, multi-tenant demo isolation, AU-first GST, DVI → portal approve spine. Honest gaps: Xero is Dry-run (gated live path, not Connected); AU Repco/Burson catalogs Planned/mock — not live Repco; SMS mock/Twilio-when-keyed; text-to-pay / portal pay path expanding (Stripe shop Stub without keys). US QBO + PartsTech are later — not day-one logos.

01

Date every claim

Capabilities and prices move. This matrix is a 2026-08 snapshot — always re-check vendor sites.

02

No #1 superlatives

We respect competitors. Wrench wins some process designs and trails on SMS/payments maturity and native AU catalogs — labeled clearly.

03

Demo is ground truth

Live multi-tenant demo beats slideware. Integration badges use Live / Stub / Dry-run / Planned — never Connected for stubs. AU day-one bar first; QBO/PartsTech US later.

04

Process over checkbox

Every row should map to car count, ARO, throughput, cash, or trust — not vanity modules.

Business processes

What every shop OS must solve

Pain, market pattern, and how Workshop Wrench addresses each process. Colour badges show relative fit — not a championship ranking.

01Wrench edge

Lead & online booking

Missed calls and voicemail silently destroy car count; website forms that only email the shop force double entry.

Stage sequence →

Typical market leaders

Leaders ship public booking widgets and SMS confirmations; capacity scoring quality varies by plan.

How Workshop Wrench solves it

Public /book/[slug] creates a real Booking via API; optional iframe embed; check-in converts to RO on the board.

Why: Car count is a first-class OS event — not a contact-form graveyard.

02Competitive

Front desk intake

Free-text tickets create duplicate customers, lost history, and unsearchable vehicles.

Stage sequence →

Typical market leaders

Mature CRM + vehicle modules are table stakes on Shopmonkey, Tekmetric, MechanicDesk, Workshop Software.

How Workshop Wrench solves it

Customer + vehicle first-class; one-path RO open; search by name, phone, rego, RO — board WIP starts immediately.

Why: Garbage in at intake becomes garbage ARO, invoices, and retention later.

03Wrench edge

Job board & bay dispatch

Invisible WIP and free-text statuses let jobs leapfrog auth/parts — ETAs and utilisation lie.

Stage sequence →

Typical market leaders

US cloud leaders set a high bar on kanban boards; some AU tools remain list-heavy.

How Workshop Wrench solves it

Kanban by RO stage with domain-enforced transitions (shared API/UI rules); blockers stay visible.

Why: Throughput only improves when “in progress” means producing, not waiting.

04Competitive

Digital vehicle inspection

Verbal upsells without evidence erode trust; paper sheets never become recoverable revenue.

Stage sequence →

Typical market leaders

Shop-Ware/Shopmonkey-class media DVI is strong; often plan-tiered photo/video polish.

How Workshop Wrench solves it

Findings with severity on the RO → estimate lines → portal decide; rich media templates expanding (honest Partial).

Why: DVI is an ARO and dispute-prevention system, not a camera gimmick.

05Wrench edge

Estimate & line authorisation

Whole-job “OK” texts hide declined lines; silent variations create write-offs and chargebacks.

Stage sequence →

Typical market leaders

Leaders push SMS estimate approval; depth of line-level portal UX varies.

How Workshop Wrench solves it

Line states PENDING → APPROVED | DECLINED | DEFERRED; token portal without shop login; board clears AWAITING_AUTH.

Why: Only structured line state protects margin, audit, and invoice integrity.

06Wrench edge

Parts readiness & purchasing

Authorised jobs stall as parking-lot bays; stock lives in a spreadsheet beside the DMS.

Stage sequence →

Typical market leaders

Inventory + PO common; true reserve-on-approve is uneven. AU catalogs strong on MechanicDesk/WS.

How Workshop Wrench solves it

Catalogue, low stock, reserve on approve, PO + goods receive; AU supplier punch-out staged (not oversold).

Why: AWAITING_PARTS must drive purchasing action, not hope.

07Competitive

Technician labour & My Day

Desktop CRM noise under the car kills time capture and finding quality.

Stage sequence →

Typical market leaders

Strong tech mobile apps on US cloud; offline reliability varies.

How Workshop Wrench solves it

Role-fit My Day, job-linked timers, DVI in context, installable PWA + offline queue path expanding.

Why: Efficiency metrics need clocks on jobs; techs need cognitive load designed for the bay.

08Competitive

Invoice, tax & cash collection

Re-keying approved work into a separate invoice tool loses lines; AR becomes a Friday surprise.

Stage sequence →

Typical market leaders

Integrated payments / text-to-pay mature on US leaders; AU EFTPOS + Xero stronger on local peers.

How Workshop Wrench solves it

GST tax invoice from authorised RO lines; payment records + AR Live; text-to-pay / portal pay path expanding (Stripe Checkout Stub without keys, live when configured); Xero Dry-run (stage + dryRunPush, gated live path).

Why: Revenue is not cash until collected — money path stays on the job aggregate.

09Wrench edge

Owner KPIs & coaching

Vanity charts staff cannot explain train owners to ignore the product.

Stage sequence →

Typical market leaders

Deep reporting is a Tekmetric-class strength; definitions often opaque.

How Workshop Wrench solves it

Owner dashboard with ARO/deferred/attention; formulas documented in domain package + resources.

Why: Behaviour change needs numbers advisors and techs can defend in a Monday meeting.

10Competitive

Customer portal & retention loop

PDF-via-text approvals do not write audit state; deferred work dies on sticky notes.

Stage sequence →

Typical market leaders

Portal depth uneven; review automation stronger on growth-oriented vendors (e.g. AutoLeap narrative).

How Workshop Wrench solves it

Token portal live for line decisions; deferred work pipeline; review automation still roadmap (honest).

Why: CX systems must change operational state — or they are vanity portals.

11Wrench edge

Onboarding, switch & multi-tenant trust

Consultant-shaped DMS projects stall independents; multi-tenant leaks destroy trust.

Stage sequence →

Typical market leaders

Sales-led demos common; import quality varies; isolation rarely demoed.

How Workshop Wrench solves it

Published demo logins (owner/tech/isolation), trial path, tenantId everywhere; import wizard staged honestly.

Why: Time-to-value and security theatre are evaluation criteria, not afterthoughts.

Vehicle lifecycle

Complete vehicle service lifecycle

The Automotive Workshop Operating System (AWOS) maps every customer moment from first contact to retention — so software follows how workshops actually earn margin.

  1. 01Lead
  2. 02Customer
  3. 03Vehicle
  4. 04Booking
  5. 05Check-in
  6. 06Inspect
  7. 07Estimate
  8. 08Approve
  9. 09Parts
  10. 10Labour
  11. 11Produce
  12. 12Invoice
  13. 13Pay
  14. 14Release
  15. 15Retain

Capability matrix

Typical closed SaaS vs Workshop Wrench

Aggregated view across the category. Open a vendor page for head-to-head detail.

CapabilityTypical closed SaaSWorkshop WrenchFit
Job board / repair orders
Operations
Yes — mature cloud boards on US leadersYes — kanban + domain state machine (live demo)Competitive
Digital vehicle inspection
Operations
Strong media DVI; often plan-tieredFindings → lines → portal live; media gallery expandingCompetitive
Customer portal line approvals
Customer experience
Often add-on or partialToken portal live — approve / decline / defer per lineWrench edge
SMS / email events
Customer experience
Core packaging on many US plansSMTP Live (dev) · SMS Stub (mock) · Twilio when keyed · portal deep linksThey lead
Public online booking
Operations
Widget often tieredLive /book/[slug] + iframe embed pathWrench edge
Inventory reserve on approve
Operations
Varies / partialLive reserve + PO receive loopWrench edge
Invoicing & tax
Money path
US tax norms; AU GST deeper on local peersGST-aware invoices from RO (AU/NZ-first helpers)Wrench edge
Integrated payments / text-to-pay
Money path
Strong on Shopmonkey/Tekmetric-classPayment records Live · Stripe Checkout Stub · text-to-pay / portal pay path expandingThey lead
Accounting (Xero / QBO)
Money path
US: QBO-first; AU peers: native Xero/MYOBGST Live · Xero Dry-run (gated live path) · MYOB Dry-run · QBO US laterWrench roadmap
Parts catalogs
Operations
US: PartsTech; AU peers: native Repco / Burson EzyPartsSupplier port · AU Repco/Burson Planned (mock) · PartsTech US later · generic StubWrench roadmap
Owner KPIs with formulas
Intelligence
Reports common; definitions often opaqueDashboard + formulas in @wrench/domainWrench edge
Process / SOP customization
Intelligence
Limited templatesProcess Studio Growth+ · authoring UI Planned/Roadmap (strength in design)Wrench roadmap
Transparent published pricing
Platform & trust
Varies — quote-led still commonStarter / Growth / Scale + Enterprise publishedWrench edge
Open API & webhooks
Platform & trust
Varies; logo marketplaces commonREST OpenAPI Live · outbound webhooks StubWrench edge
Live try-before-buy + multi-tenant isolation
Platform & trust
Often sales-scheduled; isolation rarely demoedSeeded multi-role demo · tenantId everywhere (edge)Wrench edge
Docker / self-host path
Platform & trust
Rare (SaaS only)First-class local + GCP pathWrench edge

Pricing bands and tier gates change frequently. Always verify messaging, accounting sync, and SMS quotas on the vendor’s current pricing page. Internal research lives in docs/competitors. Demo credentials and Features status labels override marketing aspiration.

Wrench edgeCompetitiveThey leadWrench roadmap

Why process comparison matters

Software only pays for itself on thin margins

Every process above maps to a profit lever. If a vendor wins a checkbox but loses the process, you still lose cash.

Car count

Booking, intake, reminders — missed first contact never becomes a bay hour.

ARO

DVI → priced lines → line decisions. Unstructured “looks fine” texts kill recovery.

Throughput

Honest stages + parts reserve. Waiting work must not look “in progress”.

Cash

Invoice from authorised scope + AR visibility. Revenue ≠ cash until collected.

Prefer a live board to another comparison slide?

Start a trial or open the seeded multi-tenant demo — owner, tech, and isolation logins published.