Solo founder or cofounder: should you start alone?
George · 3 min read
Going solo is no longer the unusual choice. With AI coding tools, managed hosting and payment providers that handle tax, one person can build and run a real product. That does not make it the right choice for everyone, and the wrong cofounder can sink a product faster than having none.
The question is not "is solo better?" It is "what is actually stopping me, and would another person fix it?"
What you gain by starting alone
Speed of decisions. You can change the pricing page at 11pm and ship it. Nobody needs convincing.
No split to get wrong. Equity, roles and money are simple when there is one person. Disagreements about them end many partnerships.
A product with one point of view. Small products often benefit from one person's taste. They stay focused on a narrow job.
What it costs you
Every job is yours. Building, support, billing, marketing, the boring renewals. The jobs you dislike tend to slip, and those are often the ones that bring customers.
Nobody catches your blind spots. A second person asks "why are we building this?" at the right moment. Alone, you can spend a month on a feature nobody asked for.
The bad weeks are lonely. When a launch brings nothing or a big customer leaves, there is nobody to share it with. This is where many solo projects quietly stop.
Signs you need a cofounder
- A skill gap blocks the core of the product. Not "I am bad at design", which you can buy or learn, but "I cannot build the thing at all" or "this product is sold through long enterprise deals and I have never sold anything".
- You plan to raise venture money. Many investors prefer teams, though it is far from a rule.
- Your own history says so. If every past project stalled when you were alone, believe that pattern.
Signs you do not
- You can build the first version and you are willing to do the selling, even badly at first.
- The missing skill is narrow and occasional: a logo, legal review, a security audit. Those are contractor jobs, not cofounder jobs.
- You mostly want company. A peer group can give you that without sharing ownership.
How to test a partnership before splitting anything
Treat it as a trial, not a commitment. Work on something real but small together for a few weeks: a feature, a launch, a weekend project. You will learn how the other person handles deadlines, disagreements and boredom, which no conversation reveals.
Then have the uncomfortable conversations while they are still easy:
- How many hours a week will each of you put in, and for how long without pay?
- Who decides when you disagree on product, and on money?
- What happens if one of you wants to stop?
- How will the equity be split, and will it vest over time?
Put the answers in writing. Vesting matters most: it means a cofounder who leaves after three months does not keep half the company. A lawyer can set this up properly, and it is far cheaper before there is anything to fight about.
If you go solo, set up what a cofounder would have given you
A second opinion. Find one or two founders at a similar stage and talk every week or two. Show them what you plan to build before you build it.
Outside accountability. Building in public works partly because it makes you ship something to talk about. Our post on what to share before you launch covers how.
Less work to share. Keep the product narrow, automate billing and onboarding, and pay for help with the occasional jobs you are worst at.
Protection for your energy. Burnout ends more solo products than competitors do. Read avoiding burnout as a solo founder before you need it.
The short version
- Ask what is stopping you, and whether a person would fix it.
- A cofounder is for a core skill gap or a pattern of stalling alone, not for occasional tasks.
- Test working together on something small first, then put roles and vesting in writing.
- If you go solo, replace what a partner gives you: peers, accountability and a narrow product.
Whichever way you start, a launch is a good first thing to ship together, or alone.
