"Fractional chief of staff" sounds like a contradiction — how does the CEO's right hand work fifteen hours a week? The confusion comes from picturing the CoS as a presence (in every meeting, always available) instead of what the role actually is: an operating system. Systems don't need forty hours. They need design, rhythm, and relentless follow-through. Here's what the engagement actually looks like from inside.
The weekly shape
A representative 15-hour week across my fractional CoS engagements:
- Monday (3h): Leadership meeting — agenda built from the decision log and tracker, not from whoever shouted last. I run the capture: every decision logged with context, every action named to an owner with a date.
- Tuesday (2h): Follow-through sweep. The unglamorous core of the job: chasing the seven commitments made Monday before they quietly die. This is where companies leak momentum, and where the role pays for itself.
- Wednesday (4h): The strategic initiative — the one or two cross-functional projects I own end-to-end this quarter: a market entry workstream, a partnership launch, a systems migration. Stakeholder calls, status discipline, blockers escalated with options attached.
- Thursday (3h): Board and investor operations. Update drafted from real metrics, board pack assembled days ahead (never the night before), intro requests triaged.
- Friday (3h): The CEO brief: what moved, what's blocked, what needs your decision — with my recommendation attached. Plus the OKR pulse-check that keeps quarterly goals from dying in week three.
The artifacts (how you audit one)
A real chief of staff — fractional or not — leaves paper. Four artifacts you should be able to demand from anyone in this role within two weeks of starting:
- The decision log: every significant decision, with context and owner. Kills re-litigation.
- The initiative tracker: every cross-functional project, status current, blockers visible.
- The leadership cadence doc: meeting rhythm, agenda standards, capture rules.
- The decision-rights doc: what the CoS decides, drafts, and escalates — agreed in writing in week one.
If you're interviewing fractional CoS candidates, ask to see redacted versions of these from past engagements. No artifacts, no operating system — just an expensive meeting attendee.
What a fractional CoS deliberately does not do
Boundaries make the fractional model work. Out of scope at 10–25 hours: managing your calendar and inbox (that's EA scope — pair them if you need both), people-managing your executives, attending every meeting as a silent shadow, and being your therapist. The fractional CoS optimises for outcomes per hour, which means saying no to presence-for-presence's-sake.
When fractional beats full-time (and when it doesn't)
Fractional wins when the company is 15–100 people, the strategic load is real but under ~25 hours a week, and the budget gap between "nothing" and "$200K+ executive" is exactly where the chaos lives. It also wins for defined pushes: a fundraise, a market entry, a 6–9 month transformation. Full-time wins when the CEO's office is genuinely a 40-hour coordination surface — usually past 100+ people, multiple geographies, heavy board cadence. The graceful path: start fractional, scale up if the load proves it, and let the documented handoff protect you either way.
The economics are covered in depth on the fractional chief of staff page; the short version is that US rates run $8–20K/month and hiring the same discipline from a senior Nairobi-based operator comes in well under that while covering EU and US East hours live.
The first 30 days, concretely
Weeks 1–2: audit the current rhythm, install the four artifacts, agree decision rights. Weeks 3–4: the cadence runs on schedule, the first strategic initiative has visible motion, and the CEO gets the Friday brief that replaces ten status conversations. If that's the operating system your company is missing, book the free 30-minute call and we'll scope it against your actual quarter.