Andrew Crossley
    CHIEF PRODUCT OFFICER

    What a Chief Product Officer actually does

    A CPO owns product strategy, the roadmap, the PM team, and the outcomes. Here's how the role breaks down, when a company needs one, and how it compares to a CTO or VP Product.

    Looking to hire one? See CPO consulting & audits → or fractional CPO cost in the UK →

    A Chief Product Officer is the most senior executive responsible for what a company builds and why. They own product strategy, discovery, the roadmap and the outcomes it produces, and are usually the named executive who answers to the board for activation, retention and revenue. The scope and shape of the job changes significantly with company stage, from hands-on discovery pre-seed to portfolio strategy at scale.

    RESPONSIBILITIES

    What the role owns

    Product vision & strategy

    Own the multi-year product bet, positioning and the roadmap that makes it real.

    Discovery & prioritisation

    Turn customer signal into a validated backlog. Kill the wrong bets early.

    Team & hiring

    Build the PM/design/analytics function. Set rituals, cadence, coaching.

    Outcome ownership

    Named executive on product KPIs: activation, retention, revenue, NPS.

    SIGNALS

    When you need a CPO

    • You've raised a Series A or later and product decisions now cost real money.
    • Multiple product lines or segments need a single strategic owner.
    • You have 2+ PMs who need day-to-day management and coaching.
    • Investors and the board expect a named product executive.
    • Cross-functional friction (product ↔ eng ↔ GTM) is slowing everything down.

    Before Series A, most teams should start with a fractional CPO , same seniority, ~20-40% of the cost. Compare in detail: fractional CPO vs full-time CPO decision framework or, if you need someone to bridge a gap right now, look at an interim CPO.

    COMPARISON

    CPO vs CTO vs VP Product

    CPO
    Product strategy, discovery, roadmap, PM team, outcome KPIs.
    CTO
    Technology strategy, architecture, engineering hiring, infra.
    VP Product
    Roadmap execution, PM management, reports into CPO in larger orgs.

    BY STAGE

    Responsibilities by company stage

    Pre-seed / seed

    At this stage the CPO is closer to a founding product lead than an executive. The work is discovery: talking to early users, shaping the problem, and shipping the smallest thing that proves the bet. There's usually no PM team yet, so the CPO does the research, writes the specs, and works directly with engineering. Reporting is informal, roadmaps are short and change often, and the main job is finding product-market fit before runway runs out.

    Series A

    Once there's early traction, the job shifts from finding fit to scaling it. The CPO starts hiring the first PMs, puts a repeatable discovery and delivery process in place, and defines the metrics the board will track. This is where a fractional CPO often hands over to a full-time one, or where a founder brings in a full-time CPO for the first time. Pricing, packaging and segmentation decisions get more scrutiny because they now affect real revenue.

    Series B and beyond

    At scale the CPO manages multiple product lines or squads through a VP Product or group PM layer rather than working with individual PMs directly. The role becomes more about portfolio strategy, resourcing trade-offs across teams, and representing product at board level. Expansion revenue and retention across cohorts matter as much as new feature delivery.

    OPERATING WEEK

    A CPO's operating week

    Discovery

    Customer calls, usability sessions or support/sales signal reviews to keep the roadmap grounded in evidence rather than opinion.

    Roadmap review

    Checking what shipped against what was promised, and re-prioritising the next few weeks based on new information.

    Metrics review

    A regular look at activation, retention, and revenue dashboards, spotting drift before it becomes a crisis.

    Stakeholder and board updates

    Translating product work into language investors, execs and sales can act on.

    Team coaching

    1:1s with PMs and designers, reviewing specs, and unblocking decisions they can't make alone yet.

    Pricing and packaging

    Periodic reviews of plans, tiers and packaging as the customer base and competitive landscape shift.

    ACCOUNTABILITY

    How a CPO is measured

    • Activation: how quickly and reliably new users reach first value.
    • Retention: whether customers keep using the product month over month.
    • Expansion revenue: upsell, cross-sell and account growth driven by product decisions.
    • Delivery predictability: whether the roadmap ships close to when it was promised.
    • Team health: whether the PM/design function is retaining people and improving its own process.

    RISKS

    Common ways the hire goes wrong

    • Hiring a CPO before there's product-market fit, when the real need is a founder doing discovery themselves.
    • Bringing in a CPO from a very different sector or business model without adjusting expectations for ramp time.
    • No clear reporting line or KPI ownership, so the CPO becomes a project manager instead of a strategic owner.
    • Skipping the fractional or interim step and going straight to a expensive full-time hire that doesn't fit the stage.
    • Letting the CPO operate without real authority over roadmap and hiring decisions, which undermines the whole point of the role.

    If you're weighing up the risk of a bad full-time hire against starting fractional, the fractional vs full-time decision framework walks through the trade-offs, and a fixed-scope product audit is a lower-risk way to get a second opinion before committing to either.

    FAQ

    Common questions

    What does a Chief Product Officer actually do day to day?
    A CPO splits time between discovery (talking to customers), roadmap and metrics review, coaching PMs, and reporting to the board or leadership team on product outcomes. The mix shifts with company stage: more hands-on building early, more portfolio and people management later.
    Is a CPO the same as a VP of Product?
    No. A CPO is the most senior product executive, usually reporting to the CEO and owning product strategy and outcomes. A VP Product typically reports into the CPO in larger organisations and owns roadmap execution and PM management.
    Does a startup need a CPO before Series A?
    Usually not full-time. Before Series A, most teams get more value from a founder doing discovery directly, or from bringing in a fractional CPO for strategy and process without the cost of a full-time executive.
    How is a Chief Product Officer different from a CTO?
    A CPO owns what gets built and why: strategy, discovery, roadmap and product KPIs. A CTO owns how it gets built: architecture, engineering hiring and technical infrastructure. The two roles work closely together but own different halves of the equation.
    What KPIs is a CPO usually judged on?
    Most commonly activation, retention, expansion revenue and delivery predictability, alongside the health of the product and design team they're building.
    Can the CPO role be done part-time?
    Yes. A fractional CPO covers the same strategic scope at 1-2 days a week, which suits companies pre-Series A or between full-time hires. See fractional CPO costs and scope in the UK for detail.

    Need product leadership?

    Start with a fractional engagement, an interim bridge, or a fixed-scope audit, I'll help you scope which fits.