Defending Copyright Title Against Implied Equitable Assignments in Startups
Statutory copyright title remains with the creator under Section 204(a) unless transferred by a signed writing, limiting startup claims to implied licenses.

Writing
Two creators left a conference room in August with forty thousand lines of repository commits and an unfiled certificate of incorporation. One believed the code belonged to the business because it paid the hosting bill and issued three checks marked for development labor. The other held the commit keys, registered the source code with the statutory registry under their own name, and refused to sign an assignment when relations broke down nine months later.
The enterprise asserted equitable ownership of the repository, arguing that shared intent and early payments vested complete beneficial property in the firm, yet legal title never moved.
Statutory copyright law sets a strict barrier against informal property transfers. Under Section 204(a) of the federal statute, a copyright transfer is invalid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the rights holder. The requirement protects creators from losing rights through informal conversations or unwritten agreements.
An equitable claim seeking to bypass this rule treats bare intention as a transfer of property. While the statute allows transfers by operation of law, that exception applies to corporate mergers, bankruptcies, and intestate distributions, not broken expectations between collaborators.
A statutory transfer of copyright ownership remains void absent an executed instrument signed by the rights holder.
Litigants seeking to enforce an unwritten transfer often invoke equity, asking for a constructive trust over disputed works and urging decision-makers to treat the author as holding legal title for the venture’s benefit. This doctrine faces sharp limits in copyright law. Where federal statute voids unwritten assignments, equity cannot construct an ownership transfer out of commercial disagreements, leaving title with the author.
Claims of promissory estoppel or unjust enrichment aimed at transferring title run into federal preemption, which bars state-law ownership theories that circumvent statutory writing requirements.

The Statutory Barrier of Section 204
Federal policy favors certainty of title over late-stage commercial convenience. Commissioning software without an executed agreement creates a structural gap that subsequent investment rounds cannot close by assertion. The statute requires a physical or verified digital record reflecting the creator’s explicit assent.
While recollections of past talks shift with interest, a signed document does not change. An author contesting an implied assignment relies on the missing signature; without written or cryptographic consent, title remains with the person who wrote the code.
Defending against an equitable assignment starts by showing that unwritten understandings transfer no rights. Disputed equity splits, verbal promises of options, and vague references to company property fail the threshold test of written execution. The author can show that discussions of corporate ownership described an intended outcome dependent on formal contracts.
If those contracts are never signed, ownership remains with the author under the statute.
A clause conditioning assignment on the delivery of fully vested equity shifts the date of transfer from the initial commit to the physical or official delivery of the certificate.

Wall
The distinction between an assignment of title and a permission to use marks a clear boundary in federal copyright law. When an author writes software for an unincorporated venture, the business often assumes it owns the copyright. Federal courts separate legal title, beneficial interest, and nonexclusive access.
Nonexclusive permission needs no signed document; it arises from conduct, code delivery, and ongoing work. Assigning title, by contrast, requires full statutory compliance. Defending title depends on forcing the venture to state whether it claims exclusive control or merely operational access.
Ownership disputes in startup capitalization often confuse nonexclusive conduct with a complete transfer of rights. A venture may argue that because an engineer pushed code to a shared repository branch, it acquired all exclusive rights under Section 106. That conclusion is unsound.
Delivering code for deployment creates an implied nonexclusive license to run the software as planned, leaving legal title with the author. The creator remains free to license the code base to others, release it under open terms, or use it to build a competing system.
Delivering repository files creates operational permission without surrendering exclusive legal title.
Defending against an implied equitable assignment requires isolating the underlying terms of the engagement across three structural layers:
- Statutory authorship status determines whether the code is a work made for hire under agency standards, which bars independent ownership if the author was a salaried employee.
- Delivery context sets the scope of an implied license, limiting the venture to the specific use intended during active development.
- Consideration structure establishes whether early payments covered labor hours or served as explicit payment for absolute transfer of ownership.
Ventures often argue that paying an independent contractor for software automatically transfers ownership to the firm. This position overlooks the distinction between paying for services and purchasing exclusive rights. An independent author hired to build core database architecture retains statutory ownership unless a signed writing transfers the title.
Payment covers engineering time and provides a nonexclusive license to run the software, while legal title remains with the creator. Assertions of complete ownership break down once title records are formally reviewed.
The contractor drew forty thousand dollars from the corporate bank account, built the product in the venture’s private workspace, and everyone in the room understood the company owned the asset from day one.

