StudioTechnical Cofounder Equity: How Much Is Too Much?
Someone agrees to build your product for equity. You are relieved. You are also about to hand over a piece of your company that you will never fully get back, and most founders have no framework for deciding how big that piece should be.
The honest answer is that there is no fixed number. But there are ranges, and there are variables that push you toward one end of those ranges or the other. This guide walks through both, plus the vesting terms that matter more than the percentage itself, and the alternative most founders never seriously consider until they have already given away too much.
What is a fair equity split for a technical cofounder?
A technical cofounder joining at the very start, writing the first version of the product and carrying early risk equally with the non technical founder, typically ends up between 40 and 50 percent. Someone joining after the idea is validated but before a product exists often lands between 20 and 35 percent. A technical hire who joins after the product is already built and traction exists usually gets 5 to 15 percent, structured as an option grant rather than founder equity.
Those ranges exist because equity is a proxy for risk and timing, not a reward for skill. The earlier someone joins and the less certain the outcome, the bigger their share, because they are betting their time on nothing but your word.
The variables that actually move the number
Two founders with the same idea can land on very different splits, and it is rarely arbitrary. Here is what pushes the number up or down.
Who had the idea, and how developed is it. A founder who spent six months validating a concept, talking to fifty potential customers, and mapping the market brings more to the table than an idea sketched on a napkin last week. That work is worth equity too, and it is usually the first thing that pulls the split away from a flat 50/50.
Who is funding the company. If the non technical founder has already put personal money into the business, whether it is incorporation costs, early tools, or a seed check from an angel, that capital risk offsets some of the equity gap. Cash in early usually buys you a few extra points.
Full time versus part time commitment. A cofounder writing code nights and weekends while holding a day job is not carrying the same risk as one who quit their job to work on this full time. Part time involvement is one of the most common reasons a 50/50 split falls apart later, because the equity no longer matches the actual hours.
What exists already. Joining pre idea, pre validation, pre everything is the highest risk moment and commands the highest equity. Joining after there is a working prototype, some users, or revenue is a materially different bet, and the number should reflect that.
Domain expertise and network. A technical cofounder who also brings deep industry knowledge, an existing customer list, or investor relationships is contributing more than code. That gets priced in too, usually as a few extra points on top of the base technical contribution.
The vesting schedule matters more than the percentage
Founders spend weeks debating whether the number should be 40 or 45 percent and then skip the part that actually protects the company: vesting.
A standard structure is four year vesting with a one year cliff. Nobody owns any equity until they have been in the company for a full year. After that, equity vests monthly or quarterly over the remaining three years. If a cofounder leaves after two months, they walk away with nothing. If they leave after eighteen months, they keep what vested and the company reclaims the rest.
Without vesting, a cofounder who contributes six weeks of work and then disappears still owns their full agreed percentage, forever. This happens more often than founders expect, and it is one of the most common reasons early stage cap tables end up with dead equity, meaning shares held by someone no longer doing any work, sitting there discouraging every future investor who reviews the structure.
If a potential technical cofounder resists vesting on their own shares, treat that as information about how the relationship will go, not as a negotiating quirk to work around.
When a technical cofounder is not actually the right move
Here is the part most equity split guides skip entirely: sometimes the right number is zero, because a cofounder is not what the situation calls for.
A cofounder makes sense when you want a long term technical partner who shares the company's upside and downside for years, through pivots, hard quarters, and whatever comes after the first product ships. That is a real and valuable role.
It makes less sense when what you actually need is a working product to test with users, show to investors, or start selling. Those are different problems. A technical cofounder search commonly takes three months to a year and does not always end in someone joining at all, as we cover in our guide on how to find a technical cofounder. If your timeline cannot absorb that, trading equity for speed you are not guaranteed to get is a bad trade twice over, once in time lost searching and once in equity given up.
The alternative is paying cash for the first build instead of equity. A fixed price product studio builds the first version, you keep 100 percent of the company, and if a technical cofounder makes sense later, you bring one on once the product exists and the person joining can see exactly what they would be signing up for. For a full breakdown of who owns what when you go this route, see our guide on who owns the code when you hire a studio instead of taking on a cofounder.
Cofounder equity vs paying for a build: the tradeoff
| Technical cofounder | Paid build (studio or freelancer) | |
|---|---|---|
| What it costs | 5 to 50 percent equity, indefinitely | A fixed price, paid once |
| Time to a working product | 3 months to a year, if the search closes | Weeks, not months |
| What happens if it does not work out | Vested equity stays with them, possible cap table dispute | The engagement ends, you owe nothing further |
| What you keep | Shared ownership and shared decisions | 100 percent of the company and the code |
For a wider comparison of who should actually build your product, including agencies and freelancers alongside a studio, see agency vs freelancer vs studio.
FAQ
Should equity be split evenly if there are two technical cofounders?
Not automatically. Even between two technical people, an even split only makes sense if both are joining at the same time, committing the same hours, and carrying the same risk. If one is full time and one is part time, or one has been building the idea for months before the other joined, the split should reflect that, not default to 50/50 out of politeness.
Does a technical cofounder always need equity, or can they be paid a salary instead?
Some early technical hires prefer a real salary plus a smaller equity grant, especially if they have financial obligations that make working for equity alone risky. This is common enough that it has a name, a working cofounder, and it usually comes with a materially smaller equity number, often in the single digits, because cash reduces their risk.
What happens to equity if a technical cofounder leaves early?
With proper vesting in place, they keep whatever portion vested up to their departure date and forfeit the rest, which returns to the company's option pool. Without vesting, they typically keep their full agreed stake even if they contributed for a matter of weeks, which is the exact scenario vesting exists to prevent.
Talk it through
If you are trying to figure out whether a cofounder search and an equity split even make sense for where you are right now, or whether you would be better off paying for the first build and keeping the decision for later, book a free 30 minute call. We will give you a straight answer, including if that answer points you back toward the cofounder search. Grab a time here, or start at unilostudio.com.