VA vs. Operations Lead: Why Most STR Operators Hire the Wrong One

Hire a virtual assistant when guest messaging volume is your only real constraint and documented systems already exist. Hire an operations lead when problems reach you before anyone has solved them, no written procedures exist, and you are running roughly three or more properties. The VA executes tasks you define. The operations lead defines the tasks, owns vendors, and removes you as the decision point. Wrong order means the same bottleneck at higher payroll.

Most operators find this out at property three, a few months after signing a VA contract that gave real relief for about six weeks. Below: what each role removes, what each costs against a median-wage benchmark, a triage process for deciding this week, and the 90-day build a competent operations lead should deliver.

Last updated: 2026-09-17

Where the Wall Shows Up

The wall is not work volume. It is that you cannot run more than two properties out of your head, and most operators try to do exactly that for a year too long.

I've spent 18+ years in real estate, focused on short-term rentals since 2016, trained more than 10,000 operators through CashFlowDiary, and recorded hundreds of podcast episodes breaking down the deals that work and the ones that don't. The pattern below shows up in every cycle.

It arrives around property three, sometimes four, rarely past five. Communication slips first, because guest messages are the only part of the operation with a clock on it. Review scores drift next. Then a cleaning crew quits on a Sunday with two same-day turns booked, and the operator concludes that scaling was a mistake.

Scaling was not the mistake; the architecture was. Nothing had been written down, so every exception routed to the founder's phone. You cannot hire your way out of a design problem with an execution hire.

Two counts tell you which side of the wall you are on: decisions last week only you could make (vendor selection, damage claims, whether to comp a night), and hours spent on operational work (vendor calls, maintenance dispatch, inventory, quality control). Above roughly 15 operational hours a week with more than a handful of founder-only decisions, the constraint is your own position in the workflow.

What Each Hire Actually Removes

⤢ Hover to enlarge

A VA removes tasks from your plate. An operations lead removes decisions from your plate. Only the second one raises your ceiling.

VAs execute the tasks you define; operations leads define them. VAs need instructions; operations leads write the instruction set and solve problems before they reach you. When a guest reports a dead smart-lock battery at 9 p.m., the VA forwards the message. The operations lead already has a locksmith on file, a backup code procedure, and a compensation rule for the inconvenience.

