Evaluating Retroactive Valuation Triggers In Unsigned Software Intellectual Property Disputes Across Federal Circuits

Unsigned software commits create latent copyright and restitution claims that convert into retroactive enterprise valuation liabilities during corporate liquidity.

8 min

Desk

A software engineer pushes forty thousand lines of repository code across seven months while working from a kitchen table, relying on text messages and an informal promise of six percent equity. No written copyright assignment passes between the parties, no independent contractor agreement is drafted, and no consulting fees change hands. The company incorporates twelve months later, closes an institutional funding round at a twenty-million-dollar post-money mark, and sends the engineer a standardized advisor agreement granting one-tenth of one percent vesting over four years.

The engineer refuses to sign. For three years, the repository sits silent while enterprise deployments expand and proprietary systems run on the unassigned architecture. When an acquisition offer arrives at ninety million dollars, the engineer files an action asserting exclusive copyright ownership, trade secret misappropriation, and quantum meruit, seeking an appraisal tied directly to the exit transaction.

Every unwritten software contribution functions as an unrecorded influx of capital. The engineer provides labor and intellectual property without formalizing terms, while the company accepts the work, treating the lack of paperwork as tacit consent. Under Section 204(a) of the Copyright Act, transferring intellectual property requires a signed writing; without an executed instrument, title never passes.

At most, the company holds a non-exclusive implied license to run the binaries, leaving the underlying work anchored to the original developer. That unrecorded exposure stays on the books until a corporate liquidity event forces a formal accounting of ownership.

Unassigned software architecture remains personal property until an executed writing conveys legal title.

Federal district courts evaluate these disputes through standard contract formation and property law. When a developer supplies software without demanding immediate payment, the commercial value of that work does not simply absorb into company surplus. The law treats the exchange as an incomplete transaction.

If the company sells the business or raises its valuation through successive funding rounds, the developer returns to seek an appraisal based on the higher valuation. In these cases, the developer maintained the repositories, supported initial deployments, and held off on invoicing under a shared understanding that compensation would follow the company’s growth.

Accrual

Suspended optical magnification hovering above a recessed circular platform frames two tiny figures evaluating joint provision requirements.

Statutory Clock Mechanisms Under Copyright Rules

Federal circuits split over when the clock starts for asserting rights over unassigned code. Under Section 507(b) of the Copyright Act, civil copyright actions face a three-year statute of limitations, but courts disagree on whether that clock begins at the moment of injury or upon discovery of the violation. The injury rule sets accrual at the time infringement occurs, blocking claims for software deployed more than three years before the complaint is filed.

The discovery rule tolls the statute until a diligent owner knew or should have known of the unauthorized use. In reviewing historical claims under Petrella v. Metro-Goldwyn-Mayer, the Supreme Court left open whether recovery can stretch back beyond three years if the plaintiff files promptly after discovering commercial monetization.

The Ninth Circuit takes a broad view of the discovery rule in software disputes. When an engineer discovers that early commits have been integrated into a commercial platform, the three-year clock begins at actual discovery, allowing retroactive recovery of profits tied to the infringement. The Second Circuit sets a firmer cap on damages: even if a claim is timely under the discovery rule, financial recovery cannot extend back more than three years from the filing date.

The Fifth Circuit ties recovery to specific acts of commercial exploitation, limiting retroactive accounting to recent revenue streams.

A funding announcement converts informal repository participation into an overt claim of exclusive title.

Small figures observe a mechanical drawing featuring a balanced apparatus with gears and a magnifying lens to inspect items.

When Does Code Contribution Become Unjust Enrichment?

Common law claims for quantum meruit and unjust enrichment seek to recover the fair market value of development work, but state-level claims often run into federal preemption under Section 301 of the Copyright Act. Federal courts use an extra-element test to decide if common law actions can proceed. If the state claim asserts rights equivalent to the core rights protected by copyright, federal law preempts it.

Preemption turns on the nature of the promise made at the founding stage:

  • Unjust enrichment claims fail across most circuits when grounded solely on the unauthorized reproduction, display, or distribution of unassigned repository code.
  • Quantum meruit assertions survive preemption if the developer establishes a clear expectation of direct payment for engineering labor, separate from any copyright transfer.
  • Promissory estoppel counts avoid dismissal when the developer demonstrates reasonable reliance on specific promises of equity that induced continued work.

When founders fail to document code authorship early, enterprise acquirers discount purchase prices by the entire projected cost of retroactive title litigation.

Variance

Two small figures stand beneath a central office chair bridged by two cracked halves of a large circular wax seal.

Circuit Approaches to Implied Software Licenses

Federal circuits take different approaches to the scope of non-exclusive implied licenses created when code is handed over without written contracts. An implied license forms when a developer builds software at another party’s request and delivers it expecting that party to use and distribute it. Disputes generally center on whether the license can be revoked upon demand, whether it allows commercial modifications, and whether subsequent funding rounds alter the original implied understanding.

