How to Build the Business Case Your CFO Will Actually Approve for a Remote Executive Assistant

 

A VP of Operations at a 90-person logistics company tried twice to get budget approval for a remote executive assistant and got rejected both times. The role wasn’t the problem. Her pitch was. She’d framed the request around how much time she personally lost to scheduling, which reads as a personal convenience request to anyone holding the budget. Her third attempt, framed entirely differently, got approved in one meeting.

That pattern shows up constantly in budget requests across departments, not just for executive support roles. HR and operations leaders who study why requests stall at the budget table find a consistent explanation: proposals get rejected far more often because the case wasn’t built in language finance actually uses, not because the underlying need was weak. A CFO evaluates a request against a fairly narrow set of financial categories: cost reduction, productivity gains, risk reduction, and retention improvement, and a pitch built around personal relief from admin work rarely maps cleanly to any of them.

Start with total cost of ownership, not a single salary number. The most common mistake in a first-draft pitch is quoting one figure, “an EA costs $70,000,” without accounting for the comparison that actually matters to a CFO: what the executive’s own time on that same work currently costs the company. A detailed breakdown of what a remote executive assistant actually costs, across salary bands, agency fees, and non-wage overhead, gives the raw numbers a CFO will want to see. Still, the pitch itself needs to pair those numbers against the fully loaded cost of the executive’s own hours currently spent on the same tasks.

Translate time saved into a dollar figure, explicitly. Vague claims like “this will free up my time” don’t survive a budget conversation. A stronger version states the math directly: an executive earning a fully loaded compensation package equivalent to $150 an hour, spending 15 hours a week on tasks a $35-an-hour EA could handle, represents roughly $1,725 a week of misallocated senior labor, or close to $90,000 a year, well above what the EA hire itself would cost. That gap is the actual business case, not the convenience of a cleaner inbox.

Propose a bounded pilot instead of a permanent commitment. CFOs approve pilots far more readily than open-ended new headcount, because a 90-day structure converts an uncertain, ongoing cost into a bounded, low-risk test with a clear evaluation point. Framing the request as “a 90-day trial with defined success metrics, reviewed before renewal” removes most of the risk objection that kills first-draft pitches outright.

Attach a risk-reduction argument, not just a productivity one. Beyond time savings, an experienced EA reduces the risk of missed deadlines, scheduling errors that damage external relationships, and the operational fragility of a single executive being the only person who knows their own calendar logic. CFOs weigh risk reduction as its own category, separate from productivity, and a pitch that addresses both moves faster through approval than one that only covers time saved.

Bring comparative numbers, not isolated ones. A request that shows only the EA’s cost invites scrutiny. A request that shows the EA’s cost next to the fully loaded cost of the executive’s current time allocation, next to the cost of a bad hire if the role goes unfilled and gets patched together informally, gives the CFO a comparison to evaluate rather than an isolated expense to approve or deny in a vacuum.

The VP who got rejected twice made exactly this adjustment on her third attempt. She replaced “I need help with my calendar” with a one-page comparison: her own fully loaded hourly cost against the proposed EA’s rate, the estimated hours she’d reclaim weekly, and a 90-day pilot structure with a defined checkpoint. The pitch didn’t change what she was asking for. It changed the language the request was made in, and that alone was the difference between two rejections and one approval.