VA team or automation, honestly

When a VA team is the right answer, when it stops being one, and how to work out the crossover point for your own agency rather than taking anyone's word for it.

Reviewed by John Carroll · Updated 7 October 2026

Nobody selling automation tells you when not to buy it, so here is that part first.

When a VA team is correct

• Under about thirty accounts. One person manages it fine and infrastructure is overkill.
• When the work is genuinely bespoke per account rather than repeated.
• When you are still testing what content works and the operation changes weekly.
• When cash is tighter than time.

When it stops being correct

• When the person managing accounts becomes a team.
• When managing the team becomes your job.
• When output quality depends on who is on shift.
• When you cannot answer "did every account post yesterday" without asking someone.
• When turnover means retraining more often than not.

Work out your own crossover

Count four things for one month: total paid to people running accounts, hours you personally spent managing them, accounts lost to bans and how long each slot stayed dead, and how many days output was below target because somebody was unavailable.

The fourth number is usually the shock. Then compare against a fleet of the same output. The calculator does the arithmetic.

The answer is sometimes both

Plenty of agencies run a fleet for volume traffic and keep a small team for the accounts that need judgement. Automation is not an all or nothing decision, and treating it as one is how people either overspend or stall.