Handbook
/
Co-Founders & Leadership
Defining Founder Roles and Responsibilities
Clear roles prevent conflict and enable speed. Here's how to divide founder responsibilities.
Two founders. Both care deeply. Both have opinions on everything. Without clear roles, you get conflict, duplicated effort, and slow decisions. With clear roles, you get speed, accountability, and leverage. Defining who does what is one of the most important early decisions co-founders make.
Why Roles Matter
Speed of Decision-Making
Clear ownership means:
One person decides
No waiting for consensus
Faster execution
Less debate
Unclear ownership means:
Everything is a discussion
Decisions stall
Frustration builds
Accountability
When no one owns it:
Problems slip through
Blame gets diffused
Nothing gets fixed
When someone owns it:
Clear responsibility
Issues get addressed
Accountability is possible
Reduced Conflict
Role overlap creates friction:
“I thought I was handling that”
“Why didn’t you consult me?”
Stepping on toes
Clear boundaries reduce conflict.
Playing to Strengths
People have different abilities:
Let the better person handle each area
Leverage complementary skills
Don’t force fit
How to Divide Roles
By Function
The most common approach:
CEO (often the “business” co-founder):
Overall strategy and vision
Fundraising and investor relations
Hiring leadership
External representation
Company culture
CTO (often the “technical” co-founder):
Product development
Engineering team
Technical architecture
Technology decisions
COO (if three or more):
Operations
Finance
HR and admin
Process and systems
By Stage
Roles evolve as company grows:
Early stage:
Everyone does everything
Roles are flexible
Whoever’s best at it does it
Growth stage:
Specialization increases
Clear functional ownership
Hire into your weaknesses
Scaling stage:
Founders become executives
Lead functions or divisions
May shift to board roles
By Skill
Look at what each person brings:
Technical ability
Sales and relationship skills
Operational excellence
Fundraising capability
Industry expertise
Assign areas that match strengths.
By Interest
Don’t ignore what people want to do:
Forced roles breed resentment
People perform better in areas they enjoy
Passion shows through
Balance skill and interest.
The CEO Question
Do You Need One?
Early on, maybe not:
Small team, flexible roles
Decisions made together
No external need for hierarchy
Eventually, yes:
Investors want clarity
Team needs single point of authority
Deadlock needs breaker
Who Should Be CEO?
Consider:
Who’s best at external representation?
Who’s the strongest communicator?
Who do investors respond to?
Who can make the hard calls?
Who’s best at hiring and leading?
It’s not about deserving it. It’s about effectiveness.
If You’re Not the CEO
Being CTO or another role is not lesser:
Critical to success
Significant ownership
Different responsibilities, same importance
Ego shouldn’t drive the decision.
Decision-Making Authority
Levels of Decisions
Not all decisions are equal:
Day-to-day decisions: Owner of area decides alone.
Significant decisions: Owner decides, consults co-founder(s).
Major decisions: Co-founders decide together.
Existential decisions: Full founder + board alignment.
What Requires Consultation
Define what needs discussion:
Spending above $X
Hiring at certain levels
Strategic pivots
Major partnerships
And what doesn’t:
Routine expenses
Individual hires
Tactical choices
Domain-specific decisions
The Disagree-and-Commit Principle
When you can’t agree:
Discuss thoroughly
If still disagreeing, the owner decides
Everyone commits to the decision
No undermining later
You won’t always agree. That’s okay.
Overlap Zones
Inevitable Overlaps
Some areas span roles:
Product direction (CEO + CTO)
Hiring (everyone)
Culture (everyone)
Major strategy (everyone)
Managing Overlap
When multiple people care:
Define who has final call
Set consultation expectations
Respect the boundary once set
Supporting Each Other
Even outside your area:
Provide input when valuable
Support decisions made
Don’t undermine
Documenting Roles
Write It Down
Create clarity through documentation:
Who owns what areas
How decisions are made
What requires consultation
How conflicts are resolved
Review and Update
Roles evolve:
Check in quarterly
Adjust as needed
As company grows, roles change
Don’t set and forget.
Common Mistakes
No Clear Division
“We both do everything.”
Problem: Overlap, conflict, inefficiency.
Fix: Define ownership even if flexible.
All Decisions Together
Every decision requires both founders.
Problem: Slow, exhausting, doesn’t scale.
Fix: Delegate authority. Trust each other.
Wrong Person in Wrong Role
CEO because you had the idea, not because you’re best at it.
Problem: Suboptimal leadership.
Fix: Assign based on skill, not ego.
Not Updating Roles
Same division at 50 people as at 5.
Problem: Roles don’t fit current needs.
Fix: Revisit as company evolves.
Undermining Each Other
Second-guessing decisions publicly.
Problem: Team loses trust, confusion spreads.
Fix: Disagree privately, support publicly.
Role Evolution Patterns
Technical Founder → CTO → Advisory
As company grows:
Technical founder starts as only engineer
Becomes CTO as team grows
May eventually step back as engineering scales
Business Founder → CEO → Chairman
Over time:
Business founder leads company
May bring in professional CEO later
Could shift to chairman role
Both Founders → Role Shifts
Not uncommon:
One founder becomes CEO
Other becomes board member
Roles shift based on company needs
When Founders Step Back
Sometimes the right move:
Company outgrows founder skills
New phase needs different leadership
Founder effectiveness decreases
This isn’t failure—it’s good judgment.
Title vs. Responsibility
Titles Are External
Titles matter for:
Investor clarity
External credibility
Recruiting
Industry recognition
Responsibility Is Internal
What matters internally:
What you actually do
How decisions get made
Where you spend time
Don’t Over-Index on Titles
Focus on:
Clear responsibility
Effective collaboration
Playing to strengths
Titles can be adjusted; working well together is what matters.
Key Takeaways
Clear roles enable speed, accountability, and reduced conflict
Divide by function, skill, and interest—don’t force fit
The CEO question: who’s most effective at the role, not who deserves it
Define decision levels: what one person decides, what requires consultation
Use disagree-and-commit: discuss, decide, commit, don’t undermine
Document roles and review quarterly—they evolve as company grows
Support each other’s domains even when it’s not your area
Roles may shift as company scales; this isn’t failure
Title vs. responsibility: what you do matters more than what you’re called
Wrong person in wrong role hurts everyone—assign based on effectiveness
AIMake has access to all of this
Our AI has access to the entire Startup Handbook. Ask it anything about building your startup.
Get started
Previous
Founder Mental Health
Next
Leadership as a Founder