Here is the question I get almost every week from non-technical founders: how much equity to give a technical cofounder versus just paying someone to build the thing. It sounds like a numbers question. It is not. It is a question about what you actually need, and most founders answer it before they have figured that out. So they give away 40% of their company to solve a problem that a contract and a budget would have solved better.
Let me walk you through how I think about this, because I have been the technical person on both sides of this deal, and I have watched founders get it very wrong.
The real question behind 'how much equity to give a technical cofounder'
Before you decide how much equity to give a technical cofounder, ask whether you need a cofounder at all. Those are two different decisions and people smash them together.
A cofounder is someone who shares the risk with you for years. They take little or no salary, they own a big chunk of the company, and they are on the hook whether the thing works or dies. You want that person if the technology is the business. If your product is a hard engineering problem, if the roadmap is technical for the next five years, if you genuinely cannot make product decisions without someone deep in the code, then yes, you want a real technical cofounder.
But a lot of founders do not need that. They need version one built. They need a product that works, that they can sell, that lets them find out if anyone wants this. That is a job, not a marriage. And you do not give away a quarter of your company for a job you could pay for. Get honest about which situation you are in first. The rest of this post assumes you have.
Cofounder vs contractor vs fractional CTO: what each actually costs you
Here is the real cofounder vs hiring a developer trade-off, laid out in what it costs you, not just in dollars but in control.
The contractor or solo developer
You pay cash. They build what you scope. When the work is done, the relationship can end and you keep 100% of your company. A good MVP from a solo developer runs somewhere in the range you can estimate with a SaaS MVP cost calculator, and it is a known, bounded number. The risk is that a contractor builds what you asked for, not what you needed, and they walk when the invoice is paid. That risk is manageable if you have a spec that survives a developer and you know how to watch the build without being technical.
The fractional CTO
This is the option most founders do not know exists, and it is often the right one. A fractional CTO gives you senior technical judgment: architecture, hiring, what to build and what not to build, without the full-time salary or the big equity grant. You pay for the brain, not the marriage. For a lot of non-technical founders this covers the exact gap a cofounder would fill in the early days, and it keeps your cap table clean. I have written more on why every early-stage startup needs the CTO mindset even when it does not need a full-time CTO.
The technical cofounder
Highest cost in equity, lowest cost in cash, highest commitment. Right when the technology is the moat and you need someone in the trenches for the long haul. Wrong when you just need a product shipped. The mistake is treating a build problem as a cofounder problem because you are scared to spend money or scared to manage a developer. Neither fear is worth 30% of your company.
How equity splits really get decided
If you do decide you need a technical cofounder, here is roughly how a technical cofounder equity split shakes out in practice. There is no magic formula, but there are honest ranges.
- 50/50. Two people, both quitting their jobs, both essential, both there from day zero with no product and no traction. Equal risk, equal reward. It feels fair, and sometimes it is, but it also means no tiebreaker when you disagree, which you will.
- 60/40 or 65/35 in the founder's favor. Common when you had the idea, you have been working on it for a while, you bring the market knowledge and the customers, and the technical person joins to build. This is the most realistic range for a non-technical founder who owns the business side.
- 70/30 to 90/10. When the technical person is joining a business that already has revenue, or customers, or funding. The more you have already de-risked, the less equity the build is worth.
The single biggest factor is timing. Someone who joins before there is anything gets more than someone who joins after you have proven people will pay. If you have already validated the idea, and you should have before you build, your equity gets more valuable and theirs should reflect that. This is also why doing the work to know whether the idea is worth it without code pays off twice: once in avoiding a bad build, and once in a better cap table.
Vesting, cliffs, and why they protect you both
Whatever number you land on, never grant equity outright. Vest it. This is the single most important protection in this whole conversation, and I have seen founders skip it and regret it for years.
Vesting means the equity is earned over time, usually four years. A one-year cliff means if the person leaves or gets pushed out before twelve months, they get nothing. After the cliff, they vest monthly. So a cofounder with a 30% grant, four-year vest, one-year cliff, who quits at eighteen months, walks away with about 11%, not 30%.
Why this matters to you specifically: imagine you give a technical cofounder 30% with no vesting, they build the MVP, and four months in they lose interest, take another job, or you two fall out. Now they own 30% of your company forever, contributing nothing, and every future investor sees a dead founder holding a third of the cap table. That deal is close to un-fundable. Vesting is what stops that story.
It protects them too. If you flake, they keep what they earned. Good vesting makes the deal honest for both sides, which is exactly what you want in a relationship meant to last years. Put it in writing before anyone writes a line of code.
The mistake that blows up cap tables: paying equity for the build phase alone
Here is the trap I see most, and it is the whole reason this post exists. Founders give a big equity slice to get the product built, then discover the person they gave it to was only ever going to build the first version.
The build is a moment. The company is a decade. If someone's contribution is "they wrote the MVP," that is a service you could have bought for cash. Equity is meant to pay for the ongoing, uncertain, years-long risk of being a cofounder, not for a bounded piece of work with a clear deliverable.
I have done a lot of codebase rescue work, and a painful number of those projects come with a cap table wound attached: a former "technical cofounder" who built a shaky first version, vanished, and still owns 25%. The code needed rewriting anyway, so the founder paid twice, once in equity and once in cash to fix it. If you are unsure whether a person is a builder or a partner, watching how they handle the handoff tells you a lot. This is also covered in when to fire your developer and keep your codebase.
A decision framework for your specific situation
Run yourself through these, honestly.
- Is the technology the business, or the vehicle? If your edge is a hard technical thing, lean cofounder. If tech is just how you deliver a business you already understand, lean paid build plus fractional support.
- Have you validated demand? If yes, your equity is more valuable and you need less of a cofounder. If no, validate first. Do not buy a cofounder to avoid finding out if anyone wants this.
- Can you afford to pay for the build? If cash exists, an MVP development engagement plus a fractional CTO for judgment often beats giving away a third of the company. Founders reach for equity because it feels free. It is the most expensive thing you own.
- Do you actually want to be married to this person for a decade? Because that is what a cofounder is. If the honest answer is "I just need the app built," you have your answer.
For most non-technical founders I talk to, the right move is not a cofounder at all. It is a clean build with senior technical judgment attached, keeping your equity intact until you truly need to trade it. If you want to talk through which path fits your specific situation, get a fractional CTO to weigh in before you sign anything you cannot take back.
