Executive support cost per leader: a 2026 workload benchmark

Key stats

Key takeaways

• Divide the same four-week workload brief across supported leaders, not a generic headcount target.
• Keep direct labor, provider management, tools, backup, and executive review time as separate cost lines.
• Use public statistics to set context, then use response windows, decision rights, and rework to test the operating model.
• Publish a lower capacity estimate when confidential work or irregular peaks make a simple per-leader ratio misleading.

Support model comparison

Why cost per leader is easy to misread

A support budget can look cheap when it counts only the invoice and expensive when it counts every interruption. The right denominator is the work a leader creates: calendar changes, meeting preparation, inbox routing, travel, documents, follow-up, and exceptions. ^[1][2]

The public wage benchmark is useful context. BLS reports a $74,260 median annual wage for executive secretaries and executive administrative assistants in May 2024. That figure does not include benefits, employer taxes, recruiting, equipment, paid time off, manager time, or backup coverage. ^[2][3][1]

Build a four-week workload denominator

Count actual work for four weeks before choosing a model. Separate recurring tasks from exceptions, record the review time each task needs, and mark which requests create a new commitment or require executive judgment. O*NET includes research, information requests, correspondence, records, and scheduling in the occupation's scope, so a calendar-only count will understate the role. ^[1][2]

Then divide the workload by the number of leaders supported, but keep the result as a planning ratio rather than a staffing rule. A board cycle, fundraising period, product launch, or travel-heavy month can make one leader temporarily create much more support work than another. ^[4][5]

Compare the full operating cost

For a direct employee, list wage, employer costs, tools, recruiting, onboarding, manager time, and coverage. For fractional or managed support, list included capacity, setup, overages, minimum term, replacement, backup, and exit terms. An internal pool also needs a routing lead and a rule for who can see sensitive work. ^[2][3][1][6]

A low cost per leader is not a win if the model creates rework or makes executives handle the exceptions. The OECD and FRED productivity series can frame the wider business case, but the team should compare its own preparation time, missed handoffs, response windows, and unresolved approvals before and after a change. ^[7][8][9]

Use demand data without overclaiming

The Census Bureau reported 531,423 seasonally adjusted U.S. business applications in June 2026 and projected 29,741 business formations within four quarters for that cohort. Those data show business activity and potential demand, not a measured need for executive support. A buyer still needs to validate workload, access, and timing inside the company. ^[5]

Global labor and productivity sources can help a distributed team compare context across markets, while Microsoft and McKinsey research provide a reason to test better retrieval, drafting, and routing workflows. None of these sources removes the need for a named human owner, review boundaries, or a backup plan. ^{[10][9][11][12]}

A decision rule for HireExecutiveTeam buyers

Choose the model that can absorb the measured workload at the required response window while keeping judgment and confidential decisions with the accountable leader. Use a direct hire when durable internal context matters and the company can manage the role. Use fractional or managed support when capacity, coverage, or setup speed matters more than employment ownership. ^[2][1][13]

Recalculate cost per leader when the number of executives changes, when board or investor work becomes recurring, or when support starts owning cross-functional follow-up. The useful output is a transparent workload brief with assumptions, not a universal price tag. ^[11][6][4]