The word "fair" is doing quiet, heavy lifting in this question. For most people it secretly means "50/50, so nobody feels cheated." That instinct is generous, and it's also how a lot of partnerships end up mismatched two years in — when one person turned out to be full-time and betting everything, and the other was helping on nights and weekends, but they own the same half. Fair isn't about matching numbers. It's about matching numbers to reality.
What a fair split actually has to account for
A split is fair when it reflects what each of you brings and risks over the life of the company — not the warm feeling of an even handshake on day one. Weigh these honestly, out loud, together:
- Time commitment. Full-time versus part-time is the biggest lever. Someone quitting their job to build this is taking a different order of risk than someone contributing evenings.
- Money in. If one person funds the runway, servers, and legal out of pocket, that capital is worth equity too.
- The idea and the head start. Whoever brought the concept, early customers, domain expertise, or an audience is carrying real weight — but an idea alone is worth less than most first-time founders think. Execution is where value gets made.
- Who owns their function long-term. A co-founder who runs all of engineering, hiring, and technical decisions for years is worth more than someone building the first version and stepping back.
- Risk and replaceability. The person with the most to lose, doing the work fewest others could do, should hold more.
Why the reflexive 50/50 often backfires
An even split feels like the safe, friendly choice, so people reach for it to avoid an awkward conversation. But it quietly builds two problems. First, it can be genuinely unfair — rewarding equal ownership for unequal contribution — and resentment compounds. Second, a true 50/50 with no tie-breaker means that when you two disagree on something important, nobody can actually decide, and the company stalls. The friendly split becomes the deadlocked one.
The most expensive equity conversation is the one you skip to keep the peace. Split by what each person really carries, and you buy years of trust instead of a slow-burning grudge.
A way to reason toward your number
- 1Start from the honest baseline. Are you genuine equal partners taking the same risk full-time? Then a near-even split may be right. If not, don't force it.
- 2Adjust for the factors above. Move the number for full-time vs part-time, cash contributed, who brought customers, and who owns their function for the long haul.
- 3Decide who breaks a tie. Whether it's a slightly uneven split or a written tie-breaker, agree in advance how a genuine deadlock gets resolved so the company can keep moving.
- 4Put both stakes on vesting. Four years with a one-year cliff, for both of you. It means anyone who walks away early doesn't keep equity they didn't earn — and it protects the one who stays.
- 5Write it all down before building. Percentages, vesting, roles, and exit terms in a signed agreement. A handshake split is how founders lose control of their own company.
Vesting isn't an insult to your co-founder — it protects both of you. If one of you leaves in year one, the other shouldn't be stuck sharing the company with a person who's no longer building it. Good partners agree to vesting easily; hesitation to accept any protection is worth paying attention to.
The ranges people actually land on
When one person owns the idea, the domain expertise, and the go-to-market, and the other builds and runs the product, balanced first-time deals commonly put the technical co-founder somewhere in the 20–40% range, with a true co-equal partnership approaching an even split. If they're taking meaningful cash instead of pure sweat, the number trends lower. Treat those as anchors to reason from, not a rule — the point is that the split follows the contribution.
Have the hard version of the conversation now
The split conversation is uncomfortable, which is exactly why it is useful. How your prospective co-founder handles it — whether they can talk openly about risk, contribution, and what happens if things go wrong — tells you more about the next five years than their resume does. Someone who gets defensive, dodges specifics, or pushes for a number without justifying it is showing you how they will behave once real money is on the line. Someone who reasons through it fairly, accepts vesting without drama, and cares that you both feel good about the outcome is the partner you want. Treat the negotiation as the first real project you do together.
When an even split is the right answer
Sometimes 50/50 is genuinely fair: two people, both full-time, both betting their livelihood, complementary skills, shared risk from zero. In that case, split it evenly and add a tie-breaker so a deadlock can't freeze the company. The goal isn't to hand over as little as possible — a real partner with a fair stake beats a resentful one with a stingy one, and both beat 100% of an idea that goes unbuilt.
Common follow-up questions
Should idea versus execution change the split?
Yes, and usually more than idea-people expect. A concept on its own is fragile; the value comes from building it, selling it, and surviving the years in between. If you brought the idea and early customers but your co-founder builds and runs the product full-time, they've earned a substantial stake. Idea plus domain expertise plus distribution is real weight — but it rarely justifies keeping the lion's share while someone else does the building.
Is a dynamic or 'earned over time' split better than a fixed one?
Vesting already gives you a version of that: equity is earned by staying and contributing over four years, so someone who leaves early keeps less. Some founders go further and tie portions of equity to specific milestones or roles. Keep it simple where you can — an over-engineered formula creates its own arguments. A clear fixed split on a vesting schedule handles most situations well.
Want this answered for your exact situation?
We build and co-found software for people who have the idea and the network but not the technical team. Tell us where you're stuck and we'll give you a straight read — even if the honest answer is "don't build it yet."
See how we work