I've been building products for over 20 years. For the last 16, I've worked independently with early-stage founders who are figuring out how to bring on technical talent without destroying the company before it gets started. The equity conversation is one of the most consistently mishandled parts of this process.
Technical cofounders get shortchanged. Or they overclaim and poison the well with investors. Or, most often, two smart people shake hands on a vague arrangement and then spend two years resenting each other before one of them leaves with nothing, or worse, with enough of the cap table to block a term sheet.
If you're asking "what agreement does a technical cofounder need to protect equity" -- that question alone tells me you've already sensed something isn't right about how the deal was structured. Let's go through what actually needs to be in writing.
Why Handshake Deals Destroy Technical Cofounders
The pattern I see most often goes like this: a non-technical founder has an idea. They find someone technical, usually through a mutual connection. The energy is good. Everyone's excited. They agree on a split over coffee, maybe 50/50 or 60/40, and they get to work.
Six months later, one of two things happens. Either the relationship sours over direction or workload, and one founder wants the other out but discovers there's no mechanism to do it cleanly. Or the company gets traction and investors ask to see the cap table, and what they find is an undocumented arrangement that creates real legal exposure.
I've been brought in during both kinds of situations. Neither is fun. The technical cofounder usually loses in the first scenario because they didn't get their equity documented before they started building. The business usually suffers in the second because cleaning up a poorly structured founding agreement is expensive and delays everything.
The fix is simple but it requires doing the boring work before you start building: a properly structured co-founder agreement.
The 5 Clauses Every Technical Cofounder Agreement Must Have
1. Equity split with a clear rationale
Write down what each party owns and why. The percentage matters less than having it documented and signed. If you agreed on 40% for the technical cofounder and 60% for the business founder, put that in writing along with what each party is contributing to justify those numbers.
2. Vesting schedule
I'll cover this in more detail below, but this is non-negotiable. If there's no vesting, anyone can walk away with their full share on day two.
3. IP assignment
Everything built during the partnership must be assigned to the company. And if the technical cofounder built anything relevant before the company was formally incorporated, that pre-existing work needs to be addressed explicitly. More on that below.
4. Decision-making authority
Who has the final call on technical decisions? Product roadmap? Hiring? You don't need to script every scenario, but you need to be clear about who owns what domain and what happens when founders disagree on something major.
5. Departure terms
What happens if someone leaves? Voluntarily or otherwise. Does unvested equity disappear? Is there a buyout mechanism? Can a departing founder compete directly? These questions feel hypothetical until they're not.
If your agreement doesn't have all five of these, it's not really an agreement. It's a conversation you wrote down.
Vesting Schedule: 4 Years With a 1-Year Cliff, Explained Plainly
If you've spent any time around venture-backed startups, you've heard "4-year vest, 1-year cliff." Here's what that actually means in plain terms.
The full grant vests over four years. That means you earn your equity progressively over 48 months. You don't own all of it on day one. If someone were to leave after two years, they'd walk away with half.
The cliff is the one-year mark. Before the cliff, if someone leaves, they get nothing. After the cliff, they've earned the first 25% of their grant all at once, and then the remaining 75% vests monthly (or quarterly) over the next three years.
Why does the cliff exist? Because the first year is when you find out if the partnership actually works. A lot of co-founder relationships don't survive it. The cliff protects the company from a scenario where someone works for three months, decides it isn't for them, and walks away with a meaningful piece of the cap table for almost no contribution.
This structure comes up in almost every technical partnership I've been part of. Investors expect it. If you don't have it, they'll ask why.
One thing that often gets missed: the vesting clock should start from when the technical cofounder actually started contributing, not from when you got around to signing the paperwork. If someone has been building for three months before you formalized the arrangement, that time counts. Get the date right.
IP Assignment: What It Means When You Built Before Founding
This is the clause that surprises technical cofounders the most, and it's the one most likely to create problems later if handled carelessly.
When you incorporate a company, all intellectual property created in service of the company's mission needs to be owned by the company. That means the code, the architecture, the design specs, everything. Most founder agreements include a straightforward IP assignment clause that says: anything you build for this company, the company owns.
The complication is what happens when the technical cofounder built something before the company formally existed.
This comes up in a few different ways. Maybe you built a prototype on your own time before you even had a co-founder. Maybe the technical cofounder was doing contract work that seeded the product. Maybe someone wrote early code as a side project before anyone decided to turn it into a real company.
In all of these cases, you need to decide explicitly whether that pre-existing work is being assigned to the company or licensed to it. If it's assigned, the company owns it outright. If it's licensed, the original creator still holds ownership but grants the company rights to use it. The difference matters enormously to future investors and acquirers.
A clean IP assignment says, roughly: "Any work created before this agreement is hereby assigned to the company as consideration for the equity grant. Any work created after this agreement is automatically assigned to the company."
If the technical cofounder is bringing in significant pre-built work, that work should probably be factored into the equity conversation itself. This is a negotiation, and the contribution of prior work has real value.
If you're working through a co-founder equity conversation right now and want to gut-check your approach before you put anything in writing, I run a small group Vibe Rescue session. Details at uxcontinuum.com/vibe-rescue.
Sample Negotiation Script for the Equity Conversation
The equity conversation is uncomfortable. Here's a script I'd suggest for the technical cofounder side of this. This isn't legalese. It's just how I'd suggest framing it with a co-founder you're trying to partner with, not fight.
"Before we go further, I want to make sure we're aligned on the structure of our arrangement. I'm committed to this and I want it to work long-term. That means we need a few things in writing so neither of us ends up in an awkward position later.
On equity: I'd like us to agree on [X]% for me, [Y]% for you, with a standard 4-year vesting schedule and a 1-year cliff for both of us. The cliff protects both sides. If either of us isn't the right fit, we haven't locked the other person into something unworkable.
On IP: everything I build from this point forward should be owned by the company. I'm fine with that. But I want to be explicit about [any prior work]. I built [describe the work] before we formed the company. I'd like that addressed in the agreement, either as an assignment or a defined license, so there's no ambiguity down the road.
On decisions: I want to be the one making final technical calls. That's not about control, it's about accountability. I can own outcomes better if I own the decisions.
None of this is adversarial. I just want us to be the kind of partnership that investors look at and feel good about."
That conversation is uncomfortable for about 10 minutes. The alternative is a lawsuit or a dissolved partnership two years from now, which is uncomfortable for much longer.
If a potential co-founder reacts badly to you asking for documented equity protections, that tells you something important about how they'll behave when harder decisions come up.
One More Thing
Get a lawyer to review whatever you draft. I can help you think through what to ask for and how to have the conversation. I can't be your legal counsel and neither can the internet. But most early-stage founders are surprised at how affordable a one-time co-founder agreement review is, especially compared to the cost of fixing it later.
If you're navigating this as you bring on a technical partner, or if you're the technical co-founder trying to figure out what to ask for, I'm usually the person founders come to for this conversation. Book a free strategy call and we can work through your situation directly. And if you're also weighing whether a fractional CTO might be a better fit than a full equity co-founder, the fractional CTO cost breakdown is worth reading first.
Dealing with something similar? The fastest way forward is usually a direct look at your setup. Book a call or check out Vibe Rescue if you're in "it works but I'm not confident" territory.