Valuing Early Code Contributions Before Formal Company Formation
Pre-formation code remains personal property until transferred to the corporation via explicit assignment in exchange for cash notes or credited vesting equity.

Source
When an engineer commits software to a private repository five months before filing articles of incorporation, that code remains personal property until a signed instrument conveys title. The creator holds copyright the instant code is fixed in a tangible medium, while the unformed entity holds no rights. Many founders assume joint work on a shared repository creates company property automatically, but the law recognizes no corporate entity prior to state filing, leaving intellectual property split among individual laptops.
When two collaborators build without a corporate structure, early work is rarely priced. One partner writes software while the other gathers customer interviews or prepares marketing outlines. The technical contributor supplies code, pull requests, and architecture, while the commercial partner gets working functionality.
Without a clear dollar value or equity split set on day one, the engineer often tracks spent hours internally, weighing late nights and bug fixes against vague promises of future fairness.
A contribution delivered without written terms accumulates as an unstated obligation that surfaces at the incorporation table.
If formal incorporation arrives four months later, the business requires a clean intellectual property assignment from every person who touched the repository. The engineer who wrote the initial prototype effectively controls corporate formation. Without their signature on a proprietary information and inventions assignment, no venture fund will wire capital and no bank will open an intellectual property line, leaving full leverage with the original author.

Hours
Valuing software written before incorporation usually starts a disagreement over measurement. The author remembers eighty-hour weeks, discarded prototypes, and technical hurdles, while commercial partners see only the file tree running on a server. Early discussions typically lean on two valuation methods, though both create distinct practical problems.

Why Market Rates Distort Early Equity Allocations?
Valuing early engineering hours at contractor market rates inflates past work compared to future work. An engineer billing one hundred twenty dollars an hour on the open market might log four hundred hours of prototype code, asserting fifty thousand dollars in value before incorporation. But that calculation assumes early software retains lasting utility.
In practice, prototype code changes quickly and is often rewritten within ninety days of onboarding users, making the original architecture obsolete.
The alternative approach assesses software purely by clean-slate replacement cost, using a third-party firm to estimate the minimum expenditure needed to rebuild the repository from functional specifications. This replacement value stays low, as a prototype that consumed four months of exploratory development might require just two weeks for a senior contractor to recreate once product specifications exist, creating sharp tension between the early collaborators.
- Replacement Cost measures the direct expenditure required to rebuild functional software from explicit technical specifications using outside contractors.
- Market Labor Value tracks accumulated developer hours multiplied by commercial market compensation, ignoring prototype obsolescence.
- Sunk Risk Parity prices early code by matching developer capital risk against commercial partner cash outlays or unpaid business development labor.
Early code delivers no guarantee of future effort. Rewarding initial software with large grants of unrestricted common stock gives the developer permanent ownership for past work alone. Should that contributor depart two months post-incorporation, the business remains tied to an inactive shareholder holding fifteen or twenty percent of equity.
This unearned equity deters follow-on investors and burdens the remaining team.

Table
Equity exists to secure future commitment, whereas pre-formation code represents past work. Separating historical software delivery from ongoing operational responsibilities requires distinct legal and financial mechanics. The transaction splits into two steps: purchasing title to the historical code, and granting founder stock tied to forward milestone execution.
| Settlement Structure | Immediate Cash Drain | Cap Table Dilution | IP Chain Security | Retention Incentive |
|---|---|---|---|---|
| Direct IP Purchase via Promissory Note | Deferred cardinal liability | Zero common stock dilution | Absolute legal assignment | Low post-formation retention |
| Unrestricted Common Stock Issuance | Zero immediate cash | Permanent non-recoverable equity | Conditional on agreement | Zero post-formation retention |
| Restricted Stock with Accelerated Vesting Credit | Zero immediate cash | Standard founder pool allocation | Complete assignment at grant | High four-year operational lock |
| Convertible Note for Sweat Capital | Zero immediate cash | Deferred conversion at financing | Secured upon note execution | Moderate interest alignment |
An author retains title until consideration changes hands. To transfer early software securely, the newly incorporated entity executes a technology transfer agreement paired with an explicit consideration package, whether nominal cash, a deferred corporate note, or founder equity structured under specific vesting terms.
Unassigned intellectual property stops outside institutional capital from closing.
Granting three to six months of retroactive vesting credit offers a practical middle ground. If an engineer spent half a year developing substantial pre-formation code, the company can issue standard four-year restricted stock with a four-year vesting schedule, crediting six months toward the initial one-year cliff. The contributor receives immediate partial tenure recognition, while the remaining thirty-six months preserve active alignment.
The legal grant requires an explicit Section 83(b) election filed with tax authorities within thirty days of stock acquisition to establish value before enterprise appreciation occurs.
The intellectual property assignment clause must define the transferred repository by cryptographic commit hash, explicitly conveying every copyright, patent claim, and trade secret to the corporation in exchange for the issued restricted shares.

Grant
Leaving terms unsaid creates friction later. When technical contributors hand over repositories without defined financial instruments, mismatched expectations grow over time. The contributor views the software as the foundation of the venture, while the business partner views it as a preliminary baseline requiring significant ongoing sales, marketing, and operational capital to monetize.
Both perspectives reflect functional reality, but failing to resolve the distinction early causes organizational gridlock.
When an early software contributor decides not to join the formal operating company as a full-time co-founder, buying out their code outright is cleaner than granting an ongoing equity stake. Granting fractional equity to non-operating early contributors establishes a permanent drain on corporate governance. A structured buyout utilizes a deferred promissory note payable upon the closing of a qualified equity financing round, paired with a non-exclusive or exclusive worldwide license assignment.
A team that resolves pre-incorporation property transfers early avoids costly ownership disputes during priced venture rounds.
Treating early code as an unpriced favor makes securing those assets far more expensive once commercial revenue appears. The company survives by transforming informal software development into documented corporate assets before the first outside dollar enters the capital structure. Past technical effort earns fair accounting or credited vesting, while future equity remains reserved exclusively for active operational commitment.