Untangling Covert Debt When Informal Technical Contributions Demand Cap Table Ownership

Informal technical contributions create unpriced equity claims that founders resolve by converting historical labor into deferred debt or advisory grants.

6 min

Floor

A repository commit timestamped at two in the morning sits beside twenty unbilled weekend pull requests. Over five months of sporadic evenings, the technical contributor built the authentication flow, connected the payment processor, and stabilized the core database schema. No contract was signed, no invoice submitted, and no corporate entity existed when the work began.

The founder viewed the effort as help between friends, while the engineer saw every milestone as equity earned in informal escrow. When an institutional term sheet arrives, the contributor rejects a standard contractor settlement and asks for fifteen percent of the common stock. The friendship ends on the spot, replaced by a dispute over corporate property.

Informal technical labor creates covert debt whenever social goodwill disguises deferred compensation. Early on, founders welcome off-the-books technical help because cash is tight and agency rates are out of reach. Friends or former colleagues review architecture or write code during free evenings.

Without an upfront price, founders assume the help is a favor given without expecting direct returns, while contributors often expect equity once the company raises money. Silence around compensation lets both assumptions coexist until a funding round forces the issue.

Unstated expectations around compensation turn informal technical help into a legal encumbrance as soon as outside investors demand clean equity title.

The resulting dispute exposes a rift in how each side tracks value. The founder remembers meals bought, introductions made, and casual chats about collaborating. The engineer points to Git logs, architecture diagrams, and timestamps of late-night deployments pushed around another job’s schedule.

To the founder, the equity demand feels like an opportunistic hold-up; to the contributor, an offer of back-pay dismisses the early risk they absorbed.

He carried the infrastructure alone while the company was still an unverified premise.

The drawing shows a school desk and chair tightly bound by a massive complex knot of thick rope, with small solitary figures observing from the distance.

Knot

Unspoken assumptions tend to harden into conflict in predictable stages. When technical work happens without a contract, both sides often dodge hard negotiations to preserve goodwill. Setting numbers early can feel prematurely transactional when a project carries little commercial value.

But delaying the conversation creates an unwritten record where each party tracks value in entirely different terms.

Friction sharpens as the venture reaches milestones like venture funding, accelerator acceptance, or a major commercial contract. These moments demand clean intellectual property ownership, exposing an unformalized technical foundation. Disputes usually unfold across three distinct points:

  • Unacknowledged Reliance builds during early development. The founder treats technical work as casual help, while the engineer spends nights fixing critical bugs under the assumption that co-founder status will follow.
  • Valuation Collision surfaces at incorporation or financing, when the founder offers a one percent advisory grant and the contributor demands twenty percent based on hours worked and core code written.
  • Title Impasse brings governance to a halt. The contributor refuses to sign intellectual property assignment agreements without a real cap table stake, leaving the code repository legally encumbered.

A contributor who has not signed an assignment agreement retains copyright over their code, regardless of whether the enterprise is incorporated.

This impasse stems directly from copyright law. Without a signed assignment agreement or a valid work-for-hire contract, copyright remains with the person who wrote the code. Incorporating a company does not automatically transfer ownership of existing software.

Even if the founder paid for servers or outlined product specs, the developer owns their original contributions. A startup seeking institutional capital faces serious risk when core software is held by an uncompensated developer.

Does informal technical input create co-founder rights, or does it simply represent an unpaid balance settled in cash?

A handbell rests atop a plush square cushion as small figures stand at the base observing the central signaling instrument.

Scale

Resolving past technical claims requires separating founder equity from vendor compensation. Cap tables exist to incentivize future commitment under multi-year vesting schedules. Past labor is completed work.

Issuing unvested common stock to an informal contributor who will not join full-time bloats the cap table with inactive shareholders who add no ongoing value.

Evaluation Criteria for Unformalized Technical Labor Settlements
Resolution Pathway Structural Instrument Equity Dilution Cash Expenditure Intellectual Property Cleared
Advisory Settlement Restricted Stock Units Minimal (0.25% to 1.5%) None Immediate via assignment covenants
Retroactive Contractor Buyout Cash plus promissory note Zero percent Market hourly equivalent Immediate upon final disbursement
Co-Founder Induction Four-year vesting common stock Substantial (10% to 25%) Zero cash outlay Secured via founder agreement
Synthetic Royalties Gross revenue percentage cap Zero percent Deferred cash from sales Transferred upon execution

A typical scenario illustrates the arithmetic. An engineer builds a prototype over five months, logging three hundred hours before the company raises half a million dollars. The engineer demands ten percent in fully vested equity.

The founder offers five thousand dollars in cash, arguing the work was an informal favor. Neither position aligns with market standards.

The code works, the infrastructure runs, and the business relies on it daily.

Three hundred hours of senior engineering work carries a market value near forty-five thousand dollars. Handing ten percent of non-dilutable equity to an engineer leaving before launch prompts incoming investors to demand recapitalization or slash the valuation. The unearned equity burden leaves the company effectively uninvestable.

Past technical labor is best settled in cash or vested options, preserving common equity for those driving future growth.

Treating informal sweat equity as automatic co-founder parity frequently derails seed diligence.

Two miniature figures stand before a graphite drawing of a rocking chair assembled from distinct jigsaw puzzle segments that imply a precarious structural unity.

Wedge

Untangling early claims requires conversion structures that decouple past hours from ongoing governance. Institutional investors expect four-year vesting with a one-year cliff on equity grants. If the contributor cannot commit to full-time work, awarding co-founder equity breaks standard corporate governance.

Negotiations then pivot from personal gratitude to structured settlement options.

  1. Deferred Cash Settlement converts estimated engineering hours into a promissory note, payable when institutional financing closes or cash flow turns positive.
  2. Vested Advisory Grants provide a small equity grant, usually between a half percent and one and a half percent, tied to a formal advisory agreement outlining future guidance.
  3. Clean IP Assignment Covenants condition all payouts or equity grants on complete intellectual property assignment and a waiver of moral rights.

Progress happens when the founder acknowledges the financial debt without diluting control. Pricing past contributions at standard contractor rates recognizes the value delivered while protecting cap table discipline.

Completed work has a fixed past value, while equity reflects a stake in future operational commitment.

Separating past work from future governance protects the enterprise.

Three small silhouettes stand at the base of a tiered pedestal supporting a single wooden stool that signifies an isolated position of central ownership.

Release

Formal documentation must resolve all competing ownership claims. Verbal agreements leave the business vulnerable to fresh litigation whenever its valuation grows. The enterprise enters into a settlement and mutual release agreement that details past work and cancels prior informal arrangements.

The contributor signs this alongside a standard Proprietary Information and Inventions Assignment agreement.

The agreement requires valid consideration to remain enforceable. If stock options or deferred notes are used, the release must state that they satisfy all past claims concerning software, architecture, and company equity. Including a waiver under applicable civil code rules prevents future revenue growth or an IPO from reopening old equity demands.

Clean legal title secures stability. The code repository moves fully under company ownership, server access is updated, and the cap table reflects clear vesting schedules for all remaining roles.

A signed release replaces informal promises with explicit terms, clearing legacy liabilities before institutional investors step in.

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.