Executive Assistant Company: 12 Questions to Ask Before You Sign

The real decision: service model, control, and risk, before the logo

Most U.S. buyers shortlist an executive assistant company from a 2025–2026 “best of” list, then discover pricing hidden behind sales calls, vague security claims, and rigid contracts. The smarter move is to decide the service model you’re signing up for, because that choice sets your control, speed to value, and exposure to risk. Once you’re clear on model, the vendor short list gets obvious and your questions get sharper.

This guide is a question set you can take into vendor calls to validate scope, talent quality, security (including SOC 2), pricing mechanics, and continuity. Keep it U.S.-specific: align on time zones and holidays, U.S.-calibrated executive presence, and data practices that meet your company’s standards.

• If you’re new to the role, see What Does an Executive Assistant Do? The Complete 2026 Guide.
• For outcomes thinking and quick wins, skim 15 Tasks Every Executive Should Delegate to an EA Immediately and Inbox Management for Executives: How an EA Takes Control.
• For cost framing, bookmark Executive Assistant Pricing Guide: What You Are Really Paying For and The ROI of an Executive Assistant: A Better Way to Measure Return.

First principles: pick the right executive assistant company model

Executive assistant company is an umbrella term. In the U.S. market, four models dominate. Use this table to match your situation to the model, then bias your questions accordingly.

Examples you’ll encounter in U.S.-facing searches include managed or hybrid firms like BELAY, Prialto, Time etc, Zirtual, Wing Assistant, and AssistPro; subscription staffing like Boldly; and boutique U.S.-based providers like Athena Executive Services (AES). Note there is brand confusion with “Athena”: AES is a U.S.-based boutique separate from Athena (athena.com), which focuses on offshore talent. Also be aware that Double has pivoted away from executive assistant services, always confirm current scope with any brand you evaluate.

Questions about scope and outcomes: contract for results, not chores

Prevent scope creep and shallow task execution by defining outcomes up front. Before you sign, press for specificity.

• 30/60/90 ownership: By Day 30, what will be stabilized (calendar triage, meeting cadence)? By Day 60, what will be proactive (inbox rules, travel playbooks)? By Day 90, what strategic projects will be on rails?
• KPIs by workstream: Calendar (accept/decline logic, double-booking rate, time-block adherence), inbox (SLA to inbox zero or a target unread count, categories/labels), travel (advance booking windows, preferred carriers/hotels, crisis response), projects (SOP creation velocity, task aging).
• What’s included/excluded: After-hours coverage, executive-facing comms (drafting updates to your leadership team), vendor management (IT, travel, facilities), event planning, expense audits, light research. Get examples in writing.
• Decision rights: What can the EA approve or purchase without your review? Dollar thresholds? Which emails can they answer as you?
• Documentation: Who creates SOPs and playbooks? How are they stored and updated? Ask for a sample SOP and a redacted onboarding plan.

If you’re new to setting outcomes, this primer helps you translate priorities into delegation: How to Hire an Executive Assistant Who Actually Frees Up Your Time.

Questions about talent quality and continuity: define “dedicated” and backup, precisely

• Definition of dedicated: Is there one primary EA? How many clients does that EA serve concurrently? What is the guaranteed weekly availability window?
• Bench depth and tenure: Typical tenure on the EA bench? Average client-EA pairing duration? Ask for anonymized ranges, not just anecdotes.
• Vetting: What background checks are performed (identity, employment verification, reference checks)? Any role-relevant testing (calendar scenarios, writing, discretion tests)?
• Executive presence: Will I meet and interview the actual EA before signing? Can I run a paid pilot or trial week?
• Backup coverage: Named backup? What percentage of work are they briefed on? How often do they shadow live meetings?
• Replacement SLAs: Response time if the EA resigns or isn’t a fit (e.g., days to present alternatives; overlap handoff).
• Knowledge capture: Where are SOPs and account maps stored? How do you ensure continuity during PTO and transitions? Request a sample handover checklist.

Questions about pricing and contracts: eliminate surprises before they bill

Pricing varies widely by provider, geography, seniority, and scope. U.S.-based managed or subscription staffing tends to price higher than offshore or marketplace options; nearshore often sits between. Instead of chasing a single “rate,” focus on the mechanics that create surprise invoices.

