Verbal Equity Promises and Intellectual Property Ownership Transfers

Unwritten equity promises convey no legal title to software code, leaving statutory intellectual property ownership with individual creators until executed in writing.

12 min

Statute

A drawing of keys on a ring morphing into a scroll that forms a deck chair with a small figure.

Default Ownership Rules in Copyright and Patent Law

Copyright and patent statutes vest initial ownership of an original work in the individual creator. Under federal copyright law, source code, technical specifications, and interface designs belong to whoever wrote or drew them. The baseline fixes at the instant of creation.

Unless a signed writing transfers those rights, the founder or corporate entity commissioning the work owns zero percent of the copyright.

Patent law operates on the same premise: inventorship and initial ownership attach to the individual inventor. Even if an engineer designs hardware architecture or writes system code on company machines in an office provided by a founder, legal title remains with that engineer. Covering early operating expenses, proposing conceptual features, or guiding product discussions in initial meetings gives a company no proprietary claim to the resulting assets.

The single statutory exception under copyright is the work made for hire doctrine, which applies in only two narrow scenarios: where the author is a bona fide employee acting within the scope of employment, or where the work is specially commissioned under a written contract signed by both parties containing the explicit phrase work made for hire. Contributors operating under advisory agreements, informal understandings, or early co-founder arrangements rarely qualify as statutory employees. Without regular payroll, tax withholdings, or formal employment agreements, courts treat these contributors as independent contractors who keep their title by default.

Unwritten promises of future equity create no automatic transfer of statutory intellectual property rights.

Graphite pencil drawing and fine pen lines delineate a silhouette hand placing a numbered domino into an open duffel bag.

The Failure of Oral Commitments to Transfer Assets

Oral equity commitments run straight into the statutory formalities required to transfer title. Under federal copyright law, any transfer of copyright ownership, outside operations of law, remains invalid without a written conveyance or memorandum signed by the owner of those rights. A late-night conversation, a verbal agreement among collaborators, or an informal handshake concerning future ownership conveys no title whatsoever to the code.

Verbal assurances regarding equity splits function at best as executory contracts to issue stock down the line, assuming the agreed terms are definite enough to enforce. They do not assign intellectual property. This splits early technical ventures across two distinct legal questions: who holds equity in the company, and who owns the source code.

A verbal commitment to grant stock in the future fails the statutory requirement for a present, written transfer of intellectual property.

Corporate records and intellectual property ownership move along separate legal tracks. Even if a court recognizes an enforceable oral contract for equity, that finding does not divest the developer of copyright title. The developer retains ownership of the codebase until executing a written document that conveys it to the entity.

Only an explicit written clause assigning present and future intellectual property alters that statutory baseline.

File

A frayed rope hangs broken in the drawing between a heap of geometric forms and the vacant expanse while plain figures wander near the rubble.

Codebase Artifacts and Inventorship Records

Repositories and technical documentation maintain a timestamped record of every commit, pull request, and architectural proposal. These logs establish an evidentiary record that contracts drafted months or years later cannot easily rewrite. Each commit links specific blocks of intellectual property directly to an individual author account.

In an ownership dispute, these technical logs determine who built specific modules, when the code was pushed, and what was written before the company legally incorporated.

Engineers routinely run up extensive commit histories on informal promises of equity. If the relationship breaks down, immediate operational leverage depends on who holds administrative credentials, where the repository sits, and whose name appears on the git logs. A developer with exclusive administrator access and local repository copies controls the asset as a practical matter.

Companies operating without signed intellectual property assignments face substantial exposure the moment they attempt to license, ship, or sell software built under uncontracted arrangements.

  1. Commit Logs verify individual developer authorship and timestamp exact contributions prior to corporate entity formation.
  2. Repository Permissions determine physical access and administrative authority over the underlying software source code.
  3. System Architecture Notes demonstrate original inventorship and document individual structural design contributions.
  4. Communications Logs capture written mentions of equity expectations set against code delivery milestones.
A graphite drawing features a small figure gesturing toward a large soft cushion near a heavy metallic bar resting on a structure.

Work for Hire Conditions and Independent Contractor Defaults

Classifying a contributor as an employee or an independent contractor turns on factual criteria rather than internal titles. Courts weigh whether the company dictated working hours, supplied equipment, ran payroll, handled tax withholdings, or permitted the worker to decline projects. When an early-stage company runs without formal payroll or standard employment agreements, the law treats its technical contributors as independent contractors.

The developer holds the copyright baseline until a signed instrument passes title to the corporate entity.

