A fractional CPO does the job of a full-time Chief Product Officer — strategy, roadmap, discovery, pricing input and hands-on delivery — but compressed into one to two days a week on a rolling monthly retainer, typically £4,000-£10,000 depending on scope. They are not a consultant who writes a report and leaves; they run the product function, ship things, and are accountable for outcomes on a cadence that matches the days they're contracted for.
Here's what that actually looks like inside a real engagement, based on running fractional CPO work alongside founding product roles at Wocal and Co-Ride.
The weekly rhythm
A typical two-day-a-week engagement has a fixed shape: one day for synchronous work — the product review, stakeholder conversations, interviews, sprint planning — and one day for deep work, which is where specs get written, prototypes get built and decisions get documented so the team can move without you in the room.
What doesn't happen is ad-hoc availability all week. Founders sometimes expect Slack responses at 11pm; a fractional CPO who is doing the job properly is usually running this pattern across two or three clients, and the discipline of fixed days is what makes that sustainable and, honestly, what makes the strategic thinking better rather than reactive.
Strategy and roadmap ownership
The first few weeks of any engagement are spent understanding the current state honestly: what's shipped, what's half-shipped, what the team believes versus what's been validated. From there the job is building (or fixing) a roadmap that ties every initiative to a business outcome, not a feature wishlist inherited from the last six investor updates.
This includes saying no in public. A large part of the value a fractional CPO adds in month one is cutting scope — killing the three parallel initiatives that are each half-resourced and replacing them with one thing done properly.
Discovery and validation
Customer interviews, usage data review, and — increasingly — building small working prototypes to test demand rather than mocking screens. A fractional CPO runs this in parallel with delivery, not as a separate phase, because pre-PMF teams don't have the runway for a research phase that doesn't touch the roadmap for six weeks.
The output isn't a research deck. It's a decision: build this, kill that, and here's the one metric that tells us if we're right within two weeks of shipping.
Hands-on delivery
Contrary to the stereotype of a fractional exec who only attends steering meetings, most fractional CPO engagements at seed and pre-seed stage involve writing specs, reviewing designs, sitting in on engineering standups, and sometimes building directly in tools like Lovable or Cursor to remove ambiguity from a brief. The closer the fractional CPO is to the actual build, the fewer handoff errors there are.
This is also where a fractional CPO differs from a pure strategy consultant: they stay accountable for whether the thing shipped and whether it worked, not just for the recommendation.
Team and hiring input
Most founders bring in a fractional CPO before they have a product team at all, or when they have one or two PMs who need senior mentoring rather than management. Part of the role is coaching those PMs, running the hiring process for the next product hire, and — often — helping the founder work out when it's time to convert the fractional role into a full-time one.
A good fractional CPO treats their own eventual redundancy as a success condition, not a threat, and builds the handover plan from day one.
What a fractional CPO does not do
They don't replace a full engineering team's technical leadership, they don't do full-time line management of a large PM org, and they're not a substitute for a founder who refuses to make product decisions themselves. At two days a week, a fractional CPO also can't be in every Slack thread — which means the team needs a clear escalation path for the other five days.
If your team is at the stage where product decisions need someone in the room daily, that's the point covered in detail in the Crossley Method's Scale stage — the same seven-stage framework (Discover, Validate, Prototype, Build MVP, Launch, First Revenue, Scale) that governs how a fractional CPO engagement should be scoped from day one, so the work is never generic advice but tied to exactly where your company sits in that sequence.
Frequently asked questions
- What does a fractional CPO do day to day?
- A fractional CPO runs product strategy, discovery, roadmap prioritisation and hands-on delivery — writing specs, reviewing prototypes, sitting in engineering standups — on one to two fixed days a week, plus asynchronous decision-making the rest of the week.
- How is a fractional CPO different from a product consultant?
- A consultant typically delivers a recommendation and leaves. A fractional CPO stays accountable for outcomes: they ship the roadmap they wrote, sit through the delivery, and adjust based on what actually happens in the product.
- Can a fractional CPO manage a product team?
- Yes, for small teams of one or two PMs, a fractional CPO can mentor and lightly manage. Beyond that, day-to-day management at two days a week becomes a bottleneck and signals it's time for a full-time hire.
- How many days a week does a fractional CPO typically work?
- Most UK engagements run one to two days a week. One day suits early pre-seed teams needing strategic input; two days suits teams that need hands-on delivery alongside strategy.