You are the technical partner. You wrote the code, built the architecture, shipped the product, fixed the bugs, and made the demo real. Your “co-founder” handled the business side. The equity conversation was supposed to happen after launch, after revenue, after the raise — and now months have passed with nothing signed.
Maybe you were promised 50/50. Maybe you were told “we’ll paper it later.” Maybe everyone called you a co-founder in pitch decks, investor emails, Slack, and customer calls. But the company records still do not show your ownership.
If you are a technical co-founder with no equity agreement, the urgent question is not just “what did they promise me?” It is: What do I own, what am I owed, and what should I refuse to sign until the equity and IP issues are fixed?
Quick Answer: A Promise Is Not the Same as Equity
A verbal promise of founder equity can matter, but it is not the same as actually being issued ownership. In an LLC, ownership should be reflected in the operating agreement, membership records, company approvals, and tax documents. In a corporation, ownership should be reflected in stock issuance documents, board approvals, a cap table, and related records.
If the company was formed and you were never added to those documents, you may own nothing on paper — even if you built the entire product.
That does not mean you have no leverage. Depending on the facts, a technical founder may have several legal and practical pressure points:
- Copyright ownership in the code if the work was never assigned;
- Contract claims if equity was promised with enough specificity;
- Quantum meruit or unjust-enrichment-style remedies for the reasonable value of services, depending on state law;
- Partnership or joint venture arguments if the parties carried on a business together before or outside a formal entity; and
- Investor diligence leverage, because unresolved IP and founder-equity issues can make a startup harder to finance or sell.
The goal is not to threaten first and sort out the law later. The goal is to understand the legal framework before you sign away the one asset that may give you negotiating power: your rights in the product you built.
The Core Legal Framework for Technical Co-Founders With No Written Agreement
1. Copyright in Code Usually Starts With the Author
Under U.S. copyright law, copyright ownership generally starts with the author of the work. Software code can qualify as a protected “literary work,” and a “computer program” is specifically defined in the Copyright Act. The key practical point: if you wrote original code, you may have started as the copyright owner unless an exception or transfer applies.
The biggest exceptions are work made for hire and assignment.
2. “Work Made for Hire” Is Narrower Than Many Founders Assume
A startup does not automatically own code just because the code was written for the startup. The Copyright Act defines a “work made for hire” as either work prepared by an employee within the scope of employment, or certain specially ordered or commissioned works where the parties expressly agree in a signed writing that the work is a work made for hire. See 17 U.S.C. § 101.
That distinction matters. In Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989), the U.S. Supreme Court held that courts use general common-law agency principles to determine whether a hired creator is an employee or an independent contractor for work-made-for-hire purposes. The Court identified factors such as the skill required, the source of tools, the location of the work, the duration of the relationship, the right to assign additional projects, the method of payment, tax treatment, and employee benefits.
For a technical co-founder, that means labels are not enough. If you were never on payroll, received no benefits, used your own equipment, controlled your own development schedule, and never signed a written IP assignment, the company may have a real chain-of-title problem. We’ve written about this failure mode from the company’s side in Do You Really Own Your Company’s IP? — as the unassigned technical contributor, you are the other half of that story.
3. Copyright Transfers Need a Signed Writing
Even if everyone intended the company to own the code, a transfer of copyright ownership generally is not valid unless there is a written instrument, or a note or memorandum of transfer, signed by the owner or the owner’s authorized agent. See 17 U.S.C. § 204.
That is why a retroactive contractor agreement, invention assignment, or “quick cleanup” document can be so important. If you sign an assignment without receiving the equity, compensation, release, or founder documentation you were promised, you may give away the leverage before the company gives you anything enforceable in return.
4. Partnership-by-Conduct May Matter Before an Entity Exists
If no entity was formed — or if the parties operated together outside the entity — state partnership law may become relevant. Under Arizona’s version of the Revised Uniform Partnership Act, “the association of two or more persons to carry on as co-owners a business for profit forms a partnership, whether or not the persons intend to form a partnership.” A.R.S. § 29-1012.
California applies a similar framework. California courts recognize that a partnership can be formed by conduct and that the existence of a partnership is usually a fact question, while also recognizing that incorporation can change the analysis. See Eng v. Brown, 21 Cal. App. 5th 675 (2018). Texas courts likewise analyze partnership formation through statutory factors and evidence of shared control, profits, and intent. See Stephens v. Three Finger Black Shale P’ship, 580 S.W.3d 687 (Tex. App. 2019).
The point is not that every informal startup relationship becomes a partnership. It does not. The point is that if you and another founder carried on a business together, shared profits, held yourselves out as co-owners, or operated before the entity paperwork caught up, there may be legal rights and liabilities beyond the cap table. We covered how the default regimes work in all three states in No Written Partnership Agreement? What the Default Rules Say in AZ, CA & TX.
Why This Gives Technical Founders Leverage — But Not a Blank Check
If you built the startup’s core technology and never signed an IP assignment, the company may not have clean ownership of its most important asset. That can affect financing due diligence, acquisition diligence, customer enterprise sales, security and vendor audits, founder departures, cap table cleanup, and any future dispute over who owns the product.
Investors and buyers do not like “maybe” when it comes to core IP. They want clean assignments, clean founder equity, clean invention records, and a clean cap table.
If You Are Still on Good Terms, Fix It Before the Next Sprint
If the relationship is still salvageable, do not wait until the next product milestone, investor meeting, or revenue target. The cleanest solution is to paper the founder relationship now. Ask for a direct founder documentation conversation covering:
- Equity percentage. What percentage do you own, and is it common stock, membership interest, options, profits interests, or something else?
- Vesting. Is the equity vested immediately, or subject to a founder vesting schedule? We broke down how the mechanics work in Startup Equity: How Founder Vesting Actually Works.
- Past contributions. How is the code, architecture, product strategy, and unpaid work already contributed being treated?
- IP assignment. What exactly are you assigning, when, and in exchange for what?
- Roles and decision rights. Who controls product, business, hiring, fundraising, spending, and major company decisions?
- Departure terms. What happens if one founder leaves, is removed, stops contributing, or is diluted?
- Deadlock. If the company is 50/50, how are ties resolved? Our 10 tips for protecting yourself in a 50/50 partnership covers the traps.
The Most Important Move: Tie the IP Assignment to the Equity Issuance
A technical co-founder should be very careful about signing a standalone IP assignment before the equity is actually issued or documented. The cleaner structure is usually a same-time exchange: the company issues or documents the founder equity; the founder signs the IP assignment and invention assignment; the entity documents are updated to match; the cap table is updated; any vesting or repurchase terms are signed; and any release, compensation, or contractor cleanup terms are handled in the same package.
That protects both sides. The company gets clean IP. The technical founder gets actual papered ownership rather than another promise.
About to sign an IP assignment or contractor agreement? Pause first. Book a founder equity review before you give away your leverage →
If the Relationship Is Already Going Sideways
If the business co-founder is avoiding the equity conversation, removing you from accounts, asking you to sign retroactive documents, or minimizing your role, shift from “founder cleanup” mode to “evidence and risk control” mode. If a co-founder departure is part of the picture, our post on what happens when a co-founder leaves maps the terrain.
Preserve Evidence
Save copies of relevant materials where you are legally permitted to do so, including: text messages and emails discussing equity; Slack or Discord messages calling you a co-founder; pitch decks listing you as a founder or CTO; investor updates referencing your role; Git commits, pull requests, deployment history, and architecture documents; payment records or unpaid invoices; customer demos and product launch materials; company formation documents; and any contractor, advisor, offer, or IP assignment documents you were asked to sign.
Do Not Sign a “Cleanup” Agreement Without Review
A sudden request to “just sign this contractor agreement,” “confirm the company owns everything,” or “paper what we already agreed” may be routine — or it may eliminate your best leverage. Before signing, understand whether the document:
- Assigns past code or inventions;
- Waives claims to equity or compensation;
- Labels you as a contractor instead of a founder;
- Includes a release;
- Contains confidentiality, non-disparagement, or non-solicit language;
- Gives the company ownership without issuing equity; or
- Creates tax consequences.
Do Not Rely on Threats as Strategy
You may have claims. You may have leverage. But sending threats before understanding the facts can backfire. The better first step is a confidential legal review of the documents, evidence, code and IP history, and entity records.
What Documents Usually Solve the Problem
For most early-stage companies, this problem is fixable with a focused founder documentation package:
| Document | What it should address |
|---|---|
| Founder / equity agreement | Ownership percentage, vesting, roles, decision rights, and founder expectations |
| Operating agreement or stock documents | The actual entity records showing your ownership |
| IP assignment agreement | Past and future code, inventions, repositories, product materials, and related rights |
| Founder vesting agreement | What happens if someone leaves early or stops contributing |
| Board / member approvals | Formal company authorization for the equity issuance and IP cleanup |
| Cap table update | The practical ownership record investors will review |
| Departure / deadlock terms | Buyback rights, deadlock resolution, removal, resignation, and dispute handling |
This is not just “paperwork.” It is the difference between being a founder with enforceable ownership and being a contributor relying on memory, screenshots, and goodwill.
The Bottom Line
If you are a technical co-founder with no equity agreement, you may be more protected than you think — but less protected than you need to be. Your code may create leverage. The promises made to you may support claims. The parties’ conduct may matter. But leverage is not the same as ownership, and claims are not the same as signed equity documents.
The safest move is to paper the founder relationship before the company raises money, signs major customers, or asks you to assign the IP. If the relationship is already deteriorating, preserve evidence and get legal advice before you sign, send, delete, transfer, or threaten anything.
Frequently Asked Questions About Technical Co-Founder Equity and IP
Possibly. If you wrote original code and never assigned it, and if the work does not qualify as work made for hire, you may still own copyright rights in the code. The analysis depends on the facts, including whether you were an employee, what documents you signed, who controlled the work, how you were paid, and whether there was a written assignment.
Sometimes, but not automatically. If you were a W-2 employee writing code within the scope of employment, work-made-for-hire rules may apply. If you were an independent contractor, advisor, unpaid founder, or informal technical partner, the company usually wants a signed IP assignment to remove doubt.
Sometimes, but verbal equity promises are fact-specific, evidence-driven, and harder to prove than written agreements. The stronger evidence includes written messages, drafts, pitch decks, investor materials, cap table references, tax documents, and consistent conduct showing the agreed ownership terms.
Being called a co-founder may help show the parties’ understanding, but it is not a substitute for actual equity issuance. If your name is missing from the operating agreement, stock records, member ledger, board consents, or cap table, you should get legal advice before signing an IP assignment or continuing to contribute uncompensated work.
In some states and some fact patterns, yes. Partnership law can apply when two or more people carry on as co-owners of a business for profit, even if they did not intend to create a formal partnership. That can create rights, duties, and liabilities. But the result depends heavily on the state, the entity history, and the parties’ conduct.
That is a strategic decision to make with counsel. Continuing to work without documentation may increase your unpaid contribution and blur the ownership record. But abruptly cutting off access, deleting work, or disrupting operations can create legal risk. A lawyer can help you decide how to pause, continue, or negotiate safely.
At minimum, understand what equity or compensation you receive in exchange, whether the equity is actually issued, whether it vests, whether the company records will be updated, whether you are releasing any claims, and whether the agreement covers past work, future work, or both.
This article is for general educational purposes only. It is not legal, tax, accounting, or investment advice, and reading it does not create an attorney-client relationship. Founder equity, copyright ownership, IP assignment, partnership, and compensation issues are fact-specific and depend on the documents involved, the parties’ conduct, and applicable federal and state law. Consult a licensed attorney regarding your specific circumstances before signing any agreement or taking action.