How Much Equity for a Technical Co-Founder?
You have an idea, some early traction, and no way to build the product yourself. So you go looking for a technical co-founder, and almost immediately you hit the question nobody wants to get wrong: how much of the company should they get? Give away too much and you have permanently diluted the person carrying the vision; give away too little and you cannot attract anyone good, or you build resentment into the foundation. This guide gives you a plain-language framework: the realistic ranges, the factors that actually move the number, the terms that protect you, and the honest alternative of not giving away equity at all.
The short answer
For a genuine co-founder who joins at the beginning, shares the risk, works full-time, and is committed for the long haul, the equity is typically substantial - often somewhere between a quarter and a full half of the founder pool. A true day-one partner with equal skin in the game frequently lands near an even split. Someone who joins later, keeps a paying job, or is really an early employee with a fancier title lands much lower, sometimes in low single-digit or teen percentages. The rest of this article is about where inside that wide range your situation actually sits, because "it depends" is only useful once you know what it depends on.
What actually moves the number
Five things drive a technical co-founder's fair share. Run your candidate against each one and you will have a defensible number instead of a gut feeling.
| Factor | Pushes equity UP | Pushes equity DOWN |
|---|---|---|
| Timing | Joins at day zero, before anything is proven | Joins after launch, revenue, or funding |
| Risk taken | Quits their job, works for little or no salary | Keeps a full salary elsewhere, works part-time |
| Commitment | Full-time, all-in, long-term | Nights and weekends, uncertain horizon |
| Contribution | Owns all of product and engineering | Builds one piece, or hands off after version one |
| Replaceability | Rare skills, deep domain fit, brings a network | Skills you could hire or contract readily |
The single most important column is risk. A person who leaves a stable salary to build your product with no guarantee is buying into the same uncertainty you are, and that is what co-founder equity pays for. A person who keeps their day job and codes on weekends is taking almost none of your risk, and their equity should reflect that, no matter how talented they are.
Common splits and what they signal
It helps to see the typical bands and what each one implies about the relationship. These are directional, from what we see in the market, not rules.
| Rough share | Who it fits | What it signals |
|---|---|---|
| ~50% | True day-one partner, equal risk and commitment | A genuine co-founder relationship of equals |
| ~20-40% | Joins early but after you, or you brought traction or capital first | A co-founder, but you are the lead founder |
| ~5-15% | Joins post-launch, or part-time, or one focused mandate | Founding engineer more than equal co-founder |
| ~1-3% | Early key hire after risk is largely removed | A senior employee grant, not a co-founder split |
The uncomfortable but useful move is to be honest about which row you are really in. Many "co-founder" arrangements are actually founding-engineer or early-hire situations dressed up in co-founder language, and pricing them as an equal split is how founders give away half their company for what a market-rate grant would have bought. If you are not even sure you need a co-founder versus a hire or a build partner, work through do I need a technical co-founder first.
Vesting and a cliff are non-negotiable
Whatever number you land on, never grant it all at once. Equity should vest over time, and the standard that exists for good reason is four-year vesting with a one-year cliff. Here is what those terms mean in plain language:
- Four-year vesting means the equity is earned gradually over four years, not owned outright on day one. It ties the reward to staying and building.
- One-year cliff means nothing at all vests in the first twelve months. If the person leaves at month eleven, they walk away with zero equity. At the one-year mark, a full year's worth vests at once, and the rest then vests month by month.
The cliff exists for the most common and most painful scenario in early startups: a co-founder who turns out to be the wrong fit and leaves after a few months. Without vesting, that person keeps a huge slice of your company forever, having contributed a few months of work, and that dead equity on your cap table can sink your next fundraise. Vesting is not a sign of distrust; it is standard, it protects both sides, and any serious co-founder will expect it. Put it in writing, signed, before anyone starts.
Equity is the most expensive money you will ever spend
Founders reach for equity because it feels free - no cash leaves your account today. It is the opposite of free. If your company succeeds, the slice you gave away could be worth far more than any invoice you were avoiding, and unlike a bill, it never gets paid off. So before you trade a large share of the company for someone to build version one, ask a sharper question: is your real need a lifelong partner who shares the risk for years, or is it simply to get the product built and in front of users?
Those are very different needs, and equity only fits the first one. If what you actually need is the build, paying cash for it is almost always cheaper in the long run than paying in company. A focused MVP built by a studio typically costs a defined amount of money - you can sanity-check the range with our guide on how much an MVP costs in 2026 or the free MVP cost calculator - while a co-founder's equity is an open-ended claim on everything you build afterward.
A framework to decide
Put it together into a sequence you can actually run:
- Name the real need. A long-term partner, or a one-time build? If it is the build, price it in cash and keep your equity.
- Place the person on the table above. Timing, risk, commitment, contribution, replaceability. Be honest about which row they occupy.
- Set a range, not a point. Pick a band from the splits table and leave room to negotiate inside it.
- Attach vesting and a cliff to whatever you agree. Four years, one-year cliff, in writing, always.
- Write it down before work starts. A signed founder agreement, not a verbal promise.
Common mistakes founders make
- Defaulting to 50/50 to avoid a hard conversation. An even split should be earned by equal risk, not chosen to keep the peace.
- Granting equity with no vesting. The single most expensive shortcut in early-stage startups.
- Confusing a contractor with a co-founder. Someone paid to build a defined thing is a vendor, and vendors take cash, not company.
- Giving co-founder equity for a part-time, salaried helper. Match the equity to the risk actually taken.
- Skipping the lawyer. The cheapest founder agreement is far less expensive than the cheapest founder dispute.
The alternative: buy the build, keep the company
If, after all of that, your honest answer is "I mostly just need version one built well and shipped," you do not need to give away any equity at all. A fixed-price development studio builds the product for a known amount of cash, and you keep 100% of the company. That is exactly how we work at SquadPrime: one fixed price from $4,000, a senior-only team, and you own all of the code - no dilution, no co-founder to buy out later if the fit is wrong. We go deeper on this tradeoff in technical co-founder vs development agency. Equity is the right currency for a genuine long-term partner; it is an expensive way to pay for a build you could simply commission.
Have a spec? Get one fixed price for it.
Bring your spec to a free 30-minute call. We will pressure-test the scope, flag anything that will inflate the build, and quote one fixed price (from $4,000). Live in 14 days or you don't pay, and you own all the code.
Get My Launch Date & Fixed PriceFAQ
Is a 50/50 split with a technical co-founder a mistake?
Not automatically. An equal split is fair when both founders start at the same time, take the same risk, and are equally committed for the long haul. It becomes a mistake when one person joined months later, keeps a salary elsewhere, or is really an early employee in disguise. Match the equity to the real contribution and risk, not to a wish to avoid an awkward conversation.
Should a technical co-founder who joins after launch get less equity?
Usually yes. Someone joining after you have proven demand, built version one, and reduced the risk is buying into a safer bet than a day-one partner, so their share is typically smaller. The later they join and the less risk remains, the closer their equity moves toward a senior-hire grant rather than a co-founder split.
What vesting terms are standard for a co-founder?
A four-year vesting schedule with a one-year cliff is the common standard. Nothing vests in the first year; if the person leaves before month twelve they keep nothing. After the cliff, the remaining equity vests monthly over the next three years. This protects the company if a co-founder walks away early, which is exactly when unvested equity matters most.
Can I build an MVP without giving away equity?
Yes. If your main need is to get version one built and in front of users, a fixed-price development studio does that for cash while you keep 100% of the company and the code. Equity is the right currency for a long-term partner who shares the risk for years; it is an expensive way to pay for a one-time build.
This article is general guidance drawn from our own experience, not legal, tax or financial advice; equity, vesting and founder agreements have real legal consequences, so confirm your specifics with a qualified attorney. Ranges reflect what we typically see and were current as of September 21, 2026. Spotted something outdated or inaccurate? Email talk@squadprime.com and we'll correct it promptly.
Related: Do I need a technical co-founder? · Technical co-founder vs development agency