Workflow Touch Audit

Find the hours your workflows are taking from you.

The calendar shows the meetings. This shows everything else: the reports nobody reads, the approvals that wait on you, the data typed twice, the account that eats your week. It opens with the question nobody asks an owner, puts a number on twenty kinds of leak, and closes by asking what you should stop owning altogether.

Say “not really” to skip any of them.
Nothing is removed on the opening screen. It names candidates; the close rules on them.
Every hour is your own numbers × 52, with the arithmetic shown.
Signed in, the answers feed the Advisor alongside your calendar.

Exit · the opening question

Before we measure anything: what would you take on again?

SAVE opens and closes on the same question. The rest of this audit asks how to do things better; this asks whether you should own them at all. Answer what you can and leave the rest empty.

If you were starting this business today, which of these would you take on again?Which client or account takes the most out of you relative to what it returns?Which service line would you quietly stop selling if nobody noticed?What are you still doing because you always have, rather than because you decided to?What would you have to stop doing for the next quarter to feel like you got your week back?

Nothing gets removed on the strength of this screen. A service line that looks unprofitable is very often just an un-automated one, so this produces a list of candidates and nothing else. They come back at the end, once there are numbers behind them.

The twenty leaks

Subtract, automate, vest, exit.

The same categories the paid audit walks through, in the same order: the cheapest hours first, the flagship moves next, and the containers a leak lives inside last. Exit is asked twice, at the start and at the end, which is what makes SAVE a cycle rather than a list.

Subtract

Cheapest hours, fastest credibility.

Recurring reports nobody acts on
Agenda-less recurring meetings the owner attends
Tool sprawl and shelfware
Context switching and fragmented attention

Automate

Visible, quantifiable, sticky.

Owner's inbox and message triage
Quoting, proposals, and estimates
Scheduling back-and-forth
Invoicing, receivables, and payment chasing
Re-keying data between systems
Location- or device-locked work

Vest

Slower to return, the flagship hook.

Onboarding done from memory
Repeated questions and tribal knowledge
Approvals bottlenecked on the owner
The "only I can do this" tasks
Rework
Waiting on external dependencies
Non-utilized talent

Exit

Keep it, freeze it, or remove it.

The disproportionate client or account
The service line that no longer earns its place
Commitments that outlived their reason