Chief of Staff

A Chief of Staff (CoS) is a senior executive who works directly with the CEO to extend their reach and multiply executive bandwidth. The role coordinates across the leadership team, drives strategic initiatives that don't fit cleanly into a functional VP's scope, manages the executive's time and priorities, and prepares board materials and executive communications. Adopted from political and military contexts where it is well-established, the CoS role is increasingly common at venture-backed startups around Series B-C as the CEO's bandwidth becomes the limiting factor on company velocity. It is one of the most-misunderstood executive roles because the scope varies enormously by company, and the role works very well at some companies and creates organizational confusion at others.

The typical responsibilities of a Chief of Staff:

Force-multiplier work for the CEO:

• Executive calendar and priority management.
• Preparation for board meetings, investor meetings, customer escalations.
• Drafting executive communications, all-hands materials, written strategic documents.
• Following up on action items from executive meetings.
• Serving as the "second set of eyes" on important documents and decisions.

Strategic initiative leadership:

• Driving cross-functional initiatives that don't fit cleanly under a single VP (e.g., M&A integration, major product launches, organizational redesigns).
• Special projects assigned by the CEO that require dedicated focus.
• Strategic analysis and research that informs executive decisions.

Operating-system coordination:

• Running executive team operating rhythms (weekly meetings, monthly business reviews, quarterly planning).
• Goal-setting frameworks (OKRs, KPIs) at executive level.
• Cross-functional project tracking.

External representation:

• Sometimes representing the CEO in meetings the CEO can't attend.
• Building relationships across the leadership team.
• Acting as an information conduit between teams.

Where Chief of Staff works well:

• High-velocity, complex companies: where the CEO genuinely is the bandwidth bottleneck and a CoS can compress decision timelines.
• CEOs with clear delegation comfort: CEOs who can let go of tasks to a CoS without micromanaging.
• Companies past Series B: where executive bandwidth has become a real constraint and the cost of CoS compensation is justifiable.
• Strong CoS candidates: typically high-potential mid-career executives (often coming from consulting, banking, or chief-of-staff roles elsewhere) who use the role as a development opportunity.

Where Chief of Staff doesn't work:

• Early-stage companies: founders should be doing their own coordination, scheduling, and prep work. A CoS at a 20-person company is premature.
• Unclear scope: CoS roles without clear definition become ambiguous "make work" roles that confuse the org.
• CEO unwilling to delegate: if the CEO can't delegate meaningful work to the CoS, the role doesn't multiply anything.
• Substitute for missing executives: hiring a CoS instead of the COO, CFO, or VP Operations you actually need is a misdirection.

The CoS as career development:

• The role is often a 1-3 year rotation, with the CoS moving into a functional VP role or general-management position afterward.
• CoS roles give high-potential executives broad exposure to the business and direct relationship with the CEO.
• The career path often runs: CoS → VP of a function → SVP or C-level.

The compensation profile:

• Typically $200-350K base depending on stage and company.
• Equity in the range of 0.1-0.5% for non-founder CoS hires (higher for very senior CoS at growth-stage companies).
• Variable comp tied to executive team performance, sometimes including some company-wide metrics.

Ryan's Take

Chief of Staff is a great role at the right company stage and a confusing waste at the wrong one. The pattern that works: Series B-C company, CEO bandwidth is the bottleneck, you bring in a high-potential mid-career executive as CoS for 2-3 years to drive specific initiatives and extend the CEO's reach. Both sides win: the company gets more done; the CoS gets exposure that accelerates their career. The pattern that doesn't work: 20-person seed-stage company hires a CoS to do "operations" because the founders don't want to deal with operations themselves. That's not multiplying anything; that's hiding from work the founders should be doing. The discipline: hire CoS when the CEO is genuinely the bottleneck and the role has clear scope, not because the title sounds important or because someone good is available.

What founders get wrong: Hiring Chief of Staff before the company is large enough to justify it, or with unclear scope that makes the role confusing rather than multiplying. The right discipline: hire CoS when the CEO is genuinely bandwidth-constrained (typically Series B-C), define the scope explicitly (what specific work will the CoS own?), give the CoS real decision authority on their initiatives, and treat the role as a 2-3 year development opportunity that ends with the CoS moving into a functional role.

Related: [CEO] · [COO] · [Founder] · [Hiring Plan] · [Succession Planning]

FAQ

What does a Chief of Staff do? A senior executive who works directly with the CEO to extend their reach, coordinate across the leadership team, drive strategic initiatives that don't fit cleanly into a functional VP's scope, manage executive priorities, prepare board materials, and serve as a force multiplier for executive bandwidth.

When should a startup hire a Chief of Staff? Typically Series B-C when the CEO's bandwidth has become the limiting factor on company velocity. Earlier-stage companies don't usually justify the role; the work a CoS would do is work the founders should still be doing themselves.

What's the career path after Chief of Staff? Typically a 1-3 year rotation. The CoS often moves into a functional VP role or general-management position after the rotation, having gained broad business exposure and a direct relationship with the CEO. Career path often runs: CoS → VP of function → SVP or C-level.