What does a fractional Chief Product Officer do?
By Raphaël Peyret ·
A fractional Chief Product Officer (CPO) leads product part time: the founder keeps the vision, the team gets decisions it can act on.
A fractional Chief Product Officer (CPO) does a product leader's job for a startup, part time. The founder keeps the vision. The fractional CPO turns it into decisions the team can act on: what gets built, for which customer, and how product and sales work toward the same buyer. They work alongside the founder and the team for a set number of days a month or a week, instead of joining full time. The aim is a stronger team, not another chef in the kitchen.
The job exists whether you hire for it or not
Building has never been cheaper. Choosing what to build is as hard as it ever was, and every team in the company has an opinion on it. Sales wants the feature from last week's deal. Customer success wants the fix their accounts keep asking for. Tech wants to try something new. The founder has the vision.
Someone has to make the call. With no CPO, that someone is the founder, on top of everything else. Some of those calls will be instinct. That's fine. What matters is that the team can tell an instinct from a plan, and that sales hears about the decision, and the reason, before customers do.
What it costs when nobody owns it
It never shows up as a line on the budget. It shows up as time:
- Months spent chasing a customer who was never going to buy.
- A way of working that got you to product-market fit, stretched until it breaks as the team grows.
- Engineers building for one buyer while sales pitches another. You pay both teams, and the work cancels out.
- An enterprise deal that stalls at the security and AI questions because nobody prepared the answers.
Fractional CPO or full-time CPO?
A full-time CPO makes sense, and it's expensive. It's also two jobs in one. Running product day to day is one. Building the product function is another: establishing product as a role in the company, and taking the day-to-day product decisions over from the CEO. The person who builds the function isn't always the person who should run it.
The takeover is where it goes wrong. The usual failure is a product lead who defers to the CEO and ends up project-managing the CEO's ideas. Knowing that doesn't prevent it, because the setup pushes them there. The CEO holds the vision and the final say, and the new hire is on trial. Pushing back on the person who decides whether you stay is a risk few take early. And when the new hire is slow, it's quicker for the CEO to step in, just this once. By the time it's a pattern, you're paying for a senior product lead and getting a coordinator, the CEO's time hasn't freed up, and the hire looks wrong when the setup was the problem.
I've seen the other side of this: a company's first product lead spending months just proving the role should exist.
What I put in place with a team in the first 90 days:
- A written split of what the product lead decides and what stays with the CEO.
- An agreed way to settle disagreements, so the product lead pushes back instead of scheduling the CEO's ideas.
- A product lead making day-to-day calls without routing them through the CEO.
Building that is the job of an experienced fractional CPO. Once it's in place and the mindset is set, a well-trained, more junior product lead can run it.
The roadmap: why the important thing keeps slipping
Every request that reaches your engineers comes with a person and a good reason: a paying client, a deal, a renewal at risk. Each yes makes sense on its own. But every yes is also a no to something else, said out loud or not. The product that matters for the company's future has nobody pushing for it in a given week, so it collects those silent noes, one at a time. The roadmap drifts toward a few clients' needs while the strategic work slips a quarter at a time.
The fix is method, not willpower: rules agreed in advance for what jumps the queue, and a fixed rhythm for re-planning. And sometimes it means cutting. I've been in a company with three products, each with backers, and the resources to win with maybe one. We cut two. The one we kept is the one that got the company acquired.
Two questions to ask this week
- What's the company, in one sentence? Who it's for, and what changes for them. If it's fuzzy, the roadmap and the pitch will be too.
- Do product and sales describe the same customer? Ask them apart. If the answers differ, that gap is where your time and money are going.
What it looks like from the founder's side
I worked this way with Anlytic, an early-stage analytics startup. Martijn Witteveen, their CEO:
"The biggest thing we were stuck on: what were we building, for who, and what was the direction? That's something that has now concretely changed: we gained clear focus. We're now very targeted in the what, for who, and why."
"Having someone own the thinking with you rather than just advise sporadically feels different."
How a fractional CPO works with you
- Advisory: a couple of days a month. An advisor on the product decisions, like an expert on the board, with no execution role.
- Fractional: a few days a week, hands-on inside the team.
Go-to-market is part of it, as strategy and coaching. The selling stays with your team.
When do you need a fractional CPO?
When the company is funded and there's no CPO in the team. The signs:
- You're still the tie-breaker on every product call.
- Sales promises things the roadmap doesn't have.
- You're about to hire your first product manager.
Common questions
How much time does a fractional CPO spend with the company?
It depends on the mode. Advisory is a couple of days a month. Fractional is a few days a week.
Does a fractional CPO do the selling?
No. On go-to-market, the work is strategy and coaching. Your team does the selling.
Who is a fractional CPO for?
Funded startups with no Chief Product Officer in the team, especially when product and sales are pulling in different directions.
How is a fractional CPO different from a product consultant?
A product consultant typically delivers a project or a recommendation. A fractional CPO stays and owns the product thinking with you over time. In Martijn's words: "Having someone own the thinking with you rather than just advise sporadically feels different."
Is fractional product leadership common now?
It's growing. Fractional Jobs, a hiring marketplace, reports that demand for fractional hires on its platform grew 149% from the first quarter of 2025 to the first quarter of 2026.
Who I am
I'm Raphaël Peyret. I built the product at Horangi from MVP to its acquisition by Bitdefender in 2023. At SHA/RP, we make products easy to back and easy to sell.
If product and sales are pulling apart in your team, send me a message and I'll tell you where I'd start.
Related: Fractional CPO and go-to-market
Senior product and go-to-market leadership inside your team, for founders who need to move fast.
Fractional CPO and go-to-marketRead next
- When does a startup need a Chief Product Officer?
A startup needs a Chief Product Officer (CPO) when someone has to decide what gets built and keep sales selling the same product. That job exists before the hire does.
- The ISO Quote
ISO 27001 was 18 months from being relevant to that company. Their vendor didn't mention that.
- How to Find the Right Fractional CPO (And When Not to Hire One)
Where to look for a fractional CPO, how to check them, and the warning signs. Plus when a full-time hire or promoting from within is the better call.