If you've ever hired a VA the traditional way, you know how it works: you define a role, you write a job description, you find someone who fits that role, and you hope they stay for at least a year. It's a static contract for a static set of responsibilities.
But your business isn't static. Your needs shift week to week. Some weeks you need heavy design support. Other weeks it's finance and operations. During a launch, everything changes again. A traditional VA hire locks you into a fixed structure that never quite matches your actual needs.
The capacity model inverts this. Instead of hiring for a role, you hire for hours. Instead of saying "I need a VA who can do design, scheduling, and customer support," you say "I need 20 hours per week of flexible capacity." Your VA adapts to what you actually need, when you need it. The structure serves your business. Your business doesn't serve the structure.
Why Traditional VA Hiring Falls Short
The traditional model treats a VA hire like a full-time employee, just without benefits. You define scope. You measure performance against that scope. If your needs change, you either renegotiate or you hire someone else.
This creates friction on multiple fronts. First, you're guessing about your future needs when you write the job description. You might think you need 60 percent customer support and 40 percent operations work. Six months in, you realize you actually need 40 percent customer support and 60 percent operations work. Your VA isn't the right fit. You're stuck renegotiating or hiring someone new.
Second, you create organizational bloat. If your VA's role is specifically defined as a scheduler, and you suddenly need design work done, that VA either says it's outside their scope or they do it reluctantly. There's role rigidity that prevents your team from being flexible. You end up hiring another contractor to fill the gap rather than flexing the one person you already have.
Third, you struggle with utilization. Some weeks your VA is overbooked. Other weeks they don't have enough to do. You're paying for a full-time slot even when the work is part-time. Or you're scrambling to find supplemental work to keep them busy. The fixed structure doesn't match the variable reality of your business.
The Capacity Model: Hours First, Tasks Second
The capacity model starts with a simple question: how many hours of flexible support do you need per week?
The answer typically falls into one of three buckets. A 10-hour package covers light operational support, basic email management, and scheduling. It's for founders who need a VA for maybe a few hours a day. A 20-hour package is the sweet spot for most growing founders. It's enough to cover customer support, scheduling, bookkeeping, and some operational work. A 40-hour package is for teams that need full-time support across multiple functions.
Once you pick your hours, your VA fills them with whatever work is most valuable that week. The schedule might look like this: Monday and Tuesday, they handle customer support and email triage. Wednesday, they dive into a project that's due Friday. Thursday and Friday, they're back to scheduling and operations work. The specific task mix adapts to what your business needs. Your VA becomes a flexible extension of your team, not a slot in your org chart.
Why This Matters: Flexibility Multiplied
The real advantage of the capacity model isn't just efficiency. It's psychological. You're not constantly negotiating scope. You're not managing role expectations. You're not thinking about whether a task is "within their job description." You simply have hours available, and you use them however makes most sense that week.
This flexibility creates profound ripple effects. Your VA can shift toward the work that's most urgent. Your team can experiment with new tasks without hiring someone new for each one. When priorities change, you don't renegotiate a contract. You just redirect the hours.
It also removes a psychological block that emerges in traditional hiring. With a role-based VA, there's often an implicit contract: you pay them to be a scheduler, so you ask them to schedule. But maybe they're actually better at operations work. Maybe they'd learn faster and produce better results if you asked them to focus on something else. But the role definition prevents that. The capacity model has no such ceiling. Your VA grows into whatever the business needs them to do.
Reducing Scope Creep and Setting Clear Expectations
The capacity model also makes scope creep impossible. You have a set number of hours per week. Your VA allocates them to whatever's most valuable. But there's a natural limit. When you've used your hours, you've used them. You're not asking for "just one more thing" indefinitely. There's a hard boundary.
This creates clarity. You know what you're paying for. Your VA knows what they need to deliver. There's no ambiguity about whether a task is included or extra. The hours are the boundary. Everything else is just how you choose to allocate them.
This also prevents the slow erosion of value that happens in traditional hiring. On a role-based contract, there's constant pressure to add tasks. "As long as you're here, can you also handle this?" Over time, scope expands without compensation increasing. The capacity model prevents this. You have a set allocation. You use it intentionally. You don't overload your VA or yourself wondering whether you're extracting fair value.
Choosing Your Capacity Level
The choice between 10, 20, and 40 hours depends on your business stage and your specific needs.
A 10-hour package works if you're an early-stage founder who needs someone to handle your calendar, filter email, and manage basic operations. You're probably doing most of the strategic and high-leverage work yourself. Your VA is purely tactical support.
A 20-hour package is right if you're generating enough work that you need consistent support across multiple functions. You might need a mix of customer support, operations work, scheduling, and basic bookkeeping. A 20-hour VA can handle this without being stretched too thin. They can maintain quality across all areas and still have flexibility for unexpected priorities.
A 40-hour package makes sense if you need full-time coverage. You have enough work volume that one person can work full-time and still be fully utilized. You get the deepest relationship, the most institutional knowledge, and the most hands-on partnership.
Most growing businesses start at 20 hours. It covers the work that's keeping you from scaling without being so much that utilization becomes a problem. As you grow, you might move to 40 hours. Or you might bring on a second VA at 10 or 20 hours depending on what you need.
The capacity model's beauty is that you're never guessing about roles or trying to fit your business into a job description. You're starting with hours and letting the work define itself. That's how you build a structure that actually fits your business.