Fractional CPO
A senior product executive on a part-time contract, owning roadmap and customer discovery without the full-time salary.
Less common than the fractional CTO model but increasingly real. A fractional CPO joins for 1 to 3 days a week to run product discovery, sequence the roadmap, and own the customer-interview cadence. They do not own engineering. They do not own design unless you ask them to.
The fit is narrow: the company needs product seniority but cannot yet justify the cost of a full-time CPO, AND the founder is willing to delegate the product call. If the founder is also the product person and is not ready to share that authority, a fractional CPO is a friction generator.
Worked example: a company has hit early traction, the founder is buried in sales, and the engineering team is shipping whatever the loudest customer asked for last week. A fractional CPO comes in to install a prioritisation framework, run a proper discovery cadence, and give engineering a sequenced roadmap instead of a queue of one-off requests. Three days a week is enough because the job is judgement and structure, not execution volume.
The common mistake founders make is hiring a fractional CPO to avoid making product decisions themselves, before PMF. That never works. Pre-PMF, the founder’s intuition for the customer is the company’s single most valuable asset and cannot be outsourced. A fractional CPO scales a product function that already has a point of view; it does not invent one. In Austria the engagement is typically a freier Dienstvertrag, like most fractional executive roles, because the deliverable is ongoing judgement rather than a fixed work product.
The honest trade-off: a part-time CPO will always lag a full-timer on context, and product context compounds. If your roadmap decisions need to be made daily off conversations the CPO was not in, the model breaks. It works when decisions can be batched weekly and the team can execute between sessions.
Related: Fractional CTO Austria.