Verbal Equity Commitments and Undocumented Code Ownership Disputes
Statutory copyright law leaves unwritten software title with individual authors, requiring signed conveyance deeds to ground corporate equity claims.
Pact
Two founders discuss a software product before incorporation and agree to split equity equally. One writes the core codebase over six months while the other builds early operational interest. Without an incorporated entity, share purchase agreement, or intellectual property assignment, the verbal agreement forms only an informal expectation.
Under statutory copyright law, the developer who writes the code remains its sole author and owner.
Under Title 17, Section 204(a) of the United States Code, a transfer of copyright ownership requires a written instrument of conveyance signed by the owner of the rights. Promising half of a future company verbally does not transfer legal title to software written before incorporation. The developer keeps full copyright ownership, leaving the planned enterprise with nothing more than an expectation of a future license or assignment.
The statutory requirement for a written copyright conveyance prevents unwritten equity discussions from altering legal software title.
Divergence of Recollection in Early Agreements
Unwritten arrangements are remembered differently as incentives shift. Once a business gains traction or brings in capital, the founders rarely recall the original deal the same way. One remembers an unconditional promise for half the company; the developer remembers a suggestion conditional on full-time commitment and matching capital.
Without contemporaneous documents setting vesting schedules, exact share counts, and IP transfers, competing claims cannot be tested. The developer who wrote the source code retains statutory ownership, leaving the company with no documented title to its product.
The business was built on the understanding that half the equity belonged to the founder who set the early operational strategy.
Trace
Version control systems log every change made to a repository. Git commits record the timestamp, author identity, and cryptographic hash for each modification, establishing clear evidence of who wrote what. Those logs prove authorship, but they do not transfer legal rights to a company.
A repository created on a developer’s personal machine or personal account remains that developer’s property. Pushing code to a shared repository or giving colleagues access grants only an implied, non-exclusive license to test and run the software. That falls short of transferring copyright, and without written contractual consideration, an implied license can be revoked by the author at any time.
| Configuration State | Copyright Ownership Holder | Corporate Transfer Instrument | Enforceability and Diligence Outcome |
|---|---|---|---|
| Unassigned Verbal Contributor | Individual Software Author | None (Verbal Expectation Only) | Defective title; author retains sole copyright and can issue cease-and-desist. |
| Independent Contractor without Assignment | Contractor Developer | Service Agreement lacking IP Assignment Clause | Economic payment creates non-exclusive license; corporate entity lacks exclusive rights. |
| Executed Inventions Assignment Deed | Corporate Entity | Written Property Assignment with Express Consideration | Clean corporate title; complete transfer of pre-incorporation source code. |
Repository Contribution Records as Evidence
Commit logs show who wrote each line of code. If a dispute arises, repository history is analyzed to separate original code from third-party libraries and later edits. A developer whose commit history shows sole creation of the core backend architecture controls the company’s technical position.
A company owns no intellectual property automatically. Paying for hosting, hardware, or a developer’s living expenses does not meet the statutory requirement for a written transfer of software rights. The author retains ownership until a written instrument explicitly assigns the title.
An executed written conveyance specifying the exact software asset is required to strip individual authorship rights in favor of a corporate entity.
The standard invention assignment agreement transfers all prior and future software contributions upon the effective date of execution.
Split
Undocumented software ownership typically comes to light during institutional fundraising or an acquisition. Investors inspect the legal chain of title from every historic developer to the corporate entity before issuing binding terms. An unassigned core codebase or an unwritten equity claim from an early contributor creates a defect in title.
When code ownership is unclear, investors halt the transaction. The business has two options: secure a signed retroactive assignment from the original developer, or rewrite the repository from scratch. The developer holds maximum negotiating power at that moment.
Why Do Early Verbal Share Promises Fail Diligence?
Unclear capitalization tables block investment because an unwritten equity claim represents an unquantified liability. Counsel cannot tell whether a claimant owns zero percent, fifty percent, or a grant subject to standard four-year vesting with a one-year cliff.
Consider a standard case: two founders work for eighteen months without incorporating or signing invention assignments. Developer A writes ninety-five percent of the codebase, while Developer B handles client discovery and secures a term sheet for two million dollars. During investment diligence, Developer B asks Developer A to sign an agreement transferring all prior commits to the new corporation in exchange for a ten percent equity stake.
Developer A refuses, maintaining that the original verbal agreement was a fifty-fifty split with no vesting conditions.
Under federal copyright law, Developer A owns the entire codebase. Developer B holds a corporate shell with a term sheet but no intellectual property. The enterprise cannot close the investment round without Developer A’s written transfer.
- Retroactive Equity Settlement requiring the company to issue the full claimed equity stake without vesting to obtain the signed copyright assignment.
- Complete Repository Replacement forcing the company to discard eighteen months of development and pay new engineers to rewrite the software without referencing the original code.
- Corporate Dissolution when investors withdraw the term sheet over unresolved IP litigation risk and unquantified equity exposure.
Undocumented software property claims exposed during corporate investment force the enterprise to yield to the developer’s terms or abandon the codebase.
The cost of resolving a disputed code title escalates exponentially once institutional capital enters the valuation equation.
Deed
Resolving an unwritten equity promise and securing title to software requires an explicit written record that replaces prior discussions. This is accomplished using specific legal instruments designed to assign historical software assets and set clear equity allocations.
A formal resolution uses two simultaneous documents: a Confirmatory Copyright Assignment Deed and a Restricted Stock Purchase Agreement with explicit vesting schedules. The assignment deed identifies every repository, commit, domain, and architecture document created prior to incorporation, transferring all past, present, and future IP rights to the company in exchange for legal consideration.
Essential Provisions of an Enforceable Intellectual Property Settlement
Executing a clean transfer requires strict adherence to corporate standards. Leaving any term unwritten reproduces the initial defect under another name.
- Explicit Asset Identification naming the specific repository URLs, commit hash ranges, software modules, and developer handles transferred to the company.
- Recital of Express Consideration documenting the monetary payment or share issuance provided in exchange for the IP title.
- Mutual General Release waiving all prior unwritten promises and understandings regarding capitalization, equity shares, and compensation.
- Waiver of Moral Rights preventing the author from asserting rights of attribution, modification, or destruction against future iterations of the code.
Verbal share splits carry no weight on corporate capitalization tables. Issuing equity without an executed assignment leaves title exposed to ongoing legal challenge.
Written contractual assignments executed with clear consideration establish the sole legal reality recognized by corporate registries and courts.
A retroactive assignment signed without fresh corporate consideration fails to alter underlying statutory ownership in multiple legal jurisdictions.
Yield
Resolving a verbal equity dispute comes down to what statutory records exist. When two founders separate after months or years of unwritten development, outcomes are set by the repository and signed legal documents. The developer who wrote the code owns the copyright, while the founder who handled business operations retains the client relationships and commercial momentum.
Taking the ground out from under an unwritten agreement leaves only what is documented in statutory filings and software commit logs.
When legal assignment fails due to a breakdown in trust, the company must execute a code purge. Engineering teams remove all commits authored by the departed developer, and new engineers rebuild the software in a clean room environment without viewing, copying, or referencing the original codebase. This eliminates copyright infringement liability and severs the former partner’s equity claims.
The former partner retains ownership of the original commits but holds no equity in the restructured company. The company operates with a clean repository and an undisputed cap table, leaving the initial verbal agreement replaced entirely by executed legal documents and repository logs.