Português

When to Hire a Chief of Staff: 4 Tests Before You Commit

Key Facts: The Chief of Staff Role

  • First hire typically lands at 150-300 employees or roughly $20M-$50M ARR, when CEO calendar saturation and cross-functional coordination load first exceed what an EA and a leadership team can absorb
  • Median CoS tenure is 2-3 years — the role is often a launchpad into GM, VP of Operations, or COO tracks, not a long-term destination
  • 2026 comp benchmarks: CoS to CEO at mid-market (100-500 employees) typically pays $180K-$260K base plus 15-30% bonus and 0.25-0.75% equity; enterprise CoS can exceed $350K total cash
  • CoS vs. EA: EA is calibrated by tasks (calendar, travel, logistics) and usually pays $80K-$130K; CoS is calibrated by strategic outcomes, operates with CEO credibility, and typically carries a graduate degree or top-tier operator background
  • Roughly 40% of first-time CoS hires are judged unsuccessful by the CEO within 18 months — failure almost always traces to fuzzy 90-day outcomes, not candidate quality

Six months after the hire, the Chief of Staff is doing something important and useful: managing the CEO's calendar, preparing board decks, taking notes in leadership team meetings, and following up on action items. They're good at it. They work hard. They're trusted.

But the CEO still feels stretched. The strategic work that was supposed to get done (the competitive analysis, the key customer relationships, the board preparation) is still getting crammed into evenings and weekends. And when someone asks what leverage they've gotten from the CoS, the CEO has trouble articulating it.

This is one of the most common Chief of Staff hiring outcomes. Not a failed hire. The person is performing. But a misdiagnosed problem. The CEO needed something the CoS role can't provide: either organizational structure that creates execution capacity, or a specific senior leader in a function that was underled. Instead, they got a high-performing coordinator who made their calendar more manageable but didn't change the underlying constraint. Harvard Business Review's research on the Chief of Staff role documents this exact failure mode as the primary driver of Chief of Staff underperformance: the role was designed for coordination before the strategic leverage need was diagnosed.

The Chief of Staff is one of the most misunderstood roles in mid-market companies. Getting the diagnosis right before hiring is far more valuable than optimizing the hire itself. The hiring-chief-of-staff playbook gives you the sourcing and assessment process once you've confirmed the role is right. This article addresses the prior question of whether it is.

