Technical Co-Founder Equity Splits: What's Fair in 2026

If you are pre-product and pre-revenue, and a technical co-founder is going to build the entire product while you handle everything else full time, the defensible range is 40 to 50 percent of the founder pool. The more evidence you bring to the table, in revenue, committed funding, a real domain moat, or a full-time head start measured in years rather than weeks, the further the split can tilt toward you, into the 55/45 to 70/30 zone.

That is the whole answer. Everything below is about how you get to a number inside those ranges, and how to structure it so nobody is quietly furious in month fourteen.

I have been the technical co-founder six times, across three continents, and I have turned the offer down far more often than I have taken it. I have also been on the other side, watching a split I was not part of poison a company that the market was actively trying to keep alive. So this is written from the negotiating table rather than from a template. The longer piece on how to find a technical co-founder covers the search itself; this one is only about the equity.

The short answer, by stage

The single biggest input is what exists on the day the conversation happens. Roughly:

• Idea only, nothing built, no revenue, no funding. Near-equal, 40 to 50 percent of the founder pool. You are asking someone to create the entire product from nothing, on the same risk you are taking. There is very little to justify a large gap.
• A prototype exists, built by contractors or by you. 35 to 45 percent. A prototype is evidence, and it reduces the unknowns the technical co-founder is absorbing. It rarely survives contact with production, so discount it accordingly.
• Real revenue or committed funding. 25 to 40 percent. Money already on the table changes the risk profile genuinely, and a rational technical co-founder will price that in.
• Established company hiring a technical leader. This is not a co-founder conversation any more. It is an executive hire, typically low single digits of the company post-funding, and calling it a co-founder role to justify a below-market salary is a tactic engineers recognise immediately.

These are ranges, not a formula. Anyone selling you a calculator that spits out a precise percentage is selling certainty that does not exist.

Why "it was my idea" is not an input

The most common opening position I hear is that the idea is worth the majority of the company. It is not, and pretending otherwise is the fastest way to lose the engineer you were trying to recruit.

Ideas are cheap in the sense that matters here: several other people are having yours right now, and the difference between them and you will be execution. If your idea genuinely is the asset, the question is why you cannot fund its construction. If the answer is that nobody will fund it yet, then the risk being absorbed by the person who builds it is real, and it prices accordingly.

What legitimately shifts the number in your favour is evidence: customers who have paid, a distribution advantage nobody can copy, domain knowledge that took a decade to acquire, funding already committed, or a full-time head start where you have been at this for two years and they are joining on Monday. Those are inputs. "I thought of it" is not.

The four things that actually move the number

When I am the one deciding whether to say yes, I am weighing four things, and they are the same four on both sides of the table.

1. Who is carrying how much risk, in cash terms. Is either of you taking a salary? Whose savings are funding the next twelve months? A founder who has been unpaid for eighteen months has contributed real capital, and it should count. So has a technical co-founder who leaves a senior salary to build for free.

2. Full-time or not. A part-time co-founder is not a co-founder. If one of you is keeping a job while the other goes all in, that gap has to show up in the split or in the vesting, and it is the single most common source of later resentment.

3. What happens if this person leaves in month six. This is a vesting question rather than a percentage question, and I will come back to it, but it belongs in your thinking from the start.

4. Whether the technology is the moat. If the product is a well-understood build, a marketplace, a booking flow, a dashboard over an API, then you need it built well rather than invented, and the equity case for a co-founder is weaker. If the hard part is genuinely hard, novel AI systems, infrastructure, security-critical products, then the person solving it is not a builder you are hiring, they are the reason the company can exist.

Vesting matters more than the split

Here is the thing founders discover late: the structure protects both of you far more than the percentage does.

Four-year vesting with a one-year cliff, for both founders, with no exceptions. Not just the technical co-founder. Both of you, including whoever holds the larger share. This is not a sign of distrust, it is the mechanism that makes trust affordable. It makes "half the company to someone who left in month four" impossible, which is precisely what allows a generous split to be safe to offer in the first place.

Put decision rights in writing. Who decides product, who decides technical architecture, what spending limits exist, and what needs both signatures. Most co-founder disputes I have watched were not about equity, they were about a decision someone thought was theirs.

Agree the exit script before you need it. What happens if one of you wants out, gets an offer they cannot refuse, or simply stops showing up. It is an uncomfortable conversation on day one and a catastrophic one to improvise in year two.

