Blog · June 20, 2026 · ~11 min read
Executive assistant retainer: how to price EA retainer packages and structure ongoing executive support engagements
Executive assistant retainers are structurally different from VA retainers in three ways that matter for pricing: the pay band is higher, the client type is different, and the scope is designed to be proactive and boundary-less — which is both the EA’s core value and the reason scope disputes are more frequent in this category than almost any other.
This post covers the three structural types of EA retainer, what each costs, how to define scope for a role whose job is anticipating needs before being asked, how to price calendar and email ownership as the most scope-intensive EA deliverable, and how to make invisible proactive work legible to principals who only ever see the outcomes.
Part 1: Executive assistant retainer rate ranges by scope
The first question for pricing an EA retainer is not “how many hours per week?” It is “what does the principal actually need the EA to own?” Three structurally different engagement types exist in EA retainer work, and they are priced differently because the depth of access, the nature of the deliverables, and the trust level required are fundamentally different across them.
Fractional EA — part-time executive support: $1,500–$4,000 per month
A fractional EA retainer provides dedicated part-time executive support to a single principal, typically covering reactive inbox management, calendar scheduling, travel coordination, research tasks, and document preparation. The EA is available for a defined set of support hours per week — usually 10–20 hours at a consistent weekly schedule — and operates on a task-driven basis: the principal assigns, the EA executes.
Monthly rates for fractional EA retainers run $1,500–$4,000 per month. A founder or small business owner who needs 10–15 weekly support hours for inbox triaging, scheduling coordination, and routine administrative work: $1,500–$2,500/month. An executive at a growth-stage company who needs 15–20 weekly support hours, requires the EA to interface with internal teams and external stakeholders on their behalf, and values a high degree of independent judgment in scheduling and communications: $2,500–$4,000/month. Effective hourly rates in this range typically run $75–$175/hour, reflecting the trust and access premium that EA work commands over general VA work — the EA is inside the principal’s calendar, email, and often their thinking.
The comparison with VA retainers is instructive. A general virtual assistant at $600–$2,500/month (covered in the virtual assistant retainer post) operates at a task-delegation distance: the principal decides what to do and the VA executes it. A fractional EA operates closer to the principal’s decision layer: the EA is expected to understand the principal’s priorities well enough to make scheduling decisions without asking, draft emails in the principal’s voice without a briefing, and route incoming requests to the right person without escalating every one. That difference in access and judgment is what drives the rate premium.
Full-time equivalent EA: $3,500–$8,000 per month
A full-time equivalent EA retainer is structured to deliver the output of a full-time EA through a fractional or independent arrangement, typically covering 30–40 hours per week at a committed schedule. The EA functions as the principal’s primary administrative infrastructure: owning the inbox, owning the calendar, handling all travel, interfacing with the principal’s full stakeholder network (team, board, investors, clients, vendors), and managing the information flow into and out of the principal’s attention.
Monthly rates for full-time equivalent EA retainers run $3,500–$8,000 per month. A CEO of a 10–50 person company who needs their EA to manage a full external calendar, handle investor and board communications, coordinate travel across multiple time zones, and run the weekly team communication cadence: $3,500–$5,500/month at 30–35 hours/week. A C-suite executive with a high-volume external communication load — frequent media appearances, speaking engagements, board commitments across multiple organizations, complex travel with tight scheduling dependencies — who needs an EA with documented experience at this level of principal complexity: $5,500–$8,000/month at 35–40 hours/week. At the upper end of this range the retainer begins to price against the cost of a full-time salaried EA including benefits; the value proposition shifts to schedule flexibility, no employment overhead, and a senior EA who is selective about principal relationships rather than dependent on the employment relationship.
Specialized EA with project management overlap: $2,500–$7,000 per month
A specialized EA retainer covers EA work plus a defined project management or operations function: the EA both supports the principal’s personal workflow and takes ownership of specific ongoing operational processes — team meeting facilitation, vendor relationship management, hiring coordination, event logistics, or process documentation. The scope is broader than pure executive support but narrower than a fractional COO or chief of staff arrangement.
Monthly rates for specialized EA retainers run $2,500–$7,000 per month depending on the ratio of executive support to project work and the complexity of the project function. A founder who needs part-time EA support plus someone to own the weekly all-hands agenda, coordinate the quarterly planning process, and manage vendor contracts: $2,500–$4,500/month. A CEO who needs a high-hours EA plus someone to run the hiring pipeline, own onboarding for new hires, and project-manage the office relocation: $4,500–$7,000/month. The critical distinction from a fractional chief of staff is scope direction: the specialized EA’s project function is defined by the principal’s operational needs, not by organizational strategy. When the project scope begins to require board-level judgment or P&L ownership, the engagement has crossed into chief of staff territory and should be repriced accordingly.
Part 2: Scope definition for a proactive role — the boundary-less scope problem
Every professional service retainer has a scope definition challenge. Lawyers face the advising-vs-litigating line. Web designers face the maintenance-vs-new-work line. Graphic designers face the format-variation problem. EA retainers face a more fundamental scope challenge than any of them: the EA’s job is to act before being asked.
The value of a great EA is precisely that they don’t wait for instructions. They monitor the principal’s calendar and notice a conflict forming three weeks out before the principal sees it. They manage the inbox and route a vendor inquiry to the right team member before it reaches the principal. They anticipate that the principal’s Tuesday board prep will require four specific documents and have them assembled on Monday without a request. Every one of these actions is in scope — and none of them was explicitly assigned. That’s what makes the EA valuable. It is also what makes the scope of an EA retainer genuinely difficult to define in a contract, because a contract that tries to list what the EA is allowed to do proactively becomes a list of authorized actions rather than a description of a working relationship.
The principal’s workflow as the scope boundary
The most defensible scope boundary for an EA retainer is the principal’s workflow — not a task list, but the domain of activities that directly serve how the principal manages their time, attention, communications, and commitments. Work that lives inside this domain is in scope; work that lives outside it — even if the principal would find it helpful — is out of scope without a specific conversation.
In practice, the principal’s workflow boundary covers five activity domains: (1) calendar and scheduling — everything related to how the principal’s time is allocated and structured, including scheduling, rescheduling, declining meeting invitations, managing buffer and focus time, and proactive conflict identification; (2) inbox and communications — managing the flow of information into and out of the principal’s attention, including inbox triaging, drafting responses in the principal’s voice, routing requests to the right people, and managing follow-up; (3) travel and logistics — research, booking, and coordination for all travel the principal undertakes, including itinerary management, hotel and transport, and pre-departure preparation; (4) information preparation — assembling, summarizing, or organizing information the principal needs to make decisions or participate in meetings, including document prep, briefing notes, meeting agendas, and pre-read packages; (5) stakeholder coordination — managing the principal’s relationships with recurring stakeholders (team members, board members, investors, key clients, service providers) at the scheduling and communication layer, not the strategy layer.
Work outside these five domains — team management, vendor negotiation at the strategy level, financial oversight, content creation, hiring decisions, project ownership with independent deliverables — is outside the EA’s scope even if the principal asks for it in a moment of need. The contract should name this boundary explicitly: “EA scope covers support of the principal’s personal workflow: calendar management, inbox management, travel coordination, information preparation, and stakeholder communication routing on the principal’s behalf. Work outside this domain is addressed as a separate conversation and quoted separately.” For the general framework on scope definition across retainer types, see the retainer scope definition post.
The project-creep pattern in EA retainers
The most common scope dispute in EA retainer relationships is not inbox management overrun or calendar complexity growth. It is the project-creep pattern: the principal has a project that feels administrative — a vendor RFP, an event to plan, a new employee onboarding sequence, a market research task — and routes it to the EA because it feels like “the kind of thing an assistant handles.” The EA takes it because declining feels adversarial and the task doesn’t feel out of scope in the moment. Three months later, the EA is managing three ongoing projects consuming half their retainer hours, the principal considers this baseline EA scope, and the retainer is structurally underpriced by $1,500–$2,500/month.
The resolution is a pre-authorization threshold: any individual task expected to require more than a defined number of hours (commonly 3–5 hours depending on the retainer size) should be flagged to the principal before the EA begins work, with a time estimate and an explicit decision about whether it draws from the monthly hours cap or is quoted as a separate project. The threshold named in the contract — “any task estimated to require more than 4 hours will be flagged for principal approval before proceeding, with a written time estimate” — converts the creep pattern into a visible capacity question. The EA doesn’t refuse the task; they surface the tradeoff and let the principal decide whether to authorize it within the existing cap or treat it as a project.
Part 3: Calendar and email ownership — the most scope-intensive EA deliverable
Most principals who are evaluating an EA retainer have one primary objective in mind, even if they don’t name it explicitly: they want someone to own their calendar and inbox so those surfaces stop consuming their cognitive bandwidth. Calendar and email ownership is the core deliverable of most EA retainer arrangements, and it is also the most scope-intensive, most relationship-dependent, and most difficult to define precisely.
Full calendar ownership vs. scheduling support
There are two meaningfully different levels of calendar engagement in EA retainer work, and they require different rates, different access levels, and different working agreements.
Scheduling support is reactive: the principal identifies that a meeting needs to happen and the EA coordinates the logistics — finding mutual availability, sending the invite, managing reschedule requests. The principal retains control of what gets on the calendar; the EA handles the mechanics. This is appropriate for fractional EA retainers at the lower end of the rate range and requires read access to the principal’s calendar plus the ability to send scheduling emails on their behalf.
Full calendar ownership is proactive: the EA manages what goes on the principal’s calendar, actively protecting focus time, declining or deferring meetings that don’t meet the principal’s stated priority criteria, identifying conflicts before they form, and designing the weekly schedule structure to support how the principal works best. This requires a much deeper understanding of the principal’s working style, priorities, energy patterns, and the relative weight of competing commitments. It also requires write access to the calendar with delegation authority — the EA acts with the principal’s calendar authority, not just their administrative access.
The contract should specify which level the retainer covers. Full calendar ownership commands a rate premium because it requires the EA to exercise ongoing judgment on the principal’s behalf — which meetings to accept, which to decline, how to sequence the week — rather than executing scheduling mechanics. Getting this wrong in the engagement letter creates a common dispute pattern: the principal expected full calendar ownership; the EA priced scheduling support; the principal is frustrated that the EA isn’t protecting their time proactively; the EA is delivering exactly what the rate supports. The contract should name it explicitly: “Calendar management under this retainer includes [full ownership / scheduling support as defined below]. Full calendar ownership requires a dedicated setup session to establish priority criteria, meeting types, recurring commitments, protected focus blocks, and delegation authority parameters before the first calendar decisions are made.”
Inbox management levels and the email voice question
Inbox management has the same two-level structure as calendar management. Inbox triaging is reactive: the EA reviews incoming email, categorizes by urgency and type, flags what requires the principal’s personal attention, and routes or archives the rest. The principal still reads the flagged items and composes responses. This is appropriate for fractional EA arrangements and requires read access and the ability to apply labels or move messages.
Full inbox ownership is proactive: the EA drafts responses to routine messages in the principal’s voice, sends them with the principal’s sign-off or independently under the principal’s email address with delegation authority, and aims to reduce the volume of messages the principal personally reads and composes to a curated minimum. Full inbox ownership requires the EA to write credibly in the principal’s voice — which requires time to develop, calibration on specific communication relationships, and periodic feedback on whether the drafts are hitting the right tone and judgment level.
The email voice calibration period matters for pricing. The first 4–8 weeks of full inbox ownership are higher-effort than steady state because the EA is developing voice, learning which stakeholders require which communication style, and getting feedback on drafts before they go out. Some EAs price this as a higher onboarding monthly fee; others account for it in the overall retainer rate. Either approach is defensible if stated in the engagement letter before the retainer begins. Principals who don’t understand that the calibration period exists experience the first two months as the EA “not being ready yet” rather than as the normal ramp of a deep-access working relationship.
The time-zone and availability question
Executive assistant retainers involve a dimension that most other professional service retainers don’t: time-sensitive decision-making on behalf of the principal during working hours. A scheduling conflict that needs resolution at 9am needs resolution at 9am, not in the EA’s next available working block. A meeting request that requires a same-day response has a decay rate that a content deliverable doesn’t.
The engagement letter should specify: (a) the EA’s committed working hours and time zone; (b) the response time expectation for different request categories (routine scheduling requests within 2 hours during committed hours; urgent calendar or inbox issues within 30 minutes); (c) what out-of-hours response looks like, if anything (available on Slack for true emergencies vs. coverage ends at committed hours vs. monitored but not committed). Principals who expect the EA to be functionally on-call during their entire working day — including evenings and early mornings in different time zones — need either a much higher rate to compensate for the availability premium or a narrower on-call window explicitly agreed in the contract.
Part 4: Client communication — making proactive EA work visible
Executive assistant work has a deeper invisibility problem than almost any other professional service retainer. Most professional service deliverables produce some visible artifact — a strategy memo, a design file, a published article, a reconciled financial statement. EA work at its best produces the absence of problems: the meeting that didn’t conflict, the email that didn’t reach the principal because it was handled at a lower level, the travel itinerary that didn’t require the principal to think about logistics, the board prep that was ready before the principal realized they needed it. The principal’s experience is a frictionless week. The EA’s experience is 30 hours of proactive decision-making that produced that frictionless week.
This invisibility is the driver of the most common EA retainer complaint: “I don’t feel like I’m getting full value.” A principal who had six scheduled conflicts proactively resolved, forty emails triaged out of their inbox, three travel itineraries coordinated, and a board deck assembled without asking cannot easily reconstruct any of that activity at invoice time — because none of it required their attention. The EA succeeded by keeping the principal’s attention elsewhere.
What to log and how to make EA work principal-legible
The EA work log should capture proactive work in the categories where it occurred so the principal can see the distribution of hours across the domains that filled the retainer. Four categories cover most EA work:
Calendar management. “Weekly calendar review: identified scheduling conflict between investor call (Tue 2pm) and product review (Tue 2:30pm); rescheduled product review to Thursday; confirmed 15-minute buffer between board prep and board call; 1.5h.” The specific conflict identified and resolved makes the calendar work real. A principal who sees “calendar management: 8h” without specifics cannot connect that number to their experience. A principal who reads that their Tuesday scheduling conflict was resolved before they noticed it understands exactly what the EA produced that week.
Inbox and communications. “Inbox triage (Mon–Fri): 127 messages processed; 8 flagged for principal attention; 34 routed to team members with context; 85 archived or handled directly; 4 vendor inquiries responded to in principal’s voice; 3.5h.” Volume metrics matter here because the principal has no way to observe inbox work directly. Knowing that 127 messages were processed and 8 required their attention reframes the EA’s contribution from invisible to quantified. The 34 routed to team members — each requiring judgment about who to route to and what context to include — are hours the principal did not spend reading and deciding where to send email.
Travel and logistics. “NYC trip (June 24–26): researched 3 hotel options against availability and location criteria; booked Marriott Midtown; coordinated 4 ground transport legs; assembled travel folder with confirmation numbers, meeting addresses, emergency contacts, and itinerary; 2.5h.” Travel coordination is the most legible EA deliverable because the principal can count the trip even if they can’t count the coordination hours. Seeing “2.5h” alongside the specific NYC trip they remember taking reframes the retainer: the principal didn’t think about their travel once, and 2.5 hours of work is why.
Information preparation and proactive support. “Board meeting prep (June 18): assembled board deck supporting materials; prepared Q&A briefing based on prior meeting action items; confirmed attendance and technical setup for 8 participants; 3h.” “Weekly stakeholder summary: compiled 5 open action items from prior week’s meetings; drafted follow-up emails for 3; sent 2 on principal’s behalf after morning approval; 1h.” Proactive work that anticipates needs — the board prep assembled before the principal asked for it, the stakeholder follow-ups drafted before the principal realized they were due — is exactly what makes a great EA valuable and exactly what is most invisible. Logging it with the specific deliverable it produced makes the proactive work real and visible rather than absorbed into the general category of “support.”
The mid-cycle hours balance and its effect on principals
Principals who can see their EA retainer hours used and remaining mid-cycle make materially different decisions than principals who don’t. A principal who sees “18 of 30 hours used, 12 remaining, cycle closes June 30” on the 15th of the month can make an informed decision about whether to route the vendor evaluation project to the EA this cycle or hold it for next month. A principal who has no visibility into hours usage until the invoice arrives cannot make that calculation — and often doesn’t realize they asked for project work that consumed 8 hours of the retainer until they receive an invoice that doesn’t match their mental model of what EA work was done.
The practical effect of mid-cycle visibility: principals surface capacity questions explicitly rather than routing additional work silently. “Do we have hours this cycle for you to coordinate the vendor evaluation?” is the question a principal asks when they can see the balance. Without that visibility, they route it, the EA accepts it, the hours are consumed, and the principal is surprised when the month’s invoice reflects more time than they expected. Neither party made a bad decision; they just lacked a shared view of the same information at the right moment.
For EA retainers running against a monthly hours cap, a live hours-remaining URL updated as work is logged gives the principal visibility throughout the cycle. The work log entries that accompany the balance — calendar management, inbox triage, travel, board prep — convert the hours number into specific work the principal can recognize. The result is an invoicing moment where the principal has been watching the work accumulate for four weeks rather than evaluating it cold alongside a bill. For the general framework on making retainer hours legible to clients across all professional service categories, see the retainer billing best practices post.
The setup checklist for an EA retainer
An EA retainer arrangement that avoids the boundary-less scope problem, the project-creep pattern, and the invisible-work complaint has five elements addressed before the first working week begins:
1. Engagement type named and scoped explicitly. The contract names which of the three scope types this retainer represents: fractional EA, full-time equivalent EA, or specialized EA with project management overlap. The type implies a different hours commitment, a different access level, and a different working relationship cadence. Principals who think they are buying a full-time equivalent EA from an EA who priced a fractional retainer will experience the engagement as perpetually under-resourced.
2. Calendar and email ownership level specified. The contract distinguishes scheduling support (reactive mechanics) from full calendar ownership (proactive scheduling decisions on the principal’s behalf) and distinguishes inbox triaging (reactive flagging and routing) from full inbox ownership (drafting and sending in the principal’s voice). Each level has a corresponding access requirement (read vs. delegation authority) and a corresponding rate. The calibration period for full inbox ownership is named explicitly with a timeline.
3. Principal workflow boundary defined with project-creep threshold. The five-domain principal workflow definition (calendar, inbox, travel, information prep, stakeholder coordination) is written into the engagement letter as the scope boundary. The project pre-authorization threshold is stated — “tasks estimated at 4+ hours are flagged for principal approval before proceeding” — so project work requires an explicit capacity decision rather than silent absorption.
4. Availability and response-time expectations stated explicitly. The EA’s committed working hours, time zone, and response-time expectations for different request categories are written into the engagement letter. Out-of-hours coverage (or absence of coverage) is stated directly so the principal knows before the first urgent evening request whether the EA is available.
5. Category-level work log shared throughout the cycle. The principal receives a work log that separates EA work by category — calendar management, inbox and communications, travel, information preparation — with specific entries that name what was done, not just hours totaled. For retainers running against a monthly hours cap, a live hours-remaining URL shared at the beginning of each cycle gives the principal visibility into the balance throughout the month, not just at invoice time.
EA retainer disputes concentrate around two structural failure points: principals who discover mid-engagement that the retainer doesn’t cover the level of calendar and email ownership they assumed it did, and EAs who absorb project work silently until the retainer is structurally underpriced and the working relationship is strained. Both problems have structural solutions: define the ownership level explicitly in the contract, name the project-creep threshold before the first assignment, log work by category with specific entries throughout the month, and share the hours balance actively so the principal can route work with full information rather than routing it into a balance they can’t see.
HourTab is a no-login retainer dashboard URL that shows the principal their hours used, hours remaining, cycle reset date, and a categorized work log — updated from the EA’s time tracker. Executive assistant clients who can see their support hours mid-cycle know whether they have capacity to route additional projects this cycle or need to wait for the next reset — before asking, and without the EA having to manage the conversation manually. Share the link at the start of each cycle; the balance updates itself as work is logged.