Head of product vs CPO: the title that actually matches your problem
Founders default to 'CPO' because it's the title they've heard, but most companies with fewer than fifteen people don't need one yet. A CPO's job is company-level product strategy, board exposure and often a seat in fundraising conversations. A head of product's job is running the team that turns strategy into shipped software. If your problem is 'my PM needs a manager', not 'nobody knows what we're building and why', you need a head of product.
The confusion usually shows up in job specs that ask for CPO-level strategic ownership at a head-of-product salary, or vice versa. Get the title wrong and you either overpay for strategic capability you don't need day-to-day, or you hire someone too junior to actually lead the team you have. A fractional engagement lets you try the right level of seniority without committing to a permanent title before you're sure which one fits.
In practice, many companies need both roles eventually, and often the CPO comes first — setting direction — with a head of product hired or promoted later to run delivery once there's a team big enough to need managing. If you're a five-person company with one PM, you almost certainly need a head of product before you need a CPO.
What good product leadership below CPO level looks like
A good head of product makes the team faster without making the roadmap theirs to reinvent every quarter. That distinction matters. Too many senior product hires arrive and immediately want to rewrite strategy, which is disruptive if the strategy was fine and the problem was execution. The job is to take direction, translate it into something a team can build against, and hold the line on quality and sequencing when everyone else wants to add just one more thing.
Concretely, that means specs an engineer can build from without a follow-up meeting. It means 1:1s that leave a PM clearer about what good looks like, not just what's overdue. It means being the person who tells sales 'no, not this quarter' so the founder doesn't have to, and being right often enough that the answer sticks.
It also means knowing when to escalate. A head of product who quietly absorbs a broken strategy and tries to execute it anyway is doing the company a disservice. Part of the value of bringing in someone experienced is that they've seen enough roadmaps to say clearly when the underlying plan, not the team, is the problem.
When a part-time head of product works, and when it doesn't
- —Works well: you have one to three PMs already shipping something, and the gap is leadership, quality and rhythm rather than direction.
- —Works well: you're between permanent hires and need continuity so the team doesn't drift for three months during a search.
- —Works well: you want to test whether a full-time head of product role is justified before committing to the salary.
- —Doesn't work: you have no PM at all and need someone hands-on writing every ticket — that's closer to a senior PM contractor, not a fractional leader.
- —Doesn't work: the real problem is that engineering leadership and product leadership disagree on priorities — that's a founder-level conflict a part-time hire can't resolve alone.
- —Doesn't work: you want someone in every stand-up, every day — at that point you need a full-time hire, not fractional coverage.
How the engagement is structured week to week
A typical two-day-a-week retainer splits roughly into a day of team leadership — 1:1s, backlog review, unblocking whatever's stuck — and a day of representation and delivery: cross-functional meetings, spec review, stakeholder updates and the admin that keeps the function legible to the rest of the business.
Unlike a strategy-heavy CPO engagement, most of the value here compounds through consistency rather than big set-piece decisions. The team gets measurably better at estimating, writing specs and prioritising because someone senior is reviewing that work every week, not because of a single strategy offsite.
The exit is usually cleaner than a CPO engagement too. Either a PM has grown into the role under supervision, in which case the handover is a formality, or we've defined the role precisely enough from lived experience that hiring for it externally is straightforward and fast.