SaaS Product Team Ratio Benchmarks
Compare your engineer, product and design headcount against the ratios a team of this size usually needs, and see which one is actually binding.
What this calculates
This divides your engineering headcount by your product and design headcount and places each ratio against a working range. The ranges are the conventions used by product organizations at this size, not measurements from a survey. A ratio outside its range is a signal about where work will queue, not a hiring instruction.
For a B2B SaaS product organization with 20 engineers, 2 product managers and 1 designer, the ratios are 10.0 engineers per product manager, 20.0 engineers per designer and 2.0 product managers per designer, which puts design furthest outside its working range.
Your numbers
Who ships
Results update as you type. Nothing is sent anywhere, the calculation runs in your browser.
Team shape against working ranges
LiveEngineers per PM
10.0
Above range
ideal 5 to 9
Engineers per designer
20.0
Far above
ideal 4 to 8
PMs per designer
2.0
Above range
ideal about 1 to 1
- PMs for 9 engineers each
- 3 (add 1)
- Designers for 8 engineers each
- 3 (add 2)
At risk
Design is the binding constraint here, not product management. One designer against twenty engineers means specifications arrive without interface decisions made, and engineers make those decisions anyway while they build. That is where the rework comes from. Fix this ratio before adding another PM, because a second PM will only produce more work for the same designer.
Pressure-test this against your real numbers
Thirty minutes on whether the next hire is a PM, a designer or neither.
No email required to see your result. The field above exists only if you want a copy.
How is this calculated?
Three divisions and three comparisons. Each ratio is placed against a working range, and the status word describes direction rather than health, because a ratio can be wrong in either direction and the two problems look nothing alike. The binding constraint is whichever ratio sits furthest outside its range in proportional terms, since that is the one that will queue work first.
Formula
Engineers per PM = engineers ÷ product managers Engineers per designer = engineers ÷ designers PMs per designer = product managers ÷ designers A ratio more than 50% above the top of its range is reported as far above rather than above.
- Headcount means people who ship. A head of product who does not own a surface is not a PM for this purpose, and a contractor at half time counts as half a person.
- The ranges describe a product organization building one connected product. A company running several independent products needs the ratios computed per product, not across the whole company.
- Platform and infrastructure engineers are included in the engineering count even though they consume less product management. If they are more than a third of engineering, run the numbers again without them.
- Nothing here measures seniority. One experienced PM covering nine engineers works. Two junior PMs covering the same nine usually does not, and the ratio cannot see the difference.
When this number misleads
These ratios describe capacity, not quality, and capacity is only the constraint when the work is well understood. A team of twenty engineers with one designer and a mature design system can outrun a team of ten with two designers and no shared components. If your ratios look bad and the work still ships cleanly, believe the work. The ratio is describing a risk you have already mitigated some other way.
Questions founders ask about this
Which ratio should I fix first?
The one the verdict names, which is whichever sits furthest outside its range in proportional terms. Fixing a ratio that is slightly high while another is far high produces no visible change, because the queue simply moves to the constraint you did not address.
Do these ranges change with company stage?
The engineer-to-PM range widens as a company matures and the product surface stabilizes, because more of the decision-making is settled. Early on, when everything is still being discovered, the same PM covers fewer engineers well. Treat the low end of each range as the early-stage figure.
We have no designers at all. What then?
Then the tool cannot compute two of the three ratios, so it treats the count as a minimum of one. That is a signal in itself. Below roughly eight engineers a founder can carry the design decisions. Above that, someone is making them whether or not it is their job.
Do you store what I enter?
No. The calculation runs in your browser and nothing is transmitted. Your last inputs are saved in your own browser so the page remembers them when you return. If you use the email field, only the result summary and your address are sent.
Book a 30-minute product strategy session
Bring the shape of your team. We will work out which hire actually unblocks it.
Book a strategy sessionNo pitch deck. No follow-up sequence.