How Many Hours Should You Hire a Virtual Assistant For?

There is no universal number of Virtual Assistant hours

The right weekly commitment depends on the work, not the title. One business may need eight flexible hours for reporting and list cleanup. Another may need daily customer coverage, order follow-up, inbox ownership, and calls. Both are Virtual Assistant work, but their capacity needs are different.

Avoid choosing full-time because it feels simpler or choosing five hours because it is the cheapest test. Estimate the recurring queue, then add communication, exceptions, documentation, and quality control. The goal is reliable capacity without paying for filler tasks.

Calculate the base workload

List each recurring task, how often it happens in a normal week, and its average handling time. Use a recent sample instead of memory. If 80 customer messages average six minutes, base handling time is eight hours. Repeat the calculation for every stable responsibility.

Separate recurring work from projects. A one-time CRM cleanup can justify temporary hours but is not permanent demand. For irregular work, use a four-week average and record the high-volume weeks so the plan does not fit only the quietest period.

1. Count weekly volume for every recurring task.
2. Sample average handling time using normal and difficult cases.
3. Multiply volume by handling time for base production hours.
4. Add meetings, reporting, documentation, and required communication.
5. Keep one-time projects separate from the weekly commitment.

Add a capacity buffer for variation and exceptions

A schedule built at 100 percent utilization fails when a task takes longer, a record is incomplete, or a correction is needed. Add a capacity buffer based on variability. Predictable data work may need less buffer than customer support, scheduling, or exception-heavy workflows.

The buffer protects quality and leaves room for documentation and improvement. If it is consumed every week, the base estimate is too low and the role should be resized.

• Test the plan against recent high-volume weeks.
• Include follow-up time when work depends on customers or teammates.
• Allow time for quality checks and maintaining the source of truth.
• Review actual hours after two to four weeks.

Account for live coverage separately

Live coverage changes the calculation. A business may have twelve hours of productive task volume but need someone available for a four-hour response window on five days. Decide whether you are buying completed work, reserved availability, or both. Do not promise immediate coverage while budgeting only for minutes when a message arrives.

Write down the client timezone, required overlap, response window, and asynchronous work. A concentrated coverage block can sometimes meet the need better than spreading a few hours across an entire day.

• Phone and customer coverage may require reserved time even when volume varies.
• Calendar, inbox, and sales follow-up often need predictable daily touchpoints.
• Research, data cleanup, and reporting may allow flexible blocks.
• Night or split-shift requirements belong in the job description.

When a part-time Virtual Assistant is a good fit

Part-time can work when the queue is contained, priorities are clear, and continuous presence is unnecessary. It also fits a new delegation model with enough recurring work for repetition but not enough for a coherent full-time role.

Part-time does not absorb unlimited urgent requests. Agree on availability blocks, turnaround, weekly cap, and approval for extra hours. Protect the schedule from several managers independently filling it.

• 5 to 10 hours: one narrow queue or contained weekly process.
• 10 to 20 hours: several related workflows with limited live coverage.
• 20 to 30 hours: substantial recurring ownership without full-day availability.
• These are planning examples, not universal definitions.

When a full-time Virtual Assistant can make sense

Full-time can fit when related work requires sustained daily ownership, broad live coverage, or one person maintaining several connected workflows. The role still needs an outcome. Forty hours of unrelated leftovers is not better design than ten hours of unclear work.

Check whether responsibilities form one realistic role. Combining bookkeeping, video editing, outbound sales, executive support, and specialist SEO because each fills a few hours creates a difficult hiring problem. Split specialist work or prioritize the operating bottleneck.

• Daily customer, sales, scheduling, or operational coverage is required.
• Recurring workload fills most of the week after a reasonable buffer.
• Workflows are related enough for one person to build context.
• The manager can provide systems, feedback, and decisions.

Three practical capacity scenarios

A consultant needs inbox triage, calendar updates, invoice follow-up, and a weekly report. Samples total nine production hours plus two hours for communication and exceptions. A 12 to 15 hour starting plan may provide room without inventing a full-time role.

An ecommerce store needs daily order checks, customer replies, returns, product updates, and reporting. Base workload is 24 hours and variation is significant. A 30 to 35 hour plan may fit, followed by a review of actual volume.

A clinic needs phones and inbox coverage throughout the business day plus appointment administration. Even if handling time averages below 40 hours, reserved live coverage and privacy-sensitive handoffs may justify full-time hours or another coverage model.

Review hours after the first month

Track planned and actual hours, completed volume, backlog, response time, rework, and manager involvement. If the assistant is under capacity, consolidate the schedule or add one adjacent workflow with a clear outcome. Do not invent random activity to use the budget.

If the assistant is over capacity, identify whether volume increased, handling time was underestimated, training is incomplete, or the role expanded. Improve the workflow or approve more hours. Do not solve a structural capacity problem with hidden overtime.

1. Compare forecast workload with actual volume and handling time.
2. Check whether live coverage and response expectations were met.
3. Review backlog age, error rate, and manager follow-up.
4. Adjust scope, schedule, process, or weekly cap using evidence.