If you are a non-technical founder about to bring on a developer as a technical co-founder, you are probably Googling equity percentages and hoping to find a clean answer. There is not one. But what I can give you is the framework that actually protects both of you, based on watching founders navigate this exact situation across 50+ startups.

The equity split is the easy part. The agreement is where most founders get this completely wrong.

The Three Equity Mistakes Most Non-Technical Founders Make

After years of being embedded in early-stage startups as a fractional technical co-founder, I see the same mistakes over and over. None of them are about choosing the wrong percentage. They are about skipping the hard conversations.

Mistake 1: Treating equity like a salary.

I talk to founders who offer 50% equity because they cannot afford to pay their technical co-founder. The thinking is: "We are equal partners, so equal split." The problem is that equity is supposed to reflect contribution, risk, and commitment over time, not just compensate for a missing paycheck. If your technical co-founder would rather have a salary, that is a signal worth paying attention to.

Mistake 2: No vesting schedule, just a handshake.

This one ends startups. A technical co-founder who has fully vested equity on day one can walk away six months later with 40% of your company. No vesting schedule means no protection for either party. I have seen this destroy founder relationships and make the company unfundable because the cap table is a mess.

Mistake 3: Skipping the IP conversation.

Who owns the code your technical co-founder writes? If it is not explicitly assigned to the company in a signed agreement, the answer might be "they do." This matters enormously if you ever raise funding, sell the company, or part ways with your co-founder. Investors will ask. The answer needs to be airtight.

Standard Co-Founder Equity Splits (and Why They Usually Feel Wrong)

There is no universally correct equity split for a technical co-founder who builds the entire product. The range I see most often is 20% to 50%, and the right number depends on factors that percentages alone cannot capture.

Here is how to think about it:

50/50: Feels fair, but usually is not. Equal splits work when both founders are contributing equally in terms of time, capital risk, and commitment from day one. When one person has the idea, the market relationships, and the customers, and the other is writing the code, the contributions are different even if both are essential. Equal splits also create deadlock risk when you genuinely disagree on direction.

30/70 or 40/60 (technical co-founder minority): Common when the non-technical founder has already built significant customer traction, secured funding, or has domain expertise that is doing real work in the business. The technical co-founder is critical but joining something that already has momentum.

50/50 with differentiated vesting: My preferred structure in many cases. Equal equity, but vesting tied to specific milestones for each founder. The technical co-founder vests as they hit product milestones; the business co-founder vests as they hit revenue or fundraising milestones. This keeps you aligned without pretending your contributions are identical.

The equity percentage matters less than most founders think. What matters more is the agreement around that equity.

Vesting Schedules: The Non-Negotiables

Every co-founder agreement needs a vesting schedule. This is not optional, and it is not something to negotiate away to make the conversation easier. Here is what a standard one looks like and what you absolutely cannot skip.

4-year vesting with a 1-year cliff. This is the industry standard and the one most investors expect to see. The cliff means your co-founder earns zero equity in year one. If they leave in month 11, they get nothing. After the cliff, equity vests monthly (1/48th per month) for the remaining three years. This protects you from a co-founder who shows up for six months and walks away with a meaningful chunk of the company.

Reverse vesting. Most founders think vesting only applies to new employees or co-founders joining later. Reverse vesting means that even if your co-founder "owns" their equity from day one on paper, it is subject to being bought back by the company if they leave before vesting. This is standard in serious startups and something you should insist on for both parties.

Acceleration clauses. What happens if the company is acquired before your co-founder finishes vesting? Single-trigger acceleration means they vest fully on acquisition. Double-trigger acceleration means they vest if the company is acquired AND they are let go within a certain period after. Double-trigger is more standard for co-founders and protects both the company's valuation and the co-founder's interest.

Buyout provisions. What does it cost to buy out a co-founder who leaves? You need a formula for this that is agreed upon in advance, not negotiated in a moment of conflict. Common structures include fair market value at the time of departure or a formula based on time served against the full vesting schedule.

None of these conversations are comfortable. Have them anyway. The discomfort of a direct conversation now is a fraction of the cost of a legal dispute two years in.

What the Agreement Must Cover

The equity percentage is a number. The agreement is what makes it real. Here is what needs to be in writing before either of you touches a line of code.

IP Assignment

Everything your technical co-founder builds for the company belongs to the company. This needs to be explicit, signed, and comprehensive. It covers code written before the formal co-founder relationship starts (if it was built for your startup idea), code written during the relationship, and any derivatives. If your technical co-founder had a side project that is getting absorbed into your product, that needs its own IP clause.