Contractor classification carries direct consequences for product ownership. An independent contractor owns whatever intellectual property they create unless a written agreement expressly assigns title to the client. Founders often assume paying an invoice or offering a monthly stipend transfers ownership of the underlying assets.

While payment compensates the contributor, absent explicit statutory assignment language the paying entity acquires only an implied, non-exclusive license to run the software. That license allows basic internal operation. It gives the company no right to claim exclusivity, enforce patents, resell the codebase, or grant exclusive rights to prospective investors.

Verbal equity promises do not modify this ownership structure. If those promises go unfulfilled, the developer retains full statutory title. The enterprise holds nothing more than a non-exclusive operational license that rarely withstands legal review in an institutional financing or sale.

Early software builds undertaken on an informal understanding of future equity remain unassigned contractor work rather than corporate work for hire.

Reliance

Graphite lines frame a chair on a pedestal secured by a crank mechanism in a drawing as two figures observe the arrangement from below.

Quantum Meruit and Promissory Estoppel Claims

When a contributor commits thousands of unpaid hours to building software based on informal equity assurances, legal claims shift away from corporate governance toward equitable principles. Promissory estoppel and quantum meruit serve as the primary legal avenues for recovering value. Promissory estoppel requires proof of a clear promise, reasonable and foreseeable reliance by the contributor, and quantifiable detriment resulting from that reliance.

Quantum meruit claims seek the fair market value of services rendered. Where an equity commitment fails because its terms were indefinite or oral, courts can direct the enterprise to pay the contributor standard market rates for engineering labor. Prevailing under quantum meruit requires demonstrating that the services were delivered in good faith, accepted and used by the company, and provided under a reasonable expectation of compensation.

Equitable claims produce financial judgments rather than stock certificates. Courts rarely grant equity percentages or board seats through promissory estoppel where corporate governance steps were neglected. Instead, the court assesses the market rate of the developer’s hours, turns that amount into an outstanding debt, and enters a monetary judgment against the company.

  • Indefinite Equity Terms destroy contract enforceability when precise percentage grants, vesting schedules, and strike prices remain unstated.
  • Uncompensated Operator Hours generate substantial quantum meruit monetary liabilities that encumber the corporate balance sheet.
  • Implied License Terminations leave corporate entities vulnerable to copyright infringement injunctions if the creator revokes informal authorization.
  • Statute of Frauds Barriers prevent enforcement of oral equity agreements that cannot be fully performed within one year from making.
A stylized watering can filled with luminous lightbulbs and attended by two small figures illustrates the nurturing of ideas that form a venture's evidence.

The Accumulation of Uncompensated Operator Hours

Unpaid technical labor generates off-balance-sheet exposure. Contributors working without cash wages or signed equity documentation accumulate claims under unjust enrichment. The company typically takes early engineering output assuming that future stock issuances will resolve any compensation questions.

Yet if that grant arrives heavily diluted by subsequent financing rounds, or sits behind a standard four-year vesting schedule that disregards historical service, the contributor can refuse the terms and seek cash restitution.

Unwritten equity promises offered during informal alignment generate monetary liabilities under equitable restitution principles.

Determining quantum meruit awards relies on industry wage benchmarks. Expert testimony establishes prevailing hourly rates for software architects, systems engineers, and technical leads. An engineer who works full-time for two years without salary generates a potential claim between several hundred thousand dollars and more than half a million dollars against the corporate entity.

Failing to execute written equity agreements before delivering code leaves the contributor without enforceable stock and facing costly litigation to recover the cash value of their hours.

Asymmetry

Graphite drawing presents a manicured bonsai beside two miniature figures facing a massive disembodied hand extending from the right.

Who Controls the Asset Block during Diligence?

The leverage between early contributors and founders changes when outside institutional investors enter the picture. Venture capital firms and private equity buyers conduct detailed reviews of corporate records and technical property before wiring funds. Diligence counsel examines contractor agreements, employment paperwork, tax records, and board consents to ensure the target entity holds clear, unencumbered ownership of its intellectual property.

Uncovering that core application code was authored by a developer who never signed an invention assignment halts a financing round. Institutional funds do not invest in companies built on unassigned intellectual property. At that point, the uncompensated contributor holds significant leverage over the founders.

The author can simply decline to execute retroactive assignments until prior equity expectations are formally ratified or bought out with cash.

