A COO runs operations. A Chief of Staff coordinates across teams on borrowed authority. A CPO decides what gets built. A PM manages one team's backlog.
The Operator Seat is the role that makes the everyday calls on what ships, inside the strategy leadership already set, and makes them happen across teams.
In 83 executive job postings at small product companies, only one gave a single role both of those responsibilities.
Every one of these is a real job, and none of them is wrong to hire. The problem is what founders expect the hire to fix.
The Chief of Staff gets the seams: the cross-team problems nobody owns. In the postings I read, 25 of 39 Chief of Staff roles were explicitly handed that work. None of the 39 got the final call. So the calls still go back to the founder, and the Chief of Staff carries messages. A liaison gathers the information and takes it to whoever makes the call. The Operator Seat makes the call.
The CPO gets the opposite half. Seven of 21 CPO postings gave the role the final call on what gets built, more than any other title. Only 2 of 21 also owned the work between product, engineering, sales and operations. The CPO, or the founder, sets what to build. The Operator Seat makes the everyday calls that get it shipped.
The COO in these postings runs the business functions. 7 of 8 carry back-office work like finance, legal and HR, 4 of 8 get some of the cross-team work, and 1 of 8 gets the call on what ships.
The one posting that gave a single role both responsibilities was a CTO at a hardware company who also owned the product roadmap. Reading the list of things that role was meant to own, I'm not sure one person could do all of it.
| Role | What it owns | Final call on what ships? | Owns the work between teams? | Where its authority comes from | What the postings show |
|---|---|---|---|---|---|
| COO | Finance, legal, HR and the operating rhythm | Rarely (1 of 8) | Sometimes (4 of 8) | Owns its own functions | 5 of 8 list finance, legal and HR |
| Chief of Staff | Cross-team problems, special projects, the operating rhythm | No (0 of 39) | Often (25 of 39) | Borrowed from the CEO | 34 of 39 use borrowed or mixed authority; 30 of 39 also carry HR, admin, finance or legal work |
| CPO | What gets built: roadmap and priorities | Sometimes (7 of 21) | Rarely (2 of 21) | Owns product | 21 of 21 own product decisions |
| CTO | Engineering | Rarely (1 of 15) | Rarely (2 of 15) | Owns engineering | 15 of 15 own engineering execution |
| PM | One team's backlog and requirements | No | No | Works inside a plan someone else set | Not in the study |
| Operator Seat | Whether what gets decided actually ships | Yes, inside the strategy the founder set | Yes | Handed over by the founder, on purpose, for a defined set of calls | 1 of 83 postings described it |
A table won't make the call for you. Look at the decisions that are waiting on you right now.
You may already have someone doing that job without the title. They just need to be blessed with it: the title, the authority to make a defined set of calls, and the knowledge to make them well. If any of the three stays with you, the calls drift back up.
A lot of founders who search for a fractional CPO already know what they want to build. What's stuck is getting it to land across engineering, sales and operations without every call routing through them.
A CPO is the right hire when the open question is what to build. When the open question is why decisions don't turn into shipped work, a CPO covers the deciding. Getting those decisions to land across engineering, sales and operations is the other half, and only 2 of 21 CPO postings included it.
One way to tell: list the last three calls that waited on you. If they're product calls, look at a CPO. If they're calls between teams, look at the Operator Seat.
In small product companies, the COO usually runs the business functions: finance, legal, HR and operations. The Chief of Staff works across teams on the CEO's behalf, on borrowed authority. In 111 postings, none of the Chief of Staff roles got the final call on what ships.
No. A COO in a small company mostly runs the back office. The Operator Seat makes the everyday calls on what ships, inside the strategy leadership already set, and makes them happen across teams, so stuck decisions stop landing on the founder's desk.
If what's stuck is deciding what to build, a CPO. If you know what to build and it doesn't land across teams, that's the Operator Seat.
Often, yes. If someone has been doing the job without the title, give them the title, the authority over a defined set of calls, and the context to make those calls well.