Capacity planning is where most growth-stage teams quietly lose months. Roles get opened the week they are already needed, contractors are bolted on without a delivery plan, and three quarters later nobody can explain why the roadmap slipped.
A staffing model fixes this by tying headcount decisions to delivery milestones instead of gut feel. Done well, it gives you a forward view of where capacity is about to become the constraint, and enough lead time to act before it bites.
Start from the roadmap, not the org chart
The instinct is to plan staffing as a fixed structure: so many engineers, so many designers, a manager per pod. That structure is an output, not an input. Begin instead with the delivery commitments for the next two to three quarters and work backwards into the capacity each one demands.
For every major initiative, estimate the shape of the team it needs and the window it needs them in. Now the gaps are obvious, and you can decide deliberately how to fill each one.
Decide the full-time vs. contract mix on purpose
Not every gap should become a permanent hire. The useful split is durability: work that is core and ongoing argues for full-time, while bounded, specialist, or uncertain work is a strong fit for augmentation.
- Core, long-lived ownership — hire full-time and invest in ramp.
- Specialist skills needed for one phase — augment, then taper off.
- Uncertain bets you may kill in a quarter — contract before you commit.
- Pure overflow against a fixed deadline — augment to protect the date.
Treat capacity as something you forecast, not something you react to. The lead time you buy is the entire point.