• Effective hourly rate and inclusions: Is coaching/QA time billed to my hours? Are internal meetings billed? Are meetings with backups billed?
• Minimums and commitments: Monthly hour floors? Do unused hours roll over? For how long? Is there a use-it-or-lose-it clause?
• Overages and surge: What happens if we exceed the plan? Do rates change at higher tiers? Can we pre-authorize a surge block at the same rate?
• Setup/onboarding fees: Are there one-time fees? What do I get for them (onboarding manager, SOP build-out, tool provisioning)?
• Mid-plan changes: Can we upgrade/downgrade mid-cycle? Any penalties or resets? How fast can capacity scale up for a product launch or fundraise?
• Contract length and exits: Month-to-month or term? Notice period to cancel or pause? Any reactivation fees after a pause?
• Buyout/non-solicit: If I want to hire the EA directly, what are the terms and fees? How long is the non-solicit window after cancellation?
• Expense handling: How are travel bookings, software seats, and vendor payments processed and reconciled?

For a deeper framework on cost drivers and hidden fees, see Executive Assistant Pricing Guide: What You Are Really Paying For.

Questions about working model, tools, and process: make the day-to-day effortless

• Time zone alignment: Which U.S. hours are guaranteed live? How many standing meetings per week? What is the default response SLA in working hours and after-hours?
• Tool stack proficiency: G Suite or Microsoft 365 mastery (delegated inbox/calendar), Slack/Teams etiquette, Zoom scheduling, travel tools (Concur, TripActions, Amex GBT), expenses (Expensify, Ramp), CRM (Salesforce, HubSpot), project tools (Asana, Notion).
• SOP creation: Who authors SOPs and keeps them fresh? How quickly after kickoff do we have first drafts? What is the review cadence?
• Documentation discipline: What gets documented weekly (decisions, preferences, vendors)? Is there a shared index of templates and macros?
• Password/access management: Do you require a password manager? Can you work with SSO/SAML? What’s the process for revoking access same-day?
• Meeting cadence: Weekly EA–exec 1:1 and a monthly ops review. Who attends (EA, backup, coach/manager)? Agenda examples?
• Asynchronous routines: Default templates for briefing notes, trip packs, and decision memos. Ask to see real (redacted) samples.

If you’re moving from in-office to distributed support, this primer explains how remote workflows outperform legacy habits: Remote Executive Assistant: How It Works and Why It Often Works Better.

Questions about security and compliance: SOC 2 clarity, data boundaries, incident response

Get an executive assistant quote today.

Part-time or full-time support for calendar, inbox, travel, vendor follow-up, and personal logistics. Tell us what you need and we will scope the right plan.

Request quote

Professionals from top brands trust Aurora

If your EA will live in your inbox, calendar, files, and finance tools, security is not a checkbox. Expect U.S.-standard answers that your IT/security team can review. Be precise about SOC 2: confirm Type I vs. Type II, which systems are in scope (e.g., scheduling platform, knowledge base, ticketing), and the audit period.

• Security certifications: Do you have a current SOC 2 report? Type I or II? Which systems and controls are in-scope? Will you sign a mutual NDA and a data processing addendum?
• Access controls: How is least-privilege enforced? Can you restrict EA access by tool, mailbox, or calendar? How are vendor tool logins stored and rotated?
• Device management: Are EAs on managed devices with disk encryption, EDR, and automatic patching? What’s the lost device response?
• Subcontractors and offshore resources: Do you use subcontractors or offshore/nearshore talent? Where is data processed? How are third parties vetted and monitored?
• PII and financial data: Policies for handling payment methods, IDs, HR data, and health/travel information. Are redaction/anonymization tools used?
• Incident response: How are incidents detected and reported? Client notification SLAs? Post-incident reviews and remediation timelines?
• Client audits: Will you support reasonable security questionnaires and evidence requests?

Questions about AI usage: helpful, or a hidden data leak?

Many providers use AI for drafting, transcription, and triage. That can be an asset, if boundaries are clear. Press for the specifics below and ensure you can opt out or sandbox sensitive data.

• Models and vendors: Which AI models/tools are used (e.g., major LLM providers, meeting assistants)? Are any models trained on client data by default?
• Data retention: Are prompts/outputs retained by the AI vendor? Is training exposure disabled? For how long is data stored?
• Human-in-the-loop: Is there mandatory human review before anything goes to external stakeholders or executives?
• Redaction and masking: Are sensitive fields (payment numbers, addresses, PII) redacted before AI tools process content?
• Client controls: Can we opt out entirely, or restrict to specified tools? Can we segregate AI usage by project or mailbox?
• Auditability: Is AI usage logged and reportable for compliance reviews?

Questions about performance management and reporting: prove ROI quickly

