When to Hire a Fractional CPO (And When Not To)

Most founders decide this backwards. They work out that a full-time CPO is out of budget, and fractional becomes the consolation prize. You'll get a bad hire that way at any price, because budget was never the thing to solve for.

When product needs an owner you have three options: hire full-time, bring in a fractional, or promote someone you already have. Each one is right somewhere, each one fails somewhere, and the failures are predictable enough to plan around.

The three options

Fractional isn't a discount on a full-time hire

On the numbers it looks like one. A full-time CPO runs somewhere around $250,000 to $500,000 a year before equity in the markets where that role is competed for hardest, and the search takes six to twelve months. Fractional costs a fraction of that and starts in weeks.

It still works only when the situation is genuinely temporary. A gap, a transition, a specific phase. It doesn't work as a cheaper way to fill a role you need permanently, and founders try that constantly.

The test is whether you can name the end. If you can say what has to be true for the engagement to be over, fractional fits. If you're honest and the answer is that you'll need this person indefinitely and you're hoping the budget improves, you're deferring a full-time hire. The deferral usually costs more than the hire would have.

Promote from within, if you can

Nobody sells you this option, which is why it gets skipped, and it is often the right one.

If you have a director who could run the function in twelve months, the question isn't whether to hire above them. It's whether anyone is available to close those twelve months. Hire a full-time CPO over a nearly-ready director and you usually lose the director. Promote them into a job they can't do yet and you lose a quarter, plus some of their standing with the team.

What works is a fractional who holds the function, develops the internal candidate on purpose, and hands over. Treat the handover as the deliverable rather than a courtesy at the end. If a fractional won't put that in writing, they're selling you a seat.

The rest of this assumes you've landed on fractional.

What a fractional CPO actually owns

A fractional CPO owns a function. One or two days a week, three to twelve months, operating as a principal: in the leadership meetings, making the calls, managing the team, setting direction. That's the line between this and consulting, and it's worth being blunt about it. A consultant advises and hands you deliverables. A fractional executive carries the outcome. Put that in the contract rather than leaving it in the conversation.

The presenting problem usually isn't the real one. A founder says they need someone to run the roadmap. What they need is someone to make the decisions everyone has been avoiding for months, then stop them piling up again.

What the engagement actually looks like

The first two weeks are diagnostic. Mapping the team, reading the current state, finding where decisions are stalling. After that it's execution: owning the operating rhythm, making the calls.

The most common version is a founding CEO who has run product for three years and can't hand it over. The other is a technical founder who built everything and never built the organisation around it. Either way the first fortnight goes on making implicit decisions explicit, which doesn't mean writing documentation. It means making the thinking visible so the team can act on it.

One or two days a week sounds thin until you see what it's spent on. A fractional isn't doing the function's work. They're deciding, sequencing and unblocking, and the team does the work between visits.

Is it a CPO or a CTO you need?

These two get confused, and it's expensive, because from the outside the failure modes look identical. Delivery is slow, the roadmap keeps moving, and nobody in leadership can say why.

The product version: the CEO was the product vision from day one, and holding a vision isn't the same skill as running the function. Conflating those two is where the gap opens, and it's why the gap takes so long to admit. Roadmaps exist, but nobody can explain how an item got its position. Discovery is whatever the loudest customer said most recently.

The engineering version: the technical founder built the product well, then the organisation outgrew what one person can hold in their head. Architectural decisions that looked reversible turn out not to be. The team structure that worked at fifteen people breaks at thirty.

If both are true, start with whichever is costing more right now.

Match the operator to your stage

The wrong fractional CPO costs you months, and usually not because they're bad. They were optimised for a stage you're not at. A pre-PMF engagement looks nothing like a scaling one, and neither looks much like an enterprise transformation. Same diagnostic, different job.

Pre-PMF

You want someone obsessed with customer discovery and ruthless about prioritisation. Premature structure is lethal at this stage, and the wrong hire builds it on autopilot, because building it is what made them good somewhere else.

The failure mode is hiring for the stage after this one. A systems builder arrives, sees no process, and builds one. That reads as progress right up until you notice it has locked in assumptions the company hasn't earned yet.

Scaling SaaS

PMF is confirmed. Now it's org design, analytics, monetisation, and a hiring engine that survives headcount doubling. Most Series A and Series B companies break here.

The tell that you're at this stage and not still pre-PMF: the hard questions have stopped being about what to build and started being about who gets to decide. When the roadmap looks reasonable but nobody can explain how an item got onto it, that's an org design problem wearing a product costume.

Enterprise, AI or deeptech

Technically deep product, long sales cycles. The job is sequencing roadmap against procurement timelines, and making a security feature land with a CFO. Technical product depth is the entry requirement here rather than a nice extra.

The cycles run long enough that a sequencing mistake takes a year to show up, so you don't get the feedback loop that would normally correct it. Judgement about order has to do that work instead, and it comes from having been wrong about it before in this domain specifically.

Founder-led

Product, go-to-market and operations run together. Someone who tidies one without understanding how they connect will quietly break the others, and you won't notice until it's expensive.

The risk is a specialist who's excellent inside their own lane. They clean up the product, the go-to-market motion that depended on the old product shape stops working, and nobody joins those two facts up for a quarter. You want someone who asks what else moves before they move anything.

Three questions before you sign

• What would you stop doing in your first month? If you're pre-PMF and the answer is a process, keep looking.
• What does the end of this look like? A fractional who can't describe their own exit is describing a retainer.
• Which of these stages have you operated in? Operated, not advised.

When fractional is the wrong answer

The role is permanent and you already know it. Run the search instead.

You want someone to confirm a decision you've already made. That's a second opinion and it costs less.

Nobody internal has the time. A fractional working one or two days a week needs the other three to move without them. If the function stalls whenever they're not in the room, you've bought a dependency.

The measure of a good engagement is the exit. If the departure causes a regression, it didn't work. What you're paying for is a function that keeps running once the fractional is gone.

SHA/RP is Raphaël Peyret's advisory practice. Originally from France, based in Dubai, UAE, with operator experience across the GCC, UK, US, Australia, Singapore, and Southeast Asia.