What a Chief of Staff Actually Is (and Isn't)

The CoS is not an EA. An executive assistant manages the CEO's time and logistics. A CoS manages the CEO's strategic and cross-functional agenda. The distinction matters because the EA role is calibrated by tasks; the CoS role is calibrated by outcomes. If you need someone to make your calendar work, hire a strong EA. If you need someone to help the organization execute your strategic agenda, the CoS question is relevant.

The CoS is not a VP. A VP owns a function. A CoS operates across functions with the CEO's credibility but in a supporting role. The CoS doesn't own revenue, product, or customer success, but they might coordinate the process by which those functions align on a shared priority. This boundary is often unclear to candidates and causes role drift when not defined explicitly.

The CoS is not a consultant. Consulting engagements produce recommendations. A CoS produces execution. The difference is accountability. A CoS is inside the organization with a stake in the outcome. If you need an outside perspective on a specific problem, hire an advisor. If you need someone to get the problem solved internally, the CoS is the right frame.

What a CoS actually is: an extension of the CEO's operating capacity into areas that require CEO credibility but not CEO presence. When the CEO's bandwidth is the constraint on the speed or quality of something important (board preparation, cross-functional coordination, strategic projects, organizational communication), the CoS is the tool for removing that constraint.

The 4 Tests

The CEO Bandwidth Gap Test

The CEO Bandwidth Gap Test is a diagnostic that asks whether CEO capacity — not organizational skill, structure, or authority — is the binding constraint on important work getting done. The test is positive when the CEO can list specific strategic activities (board prep, competitive thinking, key customer relationships, strategic communication) that are consistently rushed, skipped, or pushed to evenings and weekends despite the CEO possessing the skill to do them well. A failing test usually reveals a missing functional leader or structural problem masquerading as a bandwidth issue.

Test 1: The Bandwidth Test

Question: Are you regularly failing to do important work because of time constraints, not skill constraints?

This test distinguishes two different CEO problems:

Problem A - Time constraint: The CEO knows what needs to be done, has the capability to do it, but can't get to it because of calendar saturation, context-switching, or organizational overhead. There are strategic conversations that aren't happening because the CEO is in operational meetings. There is board preparation that's getting rushed because the CEO can't get to it until the weekend before. There is follow-up on key customer relationships that keeps slipping.

Problem B - Skill constraint: The work isn't getting done because the CEO doesn't have the skill, knowledge, or judgment to do it well. A CEO who doesn't know how to structure a performance review process doesn't need a CoS. They need an HR leader. A CEO who can't analyze a pipeline accurately doesn't need a CoS. They need a Revenue Operations leader.

The CoS addresses Problem A. It doesn't address Problem B. Before concluding you need a CoS, be honest about which problem you actually have. Most CEOs who feel overwhelmed have both, and the CoS can only solve one of them.

The test passes if: you can identify at least 3 specific, high-value activities that aren't getting done at the quality or frequency they should be, and the failure is time, not skill.

Test 2: The Leverage Test

Question: Is there a category of work that requires CEO credibility but not CEO presence?

This is the most precise definition of what a CoS does. CEO credibility means the work requires access to the CEO's information, relationships, or authority to be done effectively. CEO presence means the CEO needs to be physically or substantively in the room for the work to happen.

Some work requires both. Sensitive talent decisions require the CEO's presence and credibility. Major customer escalations that are existential require the CEO's presence. These cannot be delegated.

Some work requires credibility without presence. Board meeting preparation can be driven by someone who has access to the CEO's thinking and is trusted to represent it accurately. Cross-functional project coordination can be run by someone who can convene the VP-level team with the CEO's backing. The monthly investor update can be drafted by someone who knows what the CEO wants to communicate.

The CoS is most valuable when there's a substantial category of work in the "credibility but not presence" bucket. If most of what's falling through the cracks requires the CEO's literal presence, the CoS won't change the math. You're still the constraint.

The test passes if: you can describe 3-5 specific categories of work where a trusted person with CEO access could materially improve quality or speed without the CEO needing to be in every conversation.

Test 3: The Readiness Test

Question: Can you define 3 specific outcomes you want from this role in the first 90 days?

This is the test most CEOs skip and the one that determines whether the CoS hire succeeds or drifts.

The readiness test doesn't ask whether you have a vague idea of what the CoS would do. It asks whether you can articulate specific, measurable outcomes in the first 90 days. Not "I want them to get up to speed." Instead:

  1. "The board deck for Q3 is ready 72 hours before the meeting, structured around the three strategic decisions I need the board to weigh in on, rather than a financial review"
  2. "The Q3 QBR process is redesigned so each function uses a consistent template, I review them asynchronously, and the meeting is focused on top three issues per function"
  3. "The annual strategy offsite for November has a defined agenda, pre-work distributed, and decision log format agreed"

If you can write three outcomes like those, you're ready to hire a CoS. If you struggle to write one specific outcome (find yourself saying things like "they'll help me get more strategic" or "I need more leverage"), you're not ready, and the hire will drift.

The test passes if: you can write three specific, 90-day outcomes in 10 minutes without struggling.

Test 4: The Trust Test

Question: Are you willing to give this person access to your email, calendar, and strategy conversations from Day 1?

This is the hardest test for many CEOs because it requires a different kind of vulnerability than most leadership relationships.

The CoS cannot be effective without access. To prepare the board deck, they need to see the CEO's email threads with board members. To coordinate cross-functional priorities, they need to be in the room when those priorities are set. To draft the investor update, they need to understand what the CEO is worried about and what they're choosing not to say.

CEOs who hire a CoS but keep them at arm's length from sensitive information produce a highly motivated coordinator who can't do the work that actually creates leverage. They know the official version of everything but not the real version. Their work reflects the official version, and the CEO has to keep manually inserting the real context. MIT Sloan Management Review's research on executive trust and delegation identifies information-sharing depth as the primary driver of effective executive delegation. Leaders who grant partial access get partial leverage in return.

The test is not whether you trust a specific candidate yet. You haven't met them yet. The test is whether you're ready to give the role, in principle, that level of access. If you think about it and feel significant hesitation ("I'd want to limit what they see," "there's some things I'd want to keep private"), that hesitation is worth examining before you start the search.

The test passes if: you can honestly say yes, you're willing to share your calendar, email threads, and strategy conversations with this person from their first week.

Interpreting the Tests

All 4 tests pass: The CoS hire is likely right for this moment. Proceed.

3 tests pass, Test 3 fails (readiness): Wait. Spend 2-3 weeks clarifying what you actually want from the role. Write the 90-day outcomes. Then hire.

3 tests pass, Test 4 fails (trust): The hesitation is a signal worth examining. Either you haven't yet developed the management philosophy that makes a CoS effective, or the specific role design needs to be scoped to not require the full access. A more limited scope might be appropriate, but it will produce more limited leverage.

2 or fewer tests pass: The CoS is not the right answer. Diagnose the actual constraint. It's likely a missing functional leader, a structural problem, or a CEO time management issue that requires a different intervention.

Two Illustrations

The CoS Who Created 8 Hours a Week

A 180-person SaaS CEO hired a CoS after passing all four tests. The specific 90-day outcomes were defined: (1) board prep process owned end-to-end, (2) QBR format redesigned and managed, (3) CEO communication to company redesigned to monthly rather than ad hoc.

The CoS took ownership of board prep. The CEO's involvement went from 40 hours of work across two weeks to 6 hours of review and approval. The CoS managed the QBR process, standardized the format, and ran the prep sessions with each functional leader. The CEO attended the QBR itself but didn't manage the logistics.

Eight months in, the CEO's estimate: 8 hours per week recovered, redirected to senior customer relationships and competitive thinking. The CoS work that produced the leverage was visible and specific. Neither the CEO nor the board doubted whether the hire had been worth it.

The CoS Who Became a Project Manager

A 120-person CEO hired a CoS because they "needed more leverage" and "felt stretched." The 90-day outcomes were never clearly defined. The CoS was smart, motivated, and effective, but without a defined agenda, they optimized for what was visibly useful: managing projects, tracking action items, organizing information.

Within three months, the CoS was doing meaningful project management work. But the CEO's strategic bandwidth hadn't changed. The board prep was still being done by the CEO at 11pm on Sundays. The competitive thinking that needed to happen wasn't happening. The customer relationships that needed the CEO's time weren't getting it.

The CEO's reflection: "I hired someone who could do anything but I never told them what to do. So they found the work that was in front of them, and it wasn't the work I needed."

The CEO eventually reset the role with a defined 90-day mandate. The CoS adapted. But 6 months of leverage were lost because the readiness test hadn't been passed before the hire.

The CoS vs. EA vs. VP of Operations Decision Matrix

Dimension Executive Assistant Chief of Staff VP of Operations
Primary function CEO time and logistics CEO strategic leverage Operational efficiency across company
Decision authority None Acts with CEO credibility Owns operational domains
Typical background Operations, coordination Strategy, consulting, high-growth operator Operations, COO track
Access requirement Calendar, travel, logistics Full CEO access Standard executive access
Right when... Calendar is unmanaged Strategic work is falling through cracks Operations needs a dedicated leader

The most common mistake is hiring a CoS when an EA would solve the problem (calendar chaos, logistics overhead), or hiring a CoS when a VP of Operations would solve the problem (operational execution needs an owner, not a coordinator).

The 90-Day CoS Onboarding Plan

Assuming all four tests pass and the hire is made:

Days 1-14 - Context Immersion: The CoS attends every meeting the CEO attends. Not to contribute. To observe. They're building the mental model of how the organization works, what the priorities are, and where the CEO's attention is consumed.

Days 15-30 - Shadowing with Delegation: The CoS begins taking ownership of specific, defined tasks. The CEO reviews their work closely. This is the calibration period: the CEO is learning how the CoS thinks, the CoS is learning how the CEO wants things done.

Days 31-60 - First Independent Work: The CoS takes full ownership of the first defined 90-day outcome. The CEO is available for guidance but not involved in the execution. Results are reviewed at the 60-day mark.

Days 61-90 - Scope Expansion: Based on the first 60 days, the CoS's scope is expanded or calibrated. The three 90-day outcomes are reviewed: which were achieved, which need revision, and what the next 90-day mandate looks like.

How Rework Becomes the CoS's Workbench

A Chief of Staff needs one place where the CEO's strategic agenda lives in operational form — not a collection of docs, Slack threads, and recurring meetings. Rework Work Ops (from $6/user/mo) is built for exactly this coordination layer, which is why many CoS hires adopt it in the first 30 days as their personal operating system for the CEO.

In practice, the CoS uses Work Ops as a single board for the CEO's top priorities — board prep, QBR cycle, strategic projects, investor updates — each with owners across functions, decision logs, and status at a glance. When the CoS convenes the VP team for a cross-functional initiative, the work item lives in Work Ops, not in someone's inbox. Meeting follow-ups stop evaporating because action items are captured against the project, not in meeting notes.

For CEOs running a full CRM and revenue motion alongside, pairing Work Ops with Rework CRM/Sales Ops (from $12/user/mo) gives the CoS visibility into the commercial agenda too — key account status, pipeline health, and customer escalations — without needing separate RevOps tooling. The result is a CoS who walks into every 1:1 with the CEO already knowing what moved, what's stuck, and what decision is needed next.

The Role Multiplies What You Put Into It

A CoS amplifies whatever the CEO brings to the relationship. A CEO who has a clear strategic agenda, defined outcomes, and genuine willingness to share context will get exponential leverage. A CEO who has vague priorities, undefined outcomes, and guarded information-sharing will get competent coordination. Stanford Business School research on executive operating leverage identifies role clarity and defined outcomes as the core conditions for any executive support role to generate measurable impact. Without them, effort substitutes for results. The CEO self-evaluation framework is a useful calibration tool before defining the CoS mandate. Identifying which of the five domains (decision quality, resource allocation, organizational health) is most constrained tells you precisely what leverage you need the CoS to provide.

The Chief of Staff role multiplies the CEO's effectiveness. If you don't know exactly what you want multiplied, the role will find its own definition. And you won't like what it picks.

Frequently Asked Questions

Frequently Asked Questions

At what company size should a CEO hire a Chief of Staff?**

Most first CoS hires land between 150 and 300 employees, or roughly $20M-$50M ARR. Below that, a strong EA plus a disciplined leadership team usually covers the load. The more accurate trigger is not headcount but CEO calendar saturation combined with a backlog of strategic work (board prep, competitive thinking, cross-functional coordination) that only the CEO can move — and can't. Some founder-led companies hire earlier, at 50-80 employees, when the CEO is still operating as de facto COO and needs leverage before bringing in a full executive team.

**

What's the difference between a Chief of Staff and an Executive Assistant?**

An EA is calibrated by tasks — calendar, travel, expense, logistics — and typically costs $80K-$130K. A CoS is calibrated by strategic outcomes, operates with CEO credibility in cross-functional settings, and typically costs $180K-$260K base plus bonus and equity. EAs manage the CEO's time; CoS manage the CEO's agenda. The two roles are complementary, not substitutes — companies that hire a CoS usually still need a strong EA.

**

How long should a Chief of Staff stay in the role?**

Median tenure is 2-3 years. The CoS role is typically a launchpad, not a destination — common next steps include GM of a business unit, VP of Operations, Head of Strategy, or COO. A CoS who stays more than 4 years without a defined next move often signals the role has drifted into permanent coordination rather than strategic leverage. Plan the exit path during the hire, not at year 3.

**

Should the Chief of Staff have direct reports?**

Usually no in the first 12 months. A CoS with direct reports becomes a small department, which dilutes the core value — embedded proximity to the CEO. Once the role matures, some CoS organizations add a business operations analyst or program manager as a single direct report for capacity. Full teams (strategy, internal comms, investor relations rolled under CoS) usually appear only at enterprise scale.

**

What does a first-90-days CoS plan look like?**

Days 1-14 are pure context immersion — attend every CEO meeting, observe only. Days 15-30 shift to shadowing with light delegation on defined tasks. Days 31-60 the CoS takes full ownership of the first pre-agreed 90-day outcome (board deck, QBR redesign, or similar). Days 61-90 scope expands based on calibration, and the next 90-day mandate is written. Without three specific, measurable outcomes defined before Day 1, the plan drifts regardless of the CoS's quality.

**

What's the biggest mistake CEOs make with their first CoS?**

Hiring before writing the 90-day outcomes. Roughly 40% of first-time CoS hires are judged unsuccessful by the CEO within 18 months, and the failure almost always traces to undefined outcomes — not candidate quality. The second most common mistake is keeping the CoS at arm's length from sensitive information, which produces a highly motivated coordinator who can't generate real leverage because they never see the real context.

**

How is the CoS role different from a VP of Operations?**

A VP of Operations owns an operational domain and has a P&L or functional accountability. A CoS operates across functions with CEO credibility but doesn't own any domain — they coordinate, they don't execute. If the constraint is "operations needs a dedicated leader," hire a VP of Ops. If the constraint is "CEO bandwidth across many fronts," hire a CoS. The two are frequently confused because both carry "operations" in their mandate; they are structurally different roles.

Learn More