When to Hire a Chief of Staff
To all founders, CEOs, C-Suite executives, and VPs: You should hire a Chief of Staff when you have become the routing layer of your own organization: when requests, approvals, and decisions all arrive at you personally and get sorted by you personally, and that has been true for more than one busy quarter.
That is the short answer. The longer one matters more, because the role fails often, and it usually fails for reasons that were visible before anyone was hired.
I hold the job of Chief of Staff. Almost everything written on this question comes from recruiting firms who are paid when you hire someone, so what follows includes the parts they have no incentive to tell you.
Five reasons people hire one and regret it
Start here, because most bad Chief of Staff hires are traceable to one of these.
Because you are busy. Every senior leader is busy. Busy is the baseline condition of the job, not a signal. The question is not whether your week is full. It is whether your week is full of things that require you specifically.
Because a peer hired one. The role is highly dependent on the individual relationship and on what the principal is worst at. Watching it work for someone else tells you very little about whether it will work for you.
As a promotion for a high performer. This is the most common failure I see. The role is not a reward and it is not a title upgrade. It requires a specific and unusual temperament: comfort with invisible work, no line authority, and constant proximity to someone else's decisions. Excellent operators frequently hate it.
Because projects are slipping. That is a program manager, and program management is a real profession with its own craft. Calling it a Chief of Staff role because the title sounds more senior produces a confused hire and an unhappy person.
Because you want help "with stuff." A role with no written scope will fail regardless of who fills it. Ambiguity in the job description becomes ambiguity in the organisation, and the person ends up doing whatever was loudest that week.
Four signals that mean yes
These are the questions I would actually ask, and they are diagnostic rather than aspirational.
1. Are you the router?
Do requests, approvals, escalations, introductions, and questions arrive at you personally and get sorted by you personally?
The tell is not volume. It is that no rule exists for what should reach you. If everything that could reach you does reach you, the sorting function does not exist, and you are performing it manually on top of your actual job.
2. Do decisions sit and stall?
Not because they are hard. Because they are queued behind you.
Ask your direct reports whether they feel overloaded or blocked. Overloaded means they have too much. Blocked means they are waiting. If the answer is consistently blocked while you have reasonable time on your calendar, the constraint is in your decision layer, and that is the layer a Chief of Staff operates in.
3. Do you know what your team is waiting on right now?
If the honest answer is no, then nobody is holding that list. Nobody starts holding it spontaneously. Someone has to be responsible for knowing what is stuck, for how long, and on what.
4. Would things stop if you disappeared for a week?
Not a planned holiday. Planned absence hides this, because everyone prepares for it and you pre-approve what you know is coming. The unplanned version is the real test.
Write the list of what would actually stop. For most senior leaders it runs four to ten items, and about half are surprises.
The duration test
If three of those four land, you have the problem. One more question decides whether to act on it.
Has this been true for a full quarter, or is it one bad season?
Every executive has a six week stretch that looks exactly like the description above. The role is a response to a structural condition, not to a hard month.
What it costs, and at what scale it makes sense
A full time Chief of Staff typically runs somewhere around $175,000 to $225,000 in base salary in the United States, and roughly $225,000 to $300,000 fully loaded once you add benefits, equity, and overhead. Numbers vary by market and by seniority, and the range is wide because the role is.
That price forces a scale question, and here is the honest version of it.
The role starts to make financial sense when the decision volume flowing through one executive is large enough to occupy a dedicated person, and when that executive's time is genuinely scarce at the margin.
In practice that tends to mean a CEO of a company past roughly a hundred people, or a functional executive with a couple of hundred people in their organization. Below that, the volume usually does not justify the cost, and you end up with an expensive person looking for work to do, which is its own failure mode.
The uncomfortable middle is the large group of leaders who clearly have the problem and clearly cannot justify the headcount. That group is much bigger than the group who can, and it is where most of the pain sits.
When should a startup hire a Chief of Staff?
The hundred-person guideline above is a reasonable default and a bad fit for startups, because it measures the wrong thing.
For a founder, the threshold is span rather than headcount.
Count the number of functions reporting directly to you. Not people. Functions. Sales, product, engineering, marketing, finance, operations, people. A founder with three is running a company. A founder with seven is personally acting as the integration layer between seven things, and no amount of working weekends fixes that.
A forty-person company where the founder holds six functions has the problem. A hundred and fifty person company with a real leadership team frequently does not.
The rough stage guide
| Stage | Usually |
|---|---|
| Under 20 people | Almost never. You need an assistant or nothing. |
| 20 to 50 | Rarely, unless your span is unusual or growth is very fast. |
| 50 to 150 | The common window, particularly after a raise. |
| 150 and up | Often yes, and by now you likely need functional leaders too. |
Scroll the table sideways to see both columns.
Orientation rather than a rule. The number of functions reporting directly to you is a more reliable signal than headcount.
Treat that as orientation rather than as a rule. The span question is more reliable than any headcount number.
The trigger nobody warns you about
Raising a round is the most common moment a founder crosses this line, and it catches people out because the company has not changed size yet.
What changed is the number of things demanding your attention. A board that needs managing. Investors who want updates. A hiring plan that just tripled. Reporting expectations that did not previously exist. None of that replaces the day job, and all of it arrives in the same month.
If you raised in the last two quarters and your week has become unrecognisable while your headcount has barely moved, that is the pattern, and it is worth naming as a structural change rather than a busy stretch.
What the role actually looks like at a startup
It is not the same job it is at a large company, and the confusion here produces most of the bad hires.
The integrator. You hold too many functions and nobody is connecting them. This person runs the operating rhythm, owns the planning cycle, and makes sure the seven things you are holding actually talk to each other. Closest to the classic version of the role.
The bridge hire. You need a function run, you cannot yet justify or attract a senior leader for it, and a strong generalist holds it for two or three quarters until you can. Legitimate and common, and it works only if everyone including the person understands it is temporary.
The founder's second brain. You are the bottleneck on decisions and information, and this person filters, tracks, and closes loops. This is the version most likely to be mislabeled, because from outside it looks like an assistant and it is not.
Decide which of the three you are hiring before you write the job description. Roles that try to be all three end up being none of them.
The startup-specific trap
Here is the failure mode I would most want a founder to avoid.
Hiring a Chief of Staff instead of the functional leader you actually need.
It is tempting because a generalist is easier to find, cheaper, less risky, and does not require admitting that sales or engineering needs its own leader. So the Chief of Staff absorbs the gap, performs competently, and the underlying hire gets postponed another two quarters.
The tell is simple. If most of what you want this person to take over belongs to one function, you do not have a Chief of Staff problem. You have a missing VP, and a generalist is an expensive way to delay that conversation.
The bridge hire above is the honest version of this, and the difference is entirely whether you have named it as temporary out loud.
On cost at startup stage
The full-time figures above assume a mature market rate. At startup stage the mix usually shifts: lower cash, meaningful equity, and a candidate who is taking the role partly for the vantage point it offers.
That makes the role more affordable than the numbers suggest, and it introduces a different risk. Someone who joined for the view will leave once they have it, which is normal and worth planning for. Assume eighteen to twenty four months and treat anything longer as a bonus.
What you might actually need instead
Four alternatives, each cheaper, and each correct in specific circumstances.
An excellent executive assistant. If the problem is genuinely logistics, coordination, scheduling, and travel, this is your answer and it is a fraction of the cost. A great EA is transformative and much easier to hire. Many executives who hire a Chief of Staff needed this instead. The test is whether your problem is execution of what has been decided, or the deciding itself.
Written decision rights. If the problem is that everything escalates to you, the cause is usually that nobody has written down what does not need to. Ambiguity about ownership always pushes decisions upward, because asking carries no personal risk and deciding does. Writing four or five lines of criteria solves a surprising amount of this and costs an hour.
Intake design. If the problem is volume rather than authority, the fix is upstream. Count how many separate channels people use to reach you, then reduce them. Most senior leaders have nine to twelve and guess four. Nobody chose nine. Nine is what happens when nobody chooses.
A program manager. If what is actually failing is cross functional delivery, hire for that and call it that.
What has to be true for the role to work
If you have decided you need one, five conditions determine whether it succeeds.
You genuinely delegate judgment, not just tasks. A Chief of Staff who has to check every call with you is a bottleneck with a salary. If you cannot let go of the decisions you claim to have delegated, the role cannot function.
The scope is written down. What they own, what they influence, what they do not touch. Verbally agreed scope becomes contested scope within a month. I have created a Chief of Staff job description template for you to use that helps with this.
The organization understands they are not a shadow executive. The role has no line authority and works entirely on borrowed authority. The moment a Chief of Staff starts issuing instructions in their own name, the organization stops trusting the role.
You are willing to be told things you do not want to hear. Much of the value is in someone with proximity and no political stake telling you plainly that a plan is not working. If that will not land well, you are hiring an expensive coordinator.
You will back their calls publicly. They will make a decision on your behalf and get one partly wrong. What you do in that moment determines whether the role survives. Correct privately, support publicly, or the borrowed authority evaporates and everything routes back to you.
If you need the function but not the headcount
This is where most people reading this actually land.
You have three of the four signals. It has been true for two quarters. And you cannot justify a quarter of a million dollars for a role your board will ask you to explain.
Fractional Chief of Staff work exists for exactly this gap. The function without the headcount: someone running the intake, holding the decision list, tracking what is stuck, and building the rules that let your team filter themselves.
It works well for the operating layer, which is most of the value. It works less well if what you need is someone physically embedded in daily operations, in every room, all week. That version requires a full time person and you should hire one.
The honest starting point for most people is smaller than either option.
Before you hire anyone, find out which part of your operating system is actually failing. Four components determine what a senior leader produces, and most executives are wrong about which of theirs is binding. Hiring a person to fix the wrong one is an expensive way to learn that.
The Executive Operating Index scores all four in about five minutes and names the one holding the rest back. It is free, and your score appears before you are asked for anything.
FAQ
When should a company hire a Chief of Staff? When the executive has become the routing layer for requests and decisions, work is visibly waiting on one person, and that has been true for more than a quarter. Usually a CEO past roughly a hundred people, or a functional executive with a couple of hundred in their organization.
How much does a Chief of Staff cost? Roughly $175,000 to $225,000 base in the United States, and about $225,000 to $300,000 fully loaded. Fractional arrangements cost considerably less because you are buying the function rather than the headcount.
Do I need a Chief of Staff or an executive assistant? If your problem is logistics, scheduling, and coordination, you need an excellent EA and it costs far less. If your problem is what reaches you and what decisions clear, that is Chief of Staff territory.
Can a startup have a Chief of Staff? Yes, and many do earlier than the economics justify. Below roughly a hundred people the decision volume usually does not fill the role, and the hire ends up doing project work with an inflated title.
Why do Chief of Staff hires fail? Most often because the scope was never written down, because the principal did not actually delegate judgment, or because the role was created as a reward for a strong performer rather than as a response to a structural problem.
What is a fractional Chief of Staff? The same function delivered part time, for executives who need the operating layer run properly but cannot justify a full time hire. It suits the intake, decision tracking, and systems side well. It suits daily embedded operations less well.
When should a startup hire a Chief of Staff? Measure span rather than headcount. Count the functions reporting directly to you: three is running a company, seven means you are personally the integration layer. Most startups cross the line between 50 and 150 people, and often right after a raise.
Bob Stanke is a Chief of Staff and Executive Advisor. He writes about the operating layer of executive work: what reaches you, where your attention goes, how decisions clear, and what leaves your desk.
