Founders, Co-Founders, and CEOs: Getting the Roles Right

An idea alone doesn't make someone a founder. Execution is what makes someone a founder. This is a distinction the startup world avoids because it's uncomfortable — but it has significant implications for who should hold which role, who should own how much equity, and how the organisation structures itself through its early phases.

Titles in early-stage companies are not vanity. They define expectations, responsibilities, and the legal structure of the entity. Getting them wrong creates conflicts that are expensive to unwind — sometimes fatally so.

Founder vs Co-Founder

A founder is someone who takes an idea from nothing to initial execution — who carries the venture through its earliest, least-resourced phase. The defining characteristic is not who had the idea. It's who built it when building it was hardest.

A co-founder is someone who joins at the inception phase to provide complementary capabilities. The key word is complementary. A co-founder who provides the same skills as the founder is not a co-founder — they're an early employee with founder economics.

Founder vs CEO

A founder's primary skill is creation — identifying opportunity, building from zero, making decisions with minimal information. A CEO's primary skill set, as the company scales, shifts toward organisational leadership, talent management, capital allocation, and external representation.

• Define responsibilities, not just titles. What does each person own? What decisions do they make unilaterally? Write it down — ambiguity in the founding team is the seedbed of conflict.
• Assign roles to strengths, not seniority. The person who had the idea may not be the best CEO. Let the company benefit from the right person in the right role.
• Build in a review mechanism. Roles that made sense at founding may not make sense at Series A. Build an explicit way to revisit the organisational structure as the company grows.

Titles are tools to define responsibilities — not trophies for showing up first. The companies that get this right in the early phase create fewer expensive conflicts in the scale phase.