Quantifying Equitable Scope For Unsigned Custom Code Delivery Permissive Access
Unsigned custom code delivery transfers only an implied non-exclusive license, exposing the receiving venture to equitable quantum meruit market restitution.

Deposit
A repository invite lands on a Sunday evening. The developer attaches an uncompiled directory, issues an administrative token, and watches the build pass across remote servers. Nothing is signed.
The parties rely on an informal understanding about long-term upside, verbal assurances of equity, and a rush to launch that pushes governance aside. When custom software changes hands without executed assignments, legal ownership stays with the author. What actually transfers is simple operational permission.
Federal copyright statutes in the United States require a written instrument signed by the owner to assign exclusive rights. Without that signature, handing over binary files and administrative permissions creates only a non-exclusive implied license. The operator of the receiving enterprise assumes full title has transferred, mistaking control of a cloud cluster for ownership of the underlying intellectual asset.
The author assumes the code serves as an unpriced equity contribution, leaving a silent claim on the enterprise.
A transfer of source files without an executed assignment conveys only implied permission to run the software.
Equitable valuation begins the morning those two expectations collide. The contributor supplied thousands of hours of specialized engineering assuming equity participation. The receiving enterprise integrated that logic into commercial production, relying on steady operation to service paying customers.
Neither side defined the boundary between a permissive grant and an asset transfer while the work was being written.

Informal Handover Patterns
Technical contributors often hand over operational keys before commercial terms take shape. The builder wants to show capability and goodwill, expecting that utility will lead to an equitable partnership split. That move turns standard deal sequencing upside down.
Once an enterprise integrates custom architecture into daily billing pipelines, its commercial urgency drops to zero. Leverage shifts entirely to the entity in possession, which treats the software as a settled fact.
The builder sits outside the corporate entity, holding raw authorship rights while the enterprise collects customer revenues. When the builder tries to invoice for completed engineering hours, the venture counters that the labor was a collaborative effort. When the builder asks for shares, the venture answers that no co-ownership deal was ever authorized.
This deadlock drains the technical contributor of liquidity while leaving the operating business with permanent title risk.

Dock
Physical freight facilities rely on physical manifests. Digital infrastructure behaves differently because source files copy without leaving an empty shelf behind. A commit history records author timestamps, structural changes, and administrative credentials granted across external networks.
Those digital footprints serve as primary evidence when measuring the scope of a permissive delivery. Every pull request accepted by officers establishes knowledge and tacit acceptance of the incoming code.
Evaluating unsigned technical deliverables involves three mechanical factors to define the boundaries of an implied license. The creator must have built the material at the request of the counterparty. The creator delivered that material.
The creator intended the counterparty to copy and run the work within designated operations. In software environments, pushing revisions directly to production branches satisfies the delivery requirement completely.
A recipient who integrates unassigned code into production infrastructure accepts restitution claims based on fair market value.
The unresolved boundary centers on duration and revocability. A non-exclusive license granted without monetary consideration remains revocable at will under general contract principles. State contract statutes govern revocability where federal copyright rules fall silent.
If the software developer supplied source files without receiving wages or an equity grant, the transaction lacks formal consideration. The developer retains the power to terminate permissive access, exposing the operating venture to copyright infringement claims.

Permissive Grants and Revocation Exposure
Operating entities build substantial value on top of informal digital deliveries. When an enterprise attempts an institutional funding round or an acquisition, external counsel inspects the commit logs. Missing assignment documentation halts commercial transactions immediately.
Investors decline to capitalize an enterprise whose primary technical engine remains licensed on an unwritten, permissive basis from an unpaid engineer.
The table below outlines the legal and commercial mechanics dividing an executed asset assignment from an unsigned permissive delivery.
| Dimension | Executed Assignment | Permissive Access Implied Grant |
|---|---|---|
| Title Location | Transfers entirely to the operating corporate entity | Remains vested in the contributing software author |
| License Character | Exclusive, worldwide, perpetual across all media | Non-exclusive, limited strictly to contemplated use |
| Revocability Profile | Irrevocable upon mutual execution and delivery | Revocable when granted without monetary consideration |
| Enterprise Exposure | Clean chain of title ready for external diligence | Permanent risk of statutory copyright infringement claims |
| Remedy Basis | Actionable breach of contract for broken covenants | Quantum meruit restitution and statutory licensing rates |
Debate persists over whether ongoing commercial deployment counts as accepted consideration when compensation stays purely prospective. One legal analysis holds that access to active users and operational testing environments supplies enough value to render a permissive license irrevocable. A competing view maintains that intangible exposure cannot satisfy basic consideration doctrines.
The unpaid developer entered the arrangement expecting shares; the corporate operator assumed the software was free infrastructure.
The operator gained access to the repository, deployed the code to paying clients for twelve months, and received no invoice until an investment round was announced.

Grant
Equitable quantification steps into the silence left by missing contracts. When express contracts fail, equitable doctrines apply: quantum meruit and unjust enrichment. Quantum meruit measures the reasonable market value of the services rendered by the author.
Unjust enrichment measures the economic benefit conferred upon the receiving enterprise, preventing an operator from retaining commercial profits generated by uncompensated labor.
A software author who delivered permissive code without a contract does not automatically secure a percentage of corporate equity. Official reviews rarely construct corporate ownership splits out of ambiguous conversations. Equity grants require precise definitions of vesting schedules, intellectual property warranties, and governance rights.
Arbiters will not write a co-ownership agreement that the parties themselves avoided drafting. Relief for the developer almost always reduces to direct cash awards.
Equitable remedies convert informal equity promises into cardinal currency calculations based on replacement costs.
Restitution calculations measure what an independent engineering firm would charge to build identical functions. Industry billing rates, developer seniority, and time logs determine that baseline. The venture suddenly faces a cash liability that can exceed its liquid reserves, even while retaining the software itself.
The giving party expected partnership; the operational legal outcome yields an invoice.

