Team Sizing Calculator
Find the right PM-to-engineer ratio and team structure for your product org.
Agent-assisted engineering
Coding agents change how much reviewable output each engineer produces, so they change the ratio. Review is the part teams forget to count.
DORA measured median review time up about 91% as AI adoption rose. Whatever review cannot absorb is queued, not shipped.
Recommended PMs
7
at a 1:5-8 PM-to-engineer ratio
Your 40 engineers produce roughly the reviewable output of 45 at 30% agent assistance, a 12% lift after review drag. That output is what the PM count above is sized against.
Designers Needed
6
0.75:1 designer-to-PM
Suggested Squads
7
~6 engineers each
Current Ratio
1:10
1:11 counting agent output
Staffing Status
Understaffed
3 PMs short
Staffing Assessment
Your team is 3 PMs short. PMs are likely spread too thin across products, leading to shallow discovery and reactive prioritization. Consider hiring or reducing product scope.
Squad size of ~6 engineers is healthy. Small enough for autonomy, large enough to ship.
3 products across 7 PMs gives clear ownership per product area.
Suggested Team Structure
Industry Benchmarks
| Company Stage | Engineers per PM | Typical Squad Size | Designer Ratio |
|---|---|---|---|
| Startup (1-50) | 4-6 | 7 | 0.5:1 |
| Growth (50-200)(yours) | 5-8 | 9 | 0.75:1 |
| Scale-up (200-1000) | 7-10 | 11 | 1:1 |
| Enterprise (1000+) | 8-12 | 12 | 1:1 |
Sources: industry surveys from major tech companies. Actual ratios vary by domain, technical debt, and product maturity.
Email Me These Results
Get your calculation + related frameworks and templates.
Get this + weekly PM tools and templates.
How to Size Your Product Team
Getting the PM-to-engineer ratio right is one of the highest-impact org design decisions. Too few PMs and engineers build the wrong things. Too many PMs and you get coordination overhead with unclear ownership.
The right ratio depends on your company stage, product complexity, and how many distinct products you support. Startups typically run lean at 1 PM per 4-6 engineers because PMs wear multiple hats. Larger orgs settle around 1 PM per 8-12 engineers where each PM has deeper domain focus.
For a deeper look at structuring product teams, read our guide to building a product team. To measure whether your team structure is working, track the right product metrics. If you are hiring PMs, our resume scorer can help screen candidates faster.