When to hire a Head of Product — and the two signs you're too early

5 min read

The four signals that founder-led product has run out, what the role has to own on day one, and why hiring the title before the function exists is the most expensive mistake in this decision.

Founders usually ask this question about six months after the answer became yes, and they ask it in the wrong form: are we big enough for a Head of Product? Size is a poor proxy. I’ve seen the role work at fifteen people and fail badly at eighty.

The better question is about your own calendar: how much of the product decision-making still routes through you, and what is that costing the things only you can do?

The four signals it’s time

1. You’re the bottleneck on decisions you don’t care about. Not the big bets — those should still be yours for a while. It’s the twenty smaller calls a week: which of these two flows, what happens to the edge case, whether this is worth a sprint. If those queue up waiting for you, the company is paying founder time for mid-level decisions.

2. You have more than two PMs and nobody senior is managing them. PMs reporting to an engineering lead or directly to a founder is workable at one or two. At three it stops working, because nobody is comparing their work, nobody is developing them, and nobody notices when two of them are solving the same problem differently.

3. Nobody can say no. If every request from sales, from the board, from a named customer lands in the sprint, you don’t have a prioritisation problem — you have a missing owner. This is the signal I’d weight highest, and it’s the one founders most often misdiagnose as needing better process.

4. You can’t answer “why this and not that” for the current roadmap. Not because it’s wrong, but because the reasoning lives in your head and has never been written down. A function can’t scale on undocumented judgement.

If two of those four are true, the answer is yes and has been for a while.

The two signs you’re too early

You haven’t found product-market fit. Before fit, product decisions are the founder’s job, and delegating them is delegating the company’s central bet. A Head of Product hired pre-fit either becomes a very expensive project manager or starts making the bet for you, which is not what you wanted. Hire senior product help pre-fit as a consultant or advisor, not as an owner.

You want them to make the product decisions you’re avoiding. Some founders reach for this hire because product feels hard and they’d like it to stop being theirs. That hire fails in month four, every time, because you’ll override them the first time you disagree — and the whole company will watch you do it.

The honest test: can you name a decision you’d let this person make that you’d disagree with? If not, you’re hiring a translator and should say so in the job description.

What the role has to own on day one

If you can’t hand over all four of these, you’re hiring the title without the function:

  • Prioritisation, with the authority to refuse things. Including from sales. Including from you, occasionally.
  • The product team’s performance and development. Real management, not coordination.
  • The operating cadence — planning, discovery, reviews. How decisions get made repeatably.
  • Stakeholder alignment across exec. They represent product in the room; you stop being the only translator.

Write those four into the role description. It reads as unusually blunt next to the average job ad, and that’s the point — the candidates worth having will recognise it as a real job rather than a title.

Head of Product, VP, or a senior PM?

The most common over-hire in this decision is buying a VP because it sounds serious.

  • Senior PM — you need one more pair of hands and someone to own an area. Cheapest, fastest, and often the right answer at 15–25 people if you’re still close to the product.
  • Head of Product — you need the function to exist: someone to manage PMs, own the cadence, and hold prioritisation. The right answer for most companies asking this question.
  • VP / CPO — you need someone to build an organisation of managers and sit in a real exec seat. Below about 8–10 product people this is over-hiring, and the person will be bored inside a year.

A VP hired into a Head of Product job leaves within eighteen months. It’s an expensive way to find out you needed the smaller hire.

A good Head of Product search runs four to six months, and the cost of the vacancy is usually invisible in the plan. Meanwhile the roadmap drifts, engineering picks its own priorities, and the reasons you started the search get worse.

Two ways people bridge it, both legitimate:

  • Promote internally and support them. Cheapest, best for morale, and the main risk is that the job changes shape at that step in ways nobody warns them about. A first-time head of product with an experienced advisor for a quarter is a far better bet than one without.
  • Bring in interim cover. More expensive per day, and it does something a vacancy can’t: the interim usually ends up writing the role description and helping hire their own replacement, because by month two they know what the role actually needs — which is more than a job ad written before anyone understood the problem.

The difference between interim, fractional and consulting matters here, because most people bridging a search ask for the wrong one.

Getting the hire right

Whichever route you take, the process is where most of these go wrong — the default interview loop tests presentation skill rather than judgement. The four-stage process and the questions that separate candidates apply to a Head of Product hire with one addition: ask them to critique your current roadmap in the interview, out loud, in front of you. The good ones will do it. How they do it tells you everything about whether they’ll survive the first disagreement.