Your SOPs, versioned in the system — not a binder on the counter.

Process Studio is planned for Growth and above: staff-editable checklists and gates bound to service types. Domain state machines and audit events already enforce RO transitions today; Studio adds shop-authored SOP overlays on top.

Status honesty: Listed on Growth plans as Process Studio (basic). The authoring UI is roadmap — we do not claim a live Process Studio product surface in the demo today.

Live today

Process foundation already in the product

You do not wait for Studio to get disciplined job flow. These ship in the demo:

Repair-order status transitions enforced by shared domain rules
Audit events on sensitive mutations and stage changes
DVI findings and estimate lines as structured work evidence

Roadmap · Growth+

What Process Studio will add

Shop-authored methodology on top of the domain state machine — not a replacement for it.

JSON process definitions with checklist gates
Bind templates to service categories (brakes, diagnostics, menus)
Version history and who completed each step
Training path without paper binders

Why we still talk about it

Differentiation without fake “live” claims

Competitors often lock shops into fixed templates. Wrench is designed so your brake job, diagnostic, and service-menu SOPs can become first-class process definitions — versioned and auditable. Until the authoring UI ships, Growth pricing lists Process Studio (basic) as the entitlement target, and this page stays explicit about roadmap status.

← Public booking (live)·Compare matrix →

Run the live board while Studio is built

Start a Growth trial for DVI, KPIs, and the Process Studio entitlement path — or open the demo and walk a real RO today.