You know you need help. The harder question is how much help.

Do you need a few virtual assistant hours each week to keep recurring admin under control? Enough capacity to run several backend workflows? Or are you already describing something much closer to a substantial part-time role?

Choosing a round number first and finding work to fill it afterward gets the decision backwards.

A better approach is to measure the work that can genuinely be handed off, convert it into weekly and monthly capacity, allow room for communication and exceptions, and then choose the support level that fits.

That gives you a number based on your business rather than someone else’s idea of what a “small” or “large” VA package should contain.

Start With the Work, Not the Number of Hours

Before calculating virtual assistant hours, separate work you can realistically hand off from work that should remain with you.

“Marketing” is not useful as a workload entry. Neither is “admin.”

Break the work into specific activities such as:

• triage the inbox each weekday morning;

• update CRM records three times per week;

• research 20 prospects each week;

• upload one approved article to WordPress;

• prepare the Friday project-status report;

• schedule approved social content;

• check outstanding vendor responses;

• clean and validate spreadsheet data.

If you are still deciding which responsibilities are suitable for someone else, start with the Boost VA delegation matrix. It helps separate work that can be delegated from decisions that still need your judgment.

You can also use the virtual assistant task checklist for examples of recurring activities that may belong in your inventory.

The purpose at this stage is not to create the longest possible task list. It is to identify work that is recurring, explainable, and useful enough to justify ongoing capacity.

Turn Each Task Into Weekly Hours

Once you have a realistic task inventory, add three pieces of information to every item:

1. Frequency: How often does it happen?

2. Handling time: Roughly how long does one occurrence take?

3. Timing requirement: Can it be completed in a batch, or does it need attention at a particular time?

The basic calculation is:

Frequency per week × time per occurrence = weekly workload

For example, inbox triage that takes 30 minutes each weekday is:

5 × 30 minutes = 150 minutes = 2.5 hours per week

Do that for every recurring responsibility.

One VA provider, Ellite Assistant, similarly recommends basing starting capacity on actual delegable workload by tracking recurring tasks for one or two weeks rather than selecting an arbitrary number first.

Use a Workload Planning Worksheet

A simple table is enough.

You can copy that structure and replace the example work with your own.

For a blank version:

Track a representative period where possible. A quiet Tuesday should not define a business that becomes hectic at the end of every month.

Equally, do not build the estimate from the worst day you have had all year.

The aim is a normal recurring workload, with unusual peaks handled separately.

Convert the Weekly Workload Into Monthly Capacity

If your support plan is sold monthly, convert the weekly figure before comparing packages.

A useful average is:

Weekly hours × 4.33 = average monthly task hours

The 4.33 figure comes from dividing 52 weeks by 12 months.

Using the example above:

9 hours × 4.33 = approximately 39 hours per month

That gives you the raw workload.

It is not necessarily the final number you should purchase.

Add Room for Communication, Questions, and Exceptions

A VA does more than perform the visible task.

Real working time can also include:

• reading new instructions;

• asking questions;

• reporting progress;

• checking completed work;

• handling exceptions;

• short meetings;

• updating documentation;

• correcting an unexpected problem;

• switching between systems.

Borderless Recruit’s workload guidance suggests adding roughly a 15% to 20% operating buffer after measuring recurring work. Treat that as a planning rule of thumb rather than a universal requirement.

If the example workload is about 39 hours per month, adding a 15% buffer gives:

39 × 1.15 = approximately 45 hours per month

That is much more useful for making a support decision than simply saying, “I think I need around ten hours a week.”

Your own buffer may be smaller or larger depending on how stable the work is.

A mature, documented process with predictable inputs may need relatively little extra room. A new workflow with changing instructions, client dependencies, or frequent exceptions may need more.

Do Not Confuse Task Time With Availability

This is one of the easiest ways to underestimate the support you need.

Suppose an inbox creates only three hours of actual work each week.

If you need someone to check it every weekday morning and again in the afternoon, the requirement is not simply “three hours whenever convenient.”

You also have a coverage requirement.

The same problem appears with:

• customer-support monitoring;

• appointment coordination;

