The Founder's First-PM Timing Rule
The founder IS the product manager until scale forces the handoff — around 20 to 25 engineers.
- Difficulty
- Easy
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 88%
Cagan actively discourages founders from hiring product managers too early, and gives a clear reason and a clear trigger. Value and viability are the founder's job in an early company; bringing in a real product manager to own them creates too many cooks and conflict. The trigger to hire is scale — roughly 20 to 25 engineers, and generally after product-market fit, when the founder can no longer personally carry value and viability across products and markets.
Origin
Marty Cagan (SVPG), responding to the recurring founder position of 'we will never hire PMs' — a stance he partially endorses, then bounds with a scale trigger.
Core principles
- 01Value and viability is the founder's job in an early company — a real PM would be competing for it.
- 02If a founder hires a PM as a project manager, they are overpaying, though it may still relieve the CEO's calendar.
- 03The hiring trigger is engineering scale, not headcount ambition or investor expectation.
- 04Product-market fit is not a finish line — you then do it again for other products and markets.
How to run it
- 1
Determine which kind of PM you would actually be hiring
Decide whether you want a real product manager (owns value and viability) or a project manager in a PM title. The advice diverges completely: the first conflicts with the founder early; the second is cheap help you are probably overpaying for.
Pro tip Project-management help can be a legitimate purchase — it is just not a good use of the CEO's time to do it yourself.
Watch out Most founders who say 'PMs slow us down' have only ever met the second kind.
- 2
Keep value and viability with the founder pre-scale
While the company is small, the founder or co-founder should be the product person, personally owning whether the thing works for the customer and for the business.
Watch out Bringing in a real PM here usually causes conflict — too many cooks in the kitchen.
- 3
Watch the engineer count as the trigger
Use the number of engineers as the practical signal. Cagan's rule of thumb: up to roughly 20 to 25 engineers, it is a lot better if the founder or co-founder is the product person.
Pro tip Post-product-market-fit is the other marker — at that point you are extending into other products and markets, and one person cannot carry value and viability everywhere.
- 4
Hire a real product manager and hand over deliberately
Hire someone who can genuinely own value and viability, and transfer that ownership rather than inserting them between the founder and the product — which just slows everything down.
Watch out If the new PM does not understand real product management, you get a different and worse set of symptoms rather than relief.
In the wild
Lenny notes a repeated pattern among his guests: founders who insist they will never hire product managers eventually bring one in and say 'why didn't I do this earlier — this is exactly what I needed'.
→ Cagan's explanation: they hired at the point where they had outgrown their own capacity to carry value and viability, which is precisely when a real PM starts adding rather than subtracting.
A founder brings a real product manager into a small, pre-scale company. The PM's job is value and viability — but so is the founder's, and neither will yield.
→ Conflict and slowdown: the PM ends up positioned between the founder and the product, which is exactly the 'PMs slow us down' experience founders complain about.
Common mistakes
Hiring a PM to relieve founder workload before scale
The workload the founder wants relief from is usually project management. Hiring a real PM for it creates a role conflict over value and viability instead of relief.
Concluding 'PMs are bad' from one premature hire
The premature hire fails for structural reasons — the founder still owns the job. That is not evidence about the role at scale.
Treating product-market fit as the end of the founder's product work
As soon as you have PMF you start working on other products and other markets, so the founder's product judgment stays in demand; the PM hire distributes it rather than replacing it.
Is it for you?
Best for
Founders and early CEOs deciding whether and when to make their first product management hire
Not ideal for
Large or non-tech-native companies already past scale, where the question is quality of the PM competency, not timing of the first hire
From the transcript
“I'm one of the people that tries to discourage them from hiring product managers too soon”
“if they're a real product manager and they're woring about value and viability”
“it's too many cooks in the kitchen you need to reach a certain scale before you it helps you to have other people responsible for…”
“just to look at the number of Engineers at a certain number of Engineers usually like 20 to 25”
From the episode
Product management theater
Marty Cagan (Silicon Valley Product Group)