Co-founder conflict kills more early startups than competition does. Here is where founders actually meet, how to test a partnership before committing, and the four things to settle in writing on day one.
Solo founding is harder, and co-founding is riskier. Both are true, which is why this decision deserves more thought than it usually gets.
The failure mode is specific and common: two people who like each other agree to build something together, split equity evenly in a conversation, never write anything down, and discover eighteen months later that they wanted different companies.
The romantic version is a chance meeting at a hackathon. The realistic version is much less dramatic.
Former colleagues. By a wide margin the most common source, and the best one. You already know how the person handles pressure, deadlines, and disagreement. That information is almost impossible to get any other way.
College and alumni networks. Strong in India, particularly the IIT, NIT, BITS, and IIM networks. The shared context helps, though shared background also means shared blind spots.
Accelerators and founder communities. Structured programs put you in a room with people who have already self-selected for wanting to build. This is one of the underrated benefits of a cohort program.
Domain communities. If you are building for a specific industry, the co-founder who understands that industry is usually already in it, not in a startup community.
The worst source is a stranger who responded to a "looking for technical co-founder" post. Not because those people are bad, but because you will have no information about how they behave when things go wrong.
Never make someone a co-founder on the strength of a good conversation. Work together on something real first, for at least four to six weeks.
Look for these things specifically:
The usual advice is "find someone complementary," which founders read as "one technical, one business." That is often right but too shallow.
The split that matters more is who owns the product and who owns the customer. Every early startup needs someone waking up thinking about what to build and someone waking up thinking about who will pay. Two people who both want to build, or both want to sell, will have a gap neither notices until it is expensive.
Equity split. Equal splits are fine and common. Unequal splits are also fine when someone genuinely contributed more, but be honest about why. What is not fine is leaving it vague. Decide, write it down, sign it.
Vesting. Four years, one-year cliff. This is not distrust, it is insurance for both of you. Without vesting, whoever leaves first walks away with a permanent stake in work they did not do, and every investor will treat it as a problem.
Roles and final say. Not a detailed org chart. Just: who decides when you disagree, and on what. Product calls to one person, commercial calls to the other, is a workable default.
What happens if someone leaves. Voluntary exit, involuntary exit, and the awkward middle case where someone quietly disengages. Agree the mechanism while you still like each other.
All four belong in a founders agreement signed before you build together. Our guide to the legal documents Indian founders need covers what else belongs in that first year.
If you cannot find the right person, found alone rather than settling. A wrong co-founder is significantly worse than no co-founder, because the equity is gone and the relationship is entangled with the company.
Solo founders can hire, contract, and find advisors. What they mostly lack is someone to think with, which is why the community around a program matters more for them. That is part of what LVL1 Startup School is built to provide: operators to think with, and a cohort of founders at the same stage.
Before you spend money building, get an honest read from an LVL1 mentor on whether the problem is real. It is free.
Chennai produces some of the most capital-efficient, globally competitive SaaS companies in the world. Here's the specific playbook they use to win.
Bootstrapping and venture capital are treated as a values statement, but they are really just two different tools for two different kinds of businesses. Here is how to actually decide which one fits your startup.
A brilliant product without a go-to-market strategy is a tree falling in a forest. Here's the GTM playbook that early-stage startups in India and globally are using to acquire their first 100 customers.