The decision to split equity with a co-founder is the most consequential decision in your company's life. It outlasts every employee, every investor, and (usually) most marriages. Most founders rush it because they want to start raising. The ones who succeed take their time.
Where technical cofounders actually come from
The list, in rough order of success rate:
- People you've worked with. Past colleagues, collaborators on side projects, classmates from a graduate program. Highest signal because you know how they work under pressure.
- Friends-of-friends in your founder network. Introductions through other founders or your investors. Pre-vetted.
- Open source / community contributors. Someone who's contributed to a project relevant to your space. Their work is already public; you can read their code.
- Cofounder matching platforms. YC's, Antler's, others. Lower signal but high volume — useful if your network is thin.
Cold-applying engineers from LinkedIn is the lowest-success-rate path. Skip unless your other channels are dry.
What to look for
The traits that matter, in order:
- Builder instinct. Has shipped real things, ideally shipped to real users. Can describe specific bugs they've fought and won.
- Range. Comfortable across the stack — not because they need to be a specialist in everything, but because early-stage tech work is unpredictable.
- Communication. Can explain technical decisions to non-technical people. This becomes critical when you're selling to customers and investors who aren't engineers.
- Resilience. Has been through hard things — a failed project, a layoff, a brutal customer. Founders who've never been tested usually fold the first time the company hits a wall.
- Aligned ambition. They want to build a venture-scale company, not a profitable lifestyle business. Different goals = future conflict.
The four-month test
Don't sign equity in week one. Build something together first.
The minimum test:
- Weeks 1-2: Define a small, real problem to solve. Talk to potential customers together. Watch how they think about users.
- Weeks 3-6: Ship a small project together. Can be a prototype, a landing page, a research analysis. Watch how they plan, ship, and respond to setbacks.
- Weeks 7-10: Have a structured disagreement. Pick a real decision (architecture, hiring, pricing) and argue it through to a conclusion. How they argue matters more than how they agree.
- Weeks 11-16: Run the company together for 3-4 weeks before equity finalizes. Same hours, same decisions, same stress.
At any point in this process you might decide they're not the right co-founder. That's the point. Better to discover it now than 18 months in.
What to offer
A real co-founder gets:
- Co-founder title (CTO, technical co-founder, etc.). Not "head of engineering."
- Material equity — usually 30-50% of the founder equity, depending on timing and risk taken.
- Real decision rights over their domain. If you'll override their technical decisions, they aren't your co-founder.
- 4-year vesting with 1-year cliff. Always. Non-negotiable. Protects both sides if things don't work out.
- Founder salary parity. Once you have funding, both founders earn the same base. Different salaries between co-founders quietly poison the relationship.
Document it before any of it gets contentious
Once you've decided to commit, paper it within 30 days:
- Founders' agreement with equity split, vesting, and IP assignment.
- Articles of incorporation (if you haven't yet).
- Standard founder employment terms and confidentiality.
See our founders' agreement guide for what should be in the document. Skipping this step is the cause of half the cap-table horror stories you've heard.
Common technical-cofounder mistakes
- Promising "we'll figure out equity later." You won't. Decide before any of it gets contested.
- Skipping vesting because "we trust each other." Trust isn't the issue; protection is. Vesting protects the company and both founders.
- Hiring an "interim CTO" full-time. Either they're a co-founder or they're an employee — there's no middle ground that ends well.
- Splitting work too cleanly. "I do business, you do tech" sounds clean but breaks down within 6 months. Co-founders should overlap meaningfully on customers, hiring, and strategy.
- Equal equity when one founder did 80% of the work. The math should reflect the contribution. Forcing 50/50 to seem fair often creates the bigger fairness issue later.
Once you've found your cofounder, the next step is making it durable: paper the agreement, set up the cap table, and start building. Pair this with our founders' agreement guide and the cap table simulator.
FAQ
Should I split equity 50/50 with my technical cofounder?+
Probably not exactly 50/50. The right split depends on time of joining, capital invested, idea origination, and risk taken. Use our founder equity calculator (in development) for the structured math; default range is usually 40/60 to 50/50.
Should I find a cofounder before or after raising money?+
Before. Solo founders can raise pre-seed but it's significantly harder, and most investors expect at least 2 founders by seed. Find your cofounder first, then fundraise.
How long should I work with someone before committing?+
8-16 weeks of meaningful collaboration before signing equity. Build something real together. Have at least one disagreement and resolve it. The honeymoon phase tells you nothing useful.
Should my cofounder be technically equivalent to me?+
Different is better. The strongest founder pairs cover gaps — one technical/product, one commercial; one builder, one seller. Same skills means redundancy and disagreement on the same decisions.
What if my technical cofounder wants to leave?+
Painful but solvable if you have vesting in place. The standard 4-year vest with 1-year cliff means a year-one departure forfeits everything; later departures keep proportional equity. This is exactly why founder vesting exists.