You're drowning. Email, scheduling, invoicing, follow-ups—non-revenue work is eating your day. You need help. But here's the question that stops most business owners: should you hire a virtual assistant or bring on a full-time employee?
This isn't a romantic choice. It's a math problem with real consequences. Get it wrong and you're either paying $4,000 a month for someone to do $800-a-month work, or you're managing a 1099 contractor to do work that should stay in-house.
This guide walks through the actual cost difference, when each model makes sense, and how to decide for your situation.
The Cost Reality
Let's get the numbers on the table.
Virtual Assistant (Contractor Model): - Fully-loaded cost: $800–$1,800/month - Breakdown: $400–$1,200 as a VA rate (US or offshore), plus your time managing them (tools, communication, error correction) - No payroll tax, benefits, equipment, or training cost - On-demand: scale up or down with work volume - You pay for 40-60 hours/month of execution
Full-Time Employee (US-Based): - Salary: $35,000–$60,000/year ($2,900–$5,000/month) - Payroll tax (7.65%): +$220–$380/month - Benefits (health, 401k, workers comp): +$500–$1,200/month - Equipment, software licenses, training: +$100–$200/month - Fully-loaded cost: $3,700–$6,780/month - You pay for 160 hours/month of availability (not all execution—some is meetings, training, downtime)
Full-Time Employee (Offshore VA): - Salary: $6,000–$18,000/year ($500–$1,500/month) - Payroll tax, benefits, equipment: +$100–$300/month - Fully-loaded: $600–$1,800/month - Same availability as US employee (160 hours/month), but in a different timezone
If you're comparing a US contractor VA ($1,000/month) to a US FTE ($4,500/month all-in), the math says: hire the VA. You save $3,500/month.
But cost isn't the only factor.
When a Virtual Assistant Makes Sense
A VA is the right choice when:
1. Work is task-based, not role-based. Examples: "Handle all customer emails," "Book meetings," "Write social media captions," "Invoicing and expense tracking."
These jobs have clear outputs. You can say: "When a customer emails, send this response template and file it in Airtable. When a prospect books a call, send the calendar link and add them to the CRM." The work is done when the task is done.
A VA excels here because you pay only for the execution you need. If you get 40 customer emails a week, a VA takes 10 hours. If it drops to 20, the VA takes 5 hours. You scale.
2. Your workload is variable or seasonal. If you have three busy months and nine slow months, an FTE is expensive. A VA lets you adjust mid-month. You need 20 hours in February, 60 hours in March, 15 hours in April. Done.
3. You need offshore cost advantages. A Philippines-based VA at $600/month is functionally the same as one in Texas—except the cost. If the work can be async (emails, doc management, scheduling), time zone difference is a feature, not a bug. You go to bed, they work overnight, you wake up to finished tasks.
4. The work is well-defined and doesn't require company context. If you can write a procedure in 30 minutes and a new person can execute it without asking questions, it's VA work. Booking calendar slots. Processing invoices. Responding to FAQs. Adding leads to a spreadsheet.
5. You're testing a new process or stream of work. If you're not sure if customer support chat is worth staffing, hire a VA for three months. If it works, promote to a role. If it doesn't, you've only spent $2,400. Safer than hiring a $60k/year employee for something experimental.
When an Employee Makes Sense
An FTE is the right choice when:
1. Work is role-based, not task-based. Examples: "Head of Sales," "Software Engineer," "Marketing Manager," "Chief Operating Officer."
These aren't collections of tasks. They're domains. A sales manager doesn't just execute calls; they decide pipeline strategy, coach the team, report on forecasts, adjust messaging, and own the result. A VA can execute individual sales tasks. An employee owns the function.
2. The work requires judgment and context. "Write our Q3 marketing plan," "Decide if we should hire another engineer," "Plan the org structure," "Mentor junior designers." These require understanding your business, your constraints, your values, and your market. A VA can research and draft. An employee decides.
3. You need full-time availability and presence. If you need someone in standup meetings, involved in planning, present in Slack, and thinking about the work when you're not working together, hire an employee. A VA works on the tasks you assign and disappears between assignments. There's no ambient context.
4. The person will own proprietary work or sensitive information. A contractor has divided loyalties. They might work for a competitor (legally, they can—they're not employees). If you're building something new, protecting a process, or managing sensitive client data, an employee with an IP assignment and NDA is safer. A VA can sign an NDA, but they have less legal leverage to enforce confidentiality than an employee.
5. You need training and growth in your culture. Employees get better. You invest in them, they develop, and they become force multipliers. A VA is usually optimized at their current skill level. They're contractors, not cultural carriers. If you need someone to learn your way of thinking and evolve with your company, hire an employee.
6. Turnover cost is high. If it takes you two weeks to train someone, turnover is expensive. A VA is cheap to replace (you hire a new one). An employee is expensive to replace (recruiting, training, lost knowledge). If the role requires onboarding, hire an FTE and invest in retention.
The Hybrid Model
Some teams use both.
Example: You hire a full-time Operations Manager ($4,500/month) who owns process, strategy, and team leadership. They also work 20 hours a week on execution. The remaining 60 hours of ops work—invoicing, scheduling, email management—goes to a VA at $1,200/month. Total cost: $5,700. But you have a person thinking about operations, not just executing it.
Or: You hire a software engineer ($6,000/month) to build new features and own the codebase. A VA ($800/month) handles bug reproduction, test case management, and documentation. Total: $6,800. The engineer stays on new work; the VA handles the grunt work.
This structure works when: (1) the FTE role is senior/strategic, (2) there's routine work that doesn't need judgment, and (3) you can split it cleanly.
Contractor vs Employee Classification (The Legal Part)
The IRS and Department of Labor care about this. Misclassify, and you face back taxes, penalties, and fines.
Employee (1099-equivalent is illegal for most roles): - You control how and when they work - They're exclusive (can't work for competitors) - They work from your location (or integrated into your team workflow) - You provide equipment and training - There's an expectation of ongoing work
Contractor (valid 1099): - You control the result, not the method - They set their own hours - They can work for competitors - They provide their own equipment - The relationship has a defined end date
If you hire someone on a 1099 but require them to work 9-5, use your laptop, report to you daily, and never work for anyone else, you're misclassifying them. That person should be a W-2 employee.
The safe rule: If it looks like a job, it's a job. Hire them on W-2.
One exception: true VAs working offshore for multiple clients, setting their own hours, delivering results without supervision. That's usually legit. But a "virtual employee" working for you exclusively 9-5 Texas time on your laptop should be on payroll.
When in doubt, talk to an employment lawyer. It's cheaper than the IRS bill.
How to Decide: The Questions to Ask
1. Is the work task-based or role-based? (Task = VA, Role = Employee) 2. Does the work change month to month? (Yes = VA, No = Employee) 3. Do I need this person in the room for decisions? (Yes = Employee, No = VA) 4. Can someone new execute this work in 2-4 weeks of training? (Yes = VA, No = Employee) 5. Is the work proprietary or sensitive? (Yes = Employee, No = VA) 6. Am I replacing someone or building a new function? (Replacing/new function = depends on scale; if large, Employee) 7. What's my timeline? (I need help now = VA; I need help for 2+ years = Employee)
If most answers point to VA: hire a VA. If most answers point to Employee: hire an employee. If you're split: start with a VA. If the workload grows and the work becomes strategic, promote to an employee later. The reverse (demoting an employee to a VA) is harder legally and emotionally.
The Hard Truth
Most business owners hire an employee when they need a VA, or try to manage a VA like an employee.
The first costs you $3,000/month you don't need to spend. The second frustrates everyone because you're asking for role-based ownership from someone hired for task execution.
Make the right call based on the work, not on how you want to feel about management. Both models work. They're just different.
Next Step
If you're genuinely split on which model is right—or you need help structuring both—[talk to us](https://tantaholdings.com/consulting). We've hired hundreds of both and can help you map out the exact role breakdown, the cost model, and the management structure for your situation.
You don't have to guess. We've seen what works.
---
Related reading: - [Virtual Assistant Services for Businesses](https://tantaholdings.com/blog/virtual-assistant-services-for-businesses) - [Virtual Assistant Cost: Philippines vs US](https://tantaholdings.com/blog/virtual-assistant-cost-philippines-vs-us) - [How to Hire a Virtual Assistant in the Philippines](https://tantaholdings.com/blog/how-to-hire-a-virtual-assistant-philippines) - [Virtual Assistant Tasks List for Business Owners](https://tantaholdings.com/blog/virtual-assistant-tasks-list-for-business-owners)