CTO and CPO — When to Split the Roles and How to Do It Without Chaos

For the first 2–3 years of most startups, one person covers both roles: CTO and CPO. Someone makes architectural decisions and someone makes roadmap decisions — and often that's the same person, because it's simply faster and cheaper.

The problem appears when the startup grows. One person can't simultaneously run discovery and manage architecture, recruit engineers and talk to customers about the product. Something starts to be done worse. Usually the product — because technical urgencies have deadlines, and product thinking requires a clear head.

CTO (Chief Technology Officer): responsible for how you build. Architecture, tech stack, code quality, security, delivery process, engineer competencies. Looks inward — at the system and the team.

CPO (Chief Product Officer): responsible for what you build. Product vision, roadmap, prioritisation, discovery, alignment with business metrics. Looks outward — at users and the market.

Common misconception: the CTO is "technical" and the CPO is "business". In reality, both need to understand the business. The difference is in the direction of attention and the type of decisions.

1) Product discovery is neglected — if the roadmap is built mainly on feedback from engineers and the board without regular contact with users, a CPO is needed.

2) The CTO is a bottleneck for both tech and product — if architecture decisions and roadmap decisions are waiting on the same person, the split is long overdue.

3) You're hiring a Head of Product / PM and don't know who manages them — a PM without a CPO above them operates in a vacuum.

4) You have 15+ engineers and the CTO is still writing code — at this stage, the CTO should be managing, not coding.

5) The board asks about product strategy and you don't have a ready answer — weak product leadership.

Option A: Internal promotion. The current "CTO/CPO" clearly defines: from now I am the CTO. They promote an internal Head of Product to CPO or hire externally. Risk: if the current person is more technical than product-oriented, the new CPO may face resistance. Solution: the CEO actively defines the CPO's mandate and resolves conflicts in the first 3 months.

Option B: Fractional CPO for the transition. Before hiring a full-time CPO — hire a Fractional CPO for 3–6 months. Goals: defining the role, building a roadmap and discovery process, recruiting or onboarding a permanent CPO. Works especially well when you're unsure what you need from a CPO or the budget doesn't support a full-time hire.

Option C: Parallel Fractional CTO and CPO. If both roles are weak, simultaneous hiring is possible. Expensive, but quickly stabilises the organisation.

No clear mandate: "you manage the product" without a clear answer to "who decides when tech and product conflict" is a recipe for conflict.

CTO still influences the roadmap under the guise of "feasibility": feasibility is the CTO's input to the process, prioritisation is the CPO's decision. These two roles need to be clearly separated.

CPO without access to users: a CPO who doesn't talk to customers for at least 4 hours a week isn't a CPO — they're a product administrator.

No alignment on metrics: CTO optimises delivery (velocity, uptime), CPO optimises outcome (retention, conversion, NPS). Conflicting metrics → conflicting priorities → chaos.

At seed and early Series A stage — one person as Fractional CTO/CPO makes sense when: the startup has fewer than 15 engineers, the product is in the growth phase, and the founder has experience building products.

Over recent years I've led both roles at several companies simultaneously — Natu.Care as founder, Mindgram as CTO/CPO. It's not a permanent solution, but a good one for the stage when full-time C-level is too early or too expensive.

Does a CPO need to be technical? They don't need to code, but they need to understand technical tradeoffs. A CPO who doesn't understand what "this takes 6 weeks because of architecture X" means can't prioritise effectively.

How much does a CPO earn at a startup in Poland and CEE? Senior CPO full-time: 25,000–45,000 PLN gross per month (approx. €5,800–10,500) + equity. Fractional CPO: 8,000–18,000 PLN per month for 1–2 days per week.

Who is more important — CTO or CPO? Wrong question. Both are required when the company reaches the appropriate scale. Before that stage — one operator can run both functions.

How long does it take to onboard a new CPO? 3–6 months to full effectiveness. First 30 days: discovery. Days 31–60: first product decisions. Days 61–90: own roadmap and decision rhythm.