A Chief of Staff (CoS) is a force multiplier for a stretched CEO — not an assistant, not a COO, not a strategy analyst.
The Chief of Staff role at a startup exists to extend the CEO's bandwidth on execution, communication, and cross-functional glue work that no other function owns. It is most useful between roughly 40 and 200 employees, when the CEO can no longer personally track every workstream but the org is still too small to justify a full COO or Chief of Operations. The job is deliberately amorphous — its value comes from being deployed against whatever is on fire this quarter. That amorphousness is also why the role fails: without a clear operating rhythm and empowered ownership, a CoS becomes a shadow inbox that slows everyone down.
Does: run the CEO's operating cadence (weekly staff, monthly business review, board prep), own cross-functional initiatives that don't fit one function (e.g., pricing overhaul, org redesign, acquisition integration), draft communications on the CEO's behalf, sit in on the CEO's meetings to capture decisions and follow-ups, run occasional deep-dive analyses when data teams are stretched. Does not: manage the CEO's calendar (that's an EA — different, complementary role), own a P&L or a function (that's a VP), set strategy in isolation (they synthesize; the CEO decides). If the CoS ends up doing EA work, you've hired the wrong person or under-hired the EA.
Trigger signals: CEO regularly working >60 hours and still dropping balls; cross-functional projects stalling because no one owns the seams; board prep consuming 3+ days per cycle; the CEO can't remember what was decided in a meeting from two weeks ago. Anti-signals: CEO wants a CoS because 'other founders have one' (status hire), or to avoid the harder work of promoting a functional leader to COO. First functional VP hires (Sales, Eng, Product) should generally come before CoS — the CoS is most useful once the leadership team exists and needs orchestration.
Two archetypes work: (1) the ex-consultant/banker early-career high performer (2-5 years experience, hungry, will do anything, treats the role as a 2-year MBA-equivalent) or (2) the mid-career operator who has run something before and is deliberately taking a lateral to work with a specific CEO. Avoid: junior 'strategy' hires with no execution reps; senior execs who see CoS as a stepping-stone to CEO of your company (rarely ends well). Comp: for the early-career archetype, $130-180K base + 0.1-0.3% equity in the US. For the operator archetype, $200-280K + 0.3-0.75%. Title inflation is common; resist calling the role VP without VP scope.
Days 1-30: shadow the CEO in every meeting, read every doc, meet every direct report and every VP's direct reports, produce a written map of 'where the CEO's time actually goes' vs. 'where the CEO thinks it goes.' Days 31-60: propose an operating cadence (which meetings, who owns them, what the artifacts are), take ownership of board prep and staff meeting agendas, identify 2-3 cross-functional projects to own. Days 61-90: run the cadence, ship the first cross-functional project end-to-end, produce a 'CEO time audit' showing time reallocated. Success metric at 90 days: the CEO reports 5-10 hours per week of time returned, and at least one stalled initiative is unblocked.
Healthy exits: CoS is promoted to a functional VP role or GM of a business unit (24-36 months typical), or moves to found their own company (network effect for you as an alum). Unhealthy exits: role expands into everything and nothing, CoS burns out; new COO/CFO is hired and the CoS's scope evaporates without a replan; CEO changes and the new CEO doesn't want one. Plan the exit at hire: 'This is a 24-36 month role and here are three next-step paths I'll actively help you toward.' That framing attracts the right candidates and forces you to think about their growth.
Investor directory · Fundraising library · Articles A–Z · Company funding database