Table of Contents >> Show >> Hide
- What Is a Co-CEO Model, Really?
- Why Founders Even Consider Co-CEOs
- The Case for Co-CEOs
- The Case Against Co-CEOs
- When Co-CEOs Can Actually Work
- What Would SaaStr Say to a Founding Team Considering Co-CEOs?
- A Practical Framework: Should You Go Co-CEO?
- If You Do Go Co-CEO, Here’s How to Set It Up
- Real-World Experiences with Co-CEOs (and Near Misses)
- So… What Should You Do?
If you hang out in SaaS Twitter or at founder dinners long enough, there’s a question that eventually pops up between the third coffee and the first existential crisis:
“Should we try a co-CEO model?”
On paper, it sounds dreamy: two brilliant founders sharing the load, splitting investor calls and all-hands, tag-teaming product and go-to-market like a superhero duo. In practice, it can look more like a buddy movie that quietly turns into a drama: unclear decisions, confused teams, unhappy boards, and a lot of “Wait… who’s actually in charge of this?”
SaaStr’s Jason Lemkin has admitted he’s mellowed a bit over time on co-CEOs. Historically, many investors (and most boards) saw the model as a red flag. But reality is getting more nuanced. Data from leadership research and real-world examples from companies like Netflix, KKR, Spotify, and others show that
co-CEOs can work in specific conditionsbut those conditions are tighter than most founders want to admit.
What Is a Co-CEO Model, Really?
A co-CEO structure isn’t just “two founders both calling themselves CEO on LinkedIn.” At least, that’s not what it should be.
In a proper co-CEO model:
- Both executives hold the formal title of CEO and report to the board.
- The board holds them jointly accountable for company results.
- They split responsibilities, usually across domains (e.g., product/tech vs. sales/operations).
- They present a single, unified voice externallyto investors, customers, and employees.
Think of it as a legally binding “founder marriage with joint P&L custody.” It’s not just vibes; it’s structure, governance, and a lot of emotional maturity.
Why Founders Even Consider Co-CEOs
Founders don’t wake up one day and randomly say, “You know what this chaos needs? Two CEOs.” The idea usually emerges from real pain:
- Two strong founders both feel like “the” leader. They’ve built the company together, and neither wants to be “demoted” to COO or President.
- The business is getting more complex. One person feels stretched thin across product, people, sales, finance, fundraising, and the occasional office chair procurement.
- Complementary skill sets. One founder is deeply product-obsessed, the other is a go-to-market machine. Splitting along that natural fault line is tempting.
- Continuity and succession. Sometimes a long-time co-founder is elevated to share the top job to smooth leadership transitions.
Add to that the growing number of co-CEO structures in larger companieslike Netflix, KKR, and several othersand suddenly co-CEOs don’t seem like such a fringe idea anymore.
The Case for Co-CEOs
Let’s start with why anyone sane would choose this path voluntarily.
1. Two Brains for a Very Hard Job
Being CEO of a scaling SaaS company is intellectually and emotionally brutal. Research on CEO performance shows that top leaders juggle strategy, culture, capital allocation, and constant uncertainty. Sharing that load can mean better decisions and fewer blind spots, especially in complex, fast-changing environments.
When the co-CEOs have complementary skillssay, one is deeply technical and the other is commercially giftedthe partnership can feel like “full-stack leadership.” One goes deep on product, architecture, and long-term innovation, while the other drives revenue, GTM strategy, and capital markets.
2. Built-In Resilience and Coverage
Co-leadership can add resilience. If one CEO is temporarily outdue to health, family, or burnoutthe other can keep things moving. That’s a non-trivial advantage in high-pressure SaaS environments where the CEO is usually the central node for fundraising, major customers, and key hires.
Some leadership experts also argue that co-leaders can better model collaboration at the top, showing the rest of the organization what shared ownership and constructive conflict look like when done right.
3. Better Representation of a Complex Business
As SaaS businesses expand globally, add multiple product lines, and run more complex partnerships, no single person can be in every room. Having two CEOsone closer to product and customers, another closer to markets and capitalcan mean richer insight, more time with stakeholders, and fewer dropped balls.
This becomes especially useful in companies that span very different markets or business models, where a single leader could end up deeply out of their depth in half of the conversations.
The Case Against Co-CEOs
Now for the part most VCs and boards instinctively jump to: all the ways this can go sideways.
1. No Clear Tie-Breaker
The classic complaint: if both CEOs truly have equal power, who decides when they disagree? In theory, they hash it out. In practice, unresolved disagreements trickle down into the org, where teams get mixed signals and projects stall.
Without a clear tie-breaking mechanismeither one CEO having final say in certain domains or a board process for deadlocksdecisions can slow to a crawl just when the company needs speed most.
2. Confusion for the Team
If your employees are constantly asking, “Do I need both CEOs to sign off on this?” you have a problem. Co-CEO setups often fail not because the leaders are bad, but because the org chart is fuzzy. People don’t know who to escalate to, who owns which KPIs, or which CEO’s opinion “wins.”
In startups where clarity is already in short supply, adding ambiguity at the very top can amplify anxiety and politics.
3. Different Styles, Different Signals
Even if co-CEOs deeply respect each other, their leadership styles might diverge. One is blunt and direct, the other is diplomatic and consensus-driven. One is optimistic, the other is cautious. None of that is inherently badbut if those differences aren’t acknowledged and managed, the organization experiences them as whiplash.
Over time, teams can start “CEO shopping”going to the leader who’s more likely to say yeswhich quietly erodes the partnership and undermines authority.
4. Board and Investor Friction
Many investors still prefer the simplicity of “one neck to choke.” In a co-CEO world, the board must invest more effort in managing the relationship, synchronizing expectations, and giving feedback. If they’re not willing to do that workor if the co-CEOs aren’t open to clear accountabilitythe model quickly becomes a governance headache.
When Co-CEOs Can Actually Work
So if the default answer is “be careful,” when does a co-CEO setup make sense, especially in SaaS?
1. Long, Proven History of Working Together
Successful co-CEO pairs typically have a long shared history: they’ve worked together for years, survived multiple crises, and already learned how to disagree productively. They trust each other with reputation, equity, and hard calls.
If you’re still figuring out how to give each other feedback without blowing up, you’re not ready for matching “CEO” titles.
2. Clearly Defined and Complementary Mandates
The most functional co-CEO arrangements have a crisp split of responsibilities. For example:
- Co-CEO A: Product, engineering, design, long-term innovation.
- Co-CEO B: Sales, marketing, customer success, finance, operations.
Each leader knows which metrics they directly own, which orgs they lead, and where they have final say. They still co-own strategy and culture, but execution lanes are clear.
3. One Voice Externally
Whatever the internal split, investors, customers, and press see a united front. That means:
- Agreeing on the story before going into board meetings.
- Not contradicting each other in public or in front of the team.
- Sharing credit and blame, not playing the “I told you so” game.
If a customer or investor walks away thinking, “Wow, those two are clearly not aligned,” your co-CEO structure is already costing you.
4. Strong Feedback and Conflict Mechanisms
The best co-leadership setups treat feedback as a system, not a vibe. There are structured check-ins, agreed rules of engagement for conflict, and sometimes even external coaching or facilitation. Co-CEOs who survive and thrive typically treat their relationship as something that must be actively maintained, not passively assumed.
What Would SaaStr Say to a Founding Team Considering Co-CEOs?
If you sent this question into a “Dear SaaStr” inbox, the answer would probably start with:
“Default to one CEO unless you are very sure you’re the exception.”
In early-stage SaaS, you benefit immensely from:
- Fast, decisive decision-making.
- Clear lines of authority for the team.
- A single ultimate owner responsible for hitting plan.
Co-CEOs add overhead: more meetings, more coordination, more risk of misalignment. Unless the benefits are overwhelmingly clear, it’s usually better to pick one CEO and give the other founder a powerful, well-defined role (President, COO, Chief Product Officer, etc.) with meaningful ownership and authority.
A Practical Framework: Should You Go Co-CEO?
If you’re seriously thinking about it, run through this checklist with painful honesty.
1. Motivation Check
Are you choosing co-CEOs because it’s the best structure for the company, or because it’s emotionally hard to pick one person to be CEO? Those are very different things.
If pride and title are the core drivers, consider getting coaching, mediating the conversation, and designing roles that honor both founders without forcing a co-CEO model.
2. Trust and History Check
Ask yourselves:
- Have we already made multiple hard decisions together under pressure without damaging the relationship?
- Can we give each other blunt feedback without defensiveness?
- Have we ever successfully split ownership of major areas before?
If the honest answer is “not yet,” co-CEO is probably too big a stress test, too soon.
3. Clarity Check
Before you tell anyone externally, you should be able to write a one-page “co-CEO charter” that covers:
- Who owns which functions and metrics.
- How decisions are made when you disagree.
- How you’ll present decisions to the team and board.
- What success and failure look like for the model.
- What the exit ramp is if it’s not working.
If you can’t write that document, you’re not ready.
4. Board and Investor Alignment Check
You cannot surprise your investors with “Oh by the way, we now have two CEOs.” They willvery reasonablyask why this is better than a single, clearly accountable leader.
You’ll need to walk them through:
- Why this structure is necessary given your strategy and growth stage.
- What safeguards are in place to prevent gridlock.
- How reporting and performance evaluation will work.
If you can’t convince your most aligned capital partners, that’s a signal.
If You Do Go Co-CEO, Here’s How to Set It Up
Let’s say you’ve done the soul-searching, and co-CEOs still make sense. How do you avoid becoming a cautionary thread in some future SaaStr post?
1. Draft a Co-CEO Charter
Put your co-CEO operating system in writing:
- Division of responsibilities and reporting lines.
- Decision rights and tie-breaker rules.
- Cadence for 1:1s, strategy sessions, and board updates.
- How you’ll handle disagreements and escalations.
Treat it like a prenuptial agreement for the C-suite: ideally never needed in anger, but very helpful to have.
2. Over-Communicate with the Company
Don’t just announce “We’re co-CEOs now” and drop a new org chart. Explain:
- Why you’re doing this and what’s in it for the company.
- Which CEO owns which teams and decisions.
- How people should escalate issues and who signs off on what.
You want people to walk out of the all-hands saying, “Okay, I get who I go to for what,” not “So now I need two approvals for everything?”
3. Add Structured Feedback from the Board and Exec Team
Set a recurring review (every 6–12 months) where the board and executive team evaluate:
- How the co-CEO relationship is working.
- Whether decision-making has become faster or slower.
- Whether the organization feels clearer or more confused.
Agree ahead of time that if certain metrics or signals are negative for too long, you’ll revisit the structure.
4. Define the Exit Ramp
A mature co-CEO setup includes a pre-agreed path to “back to one CEO” without drama. That might be:
- One co-CEO eventually becoming the sole CEO, with the other shifting into a major operator or chair role.
- Transitioning to a single external CEO while both co-founders move into board or strategic roles.
Having this conversation early makes it far easier to navigate reality later.
Real-World Experiences with Co-CEOs (and Near Misses)
To make this more concrete, let’s look at a few composite “Dear SaaStr”–style experiences drawn from patterns seen across SaaS and startup leadership stories.
Story 1: The Accidental Co-CEOs
Two founders, both technical, start a developer-focused SaaS tool. Early on, nobody cares who’s CEOtitles are mostly for signing documents and investor decks. As the company grows past 60 people, things start breaking:
- Sales doesn’t know whose roadmap promises to believe.
- Recruiting hears different answers on headcount priorities.
- The board gets two slightly different versions of the strategy depending on who they talk to.
Eventually, the board nudges them to pick one CEO. They do, and within six months, decision latency drops, the roadmap stabilizes, and the founders realize that most of the tension had come from unspoken expectations. In hindsight, they admit: “We weren’t really co-CEOs; we were co-founders avoiding a hard conversation.”
Story 2: The Product & GTM Duo That Works
Another startup, this time with a clear split. One founder has 15 years of deep domain and product expertise; the other is a repeat CRO with a track record of scaling ARR from $5M to $50M+. As they hit $25M ARR and expand into multiple regions, the load becomes intense.
The board proposes a co-CEO structure with:
- One CEO owning product, R&D, and long-term innovation.
- The other owning sales, marketing, CS, and revenue operations.
They codify their charter, align on a unified story, and schedule weekly 1:1s purely dedicated to alignment. Three years later, they’ve doubled ARR, expanded into new markets, and kept the exec team relatively stable. When asked what made it work, they say: “We treat our partnership like the most important relationship in the company. We never let resentment ‘age’ more than a week.”
Story 3: The “Promotion” That Backfired
In a different case, a long-time COO is promoted to co-CEO alongside the founder to recognize their contribution. On paper, it’s a reward. In practice, nothing else changes:
- The founder still makes all major decisions.
- The new co-CEO doesn’t get full authority over any functions.
- The rest of the exec team quietly assumes the founder is still “the real CEO.”
Within a year, the promoted co-CEO leaves. The board is frustrated, the founder is exhausted, and the company has to rebuild its leadership bench. Looking back, everyone admits that a clearer, more empowered COO roleor an eventual, well-planned full transitionwould have been healthier than a symbolic co-CEO title.
Story 4: The Early Decision That Prevented a Mess
Finally, there’s the founding pair who almost went co-CEO but didn’t. They did the work: drew up a charter, talked to their investors, and even interviewed other founders who had tried co-CEOs.
They realized:
- They didn’t yet have a strong feedback culture between them.
- They still occasionally avoided hard conversations.
- One of them secretly did not want to share the CEO role long term.
So they chose one CEO, with a clear path for revisiting the structure in the future. Ironically, that honesty strengthened their relationship far more than forcing a co-CEO title ever would have.
So… What Should You Do?
In classic SaaStr style, the answer is:
“It depends… but probably not, unless you’re certain you’re the exception.”
For most SaaS startups, a single, clearly accountable CEO is simpler, faster, and easier to govern. Co-CEOs can workbut only when you have:
- A deep, proven foundation of trust.
- Very complementary skills and clearly split mandates.
- A well-defined charter, feedback system, and exit ramp.
- Full alignment from your board, exec team, and company.
If you’re still early, still figuring out culture, or still having awkward conversations about who owns what, you probably don’t need co-CEOs. You need clarity, courage, and one person whose job description literally says “the buck stops here.”
