Share
Every task in your business belongs in one of three buckets: automate it, delegate it, or do it yourself. Most founders have no system for deciding which is which. Here's the framework we use with every Jarvis client on day one.
Why this decision matters more than you think
When founders first come to Jarvis, they usually have one of two problems. Either they're trying to automate everything with AI and it keeps failing on them — customers getting bot-replies to real complaints, leads going cold because no human followed up. Or they're delegating tasks to a VA that could be handled by a $10/month automation tool, which means they're paying human rates for robotic work.
Both are expensive mistakes. The first costs you in customer trust and conversion. The second costs you in unnecessary payroll. The fix is a clear mental model for sorting tasks before you assign them anywhere.
Ask one question about every task:
"Does this require judgment, relationships, or context — or just execution?"
The two-question test
Before you decide where any task goes, run it through these two questions:
Question 1: Is the output always the same if the input is the same?
If someone orders the wrong item and wants a refund, should the response always be identical? No — it depends on the customer's history, their tone, how many times this has happened, and whether saving the relationship matters more than the refund. That's a VA task.
If a new lead fills out a form and needs a confirmation email sent, should the output always be identical? Yes. That's automation.
Question 2: Would a mistake cost you a customer or just a task?
Automation mistakes are cheap when they're low-stakes. An invoice gets sent with the wrong line item — easy to fix, no relationship damage. But if AI sends a tone-deaf response to an upset client and they screenshot it? That's a reputation problem. High-stakes communication belongs with a human.
The full task matrix: 30 examples sorted
| Task | Where it goes | Why |
|---|---|---|
| New lead form submission → CRM entry | Automate | Identical input, identical output every time |
| First response to a new inbound lead | VA | Tone and speed together — needs a person within 2 min |
| Sending weekly invoice to recurring clients | Automate | Same amount, same client, scheduled |
| Client asks to pause and renegotiate contract | VA | Requires judgment and relationship management |
| Appointment confirmation email | Automate | Templated, rule-based, no context needed |
| Rescheduling a VIP client | VA | Requires tone, priority awareness, relationship |
| Routing support tickets by category | Automate | Pattern matching, no judgment needed |
| Responding to a 1-star review | VA | Brand voice + de-escalation — high stakes |
| Instagram DM: "what's your price?" | VA | Could be a lead — needs qualifying, not a template |
| Email newsletter send | Automate | Batch send, no decision per recipient |
| Following up on an overdue invoice | VA | Tone matters — some clients need a nudge, others a call |
| Sending a payment reminder (first notice) | Automate | First touch is templated, zero judgment needed |
| Researching a prospect before a sales call | VA | Requires synthesis, context-reading, prioritization |
| Pulling a weekly revenue report | Automate | Same data, same format, scheduled |
| Reading the report and flagging what's wrong | VA | Requires understanding what matters vs what's noise |
| Scheduling social media posts | Automate | Publish at a time, no judgment needed |
| Responding to comments on social posts | VA | Brand voice, community building, relationship |
| Updating a lead status in CRM after a call | VA | Requires listening to context, not just checking a box |
| Sending a standard onboarding email sequence | Automate | Same sequence, same triggers for all new clients |
| Checking in with a client who's gone quiet | VA | Templated check-ins get ignored — needs genuine tone |
| Processing a refund that meets criteria | Automate | Rule-based, clear criteria, no edge cases |
| Handling a refund dispute | VA | Customer is upset — relationship repair required |
| Booking a meeting from a calendar link | Automate | Fully handled by Calendly, no human needed |
| Deciding which meetings are worth your time | VA | Requires understanding your priorities and context |
| Generating a client report from data | Automate | Template + data = report, every time |
| Writing the executive summary for that report | VA | Requires interpretation and communication judgment |
| Sending a follow-up 48hrs after no reply | Automate | Time-based trigger, templated message |
| Writing the follow-up when context matters | VA | Why they haven't replied affects what you say |
| Logging an expense receipt | Automate | Structured input → structured output |
| Categorizing an expense that's ambiguous | VA | Business context determines the right category |
The pattern you'll notice
Look at the VA column. Almost every task in it has one of three things in common: it involves a real relationship, it requires reading context the system doesn't have, or a mistake would cost more than money.
Look at the automation column. Almost every task in it is rule-based, templated, or time-triggered. The machine knows exactly what to do because you've already decided what the right output is.
Automation is decision execution. A VA is decision making. Once you see it that way, sorting your task list becomes obvious.
How Jarvis combines both
Every Jarvis client gets both layers. We use Durable — an automation platform with 50+ integrations — to handle all the rule-based execution: routing, triggering, logging, scheduling. Your VA handles everything that requires judgment, context, and relationship.
In practice, a task often flows through both. A new lead comes in. Durable auto-tags them by source and triggers an alert to the VA. The VA responds within 2 minutes in the founder's voice, qualifies the lead, and books the call. Durable logs the outcome and triggers the onboarding sequence when the deal closes. The founder never touches it.
The goal isn't to replace human judgment with automation. It's to clear away everything that doesn't need judgment so your VA — and you — can focus on the work that actually moves the business.
Where to start
Take 20 minutes this week and list every task you or your team does in a day. For each one, ask: "Does this require a real decision, or is it always the same if the input is the same?" Sort them into two columns. The automation column becomes your Durable setup. The VA column becomes your day-one hire brief.
That's the exercise we walk through with every new Jarvis client on the first call. Most founders are surprised how many tasks fall into automation — and how much more clearly they can see what they actually need a VA for.
Not sure where to start? Download our free delegation checklist — the 12 tasks most founders hand off in week one. Get it when you book your free call.
Not sure where your tasks belong?
We'll sort it out on a 15-minute call.
We'll map what to automate, what to delegate, and what to keep — before you hire anyone.
Book a Free CallFrequently Asked Questions
What's the main difference between the options compared in this article?
The key differences are cost, VA location (US-based vs. Philippines-based), automation capability, and model (dedicated vs. task pool). Jarvis is the only option that includes automation builds with every placement.
Is Jarvis cheaper than Belay?
Yes. Jarvis full-time placements start at $1,600/month vs. Belay's $3,000–$5,000/month. Both offer dedicated VAs, but Jarvis includes automation builds and has a faster placement timeline.
Which VA service is best for a small business?
For service businesses under $200K/month that want dedicated support plus automation, Jarvis is the strongest value. For C-suite executives with higher budgets specifically wanting US-based VAs, Belay is the premium choice.
Can I switch from another VA service to Jarvis?
Yes. Book a consultation before your next billing cycle with your current provider. We'll scope the role and give you a direct cost comparison.