Circuit Standards Governing Unassigned Software Contributions and Valuation Windows
Federal Circuit Implied License Scope Damages Window Rule Preemption Severity
Second Circuit Narrow license, revocable upon non-payment Strict three-year lookback cap on profits High preemption of quasi-contract restitution
Fifth Circuit Broad irrevocable commercial authorization Injury-driven accrual with limited lookback Moderate preemption permitting breach claims
Ninth Circuit Intent-based authorization to original scope Full discovery accrual without three-year limit Low preemption for distinct promissory acts
Eleventh Circuit Strict reliance on objective delivery conduct Three-year lookback enforced strictly High preemption barring parallel unjust enrichment

The Second Circuit views implied licenses as fragile. If software is written with the expectation of equity, failing to deliver that consideration can revoke implied permissions, turning ongoing commercial use into copyright infringement. The Ninth Circuit looks to objective intent when the binaries were pushed to production.

If the developer handed over code knowing it would power a commercial product, the implied license protects the company from statutory copyright damages, shifting the dispute entirely to contract law.

A written assignment clause signed before the first commit permanently bars retroactive valuation triggers by establishing complete enterprise title at zero ongoing royalty liability.

Measure

A standard metal desk lamp faces a complex geometric construct beside small silhouettes standing on a flat ground in this drawing.

Apportionment and Reasonable Royalty Calculations

Calculating the value of software intellectual property after the fact requires separating disputed code from the broader commercial platform. Enterprise companies rarely sell standalone source code; they sell subscriptions, hosting, services, and features built over the original repository. Under Section 504(b) of the Copyright Act, a rights holder can recover actual damages alongside any infringer profits tied to the infringement.

The statute requires the developer to prove only the company’s gross revenue, shifting the burden to the defendant to prove deductible expenses and revenue driven by other factors.

The main legal battle revolves around apportionment. If forty thousand lines of unassigned backend code underpin a platform generating fifty million dollars in annual recurring revenue, the court must determine how much of that revenue stems from the initial technical core versus sales, branding, marketing, and subsequent feature development. Courts frequently adapt reasonable royalty frameworks from patent law using the Georgia-Pacific factors, modeling a hypothetical negotiation between the parties just before first commercial release.

Software developers who deliver core functional code without stated compensation preserve an unliquidated lien against corporate liquidity events.

Federal circuits approach hypothetical negotiations differently:

  1. The Ninth Circuit metric allows expert testimony linking reasonable royalties to subsequent venture capital valuations, treating funding rounds as direct evidence of the technical asset’s market value.
  2. The Federal Circuit approach rejects overall enterprise transaction values, applying an entire market value rule that requires plaintiffs to prove the unassigned component drives buyer demand for the whole product.
  3. The Second Circuit standard ties damages to prevailing market rates for contract engineering at the time the code was written, rejecting retroactive claims based on later valuation surges.

Consider an enterprise software company that incorporates sixty days after obtaining fifty thousand lines of unassigned code from an early technical partner. If the business raises five million dollars at a twenty-million-dollar valuation in its second year and is acquired for one hundred million dollars in its fourth year, establishing the core algorithms as twenty percent of platform functionality creates a vast damages range. The claim could swing from five hundred thousand dollars under a replacement-cost calculation to twenty million dollars under an equity apportionment model, highlighting the risk of unassigned code.

Equity value reflects market sentiment whereas intellectual property recovery reflects strictly proven economic contribution to product revenue.

Charge

Two small figures stand observing a large light bulb which contains a heavy metal safe within its threaded base section.

Retroactive Triggers in Merger and Acquisition Diligence

Corporate acquisitions frequently trigger litigation over unassigned software. During merger negotiations, legal teams audit repository commit histories to verify intellectual property provenance, matching commit logs against executed agreements, board resolutions, and assignment documents. Uncovering commits written by someone without a signed assignment reveals a clear defect in title.

A funding round or acquisition forces the company to locate the former contributor and request a retroactive assignment, shifting leverage to the developer. Recognizing that the pending deal cannot close without clean title, the author can demand a premium tied to total transaction value. At that stage, replacing the software without interrupting operations, rewriting core libraries, or missing closing deadlines becomes nearly impossible.

When capital arrives eighteen months later, the dispute turns on whether federal circuit courts will eventually unify around an apportionment ceiling that caps retroactive software awards at the fair market replacement cost of engineering hours or continue permitting windfalls tied directly to venture market transaction timing.

Six fields, each writing its own terms

The terms are written where they belong. Each field holds three desks, and every entry a desk writes raises the terms it uses, each term given a meaning, a mechanism and the places it appears. The record on these pages stays first person and hand made; the fields grow the nomenclature.