• lead routing;

• urgent project updates;

• same-day CRM work;

• time-sensitive publishing;

• vendor follow-up;

• daily reporting.

Borderless Recruit makes a similar distinction between productive hours and required coverage.

So your worksheet should record both.

A task that takes four hours in one uninterrupted batch is operationally different from four hours scattered across five days.

This can influence who you hire, how the hours are scheduled, and whether a small flexible block is actually enough.

Your Own Task Time Is Only a Starting Estimate

Another common mistake is assuming that if a task takes you 45 minutes, it will always take a VA exactly 45 minutes.

That may not happen.

During onboarding, someone new to your business may need longer while they learn the system, examples, terminology, and exceptions.

Later, a repeatable process may become quicker once the assistant is familiar with it.

The work may also change after delegation. You might add a QA step, a progress note, a source-checking requirement, or a reporting field that you previously kept in your head.

Use your current handling time as the starting measurement, then replace estimates with actual VA time once the workflow is running.

That is why the first support level should be treated as a capacity hypothesis rather than a permanent commitment.

Match the Calculated Hours to the Support Model

Once you have:

• the recurring workload;

• an average monthly total;

• operating buffer;

• coverage requirements;

you can compare that number with the available support options.

At the time of this guide, Boost VA’s current support options include hourly support plus monthly packages of 30, 50, and 100 hours.

Those package sizes should not determine your workload. Your workload should determine which option makes sense.

A simple interpretation might look like this:

These are not universal thresholds for every VA provider.

They are a way to compare a calculated workload with the capacity you can actually buy.

If your estimate lands just below the top of a package, look at how variable the work is before committing.

A calculated 29-hour month with frequent urgent additions is very different from a predictable 29-hour month that rarely changes.

Check Whether You Are Describing One Role or Several

Total hours are only one part of the decision.

Imagine your worksheet contains:

• 15 hours of bookkeeping-related preparation;

• 10 hours of WordPress maintenance;

• 10 hours of prospect research;

• 10 hours of customer support.

That adds up to 45 hours, but it does not automatically mean one 45-hour generalist VA is the correct answer.

The responsibilities may need different skills, access levels, availability, or specialist oversight.

A hiring checklist from Stealth Agents recommends considering whether workloads above roughly 40 weekly hours may need more than one VA. The exact threshold is not a rule, but the principle is useful: do not force a large, mixed workload into one role merely because the arithmetic fits.

The same principle applies when deciding between a VA, freelancer, specialist, or employee.

As the Boost VA guide to scaling with virtual assistants explains, the staffing model should follow the work rather than forcing every responsibility into the same type of hire.

Run a 30-Day Capacity Check

Your first estimate does not need to be perfect.

It needs to be measurable.

For the first month, track:

After that review, one of four conclusions normally becomes clearer:

The estimate is about right.
Keep the capacity and continue measuring.

You consistently have more useful work than available hours.
Increase capacity or narrow the scope.

You consistently have unused time.
Reduce the commitment or move additional suitable work into the VA’s responsibility.

The hours look reasonable, but work still gets delayed.
The problem may be coverage, unclear ownership, missing access, poor instructions, or the wrong skill mix rather than total capacity.

That final possibility matters.

Buying more hours does not fix a badly defined workflow.

A Simple Formula for Estimating Virtual Assistant Hours

If you want the whole method in one place, use this sequence:

1. List recurring tasks that can realistically be delegated.

2. Record how often each task occurs.

3. Estimate or measure the handling time.

4. Calculate the weekly total.

5. Multiply the weekly total by 4.33 for an average monthly figure.

6. Add a realistic operating buffer.

7. Record any daily or time-sensitive coverage requirements separately.

8. Compare the result with available support capacity.

9. Run the arrangement long enough to replace estimates with actual usage.

10. Adjust the hours, scope, or staffing model when the evidence says you should.

The important number is not the neatest package size.

It is the amount of useful recurring work your business can genuinely hand over.

If you have completed the worksheet and want help turning that workload into a practical support arrangement, tell me what is currently on your plate. I can help you look at the recurring work and decide on a sensible place to start.