Founders who offered verbal equity without executing contracts find themselves squeezed between investor conditions and contributor demands. The developer holds legal title to the software, while the company cannot close the financing without that title. This impasse frequently forces founders to dilute their personal stakes or pay substantial cash settlements to secure signed assignment documents before transaction deadlines expire.

baseline-term=’Remedy Target’
>Remainder Options
Structural Comparison of Contributor and Entity Positions in Unwritten Equity Disputes
Dispute Dimension Promised Technical Contributor Corporate Enterprise Entity
Initial Statutory Asset Title Holds direct individual copyright ownership over original code. Holds zero default statutory title without signed written assignments.
Legal Basis for Corporate Right Enforces personal property rights and potential quantum meruit. Claims implied non-exclusive operational license through compensation.
Venture Diligence Leverage Maintains absolute asset block by withholding retroactive signatures. Faces transaction failure or severe equity dilution to resolve title.
Primary Financial Remedy Demands market cash rates for historical development hours. Seeks specific performance or injunction to compel code delivery.
Retains original software code to fork or launch separate venture. Must rewrite entire core technical asset from scratch to clear cloud.
A giant hand holds a thin thread tethered to the apex of a monolithic wind turbine while three small figures stand at its base.

Cap Table Defects and Institutional Financing Hurdles

Ambiguities introduced by informal equity commitments complicate capitalization records. Early verbal promises of fixed percentage grants routinely ignore future financing dilution. Telling an initial developer they have ten percent of the company creates an immediate divide in expectations: the contributor envisions ten percent of the enterprise indefinitely, whereas founders assume ten percent of common stock issued at the start, dilutable by option pools and investor rounds.

Execution settles what conversation opened.

Remedying capitalization discrepancies requires documenting every past equity grant, option allocation, and verbal commitment. Unspecified grant terms trigger conflicting interpretations during financing rounds. If an early contributor produces contemporaneous emails, chat records, or draft term sheets pointing to an agreed equity figure, company counsel must disclose the dispute as an unallocated contingent liability.

Investors routinely condition funding on receiving clean, written releases of those claims. The board must then decide whether to grant dilutive equity or pay cash to clear the ownership cloud before the closing deadline passes.

Resolution

A leather suitcase sits atop a circular platform positioned near an empty wooden chair with indistinct figures standing along a horizon line.

Retroactive Invention Assignment and Equity Grant Ratification

Resolving encumbered intellectual property requires executing agreements that settle prior equity commitments and assign title at the same time. The standard approach pairs an omnibus proprietary information and invention assignment agreement with a formal stock purchase or option contract. These instruments must explicitly encompass prior contributions, stating that all intellectual property developed before the execution date is assigned to the company.

Retroactive assignments must use present-tense conveyance rather than promises of future action. Effective language specifies that the contributor hereby assigns, and agrees to assign in the future, all right, title, and interest in the intellectual property. Fresh consideration must pass to the contributor.

Consideration can take the form of formal corporate stock issuances subject to agreed vesting terms, immediate cash compensation, or a combination of cash and equity stock options.

Equity ratifications require standard corporate governance provisions. Documentation must establish precise share figures, purchase prices, vesting start dates, single or double-trigger change-of-control acceleration clauses, and tax elections under applicable statutes. Standardizing these terms eliminates historical ambiguity, extinguishes implied license claims, and converts informal builder arrangements into explicit corporate equity holdings.

A courtyard house drawing rests upon a ceramic plate where two tiny figures occupy the transition between landscape and interior space.

Clean Severance through IP Repurchase or Abandonment

When parties choose to separate without equity, formal severance agreements must define asset ownership. A complete separation agreement pairs mutual general releases with the resolution of accrued quantum meruit liabilities and a clear determination of who owns the technical work. If the entity plans to keep and run the software, the agreement requires a comprehensive assignment of all intellectual property, a waiver of moral rights, and covenants to assist in future patent or copyright filings.

The alternative path is complete technical abandonment. If the company refuses the contributor’s settlement terms, it can choose to scrap every asset that contributor touched. Abandonment entails deleting contributed repository files, removing encumbered code from production servers, and commissioning a clean-room rewrite performed by unencumbered technical employees.

Clean-room development protocols demand strict physical and operational segregation to prevent historical copyrighted code from contaminating the new architecture.

The departing developer receives a formal release permitting them to retain their original source code and build competing applications, provided no corporate trade secrets or proprietary business methodologies are infringed. This operational split returns both parties to their default statutory baselines. Executing standard assignment paperwork when code is first written avoids the equity loss and settlement costs of resolving ownership under diligence deadlines.

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.