You have been writing code for months. The product is live, or close to it. Your partner talks about “our company,” “our users” and “our future.” But when you ask what percentage you own, the answer is something like, “Let’s sort that out later.”
If this sounds familiar, you are not alone. It is one of the most common and most expensive mistakes in early-stage startups. The good news is that you still have options, and you usually have more leverage than you think. This guide explains what to do, in what order, and what to avoid.
Note: this is general information, not legal advice. Laws differ by country and state, so talk to a qualified lawyer before signing anything.
Why a Missing Equity Agreement Is Dangerous for the Technical Partner
The builder carries the most risk
The business partner can walk away from a failed idea with a few lost weeks. You walk away with nothing if the code, the repository and the company all sit in someone else’s name. Without paperwork, “partner” is only a word.
Verbal promises are hard to prove
Maybe you were told “50-50” or “you’ll get 30%.” Without a signed document, you must prove that promise with chats, emails and memory. Courts do sometimes recognize oral agreements, but those cases are slow, costly and uncertain. Do not plan your future around winning one.
The company often owns your work by default
In many places, if you work as an employee or a company assigns you tasks, the company may own what you create. If you are an unpaid founder with no assignment document, ownership can be unclear. That uncertainty hurts you in two ways. You may not own the code, and an investor may refuse to fund until the IP question is settled.
First, Understand Your Current Position
What exactly was promised?
Write down everything you remember: percentages, dates, who said it, and where. Then collect proof. Search WhatsApp, email, Slack, Notion and voice notes. Messages like “we’ll split equally” or “you’ll get shares once we incorporate” are valuable.
Is there a company yet?
This changes your approach completely.
- No company formed: You may be in an informal partnership. Nothing has been issued, so you can negotiate the whole structure from scratch.
- Company formed, no shares issued to you: You are in the riskiest spot. The legal owner may be your partner alone.
- Company formed and you are a director or shareholder on paper: You already have rights. They need to be documented properly.
What have you built, and what have you been paid?
Note your hours, the tech stack, and any salary, stipend or expenses you received. Unpaid work is a strong argument for fair ownership.
Step-by-Step: How to Protect Yourself
Step 1: Secure your evidence
Export your chats and emails and save them in a private folder you control. Keep screenshots of commits, invoices and project boards. Do this quietly and early, before any tension begins.
Step 2: Know who controls the code and accounts
Check where the source code lives. If the GitHub organization, cloud server, domain and app store accounts belong only to your partner, your leverage is lower. Aim for shared admin access, not exclusive control for anyone.
One caution: do not delete code, lock people out or hold the product hostage. This can damage your legal position and your reputation. Protection means documenting and negotiating, not sabotage.
Step 3: Start the equity conversation calmly
Raise it as a business need, not an accusation. You might say: “Investors and customers will ask who owns what. Let’s put it in writing this week.” Most reasonable partners will agree because they also need clean paperwork.
Step 4: Agree on the numbers
Decide these points together:
- Ownership split: based on idea, time, skills, money and future responsibility
- Vesting: commonly four years with a one-year cliff, applied to both founders
- Roles: who leads product, technology, sales and finance
- Decision rights: which decisions need both partners’ approval
- Exit terms: what happens if someone leaves, becomes inactive or is removed
Step 5: Put it in a proper written agreement
A founders’ agreement or shareholders’ agreement should cover ownership percentages, vesting, roles, IP, confidentiality, dispute resolution and exit terms. Share issuance should be recorded in the company’s official records, not just promised in a document.
Step 6: Handle IP carefully and in the right order
This is the most important point for a technical partner. Your partner may ask you to sign an IP assignment that transfers all your code to the company. That can be a perfectly normal request, but timing matters.
Do not sign a standalone IP assignment before your equity is documented and issued. Sign them together, or make the assignment conditional on your shares. Otherwise you hand over your strongest bargaining chip for a promise.
Also clarify any code you wrote before the company existed, and any personal tools, libraries or open-source work you plan to reuse in other projects. List these as excluded or licensed, not assigned.
Step 7: Use a lawyer, even a simple one
A lawyer reviewing a founders’ agreement costs far less than a dispute later. If budget is tight, ask for a fixed fee for a one-time review. Ideally you should have your own lawyer, not the one working for your partner.
What to Refuse to Sign (Until It Is Fixed)
Be careful with documents that look like routine “cleanup” paperwork. Pause before signing if a document:
- Transfers all IP but says nothing about your shares
- Names you an employee, contractor or consultant when you believe you are a co-founder
- Includes a very broad non-compete that would block you from working elsewhere
- Allows the company to cancel your equity at any time
- Contains vesting that applies only to you, not to your partner
Ask for changes in writing. A fair partner will not mind.
Alternatives If Your Partner Refuses to Give Equity
Sometimes the honest answer is “I don’t want to share ownership.” You still have choices.
Convert to a paid contract
If you will not get equity, you should be paid fairly. Agree a monthly rate or project fee in writing, with clear deliverables and payment dates.
Keep ownership of your code
Under a contractor arrangement, you can license the software to the company instead of transferring it. The company gets the right to use it, and you keep ownership. This is a strong and underused option.
Ask for profit share or phantom equity
If real shares are not possible, a written revenue share, profit share or phantom equity plan can reward you for growth. These still need a written agreement with clear calculation rules.
Walk away with a clean exit
If trust is gone, negotiate a clean separation. Agree what you are paid for work done, who keeps which assets, and what each side can say publicly.
Common Mistakes Technical Partners Make
Waiting until the product succeeds
Leverage is highest before launch and before funding. Once investors appear, your partner may feel pressure to rush paperwork, or may suddenly resist it.
Trusting friendship over documents
Good friends make good partners, but paperwork protects friendships. It is not a sign of distrust.
Accepting vague words like “sweat equity”
“Sweat equity” means nothing until it is converted into a number, a vesting schedule and a signed record.
Mixing personal and company assets
Avoid building the product on your personal accounts with no plan to transfer or license them. Equally, avoid paying company expenses personally without records.
A Simple Checklist
- Evidence of promises saved and backed up
- Admin access to code, cloud and domains clarified
- Ownership percentage agreed in numbers
- Vesting schedule defined for all founders
- Roles and decision rights written down
- IP assignment signed only together with equity
- Exit terms agreed
- Independent legal review completed
Frequently Asked Questions (FAQs)
Can I legally claim equity without a written agreement?
Possibly, but it is difficult. Depending on where you live, an oral agreement, emails or your conduct may support a claim. However, proving the exact terms is hard and a legal fight is expensive. A signed agreement is always the better path.
Who owns the code if there is no agreement?
It depends on your location and your status. If you were an employee, the employer often owns it. If you were an independent contributor or unpaid founder, you may still own it unless you transferred it. A lawyer can tell you the rule that applies to you.
Should I stop working until we sign an agreement?
Not necessarily, but you should set a deadline. Tell your partner you want the paperwork finished within a short, specific period, such as two to four weeks. Continuing to build indefinitely without terms weakens your position.
What is a fair equity split for a technical partner?
There is no universal number. Many teams split equally when both founders are full-time and equally committed. The split can change based on who had the idea, who funds the project, and who works full-time. Pair any split with vesting so it stays fair over time.
What is vesting and why does it matter?
Vesting means you earn your shares over time instead of receiving them all at once. A common setup is four years with a one-year cliff. It protects the company if someone leaves early, and it protects you too, because it applies to everyone.
Is it a red flag if my partner avoids the equity conversation?
It is a warning sign worth taking seriously. Delay may be innocent, but repeated avoidance, changing numbers or pressure to sign IP documents first are reasons to slow down and get legal advice.
Can I take my code with me if I leave?
That depends on what you signed and who owns the work. If you transferred the IP to the company, you generally cannot. If you only licensed it, you may keep ownership. This is why you should never assign IP casually.
Do I need a lawyer if we are just two friends starting out?
Yes, at least for a review. Friends are the people who most often skip paperwork, and also the ones who end up in painful disputes. A single review can save years of conflict.
Final Thoughts
Being the technical partner gives you real power. You build the product, so you understand it better than anyone. But that power only protects you if it is backed by documents. Start with evidence, talk openly, agree on numbers, sign equity and IP together, and get a lawyer to check the final paperwork. Do this early and you protect both your work and your relationship with your partner.
