CoS vs VP Operations: Key Differences Explained
Understanding the boundary between CoS and VP Operations prevents a common and expensive hiring mistake — confusing scope with seniority.
Scope and Accountability
The confusion between CoS and VP Operations typically comes from companies that have outgrown informal role definitions and need clearer boundaries.
| Dimension | CoS | VP Operations |
|---|---|---|
| Scope | Manage the CEO's priorities, schedule, and information flow | Adjacent function with different ownership |
| Reporting line | Reports to CEO or COO | Typically reports to CEO or C-suite peer |
| Team size | Leads the of Staff function | Different functional scope |
| Stage fit | Series A/B | Varies |
The Organisational Boundary
These roles are most often confused at companies in the 50–150 headcount range, when the organisational structure is evolving and roles haven't been precisely defined. The clearest way to draw the boundary is by function ownership: each role should own a set of outcomes that the other role does not, and the accountability should be legible to the whole leadership team. Ambiguous boundaries between these two roles consistently create conflict and inefficiency.
Unclear boundaries between CoS and VP Operations are a structural problem, not a people problem. Resolve the structure, and the people can succeed.
Which Hire Comes First?
The answer depends entirely on where your biggest constraint is. If ceo is overwhelmed is your primary challenge, hire the CoS first. If the adjacent function is the bottleneck, consider which role creates more immediate leverage. For most Series B companies, the correct sequence is defined by the company's growth thesis — build a clear picture of the next 12 months before deciding which role to fill.
Deciding Between A CoS and VP Operations?
20 minutes. Confidential. We help define which role makes sense for your stage — and which one to hire first.
Request a Search Assessment