Stop Paying a Human to Do a Robot's Job
Photo by Photo by Surface on Unsplash on Unsplash
A founder friend of mine hired a virtual assistant last spring. Great hire, honestly — organized, reliable, quick with follow-ups. Three months in, she admitted something over coffee in Denver: "I spend an hour every morning writing instructions for tasks a spreadsheet could do."
She hadn't hired an assistant. She'd hired an employee whose full-time job was executing copy-paste workflows. And she'd become the middle manager of a one-person department.
If you've brought on a VA or contractor and somehow ended up busier, this one's for you.
The Task Triage: Person, Process, or Program?
Before delegating anything, sort it. Every task on your plate falls into one of three buckets:
Human work requires judgment, relationships, or improvisation. Handling a frustrated customer, negotiating with a vendor, proofreading a sensitive email, researching a prospect and deciding how to approach them. This is what your VA is actually for.
Workflow work follows rules but spans multiple systems. When a deal closes in your CRM, create a project, send a welcome email, generate an invoice, and update the client tracker. A human can do this. A human doing this is a waste.
Program work is single-system, repetitive, and rule-based. Data entry, file renaming, appointment reminders, report generation. This should never touch a human being, including you.
The trap most founders fall into: they hand their VA bucket two and three because handing things off feels like progress. Meanwhile they're paying a human hourly rate to behave like a $29/month automation.
The Etiquette of Not Assigning Robot Work to People
There's a fairness angle here that doesn't get discussed enough. When you assign a human a task a tool could handle, you're not just wasting money — you're spending someone's attention on work that erodes it. Copy-paste drudgery is the fast lane to contractor churn, and good VAs have options.
A simple rule of thumb I've heard from seasoned ops folks: if you can write the instructions as an if-then statement, it belongs in a workflow, not a job description. "If a new subscriber joins the newsletter, add them to the CRM and tag them by source." That's a Zap, not a task.
How to Actually Hand Off Automation-Friendly Processes
Once you've identified what should move to software, here's the practical path:
1. Have your VA document before you automate. Counterintuitive, but your VA knows the process better than you do — including the weird edge cases. Have them write out the current steps in a doc or Loom video. This takes an afternoon and becomes your automation blueprint.
2. Automate the boring middle, keep the human edges. The best handoffs aren't all-or-nothing. Maybe the CRM update, invoice, and folder setup happen automatically, but your VA still sends a personal welcome note and reviews anything flagged as unusual. You've cut the task from 20 minutes to 5 — and made their job better in the process.
3. Start with one workflow, not twelve. Pick the highest-volume, lowest-judgment process on the list. Invoice generation. Appointment confirmations. Lead routing. Get one win, then iterate.
4. Make your VA the automation owner. Here's the reframe that changes everything: your VA's job description now includes building and maintaining the workflows. They learn Zapier or Make. They monitor the automations. They fix what breaks. You've just promoted them from task-executor to systems-operator — which is more engaging work at a higher rate, and frees them for the judgment calls only they can make.
The Math That Should Convince You
Run it for your own team: take your VA's hourly rate, multiply by the hours they spend weekly on bucket-two and bucket-three tasks, and compare that to the cost of the automation tools that would replace those hours. In most cases the tools pay for themselves in the first month.
But the real return isn't on the invoice. It's that your VA stops being a very expensive macro and starts being what you actually hired: a thinking partner who handles the things software can't.
You didn't hire a person to be your robot. Build the robot, give the person a better job, and take back your mornings.
