\03  ·  Fix It

Something doesn’t do what it’s supposed to. How do we fix this workflow?

Most broken systems aren’t actually broken — they’re just doing what they were built to do, badly. A workflow that eats three hours a day.A dashboard nobody trusts. An account that’s been bleeding money because nobody had time to audit it properly. That’s the work: find the actual fault, not the symptom, and rebuild it so it stops happening again.

How it works — plainly.

01

You describe what’s actually going wrong, not what you think the solution is.

02

The real problem gets isolated. Usually it isn’t what you first thought.

03

A fix gets built and handed over — working, not theoretical.

What this looks like in practice

\A workflow fix

A three-hour daily PDF assembly job, traced to its real bottleneck and rebuilt into a two-minute automated run.

\A reporting fix

A dashboard nobody trusted, followed back to one broken data source and repaired so the numbers finally hold.

\A recovery resolved

A Google Ads account quietly overbilled for months — audited, disputed under the CGA, and the overspend recovered.

Wrong door?