A virtual assistant or automation: which one a small business needs.

The short answer

Start with your tasks. Write down everything you or your team do more than once a week that is not the work customers pay you for: answering enquiries, booking, chasing, copying, invoicing, reporting. Then sort each task by one question: is it the same steps every time, or does it need someone to think?

Same steps every time is automation's job. It runs at any hour, does not mistype a phone number and costs little per run once it is built. Someone has to think is a person's job, and a virtual assistant is a flexible way to buy a few hours of that each week.

Most businesses find both kinds of task on the list. The mix that works well is automations for the routine and a virtual assistant who handles the exceptions they flag, watches the alerts and makes the calls. That is the last half of this guide.

AI can sit inside an automation, for example sorting messages or drafting a reply for a person to check. AI agents that decide their own steps are a different topic, covered in AI agents for a small business.

Task by task

Here is where common admin tasks usually land:

• Copying each website enquiry into your CRM or spreadsheet: automation. Nobody should retype a form.
• Sending an instant confirmation to a new enquiry: automation, in your wording.
• Booking confirmations and reminders: automation, and often already built into your booking software.
• Calling a new lead back within the hour: a person. Automation can alert them and hand them the details.
• Chasing a quote that went quiet: one polite automatic follow-up, then a person for the call.
• Sorting the inbox: rules for the obvious, such as invoices to accounts, and a person for the rest. An AI step can suggest labels for a person to check.
• Payment reminders: automation sends them and stops when the invoice is paid. A person handles disputes and payment plans.
• A customer replies "can we do Thursday instead?": a person, who can see the diary and the job.
• A weekly summary of enquiries, bookings and open quotes: automation.
• Researching suppliers, booking travel or tidying a messy client list: a person.
• Entering supplier invoices: a person, or software that reads them for a person to confirm, as AI invoice processing explains.

If a task appears on both sides, split it. The routine part goes to automation, and the moment it needs judgement, it lands in front of a person with everything attached.

What a person does better

A good assistant notices that a customer who sounds calm is about to leave, that two bookings clash in a way the calendar does not show, or that a supplier's email is a scam. Software follows its rules and misses all three.

People are better at conversations, calls, tone, exceptions and anything that has not happened before. They can also improve the process itself: an assistant who repeats the same five steps every morning is the first to see which ones could be automated.

The costs are real too. A person needs training, written instructions and access to your tools. They have holidays and sick days, may work in another time zone and need someone to answer their questions. Plan for a backup, and for the hours you spend managing them, especially in the first month.

What automation does better

Automation does exactly what it was told, the same way, at 2am on a Sunday as at 10am on a Tuesday. It does not get bored, does not skip a step when busy and keeps a log of everything it did.

Its weakness is the other side of the same coin. It only handles what it was set up for. A form with an unusual answer, a customer who replies to an automatic email or a tool that changes how it sends data can stop it, or worse, make it carry on wrongly. A well-built workflow sends an alert and parks the record for a person instead of guessing, as the first automations to set up describes.

So automation needs an owner too: someone who reads the alerts, fixes the rules and decides what happens to the cases it cannot handle. That person is often the virtual assistant.

What decides the monthly cost of each

A virtual assistant's cost depends on:

• The hours you buy: many work by the hour or in a monthly block of hours, sometimes with a minimum.
• Where they are and how experienced they are, and whether they work alone or through an agency that adds cover and supervision.
• The kind of work: diary and inbox work costs less than bookkeeping or work that needs a qualification.
• Your own time: training, answering questions and checking work, which is heaviest at the start.

Automation's cost depends on:

• The build, once: your own time if you set it up yourself, or a quote from whoever builds it.
• The platform: tools such as Zapier and Make charge more as the number of runs grows, while n8n or custom code take longer to set up and suit workflows that run very often. Zapier, Make or n8n compares them.
• The plans of the tools it connects: some only allow connections on higher plans.
• Upkeep: fixing a step when a tool changes, and someone reading the alerts.

Compare them task by task. A task that takes a person ten minutes, fifty times a week, is worth automating. A task that happens twice a month and needs judgement each time is not. Our own prices for building automations are on the prices page.

