Founders ask this one constantly, usually right after a board member or investor has suggested "you need a COO" without defining what that means. The short version: a COO owns a function permanently and reports to the board on it. A chief of staff owns whatever the founder's attention can't currently cover, and the scope changes as the company does.
A COO runs a department. A chief of staff runs the gaps.
A chief operating officer typically owns operations as a standing function: hiring into it, budgeting for it, being accountable to the board for its numbers. It's a permanent seat with a permanent mandate. A chief of staff's mandate is deliberately fluid: this quarter it might be fixing a broken onboarding pipeline, next quarter it might be running point on a fundraise, and the quarter after that it might be building the systems a future COO will eventually inherit.
Cost and commitment aren't close
A COO hire is a senior, permanent executive line item, usually with equity, a multi-year horizon, and a real cost to get wrong. A chief of staff, especially a fractional one, is a lower-commitment way to get senior operating leverage without locking in a full-time executive before you know exactly what that role needs to look like. Companies that hire a COO too early often end up with someone over-qualified for the actual problem and under-used for the first year.
The sequencing that actually works
The pattern that holds up across most of the engagements I've run: chief of staff first, COO later, if ever. A chief of staff spends six to twelve months finding out what actually needs fixing, builds the systems and the decision discipline, and by the time a COO-shaped gap is obvious, you're hiring for a role you understand instead of a title that sounded right in a board meeting. Some companies never need a permanent COO at all; a chief of staff who's built durable systems and then handed them to functional leads can be the whole answer.
Signs you actually need a COO, not a chief of staff
- The operations problem is permanent and large, not a phase you're trying to get through: a standing function with its own budget and headcount that needs a permanent owner.
- The board wants a named executive accountable for operations specifically, not a founder-adjacent role that touches whatever's urgent.
- You already know exactly what the role needs to own, which means you're not paying a senior salary to figure that out.
Signs a chief of staff is the better move right now
- The real problem is the founder's time, not one function. A chief of staff absorbs coordination load across the business, not just operations.
- You're not sure yet what a permanent hire should own. A chief of staff finds that out at a fraction of the cost of guessing wrong on a COO.
- You need someone this quarter, not after a six-month executive search.
Most of my engagements start exactly here: a founder whose week is dominated by things a COO title wouldn't actually fix, because the problem isn't one function, it's coordination across all of them. If that's closer to your situation than "we need to hire a COO," see what a fractional chief of staff engagement actually looks like, or read how this compares to an operations manager as well. Book a free 30-minute call to talk through where your company actually is.