A practical guide for non-technical founders on how to split equity with a technical co-founder — what factors should drive the number, what vesting protects you both, and how to have the conversation before it becomes a crisis.
Most co-founder equity conversations don't fail because of the number. They fail because the conversation didn't happen until too late, the agreement was never documented, or the vesting terms were glossed over in the excitement of starting something together.
This guide is about doing it right, before you build anything.
You've found someone technical who believes in what you're building. They're excited. You're excited. The last thing you want to do is have an awkward conversation about percentages and what happens if one of you leaves.
So you don't. You say "we'll figure it out" or agree loosely on a number and move on. You build for six months. One of you feels like they're doing more. The other thinks the original idea deserves more weight. The product is getting real, investors are asking about your cap table, and now you're having the equity conversation under pressure, with emotional stakes, and incomplete records.
This is one of the most common preventable startup failures. It's not a technical problem. It's a paperwork-and-timing problem.
Have the equity conversation before you build anything together. Even a week of joint work without an agreement in place starts creating assumptions.
Non-technical founders often start the equity conversation with a strong sense that the idea deserves significant credit. They had the insight, identified the market, validated the concept. Surely that's worth more than the person who "just" writes the code?
Here's the problem with that framing: in the early stages of a startup, execution is the scarce resource. Ideas are common; the ability to build the thing is not. A non-technical founder without a technical co-founder can't ship a product. An experienced technical person without your idea could find another idea tomorrow.
The idea is worth more in industries where proprietary insight is genuinely difficult to replicate — specialized domain expertise, unique data access, regulatory knowledge. In most software startups, the insight is only defensible if it gets built before someone else does.
This doesn't mean the idea is worth nothing. It means it's one factor among several, not a trump card.
Rather than anchoring to the idea or to an arbitrary number, use these five factors as the basis for a structured conversation.
Factor 1: Full-time commitment Is each co-founder leaving their job to build this full-time? A co-founder who is working on the startup part-time while staying employed elsewhere is contributing less risk and less time. Equity should reflect this. If one founder is all-in and the other is hedging, the split should be unequal — and the part-time founder should have a clear milestone at which they commit fully.
Factor 2: Domain expertise and credibility Who has the knowledge that makes this specific startup credible? If you've spent 10 years in healthcare compliance and you're building a compliance tool, that expertise has real value — it will win you early customers, attract advisors, and shape the product in ways a generalist can't. If your technical co-founder has built similar systems before and knows the landscape deeply, that matters too.
Factor 3: Network and investor access Early-stage fundraising often comes down to who you know. If one founder brings meaningful relationships with angels, VCs, or potential early enterprise customers, that's a material contribution to the startup's survival.
Factor 4: Whose skills are harder to replace at this stage This is the most honest version of the question. Right now, at this stage, with these constraints — whose absence would be harder to recover from? If you're pre-product, losing the technical co-founder likely kills the company faster than losing the non-technical one. After you've raised a round and can hire engineering talent, the dynamic shifts.
Factor 5: Salary sacrifice A technical co-founder with 6 years of experience could be earning ₹30–50 LPA at a product company. If they're joining at a fraction of that, the equity is in part compensating for that sacrifice. The more a co-founder sacrifices in salary, the more equity should compensate for it. This is especially relevant when one co-founder has more financial flexibility than the other.
Y Combinator's consistent advice to founders is to split equity as close to equal as both parties can genuinely accept, paired with a vesting schedule from day one.
The reasoning is pragmatic: unequal splits breed resentment. The person with less equity works just as hard as the person with more, starts to feel undervalued, and either disengages or exits. Meanwhile, investors see large equity imbalances as a team risk — it tells them the founders have either negotiated poorly with each other or that one founder doesn't believe in the other.
Most successful two-founder companies fall in the 50/50 to 40/60 range. Splits beyond 30/70 are rare at well-funded companies and tend to signal a problem.
What "as equal as you can stomach" means practically: if you genuinely can't get to 50/50 because of a meaningful difference in contribution, a 55/45 or 60/40 split is usually acceptable. 70/30 is a red flag. 80/20 almost always becomes a problem.
A common concern with equal splits: "what if they leave?" This is where vesting does the work.
Here's how dilution works through a typical funding path. Starting with two founders at 50% each:
| Stage | Event | Founder A | Founder B | Investors |
|---|---|---|---|---|
| Day 1 | Equal split | 50% | 50% | — |
| Pre-seed | ₹1.5Cr raised, 10% dilution | 45% | 45% | 10% |
| Seed | ₹5Cr raised, 15% dilution | 38.25% | 38.25% | 23.5% |
| Series A | ₹30Cr raised, 20% dilution | 30.6% | 30.6% | 38.8% |
The founders still hold meaningful stakes — and if the company is worth something at Series A, those stakes are worth real money. The percentage is less important than what the percentage represents at exit.
The universal startup standard is 4 years vesting with a 1-year cliff.
What this means in practice:
The cliff protects both parties:
Importantly: the cliff should apply to both co-founders, not just the technical one. A non-technical founder who departs early and takes a large cap table stake creates the same problem.
Most investors will ask whether vesting is in place before any Series A conversation. No vesting schedule is a diligence red flag.
This is where the co-founder agreement earns its money.
The standard mechanism is a buyback provision: if a co-founder leaves before fully vesting, the company (or the remaining founders) have the right to repurchase unvested shares at the original purchase price.
There are two types of departure to address in your agreement:
Good leaver: The co-founder leaves for reasons beyond their control — serious illness, genuine mutual agreement, life circumstances. Good leaver provisions typically allow the departing co-founder to keep some or all vested shares without a forced repurchase.
Bad leaver: The co-founder is terminated for cause, violates the agreement, or resigns without proper notice. Bad leaver provisions typically allow the company to repurchase even vested shares at a below-market price.
The specific terms depend on your jurisdiction and the structure of the company. Get a startup lawyer to draft this. The cost of a proper founder agreement — typically ₹30,000–80,000 from a startup-specialist firm — is the cheapest insurance you will ever buy.
Three documents turn an informal equity agreement into an enforceable one:
Co-founder agreement. Covers equity split, vesting terms, roles and responsibilities, IP assignment (the code your technical co-founder writes belongs to the company, not to them personally), and what happens on exit or departure. This is the most important document.
Shareholders' agreement. More comprehensive than a co-founder agreement; governs the relationship between all shareholders. Typically drafted when the company is incorporated and investment starts coming in.
IP assignment agreement. Makes explicit that anything either co-founder creates related to the company — code, designs, trade secrets — belongs to the company. Without this, a technical co-founder who departs could theoretically claim ownership of the codebase.
Do not start building without at least the co-founder agreement in place. "We'll sort the paperwork later" is the most expensive sentence in a startup.
A technical co-founder who is forgoing market salary deserves more equity — this is how the trade-off works. If market rate for their experience is ₹25 LPA and they're drawing ₹8 LPA, they're contributing ₹17 LPA per year in deferred compensation. That sacrifice should be reflected somewhere, and equity is the right mechanism.
Conversely, if both co-founders are taking meaningful salaries from day one (funded by investment), the equity conversation is simpler — there's less sacrifice to compensate for and less reason for a wide split.
A useful question to ask explicitly: "If neither of us were sacrificing anything in salary, what would a fair equity split look like?" Then factor in the actual salary sacrifice as an adjustment. This separates the equity conversation from the compensation conversation and usually makes both easier to reason about.
Giving too little because "it was my idea." The idea is usually worth less than the execution, and a technical co-founder who walks away because equity felt unfair takes the codebase knowledge with them.
Agreeing to equity without a vesting schedule. The percentage is meaningless without the terms that govern how it's earned.
No cliff. Without a cliff, a co-founder who leaves after 6 months still owns a material portion of the company, possibly enough to complicate future fundraising or create a hostile minority shareholder.
Verbal agreements only. A conversation isn't a contract. If the relationship sours, you're litigating based on what each person remembers, not what was written.
Not revisiting the split at major milestones. If circumstances change significantly — one co-founder pivots to a different role, takes a leave, or reduces commitment — the equity terms may need adjustment. Build a mechanism for this conversation into your agreement rather than discovering later that the original terms no longer reflect reality.
Hunchbite works with non-technical founders who need to move fast on development while they figure out the right long-term team structure. We can help you ship product before the co-founder search is complete.
Call +91 90358 61690 · Book a free call · Contact form
If this guide resonated with your situation, let's talk. We offer a free 30-minute discovery call — no pitch, just honest advice on your specific project.
An honest comparison of fixed-price and hourly billing for software development — when each model makes sense, the hidden risks of both, and how to structure an engagement that protects you.
10 min readChoosing a PartnerShould you hire a freelancer, an agency, or build an in-house team? This guide compares all three options across cost, speed, quality, risk, and long-term value — with honest trade-offs.
12 min read