One business, task by task

Take a solo bookkeeper with forty clients. Each week she answers new enquiries, books discovery calls, chases clients for receipts and bank statements, sends reminders before deadlines, sends invoices and chases the late ones.

Written down, the list splits cleanly. New enquiries get an instant confirmation and land in her client list, discovery calls are booked through a booking link, document reminders go out for each missing item and stop as each one arrives, and invoice reminders stop when the invoice is paid. Those are automations, built once.

What is left needs a person: the client who sends a photo of a shoebox, the one who disputes an invoice, the call to a client who has gone silent before a deadline and the clean-up when a client's records are a mess. She buys a few hours a week from a virtual assistant for the chasing calls and the tidying, and keeps the judgement calls for herself.

Without the automations, the assistant's hours would go on reminders. With them, the hours go on the work only a person can do.

The mix that works: an assistant who watches the automations

Set it up so each side does what it is good at:

• Automations handle the routine and send every exception to one review list, such as an enquiry with no phone number or a reminder that bounced.
• The assistant works through the review list first thing each day, then the replies customers sent to automatic messages.
• Failure alerts go to the assistant and to a backup, so a broken step is noticed the same day.
• The assistant keeps the written notes for each workflow up to date, and tells you when a rule keeps catching the same case.
• You get a weekly summary: what ran, what the assistant handled and what needs your decision.

This is also how the automations get better over time. The assistant sees every case they could not handle, and each repeated one becomes a new rule. See enquiry follow-up and booking and calendar automation for two workflows that run this way.

Which to start with

Start with automation when the problem is volume: the same steps, many times a week, and an owner who is the bottleneck because they do the copying. The first workflow is usually the reply to new enquiries, because customers notice that delay most.

Start with a virtual assistant when the problem is that calls and replies go unanswered, or when the process is not written down anywhere. An assistant who documents what they do in their first weeks gives you the plan for the automations later.

Start with neither when the tasks are few. If you send three quotes a month, a reminder in your calendar and a template email may be all you need. If missed calls are the problem rather than admin, compare an AI receptionist, an answering service or text-back first.

At our free consultation we look at how often a task happens before suggesting a build, and if a setting in a tool you already pay for does the job, we say so. See automation for how a build runs.

Giving an assistant access safely

• Give them their own login to each tool, never yours, so you can see what they did and remove access in one step.
• Share passwords through a password manager, not email or chat, and turn on two-step sign-in.
• Give access to what their tasks need. An assistant who books appointments does not need the bank account.
• Run automations on accounts the business owns, not on the assistant's personal account, so nothing stops when they leave.
• Put confidentiality, who owns the work and what happens to your data at the end in a written agreement.
• Remove every login on their last day, and change shared passwords.

If your customers are in Europe, the GDPR requires a written agreement with anyone who handles personal data on your behalf, and an assistant in another country can bring rules on moving data abroad. Ask whoever advises you on data protection before they start.

Write it down, whichever you choose

A process that lives in one person's head breaks when they are away, whether that person is you, the assistant or whoever built the automation. For each task, keep one page with:

• What starts it and what a finished result looks like.
• The steps, with the wording of any message that goes to a customer.
• What counts as an exception and who decides it.
• Which tools and accounts it uses, and who to call when it breaks.

An assistant can start from that page on day one, and an automation can be built from it. The page is the most useful hour you will spend on either.

Mistakes to avoid

• Paying an assistant to copy form entries into a spreadsheet, a job a workflow does on its own once it is built.
• Automating a process nobody agrees on, so the workflow copies the mess.
• Giving an assistant your own login, so nobody can tell who did what.
• Letting automatic messages go out with nobody reading the replies.
• Expecting an assistant to answer at any hour. If you need that, automate the first reply and let the person follow up.
• No backup for the assistant's holidays, so alerts and replies sit unread for a week.

After the first month, compare three things with the month before: how long a new enquiry waits for a reply, how many tasks slipped and what the month cost in fees and your own time. Keep what moved those numbers, and stop what did not.