What it is
Most software projects fail in the gap between “we talked about it” and “we built it.” The Engagement Workshop closes that gap by making every decision explicit and writing it down before a single screen is configured — so the build is executing a spec you approved, not a vendor's interpretation of a phone call.
It's also the honest checkpoint. If the workshop shows this isn't a fit for where your business is right now, we'll tell you there — before you've committed to a build.
The agenda
Every block below ends in something written down. That's the difference between a workshop and a meeting.
Which trades you actually run, how a job moves from first call to paid, and the three or four places it reliably breaks down. This is the map everything else is built on.
You leave with: A written workflow per service line
The revenue and margin target the build is aimed at, and what has to be true operationally to hit it — more trucks, higher ticket, better close rate, or fewer callbacks.
You leave with: The target the build is measured against
Who does what today, who approves what, and what a tech sees versus what the office sees. Where the owner is currently the only path, we name a role to hand it to.
You leave with: A role map and permission model
Flat-rate structure, tiers, and markups — plus whether we sync your existing book (Profit Rhino and similar) or build it out with you.
You leave with: Pricing structure and sync decision
How calls, web forms, and missed calls become jobs. What gets asked, what qualifies as an emergency, what the AI can answer, and when a human takes over.
You leave with: Intake scripts and triage rules
What stays. QuickBooks remains your books, Stripe keeps processing at your rates, your business line stays yours — we confirm what connects and what we deliberately don't replace.
You leave with: The integration list, agreed
The handful of numbers you'll actually manage by, who owns each one, and what a bad week looks like early enough to fix it.
You leave with: KPI set and dashboard-by-role
The words your shop uses — because the software should say what your crew says. Job or service call, tech or technician, your service areas, your hours, your rules.
You leave with: Vocabulary and configuration
The commercial decision, made with the numbers in front of you: stay fully managed and keep the cash in the truck, or pay to own it and put an asset on your books.
You leave with: Your ownership path
What you walk away with
One document that contains your workflows, SOPs, role map, KPI set, integration list, pricing structure, and ownership decision. It's the spec your build is held to — and it's useful on its own, because most owners have never had their business written down in one place before.
How to prepare
We send a short pre-work portal when you book. It asks for the basics so the session is spent deciding rather than gathering:
Bring whoever runs the day with you — the owner alone gives us half the picture. If you have a dispatcher or office manager, they should be in the room.
What happens next
We carry the system, the hosting, and the AI costs. Keep the cash in the truck, and walk away whenever you want.
$30,000 total, financing available. After the twelfth payment the software is yours — an asset on the books, not a bill.
You choose the path during the workshop, with the numbers in front of you — and most shops are live 2–3 weeks later. Compare both paths in detail on the Service OS Pro site.
Book it
We talk first — a short call to confirm this is a fit for where your shop is. If it isn't, we'll say so. If it is, we book the workshop and send your pre-work portal.
