Why does hiring a third PM never fix it?

The pattern repeats almost identically between $2M and $15M ARR. A founder hires the first product manager to get tickets organised, the second to cover a second product area, and the third because the first two are drowning. Each hire made the team busier and the roadmap longer, and none of them made the company more decisive, because all three are prioritising inside their own lanes while the lane map itself belongs to nobody. Sales still routes large-customer requests straight to engineering. The founder is still the tiebreaker on everything that matters.

That is not a capacity problem. Three product managers on senior PM salaries, which run approximately $150,000–$190,000 a year in base pay in the US with benefits, bonus and equity additional, is most of half a million dollars a year of capacity already inside the building. Adding a fourth buys more of the thing you already have too much of. Direction is a different job, and nobody in that structure is doing it.

How do you test whether the problem is capacity or direction?

Score one point for each honest yes. Ask the questions of two or three people separately rather than in a room together, because the disagreement is the diagnostic. If the answers differ, the strategy exists in one person's head rather than in the company, and that is functionally the same as not having one.

• Is there a written product strategy that has said no to something real in the last quarter?
• Can your PMs name the top three customer problems in priority order, and do their answers match each other?
• When sales escalates a customer request, is there a process that decides, or a person who absorbs?
• Did the last major roadmap change come from customer evidence rather than the loudest voice in the room?
• Does anyone review outcomes, rather than shipping, on a monthly cadence?

Four or five points: you have direction. The bottleneck is genuinely capacity and the next hire is a product manager. Zero to three points: more PMs will generate more roadmap and less progress. Fix direction first, then measure the workload again a quarter later, because the number usually falls without anyone leaving.

What does each option cost over a year?

The four options below differ more in what changes inside 90 days than in what they cost, which is the opposite of how most founders weigh them. Note that the cheapest and the most expensive options both take a year or more to produce direction, and the two in the middle differ mainly in whether you wait through a search first. Compensation figures are US base or base-and-cash pay, with benefits, bonus and equity additional in every full-time row.

Swipe the table sideways to compare →

The fractional row is our own engagement, priced here so the comparison is like for like. Sivan Kadosh, a fractional Chief Product Officer for B2B SaaS companies between $2M and $15M ARR, works at $8,000 per month for 20–25 hours, which is $96,000 across a year and $48,000 for the 6-month standard term. The first 60 days run 60–80 customer and prospect interviews, because the direction problem this page describes is almost always an evidence problem underneath. Our diagnostic on which title the role should carry covers it in detail.

Why does promoting your strongest PM usually stall?

It works eventually, and it fails on the calendar. A first-time head of product learns stakeholder management, strategy and how to say no to the founder all at once, in public, while the company watches. If your growth maths can absorb 12 to 18 months of that learning curve, promote and support them, because a leader grown internally understands the product and the customers in a way no external hire will for two quarters. If the board conversation is this year, pair the promotion with senior part-time leadership so the promoted PM grows under someone who has run the play, and you do not lose the year finding out.

The sequencing point matters more than the choice. Hiring the leader first and letting them shape the next PM role, write the scorecard and run the loop is consistently stronger than hiring the PM first and asking the leader to inherit them. Leaders inherit teams. Good leaders design them, and the design starts with the next requisition.

Frequently asked questions

These four come up in almost every version of this conversation, usually in this order: the team says it is drowning, the founder wonders whether a part-time leader can really manage people, someone asks whether both hires can happen at once, and finally somebody asks what happens to the PMs already there.

Our PMs say they are drowning. Doesn't that prove we need capacity?

Drowning is what missing direction feels like from inside the team. Product managers without a strategy have no basis for declining anything, so demand is infinite by construction and every request becomes theirs, which is the same mechanism described in our piece on the founder bottleneck. Install direction, then measure the workload again a quarter later. If it is still overwhelming, the capacity case is now real and evidenced.

Can a part-time leader actually manage our existing PMs?

Yes, and at 20–25 hours a month that is precisely the model: the leader sets direction, makes the calls and coaches, while the product managers execute. It stops working the moment you also expect the fractional leader to write every specification, because that is execution capacity at executive rates.

Should we hire both a PM and a leader together?

If the budget allows, hire the leader first and let them define and run the PM search. The role gets scoped by someone who knows what the team is missing, the interview loop tests for it, and the new PM arrives into a structure rather than into a queue.

What happens to the PMs we already have?

In the version that works, they get better fast, because the ambiguity that was making their job impossible is removed by someone senior. In the version that fails, the fractional leader is used as extra hands and nothing above them changes. Our guide to when to hire your first product leader covers the transition in detail.

The question is almost never how many product managers you have. It is whether anyone is accountable for what they collectively decide not to do, and if the answer is nobody, a fourth hire will simply widen the surface area of the same problem.