The Nomad Ops Book the audit

From the audit to an operation that runs without you.

Five phases over about 90 days, each with named deliverables, so you always know what you are getting, what is still yours, and what done looks like.

Book the Operations Leak Audit Scrub the first 90 days

The first 90 days.

Scroll, drag the slider, or jump to a phase.

Day 1

The Operations Leak Audit

A 45-minute working session on one ordinary week of your business. You walk me through where work arrived, who picked it up and where it waited.

This phase hands you

  • A one-page leak map
  • The first system to build, and who should own it
  • Any proposal in writing, after the call

Still comes to you

Everything, for now. Nothing changes until we agree on the map.

Weeks 1 and 2

Map everything before fixing anything

I map every workflow, every tool, every handoff and every place where you are the only person who can move the work. I talk to your team, not only to you, because the real breakdown is rarely where the founder expects it.

This phase hands you

  • A written map of the operation
  • A gap analysis and a register of risks
  • A build plan, ranked, with the reason for the order

Still comes to you

Most of it, but now it is written down.

Week 3 onward

Build the systems, one at a time

I build inside your business, with your team, starting with the system the map ranked first; it is usually live by day 30. Each one drafts and prepares, and a named person decides and sends. Procedures get written and tested on real work, and we agree in writing who owns what.

This phase hands you

  • The first system live and owned
  • Written procedures for each process it touches
  • A decision-rights page: who owns what, and when it comes to you

Still comes to you

The exceptions each system flags, and the weekly review.

Days 60 to 75

Train the team, then hand it over

I train each owner on the system they run and work beside them until it is routine. We run the odd cases on purpose, so the first one in real life is not a surprise. I hand over when the team runs it, whatever the calendar says.

This phase hands you

  • Training for every owner
  • Recorded walkthroughs your team can rewatch
  • Playbooks for exceptions and escalations

Still comes to you

The calls only you should make, on one list.

Day 76 onward

The operation holds. I step back.

The routine runs on written systems, owned by your team, with clear escalation paths. I stay reachable for a set support window. If you call me back, it should be for the next build, or to stay on as your fractional COO.

This phase hands you

  • An operations manual for leadership
  • A check-in after the handover
  • A clear path back for the next system

Still comes to you

Only the decisions that should be yours. The routine runs without you.

What you keep when I leave.

Every engagement ends with the same three things in your hands.

  • Systems with ownersEach one named for its job, running in the tools you already use, with a person who owns it and limits on what it may do alone.
  • A procedure libraryEvery repeatable process written for the person doing the work, and tested on real work. How I write them.
  • A team that runs itA weekly rhythm, a one-page report and clear escalation paths, so problems surface before they turn into fires.

Questions about pricing, hours or fit?

The FAQ answers the ones founders ask most, and the services page shows what each system does and who owns it.

Phase one is 45 minutes.

You keep the leak map whether or not we go further.

Book the Operations Leak Audit

Complimentary while this season's openings last. I run every audit myself, so I keep the number small.

Wilkins Ndwiga, AI systems and fractional COO. Remote, working US hours.

Book the Operations Leak Audit