The Short Answer
A technical co-founder is a partner, not a resource. They take a large share of the company, they own technical direction, and they should argue with you. If what you want is someone to build what you specify, you do not want a co-founder and giving one away will cost you dearly.
Three things decide whether this goes well: getting the equity honest, vesting the equity, and working together before either of those is agreed.
The risk you are guarding against is specific. A co-founder who leaves early and keeps a quarter of your company anyway, because you never put a vesting agreement in place. The precondition matters: with standard four-year vesting and a one-year cliff, someone who walks at month four leaves with nothing, which is exactly what the cliff is for.
The reason this is worth an entire section is that a great many early teams never paper it. Two people agree a split over coffee, start building, and only discover there is nothing in writing when one of them wants out. At that point the equity is simply theirs. Investors do check founder vesting during diligence, and an unvested founding team is a problem you want to have solved long before anyone asks.
How Much Equity Is Normal
A genuine technical co-founder, joining at idea stage and working full-time, generally lands between 25% and 50%. Equal splits are increasingly the norm: Carta's data shows two-person founding teams splitting evenly in 45.9% of cases in 2024, up from 31.5% in 2015. Something like 55/45 is common where one founder started meaningfully earlier.
The number that clarifies everything
A founding engineer typically receives around 1% plus a salary. A technical co-founder receives 25 to 50% and usually little or no pay. That is a twenty-five-fold difference in ownership, and the line between them is not skill. It is risk, commitment and who owns the problem.
What about 5%? It is a real and common number, and it usually means someone who is genuinely between the two: a partner joining after the riskiest part is done, a part-time technical lead, or a very senior first hire. None of those are wrong. What matters is that the equity and the expectation match. Five percent will not buy the commitment of someone taking 30% and no salary, so if you need that level of commitment, either pay for it in equity or be direct that the role is something else.
Decide which role you are filling before you talk numbers with anyone. The common way this goes wrong is starting a co-founder conversation, flinching at the equity, and trying to negotiate toward an employee stake while still expecting a partner's hours and risk appetite.
Vesting Is Non-Negotiable
The standard is four years with a one-year cliff. Nothing is earned for the first twelve months. At the one-year mark a quarter vests at once, then the rest accrues monthly. It applies to both of you, including you.
Here is the arithmetic that makes it matter. Without vesting, a co-founder holding 40% who leaves in month four keeps 40% of your company permanently. You will spend the next decade with a stranger holding a large stake, whose signature you need for financings and whose presence on the cap table makes the company harder to fund. Investors treat an unvested founding team as a serious problem, and they are right to.
With vesting, the same departure costs them everything and costs you a difficult quarter. That asymmetry is the entire point. Raise it early and plainly: it protects you both, and the person who has done this before will bring it up before you do.
What You Are Looking For
Not the best engineer you can find. The right partner, which is a different search.
- They have shipped and then maintained something. Building is the easy half. Someone who has kept a real product running for real users understands the cost of their own decisions.
- They ask about customers. A technical co-founder who is only interested in the technology will build something elegant that nobody wants. The good ones want to know who is paying and why.
- They can disagree with you productively. You need someone who will say a plan is wrong and explain why. If they defer to you on everything, you have hired an expensive employee.
- They explain things without condescension. You will be asking questions for years. Watch how they answer the first ten.
- They are comfortable without a spec. Early startups have no roadmap. Someone who needs requirements handed to them will stall constantly.
- They complement rather than duplicate you. Two people with the same strengths cover half the ground and disagree about the same half.
Red Flags
- They refuse vesting. The clearest signal there is. It means they want the upside of leaving early, and anyone experienced knows vesting is standard.
- They want equity agreed before doing any work together. They are asking you to make your largest irreversible decision on the strength of a few conversations.
- They want co-founder equity and a market salary. Equity compensates for risk and low pay. Wanting both usually means they have not accepted the risk.
- They will not do a paid trial project. Serious people take paid work and want to evaluate you too. Refusal often means they know how they perform under scrutiny.
- They talk about the tech stack and never about users. You will end up with a beautifully engineered product and no customers, and the conversation about why will be very hard.
- They go quiet when the work is boring. Watch them during the unglamorous parts. Most of a startup is the unglamorous parts.
- You feel talked down to and tell yourself it is fine. It does not improve after they own 40% of the company. It gets considerably worse.
What to Ask
“How do you feel about four-year vesting with a one-year cliff?”
Good answer: Of course, and it should apply to you as well. They may suggest specifics. They have done this before.
Walk away: Any resistance, or a suggestion that it signals distrust. This is the single most predictive question on the list.
“Tell me about something you built that failed.”
Good answer: A specific story with their own decisions in it and what they learned about their judgment.
Walk away: Blame pointed entirely at others, or no failures at all. Both mean you learn nothing about how they handle being wrong.
“What would you want to change about my plan?”
Good answer: Real disagreement, specifically argued. This is the behaviour you need for the next five years.
Walk away: Enthusiastic agreement. Either they have not thought about it or they will not tell you when you are wrong.
“What does this look like if we are still doing it in five years?”
Good answer: A picture that includes the boring middle and a role they still want then.
Walk away: Only the exit, or visible discomfort with the timeframe. Co-founding is a long commitment.
Test It Before You Sign Anything
Run a four to six week paid project on something real before any equity conversation concludes. Pay a fair rate. You are buying information about the most consequential decision in your company, and it is extraordinarily cheap at the price.
What you are watching for: do they ship, or do they explain why they have not? Do they tell you when you are wrong? What happens the first time something breaks and it is their fault? Do they still respond quickly in week five, when the novelty has worn off? Can you stand talking to them on a bad day?
Then, before a line of the real product is written, put the founder agreement in place: the split, the vesting, what each of you owns, and what happens if one of you leaves. Write it while you still like each other. Every founder who has been through a bad separation says the same thing, which is that they knew in month two and hoped it would resolve itself.
And if the honest conclusion is that you do not need a partner, that is a good outcome rather than a failure. Consider paying for the build or hiring a founding engineer instead. Both keep the company yours.
Before You Give Away a Quarter of Your Company
Most non-technical founders start looking for a technical co-founder for one reason: there is a wall between the idea and a working product, and no obvious way over it alone. That is a capability gap, and a capability gap is a great deal cheaper to close than 25% of a company.
It is worth being concrete about the arithmetic. At a $5 million valuation, 30% is $1.5 million of your ownership. That is the correct price for a genuine partner who takes the risk with you for years. It is a very poor price for getting a first version built, which is what a large number of these searches are really about.
Theanna exists to close that gap without the equity. Build Mode™ is an agent that knows your business and holds context between sessions, working in plain language rather than assuming you already know the vocabulary. Through MCP it connects to Claude Code or Cursor so your build tool works from your actual business context. On the Connector tier at $99 a month you also get two technical office hours a month with Kyle Cupples, Theanna's founding engineer, which is where the questions you cannot answer alone get answered by someone who has shipped.
Theanna itself is the argument. It is built by a non-technical founder using the same AI tools we teach, with a founding engineer rather than a technical co-founder. That is not a claim that the arrangement suits everyone. It is evidence that the default advice, find a technical co-founder before you do anything, is no longer the only route.
Connector also includes the community of 300+ women founders, through a peer feed and founder circles, and this is the decision it helps with most. Some of them have been through a co-founder split and can tell you what month two felt like before month two happens to you. Others are mid-search right now and comparing notes on what people are asking for. Nearly every founder who has been through a bad separation says the same thing, that they knew early and hoped it would resolve itself. Hearing that from someone who lived it lands differently than reading it in a guide.
This is why Theanna is built for non-technical women founders specifically. Whether a split is fair, whether that vesting request is normal, whether you are being managed rather than partnered with: none of it is written down anywhere reliable. It moves informally, through networks women founders have historically been outside of, and the founders who have that access negotiate from a completely different position. Giving you somewhere to check what normal looks like, before you sign the most expensive agreement of your company's life, is most of what we are for.
When you genuinely do need a co-founder: if technology is the hard, ongoing problem in your business, if you need someone who will own that problem for years and argue with you about direction, then go and find that person and use the rest of this page to do it well. Software and office hours are not a substitute for a partner. They are a substitute for giving one away when what you needed was a first version.
Frequently Asked Questions
How much equity should a technical co-founder get?
If they join at the idea stage, work full-time, and take the same risk you do, the honest answer is close to equal. Carta's data shows equal splits among two-person founding teams rising from 31.5% in 2015 to 45.9% in 2024, and splits like 55/45 are common where one founder started earlier. A true technical co-founder generally lands somewhere between 25% and 50%. Numbers in the middle, around 5%, are common and usually describe someone genuinely in between: a partner joining after the riskiest part, a part-time technical lead, or a very senior first hire. That is a legitimate deal. The thing to avoid is using the word co-founder while offering equity that does not match, because 5% will not buy the commitment of someone taking 30% and no salary.
Do I need a technical co-founder to build a startup?
No, and the assumption that you do has cost founders a great deal of equity. You need a technical co-founder when technology is the hard, ongoing problem in the business and you need someone who will own that problem for years at below-market pay. If what you need is a first version built, that is a purchase and you should pay for it. If what you need is someone to build and maintain the product while you run everything else, that is a founding engineer with a salary. Give away a quarter of your company only when the alternative genuinely does not work.
What is vesting and why does it matter for co-founders?
Vesting means equity is earned over time rather than granted all at once. The standard is four years with a one-year cliff: nothing is earned until the first anniversary, then it accrues monthly. It matters because co-founder relationships end, often early. Without vesting, a co-founder who leaves in month four keeps their entire stake permanently, which means a large share of your company belongs to someone who is not working on it and whose signature you will need for years. Vesting is not a sign of distrust. Any experienced co-founder will expect it, and reluctance to accept it is one of the clearest warning signs there is.
Where do I find a technical co-founder?
Rarely on co-founder matching sites, though they exist and occasionally work. Most real partnerships come from working alongside someone first: open-source contributors on tools you use, engineers you meet at hackathons and buildathons, people who answer your questions helpfully in technical communities, and former colleagues. The pattern that works is contribution before proposition. Someone who has already seen you make decisions under pressure is evaluating a known quantity, and so are you. The worst version is pitching an idea to a stranger and asking them to quit their job for a share of it.
Should I ask a potential co-founder to do a trial project?
Yes, and pay them for it. A four to six week paid project on something real tells you more than any number of conversations: whether they ship, whether they explain themselves, whether they disagree with you well, and whether you can stand each other on a bad week. Anyone serious will welcome it, because they are evaluating you at the same time and taking the same risk. Someone who wants an equity agreement signed before doing any work together is asking you to make the largest decision in your company on the basis of a few conversations.