How long should a fractional CPO engagement last?

There is no industry template here, but there is a floor set by the work itself. The first quarter goes on a customer-evidence program, a written diagnosis, and a prioritization system that has to survive its first real disagreement. An engagement ending at week ten stops in the middle of that and leaves you with findings rather than a working function. A second quarter is where the arrangement earns its keep, because the decisions made in the first start producing observable consequences while someone who understands why they were made is still there to adjust them.

SFCPO's own terms put numbers on that shape: a 3 month minimum, 6 months as the standard engagement, $8,000 a month for 20–25 hours, 30 days' notice, and 60–80 customer and prospect interviews inside the first quarter. Treat those as one operator's structure rather than a market norm, and ask any candidate to justify their own minimum in terms of what it buys.

Longer than twelve months, and the question changes. At that point you are either paying part-time rates for what has become a permanent role, or the handover was never built. Both are worth naming out loud rather than renewing past.

What notice period is fair?

Roughly 30 days is the most common flexible termination period in fractional agreements, and some use 60. There is no single market standard, so read what you are given rather than assuming. SFCPO's own agreements use 30 days, running in both directions. What matters more than the length is when notice starts to apply: notice running from day one converts a six-month engagement into a rolling monthly one, which changes what the operator can responsibly begin. Nobody opens a sixty-interview evidence program in week two if the engagement can end in week six. Symmetry matters too. A contract where the company can leave on thirty days while the operator is bound for the full term was written by somebody expecting to be disappointed, and it is worth asking why.

Pair the notice period with explicit stop criteria rather than treating it as the only exit. Kill criteria at day 45 and day 60 give both sides a legible way to end an engagement that is not working, which is a better mechanism than a notice clause exercised in silence.

Who owns the IP?

The company, assigned in writing, covering everything produced during the engagement: strategy documents, research, roadmaps, prioritization frameworks as applied to your business, metric definitions and any specifications written. This should be uncontroversial and usually is. The two places it gets less clean are worth raising early. First, an operator's own general methods and templates typically remain theirs, licensed to you for use, and that is reasonable as long as your instantiation of them is yours outright. Second, the customer-evidence base: insist explicitly that interview recordings, notes and the pattern analysis transfer to the company, because that asset is most of what you paid for and it is the one most often left in someone else's drive.

This page describes patterns that are common in these engagements, not an industry standard, and every agreement differs. It is not legal advice, and the contract itself should be reviewed by your own counsel before signing.

Nobody opens a sixty-interview evidence program in week two if the engagement can end in week six.

What goes in the scope section?

Four things, and most disputes trace back to one of them being vague. Hours: 20–25 a month, with a stated approach to what happens when a month runs over. Workstreams: which two or three of the six areas of product management consulting the engagement covers, named rather than implied. Authority: what the operator can decide alone, what needs the founder, and specifically whether they can stop work already in flight, which is the clause founders most often leave out and most often need. Outcomes: the leading indicators for the first 90 days and the lagging metrics nominated at the start, written down before anyone begins. The measurement framework behind that last item is in how to measure a product consultant in 90 days.

What about the handover?

Specify it at signature, not at the end, because a handover assembled in the final fortnight is a document rather than a transfer. What should exist: the evidence base with its analysis, the prioritization rule in written form with worked examples, metric definitions and where they are instrumented, the open decisions with their current state, and a named internal owner for each of those things. The last item is the one that makes the difference. A handover with no internal owner is an archive. Build in a taper as well, so the final month runs at reduced hours alongside whoever is picking the function up rather than ending on a date.

What does the retainer cover, and what is billed separately?

The retainer covers the operator's time within the agreed scope: strategy, discovery, prioritization, the leadership meeting, and the workstreams named in the contract. Sivan Kadosh, a fractional Chief Product Officer for B2B SaaS companies between $2M and $15M ARR, works on a $8,000 monthly retainer against 20–25 hours, a 3 month minimum and 6 months as the standard term. Billed separately, and worth agreeing in advance: travel, research tooling, incentives paid to interview participants, and any specialist brought in for a defined piece of work.

Product management consulting for B2B SaaS is the category this contract sits inside; the fractional model is the version of it that prices an ongoing role rather than a deliverable, which is why the scope section carries more weight than it would in a project agreement. What the alternative shapes look like is in fractional CPO engagement models, and the hiring process itself is in how to hire a fractional CPO.

Typical shape: a term of 3 to 6 months, roughly 30 days' notice with some agreements at 60, a monthly retainer commonly running $5,000–$15,000, and full IP assignment including the customer-evidence base. SFCPO's own terms are $8,000 a month against 20–25 hours, a 3 month minimum and 30 days' notice. The clause founders forget is authority: whether the operator can stop work already in flight. Write the handover and the stop criteria at signature, and the notice period rarely has to be used.