What twelve minutes produces

This is what you end up holding.

One workflow, mapped end to end: twenty-seven fields, six verdicts, and a dollar figure on the coordination nobody was counting. Five steps and about twelve minutes of your own answers produce the same thing for a workflow of yours. Skim the estimates first; the map underneath them is where they came from.

Company: Riverside Mechanical
Workflow mapped: Missed call → quote → schedule → invoice for residential service
Situation it named: Capacity ceiling + revenue leakage
The call it produced: Keep tech craft and customer relationships; redesign office path and evening coverage.

Priced by step three

One workflow, priced.

$28,080–$37,440: Annual labor costThe only straight cost here. Everything below it is a ceiling to investigate, not money on the table.

Error / rework labor: $2,808–$5,242; Cost · annual labor × (error % ÷ 100)
Missed demand contribution (theoretical max / yr): $91,000–$149,240; Theoretical max · missed units/week × contribution/unit × 52 · Upper bound if every missed unit were won at stated contribution — not proven recoverable.
Non-conversion contribution (theoretical max / yr): $145,600–$255,840; Theoretical max · workflow volume × (1 − conversion%) × contribution × 52 · Not all non-conversions are operational leakage. Ceiling to investigate, not a promise.
Retention leak (theoretical max / yr): $9,828–$19,188; Theoretical max · customers/week × leak% × contribution × 52 · Requires customers/week — not inferred from workflow volume.
Cash / AR exposure in cycle: $20,800–$37,440; Delayed cash · (volume/week ÷ 7) × cash cycle days × revenue/unit · Requires revenue/invoice value per unit — not contribution.
Contribution delayed one cycle lag: $3,000–$7,029; Illustrative · volume/week × (delay days ÷ 7) × contribution/unit · Illustrative timing drag for one modeled lag — not annualized loss.

How it was produced — two fields, both the owner's own estimate: 12–16 hrs/week of coordination on this path, at $45/hr fully loaded. Your map prices itself off the same two. Riverside Mechanical is a composite, drawn from workflows we have mapped.

Six verdicts you can argue with, line by line.

KeepTech craft quality and relationship ownership on complex jobs.read off People · Role per step
ImproveNamed owner for aged quotes; written warranty decision rules.read off Ownership · Where ownership is unclear
IntegrateFSM ↔ QuickBooks so invoices do not retype job economics.read off Tools · Where data is re-entered
AutomateAfter-hours capture + callback queue — only after map confirms ownership and rules (hypothesis, not a pre-sold agent).read off Decisions · Decision latency
ReplacePaper warranty cards and monitor sticky notes — the shadow system the office rebuilds from memory every week.read off Tools · Shadow tools (texts, notes, shared drives)
BuildOnly if off-the-shelf queue + rules cannot cover evening lead capture with audit.read off Exceptions · Failure modes under volume

Twenty-seven fields — the whole workflow, written down.

Steps

Trigger / start state —: Phone rings or web form submits for service.
Step-by-step sequence —: Ring → voicemail/text → office callback → quote in FSM → schedule tech → complete job → invoice in QB.
Done / completion state —: Invoice sent and payment recorded.

People

Role per step —: CSR/office (day), owner after 5pm, two techs, bookkeeper weekly.
Backup / who covers outages —: Owner covers CSR absences; no backup for evening calls.
Who approves exceptions —: Owner only for discounts, warranty gray areas, overtime.

Tools

Primary systems —: Phone, SMS, field service software, QuickBooks.
Shadow tools (texts, notes, shared drives) —: Owner’s texts; paper warranty cards; sticky notes on monitor.
Where data is re-entered —: Job notes retyped into QB; customer phone re-entered from text thread.

Data

Inputs required at start —: Address, equipment age, urgency, preferred window.
Fields updated mid-flow —: Quote amount, parts needed, scheduled tech, payment status.
Source of truth for status —: None single — FSM vs texts vs owner’s head.

Decisions

Routine decisions —: Which tech, first available window, standard service rates.
Exceptions only a person can make —: Warranty eligibility, “loyal customer” discounts, emergency after-hours.
Decision latency —: Evenings and weekends stall until owner responds.

Handoffs

Handoff moments —: CSR → tech; tech → office; office → bookkeeper; all escalate to owner.
What must be true at handoff —: Scope, price expectation, access notes, parts status.
What gets lost or delayed —: Access codes, “customer said,” partial payments.

Exceptions

Common exceptions —: No-answer callback loops; special-order parts; warranty fights.
Failure modes under volume —: Quote lag >48h; unreturned evening leads; invoice backlog.
Workarounds people use today —: Owner answers phone on jobs; techs text price guesses.

Ownership

End-to-end owner —: De facto the owner; no named process owner.
Where ownership is unclear —: Who owns aged quotes; who owns collections under 30 days.
Who can change the process —: Owner only.

Dependencies

Upstream inputs this flow waits on —: Homeowner availability; prior invoice clear.
External vendors or partners in the path —: Parts house (2–5 days special order); financing portal.
Systems or people that freeze work when unavailable —: Owner phone; FSM login; bookkeeper Fridays.

Six symptom lists — how the situation gets named.

Capacity

We turn away or delay work we would otherwise want
Peak weeks require overtime or emergency hiring
Service quality dips when volume rises
The bottleneck is admin coordination, not craft skill

Bottleneck

One role or system gates every other step
Work piles in a queue waiting on a person or file
Status is only known by asking someone
A single shared inbox or board is the choke point

Duplication

The same facts are entered in two or more places
Customers restate information the company already has
Reports are rebuilt by hand each week
Multiple spreadsheets claim to be “the list”

Owner dependence

Exceptions default to the owner’s phone or inbox
Important relationships only move when the owner is present
Delegation fails because rules live in one head
A week without the owner slows the whole company

Revenue leakage

Leads or quotes age without a clear owner
Completed work waits days to become an invoice
Follow-up, renewals, or collections are inconsistent
Service failures create rework or lost referrals

Fragility

Critical knowledge lives in one inbox, spreadsheet, or person
No documented path for the top five exceptions
A tool outage would freeze cash or dispatch
New hires take months to learn “how we really do it”

Produced the other way

What this version cannot tell you.

Every verdict above came out of one person’s account of one workflow, written from memory in about twelve minutes. That is genuinely useful, and it is honestly bounded: the ranges are wide because you are estimating your own inputs, and the map holds your view of the work rather than your CSR’s, your techs’, and your bookkeeper’s.

The Strategy Process is the same artefact built the other way. Over 10–14 days we trace the workflow with the people who actually run it, replace your estimates with observed numbers, and attach a costed recommendation to every line that comes back Improve, Integrate, Automate, Replace, or Build — scope, assumptions, cost range, ROI model, and risks, so you can argue with each one. $2,000, credited in full against the first build it leads to.

Now do it for one of yours.

Pick the workflow that touches money, customers, or your calendar every week. Five steps, one at a time, and you have a dollar figure by step three.

Start your mapFree · 5 steps · about 12 minutes · nothing is sent until you send it