Share
Most VA relationships that fail aren't VA problems. They're delegation problems. The same VA who "didn't work out" for one founder is thriving with another founder who set them up correctly. The difference isn't the VA. It's the handoff.
Delegating to a virtual assistant is a skill. Most founders have never been taught it. They've been taught to do things themselves, hire expensive employees, or outsource to agencies. Handing tasks to a VA requires a different muscle entirely — one that takes practice and a few specific habits to build.
Here are the 7 most common mistakes, and exactly how to fix each one.
Mistake 1: Delegating Outcomes, Not Processes
"Make sure our clients are happy" is not a task. "Send a check-in email every Tuesday at 9am using this template, and flag any replies with concerns to me by noon" is a task.
Founders who delegate outcomes assume the VA has enough context to figure out the process. They don't. They've been working with you for a week. They don't know your clients' history, your communication style, or what "happy" means in your context.
The fix: define the exact steps, not just the goal. If you can't write down the steps yourself, you haven't thought the task through clearly enough to delegate it yet.
This is especially important for client-facing work. See use cases for examples of how different business types delegate client management tasks with clear process documentation.
Mistake 2: No Written Process
You explained it on a call. The VA nodded. You felt good about it. Two weeks later, they're doing it completely differently than what you described.
Verbal instructions disappear. Memory is unreliable on both sides of the relationship. If you explained a task once on a Zoom call and never followed up with a written document, you cannot be surprised when the output doesn't match your expectation.
The fix: Loom video plus written checklist for every task you delegate. Record yourself doing the task once. Write out each step in numbered format. Put it in a shared Notion page the VA can reference forever.
This takes 20 minutes upfront and saves hours of re-explaining over the following months. It also gives you a document to update when the process evolves, instead of re-training from scratch.
Mistake 3: Too Many Tasks on Day 1
You've been waiting for help. The moment the VA starts, you dump everything on them. Inbox management, scheduling, client follow-ups, social media, CRM updates. All of it.
The result: the VA does 6 things at 60% quality instead of 3 things at 90% quality. You think the VA isn't capable. The VA thinks they've failed. Both parties are frustrated by week 2.
The fix: one task per week until mastered. Start with the task that costs you the most time and has the clearest process. Let the VA own it completely before adding the next one.
By week 6, a VA who started on one task is reliably running five. It feels slower at the start. It's dramatically faster over 90 days. Check out the VA onboarding checklist for a week-by-week structure that prevents overload.
Not sure where to start with delegation?
Read what a virtual assistant does for a breakdown of the 12 most commonly delegated task categories, ranked by founder time saved.
Mistake 4: Not Reviewing Output in the First Week
You're busy. You trust the VA is handling it. You'll check in at the end of the month.
By week 3, the VA has repeated the same misunderstanding 15 times. The error is baked into their routine. Correcting it now means undoing 3 weeks of learned behavior, not just one mistake.
The fix: daily output review for the first 5 business days. Not a call. Just check the actual work. Look at the email they sent. Check the CRM entry. Read the report. Spend 10 minutes per day doing this in week 1 and you prevent a month of correction later.
After the first week, you can shift to spot-checking. But do not skip the first week.
Mistake 5: Disappearing After Day 1
Some founders overcorrect on micromanagement and go completely hands-off from day one. The VA has questions — naturally, because it's their first week — but the founder's response time is 6 to 24 hours.
The VA guesses. Guesses get turned into habits. Habits compound.
By week 3, you have a VA who has made 30 decisions you didn't know about, half of which were wrong, and none of which can be undone easily.
The fix: commit to a 15-minute response time during business hours for the first 5 days. You don't need to be available constantly. You need to be available quickly enough that the VA asks you instead of guessing.
After week 1, you can set a standard response window of 2 to 4 hours. The first week is the exception.
Mistake 6: Delegating Judgment Calls
"Use your judgment on this one" is a trap. It sounds like trust. It's actually an abdication of clarity.
Your VA does not have your context, your relationship history with that client, your risk tolerance, or your sense of what a 1% edge case looks like. When you ask them to "use judgment," you're asking them to guess at a decision framework they've never been given.
The fix: define the decision rules explicitly. "If the client is unhappy, send this template and flag me immediately. If they're just asking a question, use the FAQ doc. If it's anything else, ask me before responding."
The format is simple: "If X, do Y. If Z, ask me." Write it once. It becomes the VA's operating manual for that task category.
This is especially important in client-facing roles. See our process for how Jarvis structures decision trees for VAs from day one.
Mistake 7: Comparing VA Output to Yours
You've been running this business for 3 years. You built the processes. You know the clients. You know the edge cases. Your VA has been doing this task for 2 weeks.
When you compare their output to what you would have done, the VA will always fall short. That's not a fair comparison. It's not even a useful one.
The fix: compare their output to the defined standard, not to your intuition. The question is not "would I have written it this way?" The question is "did they follow the brief, hit the deadline, and stay on-brand?"
If yes, it's a pass, even if you would have worded it differently. If no, that's a specific correction against a specific standard — not a general judgment that the VA isn't good enough.
One founder we work with spent the first 3 weeks rewriting every email her VA sent. The emails were fine. They were just different from what she would have written. She was training the VA to be her clone instead of training them to meet a standard. Once she wrote an email quality checklist — tone, length, one ask per email, no jargon — corrections dropped by 80% in week 4.
The Real Question: Are You a Good Delegator?
Most founders who've had bad VA experiences have never asked themselves this question.
Delegating is a skill. It requires you to articulate processes that have been living in your head, unspoken, for years. It requires you to write standards you've never had to write because you were the only one doing the work. It requires you to give feedback on a specific output against a specific standard, not on a vague sense that something isn't right.
None of this is natural. None of it is taught. But it is learnable.
Before you hire your next VA, read when to hire your first virtual assistant. Then write one process. One. Before the VA starts. That's the habit that changes everything.
What Changes With a Pre-Trained VA
There's one category of delegation failure that Jarvis solves before your VA even starts: tool training.
If you hire off Upwork or OnlineJobs.ph, you're often starting from scratch on software. The VA has never used GoHighLevel. They've used a different CRM. They've never set up Buffer. They've seen Notion but don't know your workspace structure.
Jarvis VAs are pre-trained on the tools business owners at your stage actually use: GHL, Notion, Gmail, Buffer, Later, Slack, and more. That's one entire category of week-1 friction eliminated before day one.
The task-specific training still matters. You still need to write the process and review the first week's output. But you're not starting at zero. You're starting at 40%.
See virtual assistant pricing for a full breakdown of what pre-training covers and what's included in the monthly rate. And browse roles we source to understand the range of VA types available through Jarvis.
Frequently Asked Questions
Why do most VA relationships fail?
In most cases, the VA wasn't set up correctly. The tasks weren't documented, the standards weren't defined, and the first-week review didn't happen. The VA made reasonable guesses in the absence of direction, and those guesses compounded into bigger problems over time.
How long should I spend onboarding a VA?
Plan for 30 to 60 minutes of your time in week 1 across documentation and review. Not per day. Total. The investment is front-loaded. By week 3, check-ins should take less than 5 minutes per day.
What's the best first task to delegate to a VA?
Start with the task that is highest volume, lowest judgment, and most clearly defined. For most founders, that's inbox triage, CRM data entry, scheduling, or reporting. High volume means the VA gets repetitions quickly. Low judgment means fewer decisions to define upfront.
How do I know if my VA is underperforming vs. I'm not delegating well?
Check your documentation first. If you don't have a written process for the task, a quality checklist, and a defined turnaround time, you don't have enough information to evaluate the VA fairly. Write those three things, then re-evaluate over the next 2 weeks.
Can I fix a bad VA relationship, or should I start over?
Depends on where the breakdown is. If the VA is missing deadlines consistently with no communication, that's a reliability issue — hard to fix. If the output quality is off but they're responsive and asking good questions, that's almost always a documentation problem. Write better processes and you'll usually see the issue resolve within 2 to 3 weeks.
How many VAs do founders at your stage typically need?
Most founders doing $10K to $50K/month start with one VA on 2 to 3 core tasks. By $50K to $100K/month, they're often running one full-time VA plus a second part-time VA in a specialized role. The expansion usually happens organically once the first VA relationship is stable.
Set Your VA Up to Succeed
The founder who sets up clear processes, reviews output in week 1, and defines decision rules — that founder succeeds with VAs every time. The founder who skips those steps blames the VA when it falls apart.
Jarvis VAs are pre-trained and ready to execute. You still need to be a good delegator. But you're starting from a much better position than a cold hire from a freelance platform.