I've written before about the EA-versus-chief-of-staff line, but founders increasingly ask a three-way version of the question, because "operations manager" job posts now promise half of what a CoS does, and CoS posts promise half of what an EA does. Here's the clean way to cut it: don't compare the roles, compare the bottlenecks they remove.

The one-line version of each role

Diagnose by symptom, not title

Your symptoms point to an EA if: you spend 3+ hours a day on coordination; your inbox is a backlog; you prep for meetings in the corridor outside them; personal and company logistics collide weekly. → Executive Assistant or EA to Founders.

Your symptoms point to a Chief of Staff if: leadership meetings produce decisions that evaporate; the same strategic project has been "in progress" for two quarters; departments only synchronise when you personally force it; board prep is a panic. → Chief of Staff, virtual or fractional.

Your symptoms point to an Operations Manager if: customer response times drift and nobody notices for a month; onboarding lives in one veteran's head; you can't answer "what's our SLA compliance?" without a manual archaeology dig; growth keeps breaking processes. → Remote Operations Manager.

The cost logic (and the trap)

In the US, these are three salaries: senior EA $80–120K, CoS $160–250K fully loaded, ops manager $90–140K. The trap founders fall into is buying one cheap generalist to cover all three and getting junior execution on every front. The leverage move at 5–80 people is the opposite: one senior operator, fractional hours, deliberately scoped across the surfaces that are actually bleeding. That's the engagement I run as an operations partner, and hiring it from Nairobi prices the whole blended scope below any one of the three US salaries.

Sequence, if you're hiring in order

  1. First hire: EA scope. Until your time is unblocked, every other hire underperforms: you're the bottleneck reviewing their work.
  2. Second: ops systems. As soon as a team delivers to customers, reliability systems pay compounding returns. This can be a project engagement, not a headcount.
  3. Third: CoS rhythm. When the leadership team is big enough to mis-coordinate (usually 4+ executives), cadence becomes its own job.

Note what that sequence implies: the titles arrive in stages, but the underlying craft (visibility, discipline, documented follow-through) is one skill set. That's why a blended engagement often beats sequential hiring until the company is large enough to split the roles properly.

Decision matrix