The Engagement

A senior operating seat with an exit date set the day we start.

The Problem I Solve

You have a real leadership gap and more than one problem at once — but no single scoped project covers it. You don't have time to scope every fix before you know where the real gaps are, and you're not ready to hire (or wait six months to recruit) the senior operating leader you actually need — whether that's a Chief of Staff, COO, Head of PMO, Head of Product Operations, Head of Strategy, or VP of Business Operations. At a growth-stage company that might be the whole operating system. At a bigger company it might be one functional seat that's gone unowned too long.

What I Do

I embed for a fixed six-month term, working across whichever Stack layers the engagement requires — whether that's all four for a whole-system gap or deep into one function for a single-seat gap. I use The Strategic Reset, The Systems Diagnostic, and The Build as tools rather than committing to one fixed deliverable upfront. Time spent shrinks month over month by design — building AI-native systems at the Organizational Clarity and Operational Infrastructure layers as I go.

What You Walk Away With

A functioning, AI-native operating system across whichever layers needed it — owned by your team, with a clear exit date set the day we start.

How You'll Feel

The shift — during, and after.

After we start

Steadied.

A senior partner showed up — without the recruiting risk, the severance exposure, or the awkward power dynamics.

After I leave

Stronger.

Your leadership team came out the other side with more capacity, not less. The systems run without me.

How I Show Up

Zero ego. I'm not a threat to anyone's seat.

I'm not here to be the smartest person in the room, build a power base, or take credit for what the team builds. I'm here to give your leadership the bandwidth to do what they were hired to do — to be a fresh pair of senior hands so they can finally exhale. When I leave, the systems run because your team built them. That's the whole point.

How It Unfolds

Scope flexes month to month. The term, the fee, and the taper don't.

Scope is reactive by design — what gets worked on in month 3 depends on what's true in month 3. The shrinking hours per phase aren't a side effect: they're the proof that the systems are taking over. This is what a typical six months looks like.

Month 1

Embed + Orient.
~15–20 hrs / wk
Get into your leadership meetings, your Slack, and the systems across all four Stack layers. Run a fast cross-Stack read to find where the real gaps are — not the loudest complaints, the actual root causes.
Months 1–2

Triage + Roadmapping.
~12–16 hrs / wk
Decide which framework — Reset, Diagnostic, or Build — fits which problem, and in what order. Sequence the work against what's most urgent right now, not what would have been most urgent at kickoff.
Months 2–4

Execute.
~10–15 hrs / wk
Move across the Stack as priorities shift, applying whichever tool the moment calls for. Build AI-native systems at the Org Clarity and Op Infrastructure layers as I go — not as a separate workstream tacked on at the end.
Month 5

Taper.
~6–10 hrs / wk
Start stepping back deliberately as the systems take over. Documentation happens on a rolling basis — not in a frantic final-week sprint — so the handoff is already half done by the time we get to it.
Month 6

Handoff + Exit.
~3–5 hrs total
Confirm ownership, finalize documentation, close out on the date set at kickoff. Your team is already running the operating system; this is the goodbye, not the cliff.

Is This a Fit?

This works best for leaders who need more than a project — and less than a full-time hire.

Works the same whether you're filling a CEO-adjacent seat for the whole company or stepping into a single functional gap — Head of PMO, Head of Product Operations, VP of Business Operations, Head of Strategy — gone unowned too long.

Best fit for you if…

You have a real leadership gap and more than one problem at once
No single scoped engagement (Reset, Diagnostic, or Build) cleanly covers what you need
You'd hire for that seat — Chief of Staff, COO, Head of PMO, Head of Product Operations, Head of Strategy, or VP of Business Operations — if you had time to recruit one
You (CEO/COO) can stay actively involved directing where I focus each month
You want a partner with decision-making authority across functions, not advice into one
You're committed to identifying an internal owner by month 4–5 who inherits the systems

Probably not for you if…

A single scoped engagement covers what you need — Reset, Diagnostic, or Build is the better starting point
You want a permanent operating leader, not a self-eliminating engagement — hire a CoS or COO
You expect to set priorities once at kickoff and not revisit them — The Stand-In is reactive by design and needs ongoing leadership input
You don't have an internal owner who will inherit the work by month 6
You're earlier-stage and one focused engagement would serve you better than a broad one

Common Questions

What leaders usually want to know before they sign on.

Why six months specifically, and why fixed?

Six months is long enough to make real cross-Stack progress and short enough to keep urgency in the room. A fixed term means the exit date is set at kickoff — not renegotiated mid-engagement when momentum slows. That date is what forces both of us to build systems your team owns, not dependencies on me.

How is this different from hiring a fractional COO?

Most fractional engagements flatten to a constant 15–20 hours a week for an open-ended duration and end when one party decides they're done. The Stand-In is structurally tapered — time spent shrinks deliberately month over month as systems take over. The exit date is fixed. You're buying a transition, not an ongoing dependency.

What if priorities shift dramatically mid-engagement?

That's actually the design. Scope is reactive by month — what gets worked on in month 3 depends on what's true in month 3. Our weekly call covers where focus shifted this week, why, and what's next. What's not renegotiable is the term, the fee, and the taper.

What happens if my internal owner doesn't materialize?

We have a checkpoint at month 4 to identify who inherits the work. If that's not clear by month 5, we use the taper phase to do one of three things: help you interview and hire the role, shift handoff to a different existing leader, or simplify the systems so they need less ownership (more automation, leaner structure). What we don't do is extend the engagement to cover for the gap — that's how fractional engagements quietly become permanent.

What does the weekly call cover?

Where the focus shifted this week and why; decisions and blockers that need your attention; what got automated or handed off so far; and next week's priorities. It's the recalibration mechanism that makes a reactive scope actually work — not a status update.