Role Playbook
SaaS
200-500 employees
Chief of Staff · Operating Cadence Owner
You own the cadence. You don't own the decisions. That's the Chief of Staff OKR trap at 200-500 SaaS.
Decisions made, not doneThe exec meeting "agreed to ship X by Q3" — no owner, no SLA, no follow-up. By August, nobody remembers.
Cadence runs you, not the reverseWeekly exec meeting, monthly board prep, quarterly OKR review. All three slip. You're the only one who notices.
The CEO's pile compounds"Could you look into..." stacks up — CFO, CRO, CTO simultaneously, none of them reporting to you, no SLAs.
Meeting-as-substitute-for-decisionWednesday's exec sync was 90 minutes. Came out with a "let's revisit next week." That's the trap.
An exec misses the decision deadline
→
Your cadence breaks
Two functions stall on a dependency
→
You re-route the meeting
A commit decays in Slack
→
You re-surface it at L10
The job isn't running the meeting. It's making exec-team commits auditable between meetings — not at the next QBR.
THE SCORECARD
Three Chief of Staff OKRs that defend the seat at 200-500 SaaS.
You're not the exec assistant. You're not the project manager for every CEO ask. You're not the hiring coordinator. You also don't only own the meeting calendar — you own exec-cadence design, decision-tracking and follow-through, dependency surfacing, OKR cycle orchestration, board-prep coordination, and special projects on top of that. Three objectives below — picked to cover the full motion, not just one lane. None of them is "make exec meetings better." These are the three that hold.
| Objective | Key Result | Benchmark / Threshold | Target |
|---|
| Make the exec operating cadence reliable enough to ignore O1 · A cadence that runs itself stops being a thing the CoS holds together. The aspiration is invisibility, not effort. |
Weekly exec meeting agenda finalized 24h before; quarterly OKR review cycle completes within 14 days of quarter-end24h because last-minute agendas force ceremonial discussion instead of decision-making; 14d because OKR cycles that drag past 14 days lose connection to the next quarter's planning |
Same-day / 30+ days typical Threshold | 24h / 14d |
| Board prep cycle starts week 7 of the quarter, not week 11Week 7 because materials need 4 weeks of refinement; week-11 starts force stale numbers and last-minute exec scrambling |
Week 10-12 typical Threshold | Week 7 |
| Eliminate decisions that die in conversation O2 · A decision made and not closed is the same as a decision not made. The goal is closure, not capture. |
Every exec-meeting commitment has named owner + SLA within 24h of the meeting24h because verbal commitments without owner-and-SLA decay within 72h; getting the structure on Day 1 is the only sustainable enforcement |
Verbal/no-SLA typical Threshold | 100% |
| Closure rate on quarterly exec commitments ≥ 80% within stated SLA80% because below that the exec team learns commitments aren't binding and decision-discipline collapses; above 95% means the SLA discipline is theatrical |
40-60% typical Threshold | ≥ 80% |
| Stale follow-ups (no movement >30 days) surfaced to owner-of-record by Day 31, not chased by CoSDay 31 because manual chase by CoS scales to ~15 follow-ups; auto-surface to owner scales across the actual exec-team workload |
CoS chases 100% typical Threshold | 100% auto |
| Turn every exec meeting into a decision-making forum O3 · Status updates can be async. Synchronous time is for decisions only. The meeting earns its place by what it produces, not by who attended. |
≥ 75% of exec-meeting agenda items result in a captured decision (or explicit deferral with owner and revisit date)75% because below that the meeting becomes a status-share and the decisions migrate to side conversations; above 90% means agendas are over-scoped to easy decisions |
30-50% typical Threshold | ≥ 75% |
| Decision capture lag (from meeting to written decision in shared doc) ≤ 4 hours4 hours because beyond that the verbal version diverges from the written version and the "what did we decide" debate begins |
2-5 days typical Threshold | ≤ 4 hrs |
Active exec follow-up workload at 200-500 SaaS typically spans 35-60 concurrent items across 5-7 reporting functions (modeled, varies with team size and decision velocity).
How to start in week 1
Don't redesign the meeting structure. Don't propose a new tool. Do these five things:
→ Pull last quarter's exec-meeting notes. Build the closure-rate baseline: how many commitments were made, how many closed within stated SLA, how many just stopped. That's your starting number for O2.
→ Define a 1-line standard for capturing every exec-meeting commitment: What / Who owns / By when / Status. Apply it retroactively to last week's meeting. The format is the discipline.
→ Set the next 4 weekly exec meetings: agenda due Friday EOD, draft circulated Monday morning, finalized Monday EOD. Hold the cadence yourself for 4 weeks, then hand it back to the system.
→ Audit the CEO's "could you look into..." pile. List all 18 items. Force a 30-minute conversation: top 5 active, 8 deferred-to-Q4, 5 dropped explicitly. Nothing in the active queue without an SLA.
→ Start board prep at week 7, not week 11. Send the rough materials request to all execs in week 7 with clear deliverables. Iterate weekly. Materials final by week 11, not started.
Why O2 is the seat-defining objective
O1 is what the CEO watches. O3 is what the exec team feels. O2 is what makes O1 and O3 actually possible. If decision follow-through is at 40%, no cadence will hold and no meeting will feel decisive — the team learns commitments are conversational, and the cadence becomes ceremonial. When O2 is at 80%+, O1 holds and O3 follows naturally because the team starts treating the meeting as a decision-making forum.
What this actually saves you from — in CEO and board language
The dollar leakage is in Section 7 for completeness. The reasons exec teams actually buy this are operating-quality outcomes, not cost-per-decision math:
↓ Stale decisionsFrom "we'll revisit next week" indefinitely → "the breach is on file with the owner."
↓ Re-litigation dragLess exec time spent re-discussing decisions captured 3 weeks ago. The decision sticks.
↓ Board surpriseBoard materials reflect the actual operating state, not a 2-week scramble. Surprises stay out of the room.
↓ CEO confusion"Did we ever do that?" replaced with a closure rate the CoS can quote. CEO knows the operating state without asking.
↑ Decision velocityFrom 50% closure within SLA to 80%+. Exec team makes more decisions, and they actually land.
↑ CoS retention horizonFrom burnout in 4-6 quarters to a sustainable seat. The role stops being heroic and becomes orchestral.
If the conversation with your CEO is "what does this save us from," these six outcomes are the answer. The dollar math is a backup, not the lead.
STRATEGIC BETS
The three bets inside every Chief of Staff OKR stack — and the dozen your team runs without you.
Your exec assistant runs the calendar mechanics. Your communications lead runs the all-hands. Your CEO's EA owns the CEO's personal queue. You don't. Your job is the three bets that hold the operating cadence, make every exec commitment closeable, and turn meetings into decision-making forums instead of status updates.
Strategy 1 — Replace heroic agenda-building with a recurring pre-built cadence
→ O1
1.1
Weekly exec-meeting cadence: agenda due Friday EOD, circulated Monday morning, finalized Monday EOD — owners enforce on the function, CoS owns the system
All execs
1.2
Quarterly OKR cycle: kickoff in week 1 of new quarter, drafts in week 2, sign-off by end of week 3 — non-negotiable
CEO + all execs
1.3
Board-prep cadence: rough deck week 7, exec inputs week 8-10, board chair review week 11, final week 12 — runs every quarter, same dates
CEO + CFO + Board chair
1.4
Annual planning cycle: strategic narrative draft Q4 week 8, exec-team alignment Q4 week 10, board sign-off Q4 week 12 — protects Q1 from "what are we doing this year" surprise
CEO + Board
Strategy 2 — Replace verbal commitments with tracked SLA dependencies
→ O2
2.1
Decision-capture standard: every exec-meeting commitment logged with named owner + SLA + status field within 4h of meeting end
All execs
2.2
Weekly stale-follow-up surface: any commitment without movement >14 days auto-flagged to owner; >30 days flagged to CEO + owner together
Internal
2.3
Quarterly closure-rate review: at quarter-end, stale-and-dropped commitments reviewed by exec team — explicit "drop" decision rather than passive abandonment
CEO + all execs
2.4
CEO special-projects pipeline: max 5 active items, each with explicit SLA and explicit deprioritization criteria — no compounding queue
CEO
Strategy 3 — Move status async; reserve sync time for decisions only
→ O3
3.1
Agenda-design standard: every agenda item flagged as "decision required" or "context only" — meeting time biased toward decision items, status moved to async
All execs
3.2
Pre-read protocol: any agenda item with materials must circulate ≥ 24h before — meetings without pre-reads default to context-only treatment
All execs
3.3
Decision-capture mechanism: explicit "decision recorded" closure at end of each agenda item — written to shared doc within 4h, ambiguous outcomes get a "revisit" with owner and date
Internal
3.4
Quarterly meeting audit: percentage of agenda items resulting in decisions reviewed at quarter-end; below 75% triggers cadence redesign with CEO
CEO
ENFORCEMENT LAYER
Enforcement for Chief of Staff OKRs — the cadence layer above your meetings and Slack.
Notion holds notes. Slack carries verbal decisions. Asana tracks tasks. Each runs in one lane. None enforces whether the cadence ran on time, whether commitments have owners and SLAs, or whether decisions turned into action. That's where ShiftFocus runs — the cadence layer above your stack.
How this works: your team enters the KR values weekly — agenda finalized on time? commitments captured with owner and SLA? stale follow-ups surfaced? ShiftFocus runs the cadence and triggers ON those values. We don't pull from your calendar or Notion. We make the cadences your team already runs become enforceable.
Two triggers define daily pain: Trigger 1 (Missed Cadence) when an exec rhythm skips, and Trigger 6 (Dependency SLA Breach) when a captured commitment goes stale past its SLA.
The two that fire hardest at the Chief of Staff layer
Trigger 1 · Missed Cadence — when an exec rhythm skips its window
⚡ Fires whenWeekly agenda not finalized 24h before meeting, OR quarterly OKR cycle past 14-day target, OR board prep not started by week 7, OR special-projects review skipped 2 weeks running. Threshold
▎ Why this matters
Cadence is the seat. Once rhythms slip, the team learns the cadence is optional — and within 2 quarters the operating system collapses.
▎ Why ShiftFocus catches it
Notion holds notes. Calendar holds slots. Each tool sees one cadence. ShiftFocus runs all the exec-team cadence KRs through one weekly review — agenda, OKR cycle, board prep, special-projects, annual planning. When two slip the same week, you see it before either becomes a pattern.
▎ Example scenario
Tuesday week 4: agenda was built Monday at 9pm (KR slipped). Same week, board-prep KR is also yellow — week 7, deck request not out. Trigger fires with both. Friday's CEO 1:1 starts with "two cadences slipped — recovery plan for both" rather than "I'm a bit behind."
Trigger 6 · Dependency SLA Breach — when an exec commitment goes stale past its SLA
⚡ Fires whenA captured exec commitment — e.g. "CFO delivers Q3 hiring plan by Friday" — misses its SLA by >48h with no owner update. Threshold
▎ Why this matters
Commitments without owner-and-SLA decay in 72 hours. The CoS becomes the chase mechanism for everything. With SLA tracking, the breach attributes to the function — not to you for "you didn't follow up."
▎ Why ShiftFocus catches it
Asana holds tasks but doesn't link them to exec decisions. Slack carries the verbal commitment but nobody re-reads three weeks of threads. ShiftFocus tracks every captured commitment as a KR-level dependency with an SLA. When it breaks, the alert goes to the owner — not the CoS.
▎ Example scenario
Q3 week 5: CRO commits to revised Mid-Market quotas by Friday. Friday: not delivered. Monday: 72h overdue. Trigger fires to CRO + CEO + CoS. Tuesday's exec meeting opens with "Mid-Market quota commitment is breached — let's resolve" — not Slack DMs from you.
The other 4 that also fire on your KRs
Trigger 2 · Velocity Drop
⚡ WhenDecision-capture lag (meeting → written decision) climbs past 4 hours for 2 consecutive weeks across exec meetings.
▎ Example scenario
Week 6 + week 7 lag both at ~12 hours. Decision drift on the rise. Trigger fires — agenda redesign with CEO.
Trigger 4 · KPI Drift
⚡ WhenQuarterly closure-rate KR drops below 80%, OR % of agenda items resulting in decisions drops below 75%.
▎ Example scenario
Q3 closure rate at 71%. Threshold breached. Trigger fires — pattern review with exec team at quarter close.
Trigger 5 · Owner Absence
⚡ WhenAn exec-meeting decision gets captured without a named owner, or with the CoS marked as owner-by-default.
▎ Example scenario
Audit shows 6 commitments this quarter where CoS is owner-by-default. Trigger fires — owner reassignment review with exec team.
Trigger 7 · Projected Miss
⚡ WhenProjected end-of-quarter closure-rate KR < 80% at week 7, with attribution to which functions are driving stale follow-ups.
▎ Example scenario
Week 7 projection: 68% closure. Brief fires to CEO + exec team with breakdown by owner-function.
Why this works alongside your existing exec-team stack
Notion holds docs. Slack carries threads. Asana tracks tasks. Calendar holds slots. Each does its job. ShiftFocus is the cadence layer above them — where exec-cadence KRs run on one weekly review, every captured commitment becomes a tracked SLA dependency, and threshold breaches fire to the CoS before decisions go stale. Keep your stack. Add the cadence layer that makes Chief of Staff predictive instead of reactive.
ESCALATION DESIGN
The Chief of Staff escalation chain — 5 levels, all on a 48-hour clock.
Every trigger feeds into this ladder. The ladder climbs on time, not on judgment. Below is a single exec-commitment SLA breach (CRO committed to revised Mid-Market quotas by Friday, didn't deliver) threaded through all five rungs.
L1
Auto-Nudge — to the committing exec
Friday 5pm: CRO's "Revised Mid-Market quotas" commitment SLA breached. Trigger 6 fires. CRO gets Slack + email: commitment overdue, 48h SLA window, status update required. Initiative flags yellow.
Immediate
L2
Peer Flag — CEO + CoS see the breach
Monday morning: still no update. Tracked dependency now visible in CEO and CoS dashboards. The cadence layer surfaces it without a CoS Slack DM. Peer awareness creates the resolution pressure.
+48h
L3
CEO Review — direct conversation with the CRO
Tuesday: still stuck. CEO directly asks the CRO for status and a delivery commitment. The conversation is between CEO and CRO — CoS stays out of it, owning the consequence-tracking, not the chase.
+48h
L4
Pattern Brief — recurring SLA breaches surface
Week 7 audit: CRO has missed 3 commitment SLAs this quarter; CFO has missed 2. Pattern goes to CEO + exec team — not the individual instances. "Decision follow-through reliability" is now a quarterly operating concern, not a CoS housekeeping task.
Week 7
L5
Intervention — operating-cadence redesign
Quarter-end review. Closure rate at 64% (target 80%). Full exec team in the room. Decision: tighten SLA discipline at the function level, or accept the slippage and re-baseline what an "exec commitment" means at this team's scale.
Quarter-end
What this kills
The Chief of Staff failure mode where you spend Q3 in DMs reminding 6 execs about commitments they made 3 weeks ago, present a clean exec-meeting agenda Monday morning that's already missing 4 follow-ups, and absorb the closure-rate damage at the QBR for decisions that didn't have owners in the first place. Trigger 6 fires the moment a commitment SLA breaches. Same facts, same week, with the chase happening at the function — not at your desk.
EXECUTION INTELLIGENCE
How the 5 ShiftFocus metrics read on your Chief of Staff KRs.
ShiftFocus runs five health metrics on every KR — same five whether the KR is "Weekly agenda finalized 24h before" or "Closure rate ≥ 80%" or "Decision capture lag ≤ 4 hours." You don't need to compute them. The point is reading them. Here's what each one tells you on a Chief of Staff KR.
What this looks like at week 6 of Q3
$40M ARR SaaS, 320 employees. Chief of Staff has three OKRs running. Here's how the metrics read across them, mid-quarter:
What the leakage actually costs
The primary case for a CoS seat investment is operating quality — the six outcomes above. Dollar leakage is a backup framing for the CFO conversation, not the lead. Numbers below are illustrative for a $40M ARR SaaS at 320 employees, 6 execs, fully-loaded exec comp $300K — useful as a sanity check, not as a precise ROI claim.
Decisions made but not done — quarterly closure rate at 50% instead of 80%
23 commitments per quarter × 30% gap (50% vs 80% closure) = ~7 commitments dropped per quarter. Modeled at $120K avg cost per stalled exec-level decision (delayed hire, missed launch window, deferred capital allocation) = ~$840K quarterly.
1−$840K
Exec time absorbed by re-litigating decisions that weren't captured
When decision-capture lag is 2-5 days, exec-team meetings spend ~15% of time re-discussing prior decisions. 6 execs × 4hrs/week × 15% × $300K÷2080 = ~$520K quarterly in time lost to re-litigation.
−$520K
Board surprise — material discovered week 11 that should have surfaced week 7
Late board-prep cycle means surprises land in the room instead of in the prep. Modeled at 1-2 board-level surprises per quarter × $200K of governance friction (special review, follow-up meetings, board-chair time) = ~$300K quarterly.
−$300K
Cadence-collapse cost — exec team treats meetings as ceremonial after 2 quarters of slip
When operating cadence loses credibility, exec attendance drops, decisions move to side conversations, and OKR cycles drift. Modeled at $250K quarterly in lost decision velocity, missed planning windows, and exec-team disengagement compound effect.
−$250K
CoS time absorbed by chasing instead of orchestrating
When follow-ups have no SLA discipline, the CoS spends ~50% of time on chase work instead of cadence design and special projects. CoS fully-loaded comp $200K × 50% × 1.5 leverage multiplier = ~$150K quarterly of strategic capacity not deployed.
−$150K
Quarterly cost band of running a CoS seat without cadence enforcement
$2M – $4M
1 HBR 2019 — "Why We Still Need the Chief of Staff" — modeled cost-per-stalled-decision derived from this and adjacent operating-cadence research; cost values are illustrative.
Cost range reflects modeled variance across $20M–$80M ARR band; upper end assumes compounding of decision drift, board-prep slippage, and cadence collapse in the same quarter.
The case to make to your CEO
Convert "did we ever decide on X?" into "of the 23 May commitments, 19 closed within SLA, 3 are explicit Q4 deferrals, 1 is breached and assigned to the CRO" — before the next QBR. The seat-defining moment isn't dollar leakage. It's the moment your CEO stops asking "where are we on..." because they can see it. Modeled $2M–$4M quarterly leakage is the supporting math; operating reliability is the actual purchase reason.