Assigning Pre Incorporation Software Rights In Early Stage Ventures
Software created before incorporation belongs exclusively to individual authors under statutory law until formal written instruments transfer title to the entity.
proprietary software schedule
Meaning
A proprietary software schedule is an appendix to an intellectual property assignment agreement that lists the specific pre-existing codebases, libraries, and tools a founder excludes from transfer to the newly formed corporate entity. Founders draft this inventory before closing an initial equity round to protect personal prior work from corporate ownership claims. The document defines the exact boundary between personal intellectual property and company property, and it stops applying once corporate counsel finishes reviewing and countersigning the exceptions during the founding documentation phase.
Boundary Definition
Clear exclusions prevent future ownership disputes during corporate audits and subsequent funding rounds. A founder lists every line of code written prior to incorporation that remains outside the corporate asset perimeter. Corporate counsel reviews these listings to verify that no company time or equipment produced the excluded items.
Unlisted repositories automatically transfer to the corporate entity under standard employment and founder invention assignment agreements.
Licensing Mechanism
Retained codebases require a perpetual, irrevocable, royalty-free license granted to the corporation for commercial exploitation. This grant allows the business to sell products built upon the excluded foundation without paying individual royalties to the creator. The license protects the company from future injunctions or copyright infringement claims brought by the original author.
Future investors inspect this licensing grant to confirm that the business holds uninterrupted rights to deploy its software stack.
Asset Cost
Maintaining personal ownership of prior work demands careful separation of development environments and personal hardware. Creators spend non-working hours on excluded codebases to prevent corporate co-mingling claims from arising. Legal review of the schedule consumes billable hours and delays closing timelines while ownership histories undergo verification.
Corporate entities absorb the operational risk of depending on licensed rather than owned foundational technology.