Solo Founder vs Co-Founders: What the Research Says

Ask a room of investors whether a company should have one founder or several, and most will say several. Ask a researcher who tracks what happens to companies afterward, and you may get a more complicated answer. Both camps have real evidence, and they're often measuring different things.

This article lays out the conventional view, the academic evidence that pushes back on it, and what the data on co-founder conflict adds. Then it gives you a way to decide, including middle paths for founders who aren't ready to split the company. It doesn't cover who does what on a founding team (see co-founder roles) or the general definition of the team (see founding team).

The conventional view

The strongest popular statement comes from Paul Graham's essay The 18 Mistakes That Kill Startups, which lists "Single Founder" as mistake number one. His argument rests on three ideas.

• A signal. He suggests a lone founder may be someone who couldn't persuade friends, who know him best, to join. That's his interpretation, not a measured fact.
• Support. He writes, "Starting a startup is too hard for one person." Even if one person could do all the work, he argues, you need colleagues to brainstorm with, to talk you out of bad decisions, and to cheer you up when things go wrong.
• Resilience. He says the low points are so low that few could bear them alone, and that cofounders create mutual commitment.

Y Combinator's position is more measured than the essay's title suggests. Its FAQ says the accelerator regularly accepts solo founders, while its advice remains that one-person startups are tough and you're more likely to succeed with a co-founder. So the institutional stance is a preference, not a rule.

Notice what both sources are: informed practitioner judgment. They're drawn from watching many startups, but they aren't controlled comparisons. That's where the research comes in.

The academic counterpoint

Jason Greenberg (NYU Stern) and Ethan Mollick (Wharton) studied this directly in Sole Survivors: Solo Ventures Versus Founding Teams. Their data came from ventures that raised money on Kickstarter between 2009 and 2015, then formed legal entities and could be followed for several years. Summaries of the paper from NYU Stern and MIT Sloan report these results:

• Solo founders were about 2.6 times as likely to still own an ongoing for-profit venture as teams of three or more, and about 2.5 times as likely as two-founder teams.
• For-profit ventures started by solo founders also survived longer and generated more revenue, according to NYU's summary.
• The pattern reversed for nonprofits, where teams did better.

Greenberg's explanation, as the MIT Sloan piece reports it, is about friction. More founders bring more resources and networks, but they also bring social conflict that diverts time from productive work in the early days. He also argued that solo founders who succeed at crowdfunding tend to have a breadth of skills that may not match a top team's but is sufficient for success.

How far this evidence reaches

Be careful before applying this to your own company. The sample is crowdfunded projects, mostly consumer and creative products, not venture-backed B2B software with long sales cycles. A Kickstarter campaign tests whether a founder can ship a product people will pre-order. A B2B company has to hire, sell to procurement committees and survive enterprise buying cycles, where extra founders may matter more.

There's also a survivorship question: the study can only see ventures that got funded and formalized. And the NYU and MIT summaries quote slightly different figures for the drop in dissolution risk (55% and 54%), so treat the headline as "roughly half" rather than a precise number. The fair reading is that the study challenges the claim that teams always outperform, not that solos always win.

What the data says about co-founder conflict

If the academic case for solos is partly about avoiding conflict, it's worth asking how common conflict is. Harvard Business School's Noam Wasserman spent years on this question and wrote The Founder's Dilemmas. A summary of his talk at Business of Software records several of his findings:

• 65% of failures in his data came from people problems, such as tensions between co-founders or between founders and employees.
• 73% of startups split equity within a month of founding, the majority of those early decisions were never revisited, and most were equal splits.
• More than half of the startups in his dataset hired friends or family, which he compared to playing with fire.
• Founding-team tensions rise or fall with decisions about relationships, roles and rewards.

Two things follow. First, conflict is the main cost of the team route, and it's concentrated in decisions made fast and early, especially equity. Second, those decisions are at least partly under your control. A team that discusses roles, commitment and equity before it needs to is a different bet from one that shakes hands over coffee. For the mechanics, see founder equity and equity dilution.

Key Facts

• Paul Graham lists "Single Founder" as mistake number one in The 18 Mistakes That Kill Startups.
• Y Combinator says it regularly accepts solo founders but advises that a co-founder improves your odds.
• Greenberg and Mollick found solo founders about 2.6 times as likely to own an ongoing for-profit venture as teams of three or more, in a Kickstarter-based sample.
• Their nonprofit results ran the other way, favoring teams.
• Wasserman reports 65% of failures in his data were people problems, and 73% of startups split equity within a month of founding.
• The two evidence bases measure different things: practitioner judgment about venture outcomes versus survival of crowdfunded ventures.

The tradeoffs side by side

No single column wins. This table summarizes the tendencies described above plus common-sense mechanics.

The "key-person risk" row deserves its own look. A solo company is the extreme case of the exposure described in key-person risk, where illness, burnout or one bad year takes the whole business down.

When each choice makes sense

These are judgment calls, not findings. Use them as prompts.

A solo start can make sense when:

• The first version needs one person's skills and little else, such as a focused product you can build and sell yourself.
• You can reach your first customers through your own network or reputation.
• The market tolerates slow, capital-light growth, so you aren't racing to cover many functions at once.
• You've already worked with potential partners and found no one you'd trust with half the company.

A co-founding team makes more sense when:

• The company needs two or more hard-to-hire skills at once, like deep engineering and enterprise sales.
• You plan to raise venture capital early and expect investors to look for a team.
• The work is long, uncertain and emotionally taxing, and you know you'd stall without a sparring partner.
• You've worked with the person before and already trust their judgment under pressure.

One caution runs in both directions. Taking a co-founder to satisfy investors, or going solo because splitting equity feels painful, are both weak reasons. The first can leave you with a partner you don't fit with; the second can leave you with gaps you can't fill. Pair the choice with an honest look at founder-market fit: what you personally bring to this market, and what you don't.

The middle paths

The choice isn't strictly binary. Several structures give some of a team's benefits without splitting the company at the founding table.

1. Early key hires. Bring in the first engineer, designer or salesperson with meaningful equity, a clear title and real authority. They're not co-founders, but they cover a skill gap. The size of the grant is a negotiation; see the employee option pool.
2. Advisers. A few experienced people on a light-touch advisory arrangement can challenge your thinking without owning half of it. Advisers don't replace a partner's daily commitment, but they reduce isolation and fill knowledge gaps.
3. Angel backers as sounding boards. Some early investors are active partners in practice.
4. A trial period. Work on a defined project with a potential co-founder before committing equity. You'll learn how the two of you handle disagreement before you've handed over a large stake.
5. Staged equity. If you do take a partner, vesting protects both sides if someone leaves. It doesn't remove the conflict risk Wasserman describes, but it limits the damage.

Whichever path you choose, track it on your cap table from the first day, so later negotiations start from a clear picture.

How the team question changes over time

Founder structure isn't permanent. Solo founders add senior hires as the company grows, and co-founders sometimes leave. Both situations lead to the same later question of who runs what, which is covered in the management team below the founder. And if you're still working out how founders, co-founders and CEOs differ in practice, see founder vs co-founder vs CEO.

Related reading

• Founding team
• Co-founder roles
• Founder-market fit
• Founder vs co-founder vs CEO
• Founder equity
• Key-person risk
• Stages of a startup