Doctrinal Measures of Supply Value
Two distinct calculation strategies govern the quantification of unassigned code deliveries. The chosen strategy alters the financial exposure of the enterprise and the recovery sum for the engineer.
- Fair market labor value calculates the cost to reproduce delivered modules using specialized third-party contractor rates. This figure relies on documented commit velocity, architectural complexity, and regional freelance benchmarks.
- Commercial benefit restitution assesses net revenues or valuation gains directly attributable to the operational software. That approach extracts value from company growth rather than raw working hours.
- Reasonable royalty determination establishes what hypothetical arm’s-length parties would have negotiated for a non-exclusive license on the delivery date. The resulting rate attaches to every unit transaction or billing period running across the software engine.
A clear contractual clause stating that all unexecuted contributions convert to an hourly consultancy capped at one hundred dollars per hour eliminates equitable exposure entirely, turning a million-dollar equity dispute into manageable operational debt.

Rate
Calculating the exact financial quantum demands rigorous accounting. The field separates the market rate of writing code from the value of keeping operations stable. Software written under rush deadlines to salvage a launch often contains specialized intellectual property, bespoke algorithms, and custom database schemas.
When an unsigned author delivers those components, the baseline rate cannot mirror standard internal compensation. Employees receive health benefits, statutory protections, equipment stipends, and predictable payroll. Independent contributors bearing their own overhead command freelance multiples.
Consider a common scenario. Two software engineers write a proprietary transaction processing engine over nine months for an emerging payment brand. The brand’s founders control customer acquisition, payment rails, and regulatory licensing.
No written contractor agreement is signed; the engineers receive repository write permissions, production access, and assurances that fifteen percent of the holding company belongs to them. The application launches, processing six million dollars in monthly gross merchandise volume. At month ten, the brand owners present an equity agreement containing a four-year backloaded vesting schedule and heavy non-compete clauses.
The engineers refuse to sign.
The enterprise attempts to lock the engineers out of GitHub repositories and cloud consoles. The engineers respond by revoking the implied license, demanding a full stop to code execution and filing claims for equitable restitution. The brand owners argue that permissive deployment established a royalty-free license for the lifespan of the company.
That dispute highlights the friction between contribution and commercial extraction.

Which Valuation Model Survives An Unsigned Delivery?
Establishing the recovery sum involves competing accounting frameworks. The receiving enterprise argues that recovery should equal the cost of hiring an offshore agency to rewrite modules from scratch. The contributing developer contends that recovery must reflect the replacement value of an urgent, continuous build that let the venture secure paying customers.
That premium includes weekend work, uncompensated architecture design, and immediate production triage.
Uncertainty surrounds how to treat subsequent revisions. When internal staff add commits to an original codebase written by an unpaid developer, the modules become commingled. Federal law treats non-separable derivative work authored without permission as copyright infringement.
Yet when the original developer permitted initial deployment, downstream modifications carry colorable authorization. Legal mechanisms struggle to split value between the original skeleton and maintenance updates added by salaried staff.
Field research in organizational psychology confirms that unstated expectations create asymmetric memory. The giving party remembers every late-night commit, every architectural crisis resolved without pay, and every verbal reassurance uttered over a kitchen table. The receiving party remembers the software bugs, missed deadlines, and their own capital risked on marketing and legal compliance.
Over three years, the subjective value kept by the giver inflates exponentially, while the recipient perceives the supplied code as an asset whose debt was amortized long ago. When the count is finally stated aloud, the gap between the two expectations exceeds the total liquid value of the company.
This dynamic leaves an unresolved operational tension: does an enterprise gain an implied perpetual license simply by absorbing an author into daily administrative routines, or does each uncompensated billing cycle renew the author’s power to demand an accounting of profits?

Stop
The termination of permissive software access marks where informal arrangements end and property claims begin. When an uncontracted author cuts API keys, revokes credentials, or issues formal takedown notices, the operating venture faces severe disruption. The technical asset powering daily customer transactions instantly turns into an existential liability.
Enterprise leadership realizes that skipping equity conversations in the founding phase bought temporary speed at the cost of structural vulnerability.
The builder faces equal trouble. Revoking access rarely triggers a liquidity event. The developer trades a potential equity stake for a drawn-out dispute over code ownership.
Hours that could have built new products are spent drafting affidavits, pulling commit logs, and paying IP litigators. The unstated agreement, left compounding in silence, damages both parties.
Writing clear terms takes twenty minutes on the day work begins. A simple single-page document can define code delivery as a paid work product with full assignment of rights, or state explicitly that no assignment occurs until a definitive equity schedule executes. That single operational boundary stops the accumulation of covert debt.
Where no terms exist, unspoken expectations accumulate until the relationship breaks, leaving behind a bill that eventually requires cash settlement.
An enterprise that accepts digital assets without a signed contract pays the market replacement rate the moment the author walks away.