A Chief Product Officer (CPO) should own product decisions across the business when several lines of work compete for investment. A VP of Product can lead the whole function too, especially in a smaller company. The hiring choice depends on the decisions the leader can make, the teams they'll direct, and who settles disputes with engineering or sales.
What Are the Key Differences Between a CPO and VP of Product?
- A CPO brief usually carries company-wide responsibility for product direction and portfolio choices.
- A VP of Product can be the senior product leader; the title alone doesn't establish a smaller mandate.
- Nearly 60% of Fortune 1000 companies now have an established CPO function, up from 15% in 2022, and 70% of CPOs hold P&L responsibility.
- Define budget authority, reporting lines, and ownership of product outcomes before opening the search.
- Interview candidates about a product decision they reversed after customer evidence changed.
What Does a Chief Product Officer Own?
A CPO decides where the company will place its product bets and what it will stop funding. That decision becomes harder when several products have different customers, economics, and engineering needs. The CPO must be able to compare those opportunities and make a call that holds across the company.
MIT Professional Education describes the role as spanning product vision, design, development, portfolio decisions, and go-to-market leadership. A search brief should turn those broad responsibilities into named decisions. Which product lines can this executive close or combine? Can they change the investment mix when the evidence shifts? What requires CEO approval?
At a company with several business units, the CPO may also need to decide when a shared platform serves customers better than another local feature. That call has consequences for the engineering roadmap and for teams that already promised customers something else. A candidate who has only managed one successful product won't necessarily have made decisions at that level.
What Does a VP of Product Own?
A VP of Product can own product vision and strategy, manage product leaders, and report directly to the CEO. Some companies use the VP title for the top product executive. Silicon Valley Product Group's description of the VP Product role places the executive alongside senior engineering and marketing leaders, with product management and user experience teams reporting into the role.
The practical question is the remit. A VP might lead the entire product function at a single-product company. In a larger enterprise, the same title might cover one division, with portfolio decisions reserved for a CPO. Both briefs need to say which customer and financial outcomes the person owns. Without that detail, candidates have to guess whether the role calls for enterprise choices or leadership within an existing plan.
How Do a CPO and VP of Product Differ?
A CPO brief usually covers decisions across the product portfolio; a VP brief can cover the whole function or a defined part of it. Start with scope and reporting line, then establish investment authority and which decisions stay with other leaders. A VP who reports to the CEO and controls the entire portfolio might have the same mandate another company calls CPO.
CPO total compensation ranges from $320,000 to $760,000, with a national median of $480,000. FAANG companies pay a median of $624,000, pre-IPO unicorns average $552,000, and early-stage startups land around $408,000 in cash plus larger equity grants. VP of Product total compensation ranges from $275,000 to $620,000, with a national median of $405,000 in 2026. The two pay ranges overlap, which means a company can pay VP-adjacent money for CPO-level authority, or the reverse, and never notice the mismatch until the hire tries to use authority they were never given.
[Table 1]
When Should a Company Hire a CPO?
Hire a CPO when the company needs one executive to settle competing product priorities across the whole business. Two product lines might be competing for the same engineering capacity. A third has better retention but slower near-term revenue. Someone needs the authority to weigh those against each other and redirect the work.
The role also fits when the CEO has been making product trade-offs personally and wants an executive who can own them. Two signals matter most: engineering-product friction serious enough to consume founder bandwidth, and roadmap diffusion, where every team gives a different answer to what's being built and why.
The signs usually show up in planning meetings. Leaders agree on the company's goals, then leave with separate roadmaps that all assume the same budget or the same engineering capacity. An acquisition can surface the same gap a different way: the acquired product serves a valuable customer group, but its platform duplicates work already funded elsewhere. A CPO brief assigns that decision, to combine products, keep them separate, or retire one, and names the financial evidence needed to support it. Hiring another product manager to coordinate the plans leaves the actual investment choice sitting with the CEO, unresolved.
The CEO should also decide which judgments stay at the top no matter who's hired. A CPO can own the portfolio day to day and still need board approval for a major acquisition or a shift in the company's overall investment plan. Setting that boundary before the search starts lets candidates understand the job's real power, and gives other executives a clear way to challenge a product decision without reopening every roadmap meeting.
When Should a Company Hire a VP of Product?
Hire a VP of Product when the company needs senior product leadership for a defined business or a product organization that already has clear portfolio ownership. A VP can lead product managers and set priorities from customer evidence. Deciding what the team builds next comes with the job. At a smaller company, that person might report to the CEO and be the most senior product leader. At companies under 50 employees, a VP of Product often serves the CPO function outright.
Don't assume a VP role is limited to execution. The SVPG description of the role includes product vision and strategy. The search should instead specify which products fall under the VP and which spending decisions they control. Say who can change the direction once the plan is under way.
A VP hire often becomes necessary once product managers are each making sound calls for their own teams, but nobody's developing the people who make those calls. Discovery quality starts to vary by team. Sales ends up routing requests straight to engineering because the product process can't resolve them fast enough. A VP with authority over the function sets a common standard for customer evidence and coaches product leaders while staying close to the roadmap.
The reporting line changes what needs spelling out. Under a CPO, the company has to draw the line between portfolio decisions that sit above the VP and the ones the VP can make alone. Reporting straight to the CEO raises a different question: does this person own product strategy, or are they running a plan the founder still controls?
When Should a Company Define the Mandate Before Hiring?
Neither title fixes a product organization with no agreed authority to change priorities. A company can hire a senior executive and still let every large customer request bypass the roadmap through sales. In that situation, the CEO and commercial leader need to decide first which commitments require product review and who can decline them. The search brief can then define the new hire's part in that decision.
Sometimes the problem is narrower. A single product team might need a director who can coach managers and improve discovery, while the founder keeps owning company-wide product direction. A CPO would have too little room to exercise real portfolio judgment there. A VP title runs into the same wall if the company expects the person to manage one small team without authority over its own budget or priorities.
Look at what's failing before deciding on seniority. Missed releases might trace back to unreliable engineering capacity, thin customer research, or product commitments nobody tested with the teams responsible for shipping them.
How Can a CPO and VP of Product Work Together?
Both roles make sense once a company has enough product scope to split portfolio choices from running a defined product organization. A CPO can decide which line gets the next round of investment. A VP leads the largest of those lines, develops its product managers, and makes calls inside the approved budget. That split gives the VP real authority instead of asking them to seek approval for every change.
The company also needs to define escalation. If the VP finds evidence that the approved investment no longer serves customers, they need a route to raise it. The CPO reviews that evidence and can change the portfolio allocation when it's warranted. Day-to-day priorities within the VP's remit stay with the VP, because two people can't both be the final call on the same feature.
For a search committee, this changes how you assess candidates. What counts as evidence differs by role. A CPO candidate needs judgment across products with different economics behind them. For a VP, the bar is narrower: did they make the organization they led better, with real budget on the line?
What Should Companies Test During the Search?
Ask each candidate to walk through a product decision that cost them something. Which customer evidence challenged the plan? What did they stop building? Who disagreed, and what changed after release? A useful answer names the trade-off and the outcome the company measured. A polished account of a roadmap meeting gives far less evidence.
For CPO candidates, ask about a choice across product lines that put them at odds with the CEO or CTO. Who made the final call, what did the candidate personally decide, and what happened afterward? For VP candidates, ask how they developed product leaders and changed team priorities when customer evidence challenged the original plan.
Reconstruct one consequential decision from beginning to end. Ask what the customer data showed before the decision. Ask what alternatives were on the table. Ask which measure moved afterward. If the candidate says a launch improved retention, pin down the baseline and the period measured, then ask what happened to the customers who didn't adopt it. Questions like these separate the leader's actual work from a company outcome that just happened to land during their tenure.
A different kind of check tells a different part of the story. Engineering peers and commercial peers see different failure modes. One will tell you whether trade-offs came early enough to plan around. The other remembers what happened when a customer promise didn't hold up. For a portfolio role, ask a CEO or finance counterpart how the person argued for stopping an investment that still had supporters. Tie each reference question back to a decision named in the brief itself.
What Should Success Look Like in the First Year?
The first-year goals should match the mandate the company gave the hire. For a CPO brought in to reset a portfolio, year one should produce two things: a named list of which products merit continued investment, and a process for revisiting that list without starting from zero each time. A VP's first year looks different on paper: stronger product managers, a tighter path from customer evidence to roadmap. It should still be just as concrete.
The right measure depends on the business. A subscription company cares about renewal reasons and whether a redesigned product got adopted. An enterprise software team is watching something else entirely: implementation time, and how often what's on the roadmap ships.
That scorecard gives interviews a firmer footing. A strong candidate can explain how they'd inspect the current portfolio. They can say which decisions they'd hold off on until customer evidence arrives, and which disputes they'd resolve in their first few months. The answer should point to this company's products and people. A generic 90-day plan gives the committee little evidence of how the person would handle its trade-offs.
How Does Christian & Timbers Define the Product Leadership Mandate?
Christian & Timbers runs CPO searches at high-growth technology companies and private equity-backed businesses, through to public enterprises. Before mapping candidates, the company should define the products in scope and the decisions the new leader will control. That makes it possible to assess a CPO, VP of Product, or Head of Product against the same mandate.
The hiring team can then test candidate experience against the decisions it needs made. Expanding a successful product inside one division is one kind of evidence. Reallocating investment across an entire portfolio is a different kind, and the two shouldn't be scored the same way. The interview makes that difference visible before a title or a strong company name decides the shortlist.
Getting the mandate wrong costs more than a bad hire. It costs the months a company spends discovering the title didn't match the authority. Contact Christian & Timbers to begin with a structured assessment of your product leadership hiring needs.
What Else Should Companies Know About These Roles?
1. Is a CPO higher than a VP of Product?
A CPO usually sits above a VP of Product when a company has both roles. The CPO commonly holds portfolio-wide authority. The VP leads an assigned product organization beneath it. If the company has only a VP, that executive can be its senior product leader and report directly to the CEO.
2. Can a VP of Product report to the CEO?
Yes. A VP of Product can report directly to the CEO and lead the entire product organization. The reporting line should be in the job brief because it helps candidates understand who sets strategy and who settles conflicts with other functions.
3. Does a company need both a CPO and a VP of Product?
A company needs both when the work can be divided into clear mandates. At larger organizations, the CPO owns decisions across multiple product lines, and a VP runs one organization beneath that portfolio. If both roles claim final authority over the same roadmap, the structure needs to be settled before either search begins.