Write it down properly, with a lawyer, before anyone writes code. Handshake splits between friends are the single most expensive form of optimism in startups. The document costs a small fraction of what fixing its absence costs.

A fair split with no vesting is worse than an aggressive split with proper vesting. If you only take one thing from this piece, take that.

Co-founder, first engineer, or advisor

Three very different roles get labelled as co-founder, usually because equity is easier to offer than salary. The market ranges are not close to each other:

• Technical co-founder: the double-digit percentages above, vesting over four years, full-time, sharing the risk and the decisions.
• First engineer: typically 0.5 to 2 percent, with a salary, joining after the founding risk has been partly absorbed.
• Advisor: typically 0.25 to 1 percent, vesting over two years, for a few hours a month of judgment rather than ownership of delivery.

If what you actually need is someone to build the thing, and you call it a co-founder role to avoid paying, you will attract exactly the engineers who cannot tell the difference. That is the opposite of the selection you want.

Three patterns that turn a fair deal into resentment

The silent part-timer. One founder is full-time, the other is keeping a job "for another couple of months" that becomes another year. The equity was agreed on the assumption of parity that never arrived. Fix this with vesting tied to actually starting full-time, and by saying the quiet part out loud early.

The renegotiation after the hard part. The product ships, the company raises, and suddenly the split is revisited because the technical work "is done now". It is never done, and nothing destroys a technical co-founder's commitment faster than discovering their share was contingent on a phase.

The 90/10 that was accepted quietly. An engineer takes a token share because they wanted to work on the problem, tells themselves it is fine, and spends two years watching a company they built be mostly owned by someone else. It does not stay fine. It converts into slow disengagement, and it will cost you far more than the equity would have.

A split that leaves either founder quietly resentful is a liability on the cap table that no amount of traction fixes.

The option most founders never price

Before you give away a third of your company, it is worth doing the arithmetic on the alternative coldly, because most founders never do.

If your product is a well-understood build and your unfair advantage is distribution or domain knowledge, you may not need a co-founder at all. You need the product built well and senior technical judgment available while you build the company. That is a cash cost with a defined end, not a permanent claim on your exit.

That is the trade I offer founders now. I build MVPs priced per screen, so the total is known before anything is built, and I work as a fractional CTO with the pricing published, at a monthly cost that is a rounding error next to a co-founder's equity. The cost and rates guide has the full comparison against a full-time hire.

And sometimes, a few months into an engagement like that, it turns into something more permanent. That is the best possible way to choose a co-founder: after you have already worked together, shipped something, and seen how the other person behaves when it breaks at two in the morning.

Frequently asked questions

What is a fair equity split for a technical co-founder? Pre-product and pre-revenue, with the technical co-founder building everything, 40 to 50 percent of the founder pool is defensible. With a prototype, 35 to 45. With revenue or committed funding, 25 to 40. Below roughly 20 percent for a genuine full-time founding role, expect most experienced engineers to decline.

Should a technical co-founder get 50 percent? Often yes, at the idea stage, and it is less frightening than it sounds once both sides vest over four years with a cliff. The scenario founders fear, handing half the company to someone who leaves, is exactly what vesting prevents.

What if I have already built a prototype? It shifts the number modestly, not dramatically. Be honest with yourself about whether the prototype is an asset or a liability the co-founder will have to rewrite. A contractor-built demo usually does not survive production, and every experienced engineer knows it.

Do co-founders always split equally? No, and equal splits are not automatically correct. They are simply common at the idea stage because the contributions genuinely are comparable. Unequal splits work fine when the reason is a fact both people agree on, and fail when it is a position one person negotiated harder for.

How does vesting work for founders? Standard is four years with a one-year cliff: nothing vests until twelve months, then monthly. It applies to every founder including the majority holder. Add acceleration terms for a change of control if you want, but do not skip the cliff.

What about equity instead of salary for a fractional CTO? That is a different and much smaller conversation, usually a partial swap rather than a founder-sized grant. I do it case by case, from a small equity component up to roughly half and half, depending on stage and how long we expect to work together. It is a way to share risk without restructuring your cap table.

When should I not look for a technical co-founder at all? When the technology serves your advantage rather than being it, when you can fund development modestly, or when the search would take the six to nine months you do not have. I covered the full version of this in how to find a technical co-founder.

If you are in the middle of this decision, tell me what you are building and I will give you the straight read on whether the situation calls for equity, a retainer, or neither yet. I take on technical co-founder partnerships very selectively, and everything on this page is the same bar I apply to myself.