Skip to content

When Should Your Startup Hire a Head of Product? - ProductFTW #73

It's about complexity, not funding stage.

🖇️
Did someone forward this to you? Subscribe to ProductFTW today.

As a follow-up to ProductFTW #70, Do Startups Need Product Managers?, I was asked: when should a startup hire a head of product? I wrote about this topic years ago on my personal blog in Startups and Heads of Product, but it was more pondering than prescriptive.

Ellen made the case in #70 that startups "need to hire a Product Manager when misalignment starts costing real money." I made the case in my personal post that you can hire a head of product on day one. This disconnect leads to two key questions:

  • What exactly is a "head of product"?
  • When is a single PM not the head of product?
As an aside, does anyone else find the title "head of" to be quite amusing? According to my research assistant Claude, the shift from traditional "VP" titles to "head of" titles occurred in the 2008-2015 era, driven by a push for flatter organizations (à la Zappos) and greater title flexibility. Clearly, a future post is in the making on Head of Product vs. CPO.

In startups without a Chief Product Officer, the Head of Product is the de facto leader of the product organization. This person is responsible for leading the product team, organizing the product roadmap, and ensuring that product management processes are followed.

Office hallway with a wood door at the end. The door has a window and on the window is a sign reading "head of product."

So if a startup has only a single PM, are they not, logically, the head of product? Well, yes and no. In a small startup — especially one without a CEO with a product background — the PM is typically responsible for the day-to-day product work: developing requirements, collaborating with engineering, and so on. In that sense, they share some responsibilities with a head of product. But at this stage, the CEO typically owns the roadmap itself. The PM is more of an execution-focused resource than a strategic one.

When a company needs a head of product isn't simply a matter of funding stage (people often ask me: is it Series A? Series B?), but of the size and complexity of the product and organization.

What does Series A mean anymore anyway? Marketing has driven a long slide in the definition of equity rounds. While Series A used to denote the first institutionally-backed venture capital round, typically around $5MM, we now have Series Seed, Pre-Seed, and probably soon something like Series Just an Idea. If I raise VC again, I want to convince my investors to let me start at Series Z and work backwards.

With ongoing changes in product development driven by LLMs, it's genuinely unclear how these roles will evolve. Traditionally, I would have said that once a company has at least three or four product development teams (pods, squads, whatever you call them), you start to need a head of product.

In that construct, the head of product looks a lot like a Group PM at a larger company: responsible for managing a small team of individual contributor PMs, aligning cross-team interactions, ensuring consistency in process and artifact development, and maintaining the roadmap.

Note, I said maintaining the roadmap, not owning it; that probably still sits with the CEO. Maintenance means keeping it current, surfacing trade-offs, and connecting the dots across teams.

If you have three or four squads, you likely have either a growing and complex product or more than one product line. That's the real inflection point. When a PM's scope is narrow (we just make this one app), it's easier to scale without adding a management layer. When does complexity typically demand it? Usually, when revenue exceeds $10MM annually, or fundraising is at Series B. OK, there's your answer.

You'll often see the title appear earlier, because people love titles (even people who say they don't). We're social, status-driven creatures, and it matters. A strong PM who joins early may ask for and receive the "head of product" title over time, even if the role doesn't fully justify it yet. We hand out co-founder titles like CEO and CTO when there are only two people in the company, so it's nothing new.

If you're weighing whether you need a head of product, focus more on specific responsibilities, team size, and product complexity than on the funding stage. A good leading indicator: when the product team starts to feel disconnected or uncoordinated, that's usually the right time to bring in someone who can manage it all.

About ProductFTW

ProductFTW is a weekly newsletter about product management, with a focus on real-life experiences in startups. We want to help product leaders be successful by giving realistic approaches that aren’t for giant tech companies. We know you don’t have a full-time product designer on each team. We know your software probably hasn’t been used by millions of people worldwide–yet. We’re here to bridge the content gap from building your product and team to scaling it.


Part of the Product Management Leadership & Career Guide — ProductFTW's collected essays on the PM role, leading without authority, hiring, and getting hired.

Subscribe to ProductFTW

Don’t miss out on the latest posts. Sign up now to get access to the library of members-only posts.
[email protected]
Subscribe
Start typing to search...