Virtual Assistant vs Automation Calculator

What this tool does

Describe one repetitive task — how many times it happens a month, how long each instance takes, what a VA charges per hour — and the calculator builds the VA column. Then enter the estimated build cost and monthly running cost of automating it, and it builds the automation column.

The output is a break-even point expressed in task volume and in months, plus the honest caveats: management time on one side, maintenance on the other.

A worked example

Data entry from inbound enquiry emails into a CRM. It happens 600 times a month and takes four minutes each. That is 40 hours.

At a VA rate, 40 hours a month is a recurring cost that never goes away and grows exactly in proportion to volume. It also carries management time — writing the SOP, answering questions, checking a sample, handling holidays — which is your time, not the VA's, and which people almost never cost.

Automation is a one-off build plus a small monthly platform cost, and it is flat regardless of whether volume doubles. It also has a floor of maintenance: an API changes, a field gets renamed, and someone has to fix it.

The calculator finds the month where cumulative automation cost drops below cumulative VA cost. For a task at this volume it is usually within a few months. For a task that happens twice a month, it may be never — and that is the answer the tool exists to give you honestly.

What each column carries

Where people go wrong

Forgetting management time. A VA needs direction, review and a person to ask. That is your hourly rate, and on a complex task it can approach the VA's own cost.

Automating a task that is not stable. If the process changes every month, the build changes every month. Automate the steps that have settled; leave the judgement calls with a person.

Treating it as either/or. The best outcome is usually automating the 80% that is mechanical and leaving the exceptions to a VA who now handles a fraction of the volume. Model that as a third column by halving the VA hours.

Ignoring the error rate. Manual data entry has a non-zero error rate, and every error costs rework downstream. Automation has a different failure mode — it fails loudly and completely rather than quietly and occasionally, which is usually easier to manage.

Underestimating the build. Be generous with the estimate. A build that comes in under budget is a pleasant surprise; one that comes in over invalidates the whole comparison.

FAQ

Is automation always cheaper eventually?

No. Below a certain volume the build cost never amortises, and a VA is simply the right answer. The calculator will tell you when that is the case.

What should I use for the build cost?

If you are building it yourself, your hours at your rate. If you are hiring it out, the quote. The project cost calculator helps if you have not scoped it yet.

How much maintenance should I budget?

A sensible default is an hour a month per meaningful integration. Workflows touching third-party APIs need more than ones touching only your own systems.

Does a VA plus automation make sense?

Very often, yes. It is the most common outcome in practice: the automation handles the volume, the VA handles the exceptions, and total cost falls without anything becoming brittle.

What about AI doing the judgement calls?

That changes the maths but adds a per-use cost and a quality question. Cost it separately with the AI agent cost calculator rather than folding it into a flat monthly figure.

Next steps

What Is Workflow Automation is the right starting point if you are new to this, and How to Automate Client Onboarding is a worked example of exactly this trade-off. To find which tasks are worth the analysis in the first place, run the employee time waste calculator.

Both sides of this comparison are worth sourcing rather than guessing. US Bureau of Labor Statistics data puts median pay for office and administrative support occupations at $46,320 a year as of 2024 (BLS Occupational Outlook Handbook), which is the honest floor for a full-time in-house equivalent before employment costs. On the automation side, n8n's pricing shows why the running cost stays flat as volume rises: you are billed per workflow execution, not per hour worked.

Want a second opinion on which tasks to automate first? Book a discovery call.