7 min read
Your first operations hire: EA, ops manager, or COO?
The title matters less than the gap you are filling. Name the gap first, then the role.
At some point the work outgrows the founder, and the instinct is to hire someone to run operations. It is the right instinct and the wrong place to start. Founders reach for a title — an EA, an ops manager, a COO — before they have named the gap the hire is meant to fill. The title matters far less than the gap.
Name the gap first
There are three different problems founders lump together as “operations,” and each points to a different hire:
- Your time is eaten by admin. Scheduling, inbox, travel, follow-ups, the logistics of your day. The fastest relief here is an executive assistant, and it is often underrated — a good one buys back hours within weeks.
- Work drops between people.Projects stall, handoffs get missed, nothing is quite anyone's job. This is a coordination gap, and it is owned by an operations manager who runs the systems and the rhythm.
- You need someone to run the business. Real decisions, full days, accountability for outcomes across the whole operation. That is a COO — and it is the one most often hired too early.
Why too senior, too soon disappoints
A COO is a multiplier on structure that already exists. Drop one into a business that runs entirely out of the founder's head, and they spend their first year reverse-engineering what you know rather than running anything — at a senior salary, with mounting frustration on both sides. If there is no defined operation to run, it is too early for the person whose job is to run it.
The usual right order
For many founders the sequence is an EA to reclaim time, then an operations manager to own coordination as the team grows, then a COO once there is a real operation worth a senior leader. It is not a rule — a particular business might jump a step — but it beats the common mistake of hiring the most expensive title to fix a problem a clearer role would solve sooner. (On the COO question specifically, there is more in When to hire a COO — and what to do first.) Name the gap, then the role, and the hire actually helps.
Questions
Should my first operations hire be an EA, an ops manager, or a COO?
It depends on the gap, not the stage. If your time is lost to scheduling, admin, and inbox, an executive assistant buys it back fastest. If work is dropping between people, an operations manager owns the coordination. If you need someone to run the business day to day and make real decisions, that is a COO — and hiring one before there is a business to run usually disappoints. Name the gap, then the role.
When is it too early to hire a COO?
When there is no defined operation for them to run. A COO is a multiplier on structure that already exists; drop one into an undefined, founder-dependent business and they spend a year reverse-engineering what is in your head, often at a senior salary. Build the basic ownership and rhythm first — sometimes a strong ops manager or EA is the right step, and the COO comes later.
Name the gap first
A three-minute diagnostic that clarifies whether your gap is time, coordination, or ownership — so the next hire fits the problem.
Name the gap first