TL;DR
A technical co-founder who joins early, before real funding, and takes genuine risk usually gets somewhere between 20% and 50% of the company, and most often lands near an equal split when they're building the entire product from scratch. The number moves down as the non-technical founder has already removed risk (a working product, paying customers, money raised, a prior exit) and as the technical person takes a real salary. It moves up the earlier they join, the more the business depends on what they build, and the less cash they're paid.
Two things matter more than the exact percentage: get it in writing with a vesting schedule (typically four years with a one-year cliff), so neither side is trapped or robbed, and treat this as general guidance, not legal advice, a startup lawyer should paper the actual split. The rest of this guide gives you the range, the factors that move it, a simple way to reason about your own number, and the alternative if giving away a large slice of your company feels wrong.
Key Takeaways
- A technical co-founder who joins early and takes real risk usually gets 20% to 50%, often near an equal split when building the entire product.
- The share moves down as the non-technical founder has removed risk (a working product, customers, money raised) and as the technical person takes a salary.
- It moves up the earlier they join, the more the business depends on what they build, and the less cash they are paid.
- Get it in writing with a vesting schedule, typically four years with a one-year cliff.
- Treat this as general guidance, not legal advice; a startup lawyer should paper the actual split.
The honest starting point: near-equal
For a true co-founder who joins early and shares the risk, the honest default is to start the conversation near an equal split, not at a token 5% or 10%. This surprises many non-technical founders, especially when the company is built on their idea, so it's worth being blunt about why.
Ideas are cheap; execution is what creates value. A startup is worth nothing until something is built, shipped, and used, and in most software companies that work falls on the technical founder. A strong engineer can usually build a product on their own and go find a business partner later, which means when they join you, they're giving up the option to keep 100% for themselves. The equity is what makes that trade worth it. Undervaluing it is one of the most common reasons good non-technical founders stall for months: they try to hand over 5%, no serious engineer accepts, and the product never gets built.
That does not mean every technical co-founder gets 50%. It means 50% is the honest starting point for two people taking similar risk and making similar contributions, and you adjust from there based on what each side actually brings.
What moves the number up or down
The split is really a question of relative risk and contribution. Here's what pushes a technical co-founder's share in each direction.
| Pushes their share DOWN (you've de-risked it) | Pushes their share UP (more risk on them) |
|---|---|
| There's already a working product | They join at the idea stage, nothing built |
| There are paying customers or real traction | No traction yet, they build it from zero |
| You've raised funding | No funding, they work unpaid |
| You take little or no salary too | They forgo salary while you're paid |
| You have a prior exit or strong track record | Neither founder has a track record |
| You bring the money, network, and sales | You bring mainly the idea |
| They take a meaningful salary | They take equity in place of salary |
The logic is consistent: every risk you've already removed is worth equity you get to keep. If you show up with a live product, paying users, and money in the bank, the technical co-founder is joining something far safer, so their fair share is smaller. If they're the one turning a blank page into a real product with no salary, their share is larger.
A simple way to reason about your number
One widely cited approach (popularized by Nathan Hurst) is to reason subtractively: start both founders at roughly equal, then reduce the incoming technical co-founder's share for each meaningful way you, the non-technical founder, have already reduced the company's risk. A working prototype you paid to build, paying customers, capital raised, a prior successful startup: each of these is a real de-risking event, so each trims the slice the technical person needs in order to be fairly compensated for the risk they're taking now.
A worked example, in that spirit and with round numbers:
- Start the technical co-founder near 50% (equal risk, equal contribution assumed).
- You already have a working product built: trim it (say to ~40%).
- You have early paying customers: trim again (say to ~30%).
- You've raised a small round: trim again (say to ~20% to 25%).
So a non-technical founder who shows up with a working, revenue-generating, funded product might fairly offer a strong technical co-founder in the low-20s percent, while one who shows up with only an idea should expect to be near an equal split. These are illustrative, not rules: the point is the direction of the logic, not the exact digits.
Real-world ranges founders actually agree on
Advice essays give principles; here's roughly where real early-stage deals tend to land, based on how founders and engineers consistently talk about it. Use it as a sanity check, not a formula.
| Situation | Typical technical co-founder share |
|---|---|
| Joins at idea stage, builds everything, no salary, no traction | 40% to 50% |
| Joins early, builds the product, small or no salary, little traction | 25% to 40% |
| Joins with some traction and/or a modest salary | 15% to 25% |
| Joins after the product exists and is funded, takes a real salary | 5% to 15% |
Notice the pattern: the more they build, the earlier they join, and the less cash they take, the closer to half they should be. Below roughly 10% for someone building and running all the technology, you're offering a lead developer package, not a co-founder one, and strong candidates will read it that way and pass.
Salary versus equity: the core trade-off
Equity and salary are the two levers, and they move against each other. A technical co-founder taking founder-level risk with no salary is entitled to more equity, because their compensation is entirely a bet on the future. If you can pay a real salary, it's fair for their equity to be lower, because you've removed their personal financial risk.
The honest framing for your offer: decide what cash you can pay (often between zero and a lean "ramen" salary early on), then set equity to match the risk that's left. What you should not do is pay nothing and offer a tiny equity slice, that's asking someone to take all the risk for almost none of the upside, and it's exactly the offer serious engineers have learned to decline instantly.
Always vest: protect both sides
Whatever percentage you agree on, it must vest. Vesting means the equity is earned over time rather than granted all at once, and it protects everyone:
- Standard is four years with a one-year cliff. Nothing vests for the first year; if the co-founder leaves (or it doesn't work out) in month six, they keep nothing. After the cliff, equity vests gradually, usually monthly.
- It protects you from the nightmare of a co-founder walking away in month three still owning a huge, permanent chunk of your company.
- It protects them by making the commitment real and mutual, and it's what investors will expect to see anyway.
Handing over un-vested equity on a handshake is one of the most damaging mistakes early founders make. Get a cap table, a vesting schedule, and written terms, and have a startup lawyer set it up. This is the part where "we trust each other" is not a substitute for structure.
Remember: you're recruiting a partner, not buying code
A recurring confusion is treating equity as the price of the code, as if you're paying for a deliverable. You're not. A co-founder's equity reflects partnership and shared risk over years, not the hours to build version one. This is the difference between a co-founder and a hire: you can hire a developer or even a CTO for salary, but a co-founder is someone taking the journey with you, and their stake has to reflect that. If what you actually want is the product built, without giving away a large, permanent share of the company, that's a different decision, and a legitimate one (next section). For how to actually find and vet that partner in the first place, see how to find a technical co-founder.
The alternative: keep your equity, build it with a team
Here's the honest counter-question worth asking before you give away 20% to 50% of your company forever: do you need a co-founder, or do you need the product built?
If it's mainly the latter, there's another path. You can hire a specialist team to build your MVP, keep 100% of your equity, get real users, and then decide whether you even still need a technical co-founder, or attract a much stronger one on the back of proven traction. Giving away half your company to someone whose fit you can't yet know is a permanent decision made at the point of maximum uncertainty. Building first, and keeping your equity, defers that decision until you have real information.
That is the alternative we offer: instead of signing away 20% to 50% of the company to get a product built, you keep all your equity and pay a fixed price for the build. We scope the core flow with you, agree the price before any work starts, and ship it in 3 to 4 weeks, with auth, payments, deployment, and code you own outright. Then you validate, and decide on a co-founder, if you still want one, from a position of traction, where the equity you would give up buys far more. If you are weighing an equity offer against just getting it built, price the build before you price the equity.
Common mistakes founders make
- Offering a token slice to a real co-founder. 5% to someone building and running all the technology won't attract anyone good, and signals you don't value the work.
- Skipping vesting. Granting equity outright, then watching a co-founder leave early with a permanent chunk.
- Paying nothing and offering little equity. All risk, no reward: the fastest way to get ignored by strong engineers.
- Treating equity as the price of code. It's the price of partnership and years of risk, not of building version one.
- Doing it on a handshake. No cap table, no written terms, no lawyer, which is how co-founder disputes and lawsuits start.
- Anchoring to your region's low salaries. Fair equity for co-founder-level risk doesn't shrink because cash is cheap where you are.
Related guides
- How to find a technical co-founder: where to look, how to vet, and how to make the offer
- MVP for non-technical founders: all four paths to a built product
- Freelancer vs agency for MVP: the paid alternatives to giving up equity
- MVP development team: who you actually need to build an MVP
- How investors evaluate an MVP: why a clean cap table and real technical capability matter for raising
Frequently asked questions
How much equity should a technical co-founder get?
A technical co-founder who joins early, before meaningful funding, and takes real risk typically gets between 20% and 50%, and often close to an equal split when they build the entire product with little or no salary. The share drops as you (the non-technical founder) have already removed risk (a working product, paying customers, raised capital, a prior exit) and as the technical person takes a salary. Below roughly 10% for someone building and running all the technology, you're offering a lead-developer package, not a co-founder one.
Is a 50/50 split with a technical co-founder a good idea?
An equal split is the honest default for two people joining at the same early stage, taking similar risk, and contributing similarly, and it keeps both sides fully motivated. It becomes less appropriate when one founder has already de-risked the business substantially (built the product, found customers, raised money) or is putting in far more time or capital. The key is that the split reflects real relative risk and contribution, and that it vests over time regardless of the percentage.
Should a technical co-founder get salary and equity, or just equity?
It's a trade-off. A co-founder taking no salary is entitled to more equity, because their entire compensation is a bet on the future. If you can pay a real salary, it's fair for their equity to be somewhat lower, since you've removed their personal financial risk. Early on, cash is usually between zero and a lean salary, so equity carries most of the compensation. What's not fair is offering neither meaningful salary nor meaningful equity.
How much equity for a technical co-founder when there's no funding?
With no funding and no salary, a technical co-founder building the product from scratch is taking maximum risk, so their fair share is high, often in the 30% to 50% range depending on traction and what the other founder brings. If some risk has already been removed (a working prototype, early users) the number comes down accordingly. The absence of funding generally pushes the equity up, because the technical person is effectively investing unpaid time.
What if the technical person joins after the product is already built?
Then they're joining something more de-risked, so their co-founder equity is lower, commonly in the 5% to 20% range, especially if they also take a salary. It also raises a real question: are they a co-founder or a senior hire? If they'll own and drive all technology as a genuine partner, co-founder equity (with vesting) makes sense. If they're maintaining and extending an existing product for pay, a lead-developer or founding-engineer package may fit better than a co-founder split.
Does the equity need a vesting schedule?
Yes, always. The standard is four years with a one-year cliff: nothing vests in the first year, then equity vests gradually. Vesting protects you if the co-founder leaves early (they don't keep a large permanent stake) and protects them by making the commitment mutual and real. Investors expect it. Granting un-vested equity on a handshake is one of the most damaging early mistakes founders make.
Sources & references
This guide synthesizes widely used startup equity frameworks and common practitioner guidance. Equity splits vary widely, so treat these as principles to reason with, not fixed rules, and have a startup lawyer paper the actual agreement.
- Nathan Hurst, How Much Equity a Technical Cofounder Should Get: the subtractive "start near equal, reduce for de-risking" model
- Y Combinator, Startup Library: co-founder equity and splitting equity fairly
- Y Combinator Co-Founder Matching: finding a co-founder in the first place
This article is general educational information, not legal, tax, or financial advice. Consult a qualified startup attorney before finalizing any equity split or vesting agreement.
