Selling to a chief product officer

A chief product officer buys outside help for one reason. The roadmap they promised is slipping, and they can't hire their way out fast enough.

Everything you write to a CPO should start from that pressure. Not your capabilities. Their dates.

What a CPO owns

The CPO owns what gets built and why. They own the roadmap, the product teams, the pricing and packaging decisions in many companies, and the story the CEO tells the board about what's coming next.

They're measured on outcomes the business can feel. Revenue from new products. Adoption of new features. Retention. And above all, shipping what was promised on something close to the date that was promised.

That last one is where services firms come in. A CPO with a credible roadmap and a team that can't deliver it is a buyer. A CPO with a team that's keeping up is not.

What they ignore

CPOs ignore anything that sounds like a body shop. "We have 400 engineers ready to deploy" tells them you sell headcount, and headcount is the least interesting thing to a product leader.

They ignore pitches about process. Agile transformation, product operating models, frameworks with acronyms. Most CPOs have opinions about how product should be run, and they didn't ask for yours.

And they ignore anything addressed to the CTO. If your message is about architecture, cloud costs or platform modernization, it belongs with engineering leadership. The CPO cares whether the platform lets them ship, not how it's built. For the engineering side of the same account, see selling to a CTO.

Signals that matter for this seat

A new CPO is the strongest signal. In the first 90 days they'll audit the roadmap, find what's behind and decide what to cut, delay or bring in help for. That's when outside teams get hired.

Hiring for product and engineering roles is next. A company posting for product managers, designers and senior engineers all at once is trying to build capacity it doesn't have. If the posts mention a specific product line or a new platform, you know where the pressure is.

Product launch announcements and leader posts about what's coming tell you the promise. Earnings language about "accelerating our roadmap" or "time to market" tells you the board is watching. And funding rounds put a clock on everything, since investors expect the money to turn into product.

When two or three of these stack in the same few weeks, the CPO is likely feeling it.

An example opener

Say a mid-size software company announces a new CPO who came over from a larger competitor. The same month, the company posts six product and engineering roles tied to a new analytics module that was announced at last year's customer event.

Saw you took the CPO seat, and the team is hiring for six roles around the analytics module. In the first 90 days you'll be asked whether that launch date still holds. My guess is the hiring won't land fast enough to hit it, and you're deciding what to protect and what to push. Is that close, or is the bigger issue something else?

It names a real event. It ties it to the seat and the first 90 days. It guesses at a specific problem. And it's easy to correct.

Who else is on the committee

A CPO rarely buys alone. The CTO or VP of engineering will have a view on any outside team touching the codebase. The CFO will care if the spend wasn't planned. And there's often a product director or group PM who'll be your day-to-day champion.

Write to each of them with a different misery hypothesis. The CPO worries about the date. The VP of engineering worries about quality and onboarding cost. The product director worries about being the person who manages an outside team on top of everything else.

How to talk once they reply

When a CPO answers, they'll usually tell you what's behind and why. Listen for whether the problem is capacity, skills or decision-making. Capacity problems want people. Skills problems want specialists. Decision-making problems want an advisor, and they're the hardest to sell and the stickiest once you're in.

Then match your offer to the real problem, not to what you had planned to pitch.

CPOs buy from people who understand the roadmap is a promise. Start there, and you'll get the reply.