ROLES

CTPO

Chief Technology & Product Officer

One operator owning both the technology and the product roadmap, when splitting them across two C-suite hires is too slow or too expensive.

Last reviewed: 2026-05-24 byKevin Riedl wiki β†—

A CTPO carries the responsibilities of a CTO and a CPO under one neck. They own what gets built, how it gets built, and whether it actually solves the customer’s problem. The role exists because pre-product-market-fit startups cannot afford two senior hires and cannot afford the politics of a CTO and CPO disagreeing about priority every Tuesday.

In a Wavect engagement, a CTPO is usually fractional. One operator joins the cap table or the contract, runs product discovery and technical architecture in the same week, and hands off to a permanent split (CTO + CPO) once the company has the revenue and the org structure to justify both.

The risk: one person becomes the single point of failure. The mitigation: a CTPO who knows when to stop being one and recruit their replacement. Anyone unwilling to fire themselves is the wrong CTPO.

// FAQ

FAQs

FAQs

A CTO owns engineering. A CTPO owns engineering and product. If your roadmap, your sprint board, and your customer interviews all live in different people’s heads, you probably need a CTPO until they do not.
Real. A fractional CTPO works 1 to 3 days a week against a defined scope, attends the same board meetings as a full-time one, and is bound by the same SoW. The only thing fractional about them is the calendar.
When the engineering team is large enough that engineering management is a full-time job (usually 8+ engineers) AND product is shipping fast enough that prioritisation cannot be batched weekly. Until then, splitting just creates a coordination tax.