One of the most common questions I get from founders considering a Fractional CPO engagement is a version of this: “I understand the concept. But what actually happens? What will you be doing on a Tuesday afternoon three weeks in?”It is a fair question. The Fractional CPO model is well understood in theory but poorly documented in practice. Most of what is written about it stays at the abstract level — “embedded leadership,” “strategic direction,” “team development” — without telling you what that actually looks like inside a real company over a real three-month period.This article fills that gap. It is a week-by-week account of what a well-run Fractional CPO engagement actually looks like, drawn from 18 years of experience and 50+ companies across the UK, MENA, and globally. The specifics will vary depending on your company’s situation. The underlying structure is consistent.
Before Day One: The Scoping Conversation
A Fractional CPO engagement should not start with a contract. It should start with an honest conversation about whether the model is the right fit for your specific problem.Before any engagement begins, a good Fractional CPO will want to understand: what has been tried before, what the founder’s current relationship with the product function looks like, what the board’s expectations are, whether there is a product team in place or not, and what a successful three-month outcome would look like to the people who matter most.This conversation is not a sales call. It is a diagnostic. And the answer should sometimes be “this is not the right model for you right now” — in which case a good Fractional CPO will tell you that directly and point you toward what would actually help.If the fit is right, the engagement begins with one non-negotiable: a two-week discovery sprint before any recommendations are made, any priorities are set, or any changes are introduced.
Weeks 1 and 2: The Discovery Sprint
What is happening
The Discovery Sprint is the foundation of the entire engagement. Nothing changes during these two weeks. No roadmap decisions. No team reorganisations. No new processes introduced. The only activity is structured diagnosis.In practice, that means a series of conversations and a rigorous review of existing materials.
Stakeholder interviews: Every person who has a meaningful relationship with the product function gets a conversation. The CEO or founder. The Head of Engineering or CTO. The commercial team — Head of Sales, Customer Success. The product managers themselves. Sometimes key customers. These interviews follow a structured format, but the most valuable moments are always unstructured — the things people say when they feel genuinely heard rather than surveyed.The questions are consistent across every interview: What is working? What is not working? What would you change if you could? What are you afraid to say in a group setting? That last question, asked directly and privately, produces the most honest answers of the whole discovery process.
Product and delivery audit: The Fractional CPO reviews everything that can be reviewed. The current roadmap and its history — specifically, what has changed and why. The backlog and its age profile. The delivery data for the last two quarters — what was planned, what shipped, what did not, and whether the reasons given were accurate. The product metrics and what story they are actually telling versus what story the team has been telling about them.
Customer and user research review: What does the company already know about why customers buy, why they stay, and why they leave? Is that knowledge current? Is it documented? Is it actively informing decisions? In most engagements, the answer to at least one of these is no.
Operating model observation: How does the team actually work? Not the official process — the actual process. How does a feature get from an idea to the backlog? How does the backlog become a sprint? Who makes what decisions and by what criteria? The gap between the documented process and the actual process is almost always where the most significant problems are hiding.
What you receive at the end of Week 2
A written findings report. Not a slide deck. A document that clearly states: what is working, what is not working, the root causes behind the problems rather than the surface symptoms, and a prioritised set of recommendations for the engagement ahead.This report also serves as the basis for a decision. The Fractional CPO presents the findings, you discuss whether the diagnosis is accurate, and both parties decide whether to proceed with a full engagement or whether the findings point somewhere different. In a small number of cases, the discovery sprint reveals that the problem is not a product problem at all — it is a commercial problem, a team structure problem, or a market problem. When that is the case, a good Fractional CPO says so.
Weeks 3 and 4: Design and Immediate Priorities
What is happening
With the diagnostic complete, the engagement moves into its first active phase. Two things happen simultaneously during weeks three and four.
Immediate priority stabilisation: Based on the discovery findings, the most pressing issues get addressed first. This typically means one or more of the following: clarifying the product strategy at a level specific enough to use as a decision filter, restructuring the current roadmap around the single most important outcome for this quarter, establishing or clarifying the decision rights framework so that everyone knows who can decide what, and removing the most visible sources of delivery friction — the meetings that should not exist, the approval steps that have outlived their purpose, the informal stakeholder channels that are bypassing the product team.These are not glamorous changes. They are structural changes, and they tend to produce immediate and visible relief for the team.
Operating cadence design: Every Fractional CPO engagement establishes a set of recurring rituals that give the product function its working rhythm. These are designed around the specific company’s needs — not imported wholesale from a methodology textbook. The core elements are consistent: a weekly product review that makes decisions rather than reporting status, a regular PM one-to-one cadence, a sprint planning process that connects work to outcomes rather than just filling capacity, and a stakeholder communication rhythm that keeps leadership informed without turning every decision into a committee exercise.Getting these rituals right early is disproportionately important. The operating cadence is what creates the feeling of forward momentum — which is often what has been most visibly absent.
Weeks 5 through 8: Embed and Execute
What is happening
By week five, the structural work of the first month has taken hold. The operating cadence is running. The roadmap has been restructured around clear priorities. Decision rights are clearer than they were. The team has had a few weeks to experience what it feels like to operate with stronger strategic direction.This phase of the engagement is less about setting things up and more about embedding and executing.
Roadmap execution: The Fractional CPO is actively involved in sprint planning, in the weekly product review, and in the day-to-day decisions that the team faces. Not in a micromanaging way — the goal is to model good product leadership, not to replace the PMs’ judgment with another authority figure. But present enough to catch the patterns that derail delivery and address them in real time rather than retrospectively.
PM coaching: In parallel with the structural work, the Fractional CPO is actively developing the product managers. Not through formal training sessions — through the work itself. Reviewing PRDs and asking the questions that should have been asked. Sitting in customer calls and demonstrating what good discovery looks like. Giving direct, specific feedback after difficult stakeholder meetings. The goal is that every PM is meaningfully better at their craft by the end of the engagement than they were at the start — not dependent on the Fractional CPO’s presence, but more capable in their own right.
Stakeholder management: In most companies, one of the most time-consuming elements of this phase is working with the senior stakeholders whose informal influence has been distorting the roadmap. This is delicate work. The goal is not to remove stakeholder influence — it is to channel it through a structured process that protects the product team’s ability to make good decisions. This typically involves a combination of increased visibility into how decisions are made, a clear process for surfacing and evaluating new requests, and a regular stakeholder update that keeps people informed without requiring them to intervene.
Discovery restart: If the company’s customer discovery has been inconsistent or absent, weeks five through eight are when that changes. A rhythm of regular customer conversations gets established — not as a one-time research project, but as an ongoing practice that the PM team maintains independently after the engagement ends.
Weeks 9 through 12: Momentum and Measurement
What is happening
By the third month, the engagement has shifted from repair to momentum. The structural foundations are in place, the team is operating more confidently, and the question shifts from “what is wrong?” to “how fast can we move?”
Delivery against plan: This is typically where the first meaningful delivery metric improvement becomes visible. Not because the team is working harder — they were almost certainly already working hard. But because the friction that was slowing them down has been reduced. Features that should take two weeks are taking two weeks. Priorities are not shifting mid-sprint. The engineering team is spending more of its capacity on roadmap work and less on unplanned requests.
Metrics review and iteration: The Fractional CPO and the team review the product metrics together with fresh eyes. What has moved? What has not? Were the initial diagnostic findings accurate? What has the last 12 weeks of execution revealed that the discovery sprint did not? The answers inform whether the roadmap priorities for the next quarter need adjustment and what the ongoing focus should be.
Board and investor narrative: If board updates are part of the engagement scope — and they often are — the third month is when the new product narrative gets crystallised. A clear description of the strategy, a set of metrics that tell an honest and coherent story, a roadmap that the board can understand and interrogate with confidence. This is often one of the highest-value outputs of the whole engagement, because it directly affects the company’s ability to raise its next round.
Handover planning: From roughly week ten, the Fractional CPO is actively planning for the end of the engagement. Not in a way that creates urgency or disruption, but in a way that ensures the product function can continue to operate effectively without the external leadership. The operating playbook gets documented. The PM team is supported through the transition. The hiring plan for permanent product leadership — if a full-time CPO is the next step — is shaped.
What Changes by Day 90: The Realistic Outcomes
It is worth being specific about what a well-run 90-day Fractional CPO engagement should produce — because vague promises about “transformation” are not useful to anyone making a real business decision.
What typically changes:The product strategy is written down, agreed by the leadership team, and specific enough to use as a decision filter. Before the engagement, it existed in the founder’s head in different versions for different audiences. After it, it is a single coherent document that everyone can reference.The roadmap is tied to outcomes rather than features. It is shorter and more focused than it was at the start. The team can explain the rationale behind every item on it.The operating cadence is running without the Fractional CPO having to push it. The weekly product review happens because it is useful, not because someone is enforcing it. Sprint planning produces decisions, not just capacity allocation.The PM team is more confident and more capable. The most visible sign of this is usually that they are having harder conversations — with engineering, with stakeholders, with each other — that they were previously avoiding.Delivery against plan has improved. The specific number varies, but improvements of 20 to 40 percent in delivery reliability within a quarter are common when the primary constraint was operating model chaos rather than capacity shortage.
What does not change in 90 days:A 90-day engagement will not solve a
product-market fit problem that requires fundamental repositioning. It will not replace the need for a full-time CPO if the company has reached the stage where one is genuinely needed. It will not fix a retention problem that is rooted in a product that fundamentally does not deliver enough value — it will diagnose it clearly and create a plan to address it, but the execution takes longer than 90 days.A Fractional CPO engagement is not a magic fix. It is a structured, experienced intervention into a system that has been operating without the right leadership. It creates the conditions for the team to do their best work. The best work still has to come from the team.
The Question to Ask Before You Start
If you are considering a Fractional CPO engagement, there is one question worth sitting with before you make any decision: what does success look like at day 91?If you can answer that question with specificity — “the roadmap is stable, the team is shipping against plan, and I am spending less than half a day per week on product decisions” — you have a clear enough picture to evaluate whether a Fractional CPO engagement is worth pursuing and how to structure it.If you cannot answer it, that conversation — about what success actually looks like — is where the engagement should start.Want to understand what the first 90 days would look like for your specific company? Book a free 30-minute strategy call at
elvanis.com. We will map out exactly what the engagement would focus on and what you should expect to see by the end of it.
Sally Abas is the founder of Elvanis and a Fractional CPO with 18+ years of experience across SaaS, fintech, e-commerce, and enterprise transformation. She has worked with 50+ companies across 9 countries.Related reading: The Fractional CPO ROI Playbook |
Fractional CPO vs. Full-Time CPO: What UK SaaS Founders Actually Need to Know
