Virtual Executive Assistant vs Chief of Staff: What CEOs Actually Need

Founders ask me this question more than any other: "Do I need a Chief of Staff or just a really good EA?" The honest answer is that the line is fuzzy, the titles get used inconsistently across companies, and the right hire depends on stage and personal operating style — not on what's fashionable in your investor's portfolio.

This piece is the framework I use to figure out which role solves a specific founder's actual problem. It's also why I run engagements as a hybrid more often than as either pure role.

The textbook definitions (and why they don't help)

If you read the standard playbook, the distinction looks clean:

• Executive Assistant: Owns the executive's day. Calendar, inbox, travel, meeting prep, communications. Operates around the executive.
• Chief of Staff: Owns the executive's strategic agenda. OKR cadence, leadership-team rhythm, cross-functional initiatives, special projects. Operates the company through the executive.

Clean on paper. Useless in practice. In actual companies, the work overlaps constantly. The CEO's calendar is also a strategic instrument. The leadership-team meeting prep is also stakeholder coordination. The board pack assembly is also a strategic communications artifact. Real engagements blur.

A better question: what's the bottleneck?

Instead of "which role do I hire," ask: "where in my week is the work piling up that nobody is doing?" Three patterns, three different hires:

Pattern A — coordination overhead is killing your week

Symptoms: 6+ hours a day in calendar Tetris, scheduling, email, follow-ups. Board pack assembled in panic the night before. Stakeholders dropping balls because nobody is tracking commitments.

You need: a senior Executive Assistant. Not a chief of staff. The work is high-volume, judgement-heavy, and operational. Hire someone who treats this as their craft, not as a stepping-stone.

Pattern B — strategic initiatives keep stalling

Symptoms: cross-functional projects with no owner. OKRs set in Q1 are forgotten by Q3. Leadership team meetings happen but nothing changes between them. The new market launch is "in progress" for nine months.

You need: a Chief of Staff. The bottleneck is strategic execution, not coordination. Hire someone with operations or consulting background who can hold cross-functional accountability without title authority.

Pattern C — both, simultaneously, and you've been bandaging it for too long

Symptoms: all of A and B. You have one person trying to do both badly, or two people trying to do them separately and stepping on each other.

You need: a hybrid for 6–12 months while you scale into separate hires. Most founders at 15–80 employees actually need this, even though investors push them toward "hire a Chief of Staff." The hybrid has the budget profile of an EA and the strategic scope of a junior CoS.

Why the hybrid often beats either pure role

At sub-100-person companies, two things are usually true: (1) the strategic work is non-trivial but not yet a full-time CoS role, and (2) the operational work is non-trivial but not yet a full-time EA role plus a separate CoS. Splitting the work into two roles too early creates handoffs and ambiguity that swallow the benefit.

A senior operator working 25–35 hours a week as a hybrid — owning calendar/inbox/comms and running 1–2 cross-functional initiatives at any time — fits this stage cleanly. The cost is roughly that of a senior EA. The output covers what most founders are actually missing.

This is what most of my engagements look like. The services page describes the workstreams; the framing is "what's the bottleneck this quarter," not "which textbook role."

When to hire pure EA vs pure CoS

Pure EA makes sense when:

• Your time-leak is purely coordination, not strategy.
• You already have a strong leadership team that owns cross-functional execution.
• You're at a stage (200+ employees) where the EA and CoS roles have genuinely separated.
• Or: you genuinely have a separate Chief of Staff already, and you need calendar discipline on top of it.

Pure Chief of Staff makes sense when:

• You already have a senior EA running your day.
• You have specific strategic initiatives that need an embedded operator (M&A integration, new market entry, leadership-team scaling).
• Your company is 100+ people and the role can plausibly become VP Operations in 18 months.
• Investors are explicitly asking you to hire one (uncommon, but happens).

Common failure modes

1. Hiring a CoS before you have an EA. The CoS ends up doing calendar work because nobody else is. They become an expensive EA, leave in nine months, and you're back at zero.

2. Hiring an EA expecting them to "grow into" CoS work. Some can. Most can't. They're different skill sets — coordination craft vs. strategic operations. Don't bet on transformation.

3. Hiring two people too early. Splitting EA and CoS at 25 employees creates handoff drag that swallows the benefit. Hybrid one senior person until you genuinely outgrow it.

4. Underspecifying decision rights. Whichever role you hire, write the decision-rights memo in week one. What can they approve on your behalf? What must they escalate? Update as trust grows.

Pricing reality check

For comparison, in 2026:

• Senior remote EA (Kenya, Eastern Europe, LatAm): $3,500–6,500/month full-time.
• Senior remote EA-CoS hybrid (same geographies): $5,500–9,000/month.
• Pure Chief of Staff (in-region, US/UK): $150,000–250,000 base + equity.
• Pure Chief of Staff (remote, Eastern Europe / LatAm): $80,000–140,000 base.

The hybrid is the most cost-efficient option for the majority of sub-100-person companies. Below that, you don't yet have the strategic complexity to justify a CoS. Above it, you usually need both as separate roles.