Less chaos.
More clarity.
I work with founders, small businesses, agencies and freelancers on the friction between tools, people and process. I map it, fix it, and make it repeatable. When it helps, I build the tool too.
practice snapshot
What I do
Execution support,
without the overhead
Operations
The work runs on process, not on whoever remembers.
/02Reporting
Vital signs, not vanity charts. A small family of measures everyone trusts.
/03Systems
Tools that talk to each other. Hand-offs without the copy-paste.
/04AI & automation
Automation where it pays for itself. Judgment stays human.
The friction audit
Six honest checkboxes
Let's do a quick friction audit and see where you stand. Tick whatever sounds familiar, then hit the button below. We'll narrow down the problem together.
friction score 0/6 · Untick everything and I will worry about you.
Book a call with this →How it works
Map. Define.
Close. Improve.
A formal improvement method, applied without the ceremony. The same discipline the textbooks spend on thousand-person companies, right-sized for yours. And it never actually ends, by design.
-
Map the current state
How the work actually flows today. Inputs, activities, outputs. Root causes separated from symptoms, bottlenecks found, and every step asked one question: does this add value?
-
Define the desired state
Where the process ought to be for the business you're becoming, not the one you were. Honest about what "good" means, so the distance between the two states is the real work.
-
Close the gap
Quick wins first, structural changes second, so momentum pays for the deep fixes. Never shifting a problem to a different desk and calling it solved.
-
Document, measure, go again
Owners, hand-offs, and a small balanced set of measures: cost, quality, time. Report, re-scope, start the next wave. Tools, people and markets keep changing, so improvement is a loop, not a finish line.
Custom tools
If technology solves it, I build it. For you alone. Never shared.
-
→The problem picks the tool
Sometimes the fix is a workflow. Sometimes it's a script, an AI integration, or a small app built into the stack you already run. Technology follows process. Never the other way around.
-
→Adoption is part of the build
A tool nobody opens is a liability with a subscription fee. Everything ships with a dry run and a reason to use it, so it lands in the daily work instead of next to it.
-
→Private by default
Built for your workflow, shared with you alone. Never published, resold or reused.
Who this is for
Small teams with
real momentum
You're already moving. The problem isn't effort, it's structure. That's where I come in.
-
Founders
Execution support without a full-time hire.
-
Small businesses
Operations and growth that run on process, not luck.
-
Agencies
Workflows that finally give you visibility.
-
Individuals
Freelancers who want systems, not chaos, around their craft.
FAQ
Asked straight, answered straighter
I'm a founder. Everything runs through me. Is that fixable?
That's the most common starting point there is. The work gets mapped, the decisions only you can make get separated from the ones you shouldn't be making, and the rest gets a documented home with an owner. The goal is a company that keeps its shape when you take a week off.
We're a small business. Can we afford real operations work?
Yes, because it starts small on purpose. One process, scoped and fixed, with the cost agreed before work begins. Done right, it pays for itself in recovered hours long before it feels like an expense.
We're an agency. Clients only see the chaos at the end. Help?
Client work gets a visible flow: where every project stands, what's waiting on whom, and what the client sees before they ask. Fewer status calls, fewer surprises, and the delivery team stops being the firewall.
I'm a freelancer. Isn't operations a big-company thing?
It's a leverage thing, and leverage matters most when you're alone. Invoicing that runs itself, client updates that write themselves, a pipeline you can read at a glance. The craft stays yours. The admin stops being.
How do you know if it actually worked?
A small, balanced set of measures is agreed before anything changes, baselined against real historical data: cost, quality, time. Value gets defined your way, not forced into a spreadsheet. Roughly right beats precisely wrong.
Will changing how we work slow us down first?
Honestly: yes, briefly. Performance dips when any new process lands. The dip is predictable, so it gets managed openly, with dry runs and a clear case for change, and performance climbs past where you started.
Is this an AI consultancy?
No, it's an operations practice that knows AI well. Automation and models have a place across the whole lifecycle: spotting the problem, surfacing it, resolving it. The work is choosing where, and just as often, where not.
Who owns the tools you build?
You do. Custom tools built during an engagement belong to your company, for your use. They are never shared with anyone else.