The Airbnb co-host role is a useful reference for how narrow platform-level delegation actually is: a co-host can be granted permission to manage a listing, respond to inquiries, and message booked guests (Airbnb's co-hosting documentation). That covers the guest-facing surface. It does not cover linens, par levels, locksmiths, damage claims, or who answers at 2 a.m. Platform permissions are not an operations function.

Hiring execution without architecture has a name in the management literature. Oncken and Wass called it the upward delegation of "monkeys": every unresolved problem hops back onto the manager's back until the calendar fills with other people's next moves (Management Time: Who's Got the Monkey?, Harvard Business Review). A VA with no written procedures generates monkeys quickly and politely.

The Cost Math on Both Hires

Compare the two hires against founder hours, not against each other. The operations lead is an arbitrage on your time, and it only pays if you actually redeploy the hours you get back.

The planning ranges I use are $15–$35 per hour for a VA and $50K–$80K a year for an experienced operations lead, or $35–$60 per hour fractional. Those are working assumptions for a budget, not published data — what you actually pay depends on scope, market, hours, and whether the person is a contractor or an employee. Get two real quotes before you commit to a number.

For an independent benchmark, federal occupational data is a better anchor than agency marketing. O*NET reports 2025 median wages of $22.86 per hour ($47,540 annually) for secretaries and administrative assistants, and $33.29 per hour ($69,250 annually) for lodging managers — the occupation whose task list, including setting rates, budgeting, and coordinating property activity, most closely matches a small-portfolio operations lead (O*NET, Secretaries and Administrative Assistants; O*NET, Lodging Managers). The roughly $22K spread between those two medians is a defensible estimate of what the upgrade costs at market rate, and it is smaller than most operators assume while they stall on the decision.

The table below is an illustration built on those planning ranges, not measured results. Substitute your own hours and rates.

Run the arithmetic on yourself before you sign anything. Twenty hours a week of operational work is about 80 hours a month; at $100 an hour on founder time that is $8,000 a month of opportunity cost sitting in your own calendar. The $100 is an assumption, not a measurement — replace it with the cash your last acquisition or repricing project produced, divided by the hours it took.

The honest failure case: operators who buy back 15 hours a week and spend them on the same operational work out of habit get no return at all. The return comes from what you stop doing.

A Five-Step Triage Process for the Hiring Decision

⤢ Hover to enlarge

Run this in one sitting with your calendar and your books open. It takes about 90 minutes and it settles the question with evidence instead of vibes.

Step 1 — Log two weeks of operational hours by category

Track every operational task in five buckets: guest messaging, vendor and cleaner coordination, maintenance dispatch, inventory and supplies, quality control and reviews. A phone note is fine, and two weeks is enough to see the shape. If more than 60% of the hours land in guest messaging, you have a VA problem. If messaging is under half and the rest is spread across vendors, maintenance, and supplies, you have an architecture problem.

Step 2 — Count founder-only decisions

Mark every decision in that log only you could have made, then ask why: capital authority, or nobody wrote down the rule? Capital authority is legitimately yours. The rest is an undocumented procedure masquerading as judgment.

Step 3 — Check the revenue and door signal

Door count and revenue are the signals operators reach for first, and they are the weakest ones. In my own portfolio and in the operators I work with, the break tends to land around three to five properties — but that is my observation, not a measured threshold, and it moves with nightly rate, turn frequency, and how far apart the doors sit. The signal I trust: when adding another property sounds exhausting rather than interesting, you are past the VA threshold.

Step 4 — Price both options against your own hourly number

Use the cost table above with your figures substituted. Write down the monthly cash cost, the hours you expect back, and what you will do with those hours specifically — name the project. If you cannot name the project, delay the hire and fix your systems documentation first, because you will not capture the return.

Step 5 — Decide, sequence, and set a 90-day review

If the log says architecture, hire the operations lead first and add execution support after the systems exist. If the log says messaging volume and your procedures are already written, hire the VA and revisit in two quarters. Either way, set a calendar review at day 90 with three named outcomes: keep, adjust scope, or replace. Our 90-day cash flow systems blueprint walks the same review discipline from the money side.

Most operators run this backwards. They add a VA, then six months later realize they needed an operations lead — and now they are managing a VA while still carrying the operational load. Sequence determines outcome.

What a Competent Operations Lead Builds in 90 Days

If your operations lead has not produced written systems by day 90, you hired an expensive VA with a better title.

The build has five parts. Vendor bench: named cleaners, maintenance techs, locksmiths, and supply vendors, each with a backup and agreed response windows. Inventory system: par levels per property, a stock-check cadence, and a reorder trigger that fires without you. Maintenance protocols: response trees for the recurring failures — across five doors, the same handful of failures — running toilets, dead lock batteries, WiFi outages — recur often enough to deserve a written path instead of a phone call. Quality control: pattern reading, so three guests mentioning slow WiFi turns into a call to the provider before it becomes a rating problem. Communication systems: templates, escalation paths, and compensation limits the VA can use without asking.

Software and AI belong inside that build, not instead of it. Demand-based pricing, message automation, and review-response tools all shorten the work, and each needs someone to set the rules, watch the outputs, and own the exceptions. Handing a pile of tools to a VA with no written procedures just makes the mistakes arrive faster.

Classification, Payroll, and the Part That Bites Later

⤢ Hover to enlarge

Whether your operations lead is a contractor or an employee is not a naming choice, and getting it wrong is expensive in a way no operational win offsets.

The IRS applies common-law rules across behavioral control, financial control, and the type of relationship to determine worker status; the agency's guidance states plainly that a worker is an employee when the business has the right to control what will be done and how it will be done, even if that control is not exercised (IRS, Independent contractor (self-employed) or employee?). Read the definition of a common-law employee alongside it (IRS, Employee (common-law employee)).

That maps directly onto this role. An operations lead works precisely because they set the schedule, choose the method, and decide the sequence — the opposite of the control profile that supports contractor treatment. The more system authority you hand over, the more the relationship can look like employment, and state tests are frequently stricter than the federal one. Budget for the employer-side costs before you fall in love with the salary number.

This is not tax or legal advice, and nothing here is a determination about your situation. Have a CPA and, where employment law is involved, an attorney review the arrangement and any threshold before you sign — classification rules and state tests change, and they vary by where the worker sits.

One cost never shows up in the spreadsheet. The World Health Organization defines burn-out in ICD-11 as a syndrome resulting from chronic workplace stress that has not been successfully managed — energy depletion, mental distance from the job, reduced professional efficacy (WHO, ICD-11 classification of burn-out). That is a fair description of being the only exception handler for five doors.

If you want a second set of eyes on your own hours log before you hire, book a complimentary one-on-one diagnostic call and bring the two-week category breakdown from Step 1.

The same discipline applies upstream when you pick a market — see how to choose your first STR market — and further out in how operators who scale past ten properties think about failure.

Frequently Asked Questions

When should I hire a VA instead of an operations lead?
Hire the VA when guest messaging volume is your binding constraint and your procedures are already written down — templates, escalation rules, vendor contacts, compensation limits. A VA executes inside a system. If the system exists only in your head, the operations lead comes first.

How much does an operations lead cost compared to a VA?
Use $15–$35 per hour for a VA and $50K–$80K a year for a full-time operations lead, or $35–$60 per hour fractional, as budgeting assumptions rather than quoted prices. The verifiable anchor is O*NET's 2025 medians: $47,540 for administrative assistants and $69,250 for lodging managers. Add employer-side costs if the role is an employee, and confirm the treatment with your CPA.

What property count means it is time to upgrade?
Three to five properties is where I usually see it break, but door count is a weak signal on its own. The reliable one is where your hours go: if operational work exceeds about 15 hours a week and few procedures are documented, the upgrade is overdue regardless of door count.

Will AI tools remove the need for an operations lead?
No. Message automation, demand-based pricing, and review-response tools shorten the work; someone still has to set the rules, monitor the outputs, and handle exceptions. Tools raise an operations lead's output. Handed to a VA without written procedures, they raise the speed at which mistakes reach guests.

I already hired a VA and I am still the bottleneck. What now?
That is the common case, not a failure. Keep the VA, bring in an operations lead — full-time or fractional — to write the systems, then move the VA inside those systems as the executor. Do not fire first; you would lose the messaging coverage while the build is happening.

Sources

• O*NET OnLine — Lodging Managers (11-9081.00), 2025 median wages — supports the $33.29/hour, $69,250 annual median used as the operations-lead benchmark.

• O*NET OnLine — Secretaries and Administrative Assistants (43-6014.00), 2025 median wages — supports the $22.86/hour, $47,540 annual median used as the VA-tier benchmark.

• IRS — Independent contractor (self-employed) or employee? — supports the common-law control tests behind the classification warning.

• IRS — Employee (common-law employee) — supports the definition of employee status when the business controls what is done and how.

• World Health Organization — Burn-out an "occupational phenomenon": International Classification of Diseases — supports the ICD-11 definition of burn-out quoted in the closing section.

• Airbnb Help Center — Co-hosts: an introduction — supports the description of what platform co-host permissions cover.

• William Oncken Jr. & Donald L. Wass, Management Time: Who's Got the Monkey?, Harvard Business Review — supports the upward-delegation pattern behind hiring execution without architecture.