Everything founders ask about a fractional Chief of Staff

A fractional Chief of Staff is a senior operator embedded part-time (typically 10–30 hours per week) alongside a founder-CEO. They own the operating cadence, cross-functional projects, and follow-through that would otherwise route back through the founder. Unlike a consultant who delivers a report, a fractional Chief of Staff works inside your tools, meetings, and rhythms.

Runs the weekly leadership cadence, converts meetings into owned action items, drives cross-functional projects to completion, prepares board and investor communications, and builds the systems (dashboards, trackers, docs) that keep the company aligned without the founder in every thread.

A consultant diagnoses and recommends. A fractional Chief of Staff implements and stays accountable for the outcome. I sit in your meetings, hold owners to commitments, and leave behind working systems rather than a slide deck.

Yes. Engagements are remote-first and run inside your existing stack — Slack, Notion, Asana, Google Workspace, Linear, or whatever you already use. I do not ask teams to migrate tools to accommodate me.

A COO is a permanent C-suite executive who owns operations as a function, usually right for companies past roughly 50 people with a defined ops org. A Chief of Staff is a force multiplier for the CEO across whatever matters most this quarter. Most early-stage teams need Chief of Staff leverage years before they need a COO.

Yes. Every system I build is scale-ready. When you are ready to hire a full-time COO or Chief of Staff, the operating rhythm, documentation, and playbook are already in place — which reduces hiring risk and shortens ramp.

An Executive Assistant protects the CEO's time: calendar, inbox, travel, scheduling. A Chief of Staff multiplies the CEO's execution: decisions, projects, cadence, and cross-functional follow-through. They are complementary roles, not substitutes — many CEOs eventually have both.

Sometimes. It requires a step up in scope: from managing the calendar to managing the operating cadence, from tracking tasks to owning cross-functional follow-through. The move is real, but it is not automatic.

Go fractional when the need is real but not yet 40 hours a week, when you want senior judgment without a six-figure commitment, or when you want the role proven before you write the job description. Go full-time when operating load is consistently more than 25–30 hours per week or the role runs board and fundraising work indefinitely.

Foundation is right when you need cadence and clarity installed. Momentum fits when projects need an owner who drives them weekly. Command suits fundraise, board, and scaling seasons where the founder needs a true operating partner.

Engagements typically start with a defined initial period (usually 60–90 days) so there is enough runway to install systems and show results, then continue month to month. Scope can scale up or down as the company changes.

Days 1–30: listen — sit in every recurring meeting, interview each leader, and map the current operating rhythm, ending with a written diagnostic. Days 31–60: install the cadence — one weekly leadership sync, one monthly business review, a decision log, an OKR doc, and a weekly founder update. Days 61–90: hand off — charters for the top three responsibilities the founder should no longer own.

By founder time reclaimed, decisions made without escalation, project completion rate, and cadence adherence. A fractional Chief of Staff should return roughly one day per week of founder time by day 60 and clear at least three stalled cross-functional projects by day 90.

I plug in as an operating partner, not a layer of management. Ownership stays with your team; I make ownership explicit, unblock it, and follow through. Nobody loses scope because I joined.

You keep everything: the cadence, dashboards, templates, decision docs, and trackers. The goal is a company that runs the system without me, and a clear brief if you decide to hire the role in-house.

Common triggers: the founder is the bottleneck for most decisions, the team has grown past roughly 10–15 people, projects stall between meetings, or a fundraise, board buildout, or new market is adding operational load faster than the team can absorb.

Founder-led companies and small leadership teams — startups, professional services firms, and mission-driven organizations — where one or two people carry most of the operational weight.

Often, yes — early teams usually need focus more than cadence. If most of your friction is founder time and decision routing rather than headcount coordination, a short Foundation engagement may still help. I'll say so honestly on the consult if the timing is wrong.

A 30-minute consultation: what's breaking, where your time goes, and what the next two quarters demand. You leave with a point of view on the right scope, whether or not you work with me.