Roles and Responsibilities

Who is responsible for what decisions? The technical co-founder owns the stack decisions, the architecture, the engineering hiring when you get there. The business co-founder owns the go-to-market strategy, the fundraising relationships, the sales process. These are not rigid walls, but they need to be documented so there is a default when you disagree.

Decision Rights and Veto Powers

Some decisions should require both co-founders to agree. Equity dilution, major pivots, adding another co-founder, taking on debt, selling the company. Other decisions should be made by one person with the other informed. Write down which is which. The worst co-founder conflicts I have seen happen when both people think they have final say over the same decision.

Compensation During Pre-Revenue

Are you both working for free? Drawing minimal salaries? Getting reimbursed for expenses? Put the current arrangement in writing, and put a process in place for revisiting it when revenue starts coming in.

Exit Provisions

What happens if one co-founder wants to sell their shares? Right of first refusal means the company or the other co-founder gets the first chance to buy those shares before they go to an outside party. Drag-along rights mean if the majority wants to sell the company, the minority co-founder can be required to sell too. These are not optional clauses; they are the standard floor for any co-founder agreement.

Confidentiality and Non-Compete

Standard, but do not skip it. Especially for a technical co-founder who has access to your architecture, your code, and your customer data.

What Each Party Must Bring to the Agreement

Before you sit down to negotiate, get clear on what each person is actually contributing.

What the non-technical founder typically brings:

Domain expertise and customer relationships
Initial capital or access to capital
The business vision and go-to-market plan
Sales and fundraising relationships

What the technical co-founder typically brings:

Architecture decisions and technical strategy
Hands-on development through the early stage
Ability to hire and evaluate future engineers
Technical credibility with investors

Neither side is more important than the other. But the agreement needs to reflect the real contributions of each party, not just the roles you expect to play.

The Cost of Getting This Wrong

I want to be clear: I am not a lawyer, and this is not legal advice. Get an actual startup attorney to draft or review your co-founder agreement. The cost is usually a few thousand dollars and worth every cent compared to the cost of fixing a broken agreement later.

Here is the real math:

Cost to do it right: $2,000-5,000 with a startup attorney
Cost to fix it later: $50,000-200,000+ in legal fees to untangle

The founders I see fight over cap tables at Series A are almost always the ones who shook hands at the beginning.

The Equity Conversation Framework

Most non-technical founders avoid this conversation because they do not know how to start it. Here is a direct way to open it that works in my experience.

"Before we go any further, I want to make sure we are aligned on how equity works between us, because I have seen these conversations get hard when they are left too long. I want to get all of this in writing before we start building.

Here is what I am thinking: [X]% for you, [Y]% for me, both on a 4-year vest with a 1-year cliff. That protects both of us. We should also talk about who owns what decisions, what happens if one of us wants to leave, and make sure everything you build is formally assigned to the company.

I want to get a startup attorney involved to draft the actual agreement. I would rather spend a few thousand dollars now than have this get complicated later. Can we set up a call this week to walk through the terms together before I hire anyone?"

This framing does a few things. It positions the agreement as protection for both parties, not as distrust. It signals that you have thought about this seriously. And it gives your technical co-founder a clear picture of what you are proposing before they have to respond in the moment.

The founders who skip this conversation do not just risk legal problems. They risk the entire relationship. A technical co-founder who feels like they were not dealt with fairly is not a co-founder you want for the next five years.

Decision Framework: Determining the Right Split

Use this to arrive at a starting point before you negotiate.

Step 1: Assess your stage

Idea only: start at 40-50%
MVP built: start at 25-35%
Revenue ($1-10K MRR): start at 15-25%
Revenue ($10K+ MRR): reconsider whether you need a co-founder or a hired CTO

Step 2: Adjust for contribution

Just coding skills: subtract 10%
Technical leadership plus architecture: baseline
Product sense plus strategy: add 5%
Investing their own capital ($10K+): add 5-10%

Step 3: Adjust for risk and commitment

Full-time from day one: baseline
Part-time until validation: subtract 15% or pay hourly instead
Quitting high-paying job: add 5%

Step 4: Add required terms

4-year vesting minimum
1-year cliff
Full-time commitment clause
IP assignment
Documented in a legal agreement

If you are navigating this and want a second opinion on the technical side, including how to structure the co-founder relationship so your technical decisions are sound from the start, I work with non-technical founders as a fractional technical co-founder.

Start with a Discovery Sprint at uxcontinuum.com to figure out what you actually need before you commit to anything.

Technical Co-Founder Equity Agreement: What You Actually Need