Founder Roles

Founder roles is the explicit division of responsibilities, decision-making authority, accountability, and titles among co-founders, ideally documented at company formation in the founders agreement. The discipline exists to prevent the ambiguity that compounds into founder conflict over time. The typical division involves one founder taking the CEO role (strategy, fundraising, external relationships) and others taking domain-specific roles (CTO for technical leadership, COO for operations, CPO for product). The structural clarity matters more than the specific division: clear-division-A and clear-division-B both work fine, while ambiguity in either direction fails. It is the foundational structural decision that determines how the founder team will operate, and the area where many founders avoid hard conversations at formation that cost them dearly later.

The components of founder-roles definition:

Titles:

• CEO: who is the chief executive? Usually one founder; rarely co-CEOs (which create their own problems).
• Technical leader: CTO or VP Engineering. Often a co-founder.
• Other C-level titles: COO, CPO, CMO, CFO depending on what the founders specialize in.
• Co-founder qualifier: many founders use "Co-founder & [Title]" to signal founder status while having a specific role.

Responsibility areas:

• Who owns what functions: at minimum, product, engineering, sales, marketing, finance, operations, HR. Each function should have a designated owner (which can be one of the founders or a future hire's responsibility).
• Who is the customer-facing face: typically CEO; sometimes others depending on customer type and founder strengths.
• Who runs investor relationships: typically CEO; sometimes shared with CFO or specific board members.

Decision-making authority:

• What decisions does each founder own unilaterally: e.g., CTO owns technical architecture, CEO owns fundraising strategy.
• What decisions require joint approval: typically major strategic decisions, major hires, financial commitments above thresholds.
• What decisions require board approval: per the protective provisions in the financing documents.
• Dispute resolution: when founders disagree on a joint decision, what's the resolution mechanism? Often deference to the relevant domain owner, sometimes board involvement.

Accountability metrics:

• What is each founder accountable for: revenue (CEO), product velocity (CTO), customer metrics (CPO), operational efficiency (COO). Each founder should have a few clear metrics.

The common patterns:

Two founders with clear split:

• CEO + CTO (most common). CEO runs business; CTO runs technology.
• CEO + COO. Less common but works when one founder loves operations and the other loves external relationships.

Three founders with role split:

• CEO + CTO + CPO (product). Works at heavily product-focused companies.
• CEO + CTO + COO. Works when operations require dedicated focus.

Two founders without clear split (problematic):

• "We're both the boss." Creates ambiguity, slow decisions, eventual conflict.
• Co-CEOs. Famous in some companies (Atlassian, Salesforce historically) but typically creates problems unless the founders have a long working history of seamless coordination.

When founder roles change over time: roles often evolve as the company grows. Early-stage founder roles (everyone does everything) give way to more-specialized growth-stage roles. Founder-CEOs sometimes transition to chairman or CTO roles at later stages. Anticipate the evolution but document the current state clearly.

What founders get wrong: Avoiding the founder-roles conversation at formation because it feels awkward or premature, then watching the ambiguity create friction that compounds into conflict over years. The right discipline: at formation, have the explicit conversation about titles, responsibilities, decision authority, and accountability. Document in the founders agreement. Revisit annually. The conversation gets harder over time; the upfront awkwardness is much less than the eventual cost of unaddressed ambiguity.

Related: Co-founder · Founders Agreement · Founder Conflict · CEO · CTO

FAQ

What are founder roles?
The explicit division of responsibilities, decision-making authority, accountability, and titles among co-founders. Ideally documented at company formation in the founders agreement to prevent ambiguity that compounds into conflict over time.

What's the typical founder-role split?
For two-founder companies, CEO + CTO is most common (CEO runs business, CTO runs technology). Other patterns: CEO + COO (less common), and for three-founder companies, CEO + CTO + CPO or CEO + CTO + COO depending on what the founders specialize in. Co-CEO structures exist but typically create problems unless founders have a long working history.

Should founder roles change as the company grows?
Yes, often. Early-stage founder roles (everyone does everything) give way to more-specialized growth-stage roles. Founder-CEOs sometimes transition to chairman or CTO roles at later stages. Anticipate the evolution but document the current state clearly. Revisit role definitions annually to ensure they reflect current reality.