• Time tracking: Do you provide itemized time logs by workstream (calendar, inbox, travel, projects)? Can we see trends over time?
• Outcome reporting: Do you report against agreed KPIs (e.g., double-bookings avoided, turnarounds, booking savings)?
• Quality reviews: Who coaches the EA? How often are QA reviews conducted and by whom? Will you share anonymized benchmarks?
• Escalation paths: If something slips, who do we contact and what is the expected response time?
• Executive satisfaction: Do you run quarterly satisfaction surveys or NPS? What actions follow below-target scores?
• Continuous improvement: How often do we revisit SOPs, automation, and delegation cadence to unlock new leverage?

Questions about availability and coverage: match the reality of your calendar

• Business hours: Exact U.S. time zone coverage, with overlap windows stated in writing.
• After-hours and on-call: What qualifies as after-hours? Is there an on-call addon? How is urgent travel handled at 10 p.m.?
• Holidays: Which holidays are observed (U.S. federal, provider country, both)? What is the coverage plan around long weekends and Q4 crunch?
• Surge capacity: Can you double capacity for a product launch, board prep, or fundraise? With what notice and at what rate?
• PTO coverage: Named backup, warm handoffs, and coverage SLAs during vacations and sick days.
• Travel crisis support: What’s the documented playbook for cancellations, weather, or missed connections? Do you provide 24/7 vendor escalations?

Brand landscape notes: avoid confusion, verify current scope

U.S. SERPs mix managed services, staffing subscriptions, and marketplaces. In your diligence:

• BELAY, Prialto, Time etc, Zirtual, Wing Assistant, and AssistPro often present as managed or hybrid services; Boldly is frequently positioned as premium subscription staffing. Confirm the exact model and backup coverage.
• Athena naming: Distinguish Athena Executive Services (AES), a U.S.-based boutique, from Athena (athena.com), which focuses on offshore talent. Verify which you’re evaluating and where work is performed.
• Model changes happen: Some brands shift focus (e.g., Double pivoted away from EA services). Confirm current offerings, contract terms, and security posture from each provider’s latest materials, not third-party roundups.
• “U.S.-based” can be nuanced: A provider may be U.S.-operated while using nearshore/offshore team members or subcontractors. Ask for specifics on locations, data processing, and who can access your systems.

A concise checklist: questions to ask before you sign

1. 1Model fit: Which model are you (managed, staffing, direct hire support, marketplace), and why is it right for my use case?
2. 2Talent match: Who is my EA? May I interview them and see work samples (redacted)? How many clients do they support?
3. 3Continuity: Who is my named backup, and what is your replacement SLA? Show me your handover checklist.
4. 4Scope and outcomes: What will be owned by Day 30/60/90? Share sample SOPs and KPI dashboards.
5. 5Pricing mechanics: What are the minimums, overage rates, rollover rules, and setup fees? Can I upgrade/downgrade mid-cycle?
6. 6Contract risk: Term length, notice to cancel/pause, non-solicit period, and buyout terms (if I hire directly).
7. 7Working model: U.S. hours covered, meeting cadence, documentation rhythm, and tool proficiency (G Suite/O365, Slack, Zoom, travel/expense tools).
8. 8Security and compliance: SOC 2 status and scope; device management; subcontractor controls; incident response; NDA/data processing terms.
9. 9AI usage: Models used, retention/training exposure, opt-outs, and human-in-the-loop policy.
10. 10Reporting and QA: Time tracking granularity, outcome reporting, QA/coaching, and escalation paths.

How to run a low-risk pilot that proves value in 30 days

Ask for a 30-day pilot with a narrow, high-impact scope and explicit exit ramp. Define three measurable outcomes (e.g., reduce inbox to <50 unread, institute a no-surprise calendar with 2-day lookahead briefs, ship a travel playbook and execute one mid-complexity trip). Require weekly metrics and a written retro by Day 30. If the provider can’t commit to that level of clarity, treat it as a signal.

Red flags that predict disappointment

• Pricing that’s only annual or requires large prepayments without a clear cancellation path.
• “Unlimited tasks” without written SLAs, exclusions, and examples of what’s actually unlimited.
• No named backup or replacement SLA; “someone will step in” is not a plan.
• Vague security answers; no willingness to share SOC 2 scope or sign NDAs/data processing terms.
• Refusal to let you meet the actual EA, or heavy pushback on a paid pilot.
• No written 30/60/90 plan, or KPIs that are purely activity-based (hours logged) rather than outcomes.

Where the value shows up: a simple way to measure ROI

Keep the math simple: quantify time returned to your highest-value work and the risk avoided by having mature process and backup. Track (a) calendar quality (fewer collisions, better focus blocks), (b) inbox responsiveness to key stakeholders, (c) travel friction removed, and (d) projects shipped on time. Put a dollar estimate on those hours and risks to compare against your effective rate. For a structured approach, see The ROI of an Executive Assistant: A Better Way to Measure Return.