Consideration
Payment checks alone do not transfer a copyright in software. In pre-incorporation projects, founders frequently pay small amounts from personal accounts, cover living expenses, or promise equity that goes unissued. If the software succeeds, the venture may claim these early payments served as consideration for an equitable assignment.
The author counters by demonstrating that payments covered working hours or nonexclusive usage, leaving any transfer of title unsupported by a bargain.
Consider an engineer who builds a financial reporting module over six months without an employment contract. The founder transfers fifteen thousand dollars across three wire payments marked as consulting fees and sends a message promising ten percent of ordinary shares upon incorporation. The company incorporates, but the shares are never issued because investors require a clean capitalization table.
When the engineer leaves, the founder brings a claim asserting the enterprise owns the module through an equitable assignment backed by the fifteen thousand dollars and the equity promise.
Because consideration alone transfers no rights, the defense shows that the fifteen thousand dollars compensated engineering time at market rates, while the equity promise was never fulfilled. An unperformed promise to grant shares does not constitute consideration for a copyright transfer. The startup cannot claim the asset while withholding the equity supposed to buy it.
Where consideration is missing or unperformed, equity will not strip the author of statutory title.
| Grant Category | Writing Prerequisite | Title Locus | Infringement Standing | Revocability Status |
|---|---|---|---|---|
| Statutory Assignment | Signed written instrument | Assignee holds full legal title | Assignee possesses exclusive standing | Irrevocable absent explicit condition |
| Implied Equitable Assignment | Unwritten or defective memorandum | Contested beneficial claim | Chancery petitioner lacks standing | Unenforceable against statutory titleholder |
| Implied Nonexclusive License | No writing required | Author retains legal title | Licensee lacks statutory standing | Irrevocable if consideration paid |
The table illustrates why startups attempt to frame a nonexclusive license as an equitable assignment. Under a nonexclusive license, the company cannot sue competitors who use identical code, nor can it stop the author from commercializing the codebase elsewhere. Institutional investors reviewing asset records flag this exposure quickly, which can lead to reduced valuations or stalled funding rounds.
The author’s legal position depends on keeping the arrangement within the third category, where the statutory rule keeps it.
An unperformed promise of corporate stock cannot serve as executed consideration for a permanent property transfer.
Fiduciary duty claims face similar hurdles. Startups frequently argue that an early contributor owed fiduciary duties as an officer or de facto director, creating an obligation to assign software to the company. The author counters by showing the software was created before the corporation legally existed, meaning no fiduciary duty was owed at the time of writing.
An individual cannot owe duties to an entity that does not exist. Moreover, an officer creating work outside specific contractual duties retains title unless a written contract provides for automatic assignment.
Attempting to enforce an unwritten assignment through retroactive claims creates significant legal uncertainty, clouding the company’s IP portfolio and discouraging institutional investment.

License
Permissive use is the standard alternative to an absolute transfer of title. When an author provides source code to a venture without an assignment, courts infer an intent to allow the business to use the software for immediate operations. This implied nonexclusive license protects the venture from direct claims of copyright infringement while leaving title with the author.
Preserving ownership requires defining the scope of this permission and limiting unauthorized expansion or derivative works.
The scope of an implied license is tied to the shared intent of the parties at delivery. An author who develops an authentication module for a local pilot program does not give the startup a license to white-label that module for international enterprise clients. If the company expands usage beyond the original scope, the author can claim infringement for the unauthorized uses.
The license protects the business only within its original operational limits.
Establishing that an arrangement is a limited license rather than an equitable transfer follows a clear evidentiary sequence:
- The author shows that no signed transfer agreements exist in physical or digital communications.
- Repository logs are verified to confirm that commits were made under individual author accounts before any assignment agreement was presented.
- Payment records are identified as hourly or project fees rather than capital paid to purchase underlying IP rights.
- Written notice is sent outlining the nonexclusive scope of the venture’s license and stating that title remains with the author.
Revocability often decides licensing disputes. If the company paid no monetary consideration for the development, the implied license remains revocable at will, allowing the author to issue a cease-and-desist notice ending the firm’s authority to host or distribute the code. Even if early payments make the license irrevocable, that status applies only to the specific code versions delivered during the engagement.
It grants no rights to subsequent updates, structural changes, or new modules built after separation.
A key open question is whether an implied nonexclusive license survives a corporate restructuring where the original entity dissolves into an acquirer without the author’s consent.

Gate
Confirmatory paperwork is often where informal arrangements face formal scrutiny. Due diligence by prospective investors routinely uncovers missing IP assignments for early code bases. At that point, the startup usually presents the departed author with a confirmatory assignment, framing it as a routine administrative step.
An author familiar with IP rules recognizes the request as an implicit acknowledgment that title never transferred.
A confirmatory assignment intended to ratify an unwritten transfer cannot create a writing retroactively. If the author declines to execute the document, the startup cannot force execution absent an existing contract to assign. Without a signed document, the startup holds software supported only by a nonexclusive license while attempting to assure investors of sole ownership.
Leverage shifts to the author who maintained legal title by declining to execute unwritten agreements during early development.
A request for a retroactive assignment confirms that existing title remains with the independent creator.
Dissecting a startup’s ownership claims highlights the difference between corporate assumptions and statutory IP law. The common assumption is that shared effort and informal collaboration automatically vest code in the enterprise. The statutory framework dictates that title remains with the individual author until a signed writing transfers it.
If the author insists on the statutory requirement, the company must either purchase the title at market value or rebuild the codebase from scratch.
Title remains with the author until an instrument of transfer is signed.