Scaling from One Author VA to a Team
Most authors who hire their first VA think of it as the endgame — the arrangement that solves the operational overflow problem and gives them back their writing time. For authors whose publishing businesses are growing, it often turns out to be the beginning. A VA who started out handling social media and ARC coordination may, two years later, be at capacity across those tasks plus launch coordination, newsletter management, and a growing reader community — while your catalog has expanded, your reader base has grown, and the tasks that genuinely need doing have multiplied faster than any single VA can handle.
This isn't a failure of your VA or your systems. It's a sign that your publishing business is working. The question of when to scale from one VA to a small team is one that most authors face later than they should — because adding a second person feels like a significant complexity increase, and because managing a team feels like a job description that belongs to someone else. This article addresses both of those concerns and lays out what scaling actually looks like in a well-run author operation.
Recognizing When One VA Is No Longer Enough
The signals that you've reached the capacity ceiling of a single-VA setup are usually gradual rather than sudden. The most common pattern is task accumulation: tasks that used to get done consistently start getting deprioritized, your VA's weekly updates begin noting more items carried forward to the next week, you find yourself picking up operational tasks that were previously delegated because your VA doesn't have bandwidth, and the quality of work in lower-priority areas starts slipping because there's only so much any one person can do.
Your VA is consistently working at or near their committed hours with tasks remaining undone — not because of inefficiency but because the task volume genuinely exceeds the available time
You're personally handling operational tasks that you previously delegated, not because the VA failed at them but because their plate is full of equally important work
Launch periods are particularly strained — the additional task volume of a launch week overloads a VA who is managing the baseline week adequately, which means launches produce a choice between operational quality and launch quality
Your catalog has grown to a point where consistent backlist maintenance (metadata optimization, back matter updates, promotional submissions) would consume a significant portion of a VA's hours that are currently needed for new release work
There are entire task categories from this section's list that you want addressed but that your current VA genuinely doesn't have capacity for
The Specialization Case for a Second VA
The most common mistake authors make when they decide to add a second VA is looking for another generalist — someone who can help with 'everything' the way the first VA does. This usually produces two VAs with overlapping skills and unclear ownership, and the management overhead of coordinating two people doing similar things.
The more effective model at the scale most indie authors reach is specialization: your first VA handles the functions they do well (social media, reader community, ARC coordination, newsletter), and the second VA brings specific expertise in a different area — metadata and advertising analytics, website and technical tasks, graphic design, or book launch project management. The two roles complement rather than duplicate, and the ownership of each function is clear.
Your First VA as Team Lead
One of the most underused scaling options available to authors with an established, trusted first VA is elevating that VA into a team lead or VA director role — where they take on some of the coordination and oversight of a second VA rather than requiring you to manage two separate VA relationships independently. This works particularly well when your first VA has been with you long enough to deeply understand your business, your standards, and your voice, and when they have the organizational and communication skills to coordinate with another person effectively.
The VA director model isn't right for every situation — it requires a first VA who has the skills and interest for a coordinating role, and it introduces a new dynamic into the relationship that needs to be discussed and agreed to explicitly rather than assumed. But for authors who have built a genuinely strong long-term relationship with their first VA, it's often the most efficient scaling path: your existing VA knows your systems, your SOPs, and your standards, and can onboard a second VA far faster than you could from scratch.
What Changes When You Add a Second VA
Adding a second person to your author support operation changes a few things that are worth planning for explicitly rather than discovering reactively.
Role clarity becomes non-negotiable: with one VA, ownership of any task defaults to the VA. With two, 'who handles this?' needs a clear answer for every task category, or work falls through the gaps between them
Communication structure matters more: a brief weekly team update — where both VAs share what they're working on and any dependencies they have on each other — prevents the coordination problems that arise when two people are working on related tasks without a shared picture
Your SOP library becomes essential infrastructure: the second VA's onboarding depends on the SOPs you built for the first one. This is the strongest argument for building documentation thoroughly from the start rather than assuming you'll catch up later
Your management time increases modestly, but not proportionally: managing two VAs with clear roles and good systems takes meaningfully less than twice the management time of one, because the systems handle most of the coordination overhead
Team Communication Structure
A small author support team — even two VAs — benefits from a minimal but explicit communication structure that keeps everyone informed without requiring constant coordination. The simplest version that works for most authors:
A shared task management space where all tasks are visible to both VAs — Trello, Asana, or Notion — so each VA knows what the other is working on without needing to ask
A weekly async team update from both VAs to you: what was completed, what's in progress, any dependencies on the other VA or on you, and what's planned for the coming week
A brief weekly sync between you and both VAs together — thirty minutes is usually sufficient — for anything that genuinely needs to be discussed as a group rather than handled in writing
Clear communication about task handoffs: if VA one completes a task that VA two needs to pick up (a blog post formatted and ready to be scheduled, a press release drafted and ready to send), the handoff is documented in the task system rather than communicated through ad-hoc messages
Managing the Transition Period
The transition from one VA to a team typically has a three to four week adjustment period while the second VA is onboarding, roles are being clarified, and both VAs are learning to work together. This period feels more chaotic than the steady state will be, and it's important not to interpret that transitional friction as evidence that scaling was the wrong decision.
Plan the transition deliberately: bring the second VA on during a period without a major launch in the immediate window, invest in the onboarding properly (your existing SOP library does most of the work), and communicate clearly with both VAs about how the role division works. Within four to six weeks, the team typically reaches a rhythm that produces noticeably more output than the single-VA arrangement it replaced.
Conclusion
Scaling from one VA to a small team is a business development milestone that most authors can reach faster than they expect if they're willing to invest in the systems and role clarity that make a team function. The discomfort of the transition is real but temporary; the capacity it creates is lasting. The next article covers a related question: how to invest in your VA's growth so they become increasingly valuable to your business over time rather than hitting a ceiling and stagnating.
Hello, I'm Randall Wood. When I'm not pounding the keyboard or entertaining my giant dog I like to build tools for my fellow indie authors. In these articles, you'll find lessons learned over sixteen years spent in the indie author world. I share it all here to help you get one step closer to where you want to be.— Randall