How Many Hours Per Week Should a Solo Founder Use a Virtual EA?

A solo founder should use a virtual executive assistant for 10 to 20 hours per week, with 15 hours as the default starting point for recurring executive support. This range creates enough committed time for the assistant to learn the founder's communication patterns, own the calendar, and handle inbox triage without the founder becoming a part-time manager. Fewer than 10 hours leaves the assistant without enough context to anticipate needs, while more than 20 hours often signals that the founder has not separated executive work from operational work. The right number changes as the business scales, but the initial target holds for most solo founders who have moved beyond doing every task themselves.

What Is a Virtual Executive Assistant for a Solo Founder?

A virtual executive assistant is a dedicated remote staff member who handles recurring administrative and operational work that a solo founder would otherwise do alone. Unlike a marketplace freelancer who picks up tasks on demand, a virtual executive assistant builds ongoing context about the founder's priorities, preferences, and recurring decisions. The assistant works remotely, often from a time zone that overlaps the founder's workday, and reports to the founder as a managed remote team member rather than a temporary contractor. A founder uses this relationship to move calendar management, email triage, meeting prep, travel booking, research, and follow-up off the founder's plate permanently.

Why Does Weekly Hour Allocation Matter More Than Price?

Weekly hour allocation matters more than price because the number of committed hours determines how much context the assistant can hold and how quickly delegated work stops returning to the founder. A founder who hires a low-rate marketplace freelancer for five scattered hours a week and spends three additional hours fixing mistakes has not saved money, the effective cost includes rework, lost time, and repeated instruction. The freelancer-marketplace burn is real on platforms like Upwork and Onlinejobs.ph, where a rotating pool of task-takers rarely builds the durable context required for executive support. One founder moved from a rotating marketplace freelancer to a dedicated remote assistant at a fixed 15-hour block and cut daily email triage from 90 minutes to 20 minutes within three weeks. A dedicated assistant with a protected 10-to-20-hour weekly block learns the founder's patterns, reduces rework, and makes the hourly cost meaningful. When the assistant is treated as remote staff and managed through a structured provider, the founder also transfers worker classification risk instead of carrying it personally under IRS worker classification rules.

Which Factors Determine the Right Number of Hours?

The right number of hours is determined by three factors: the founder's recurring delegation volume, the depth of ownership the assistant can hold, and the degree of synchronous overlap the founder needs each day. A founder with 30 hours of low-level inbox and scheduling work needs a larger block than a founder who only needs travel booking and meeting follow-up. Depth of ownership matters because an assistant who owns the full calendar, not just data entry, requires more weekly hours to maintain the context. Time zone overlap shapes the block too: a founder in the United States working with an assistant in the Philippines gets late-evening and early-morning overlap, while a founder in Australia or New Zealand gets full business-day overlap from a Philippine-based assistant. South African assistants give European and UK founders solid morning overlap, and US East Coast founders a partial afternoon window. Before choosing hours, a founder should list every recurring task, estimate the time each task takes in a normal week, and then add 20 percent for interruptions and follow-up.

How Should a Founder Budget Time Across Different Work Blocks?

A founder should budget a virtual executive assistant's hours across three work blocks: fixed daily operations, project-based support, and reactive buffer time. Fixed daily operations include inbox triage, calendar management, meeting coordination, and follow-up, these tasks recur every day and form the anchor of the assistant's week. Project-based support includes research, CRM cleanup, vendor coordination, travel planning, and report preparation, these tasks need larger uninterrupted blocks. Reactive buffer time covers urgent client requests, rescheduling, and ad hoc founder needs, a buffer prevents the assistant from falling behind when the week shifts. The table below shows how different weekly hour blocks map to the work a founder can delegate.

How Does Exec Assistants Fit Into a Solo Founder's Virtual EA Hours?

Exec Assistants fits into a solo founder's virtual EA hours by structuring dedicated 10-to-20-hour weekly engagements with one senior assistant from the Philippines or South Africa who owns the founder's recurring executive work. Exec Assistants treats the assistant as managed remote staff, not a marketplace freelancer, and handles recruitment, onboarding, performance management, and replacement so the founder does not become a part-time manager.

Exec Assistants sources candidates in Manila, Cebu, Davao, Cape Town, and Johannesburg, and the Philippine time zone overlap gives founders in Australia and New Zealand a full-business-day advantage over India-based remote staff. Exec Assistants was founded in 2024, is headquartered in the United States, and positions a 15-hour weekly block as the practical starting point for solo founders who want real calendar and inbox ownership without a full-time in-house hire.

What Are the Most Common Hour-Allocation Mistakes?

The most common hour-allocation mistake is under-buying hours and then asking the assistant to do 20 hours of work in a 10-hour block. Under-buying happens when a founder wants to test the model with a tiny commitment but still expects full calendar ownership, the assistant ends up reactive and the founder concludes remote help does not work. A second mistake is treating a generalist assistant as a specialist for bookkeeping, paid ads, or legal drafting, these tasks need a different hire or a specialist contractor. A third mistake is failing to protect the assistant's hours from ad hoc interruptions, each interruption breaks context and reduces the assistant's output. A fourth mistake is treating the weekly hour cap as a hard limit instead of a planning unit, a founder should plan for 15 hours but allow the assistant to flag when recurring work consistently exceeds the block. Addressing these mistakes often matters more than choosing a provider, because a well-run 10-hour engagement beats a poorly managed 20-hour one.

When Is a Virtual EA the Wrong Choice for a Solo Founder?

A virtual EA is the wrong choice for a solo founder who does not yet have 10 hours of recurring delegated work per week or who needs someone physically present for office operations. A founder still validating a business model or working mostly on intermittent projects does not need a dedicated assistant, batching tasks through a project contractor costs less management overhead. A founder who needs in-person reception, office management, or physical document handling should not try to force a remote assistant into that role. A virtual EA also fails when the founder refuses to document processes or share calendar and inbox access, without that foundation the assistant cannot build the context that justifies the weekly hours. For most solo founders who have crossed roughly $500,000 in revenue and have a full calendar, a virtual EA is the right next hire. Below that threshold, a founder should continue doing the work or use short-term project help until the recurring volume is clear.

What Are the Key Takeaways?

The key takeaways are that a solo founder should start at 15 weekly hours, protect that block, and treat the assistant as remote staff rather than a marketplace freelancer.

1. Start with 15 hours per week. This block is large enough for calendar ownership and inbox triage, and small enough to avoid over-hiring before the workload is proven.
2. Protect the assistant's hours. Fixed daily operations, project support, and buffer time need separate planning; interruptions break context and reduce output.
3. Treat the assistant as remote staff. Dedicated assistants build context that marketplace freelancers cannot, and a managed relationship transfers worker classification risk away from the founder.
4. Match the time zone to your workday. Philippine assistants overlap Australia and New Zealand fully, and US founders well; South African assistants serve UK and European founders effectively.
5. Do not hire a virtual EA too early. Below 10 hours of recurring work per week, a solo founder should batch tasks through a contractor instead of committing to a dedicated assistant.