Can a founder retain ownership of software built before incorporation?

A founder may own software created before a company was incorporated, but ownership does not automatically transfer to the company merely because the founder later becomes its director or shareholder. A startup can use such software through a valid assignment or licence, yet the distinction matters for investment, product development and any future sale. The correct starting point is to identify who wrote the original code, under what contracts, and which copyright or other rights existed before incorporation.

In Pakistan, computer programmes fall within the relevant literary-work framework of the Copyright Ordinance, 1962. Initial ownership and assignments require attention to statutory exceptions and actual agreements. A company cannot own assets before it legally exists in the ordinary way, and a founder's intention that the company will eventually use the code should be translated into documentation once the entity is formed.

Trace how the software was created

Begin with the first repository, development history, contributor list and relevant design documents. Determine whether the founder wrote all important parts independently, commissioned freelancers, collaborated with university researchers or reused code from a former employer. The person presenting the startup may not possess exclusive title to every component.

Preserve original timestamps, commit histories, invoices and contracts. If several founders jointly contributed, their respective rights must be considered; merely naming one person as 'technical founder' is not proof of exclusive ownership. Open-source libraries and commercial dependencies also require separate licence analysis.

Copyright ownership before incorporation

Where a founder independently created original software without conflicting employment or commissioning obligations, the founder may hold relevant copyright in that work. The rights should be assessed under the Copyright Ordinance, including the nature of the work, its author and any statutory first-ownership exception.

A company incorporated later does not necessarily become copyright owner by using the same product name or receiving the source files. The business should distinguish an express transfer of ownership from a non-exclusive permission to use the software. Both may permit development, but their consequences during investment or termination of the founder's role are quite different.

Assignment versus licence to the company

An assignment transfers identified copyright rights according to its terms and applicable law. A licence may permit defined use while ownership remains with the founder. Founders should decide which structure suits their business model and make it explicit in a signed instrument identifying the software, permitted uses, modification rights and consideration where relevant.

A licence should address duration, territory, sublicensing, source-code access, termination and changes of control. An investor will generally examine whether a founder could revoke permission at a critical moment. Where the software is the startup's core asset, a broad and durable rights structure is often necessary to support the company's valuation.

Earlier employment and consultancy obligations

A founder may have written parts of the code while employed by another business or under a consultancy arrangement. The previous employer or client may claim rights under law or contract. The founder should not assume that developing the product at night using personal equipment always resolves the issue, nor that a former employer owns every unrelated personal project.

Examine the old contract, assigned duties, resources used, confidentiality terms and overlap with the employer's protected business. Where third-party rights are disputed, obtain independent advice before transferring the code to a new startup or representing it as free of encumbrances.

Independent contractors and co-developers

A freelancer may write a mobile interface, backend module or machine-learning component before incorporation. The company needs reliable documents dealing with ownership and the scope of any licence. Payment of a development invoice should not be treated as universal proof that all software rights have vested in the company.

Where the original arrangement was with the founder personally, consider whether the later company has received a valid assignment or novation of rights. A missing link in the chain can become a serious issue when an investor requests warranties over ownership of the entire platform.

Open-source code and third-party components

Use of open-source code is often lawful, but the company must understand the relevant licences. Some require notices or particular treatment of modifications or distribution; others are more permissive. A public repository is not necessarily free of all conditions. The company should preserve a software bill of materials and material third-party licences.

A founder cannot assign exclusive ownership of code that belongs to third parties simply by including it within a repository labelled proprietary. The assignment may cover the founder's original contributions while licensed dependencies remain governed by their own terms. Technical and legal records should reflect that distinction.

Investor expectations and due diligence

A venture investor commonly expects the startup to own or securely control its core technology. If the founder personally owns essential software and the company holds a revocable licence, the investor may seek a transfer, stronger licence or additional safeguards as a condition of funding. A substantial share valuation may be unsustainable if the company cannot operate without the founder's permission.

The board should maintain an intellectual-property schedule identifying software, domains, trademarks, patents, licences and assignments. Any restrictions affecting transfer or change of control must be disclosed. A founder should not silently retain personal rights while signing warranties that all company technology is owned outright.

What happens if the founder leaves?

The distinction becomes acute when a founder resigns as CTO or sells shares. Employment, directorship, share ownership and software copyright are separate legal positions. A company that has no reliable licence may face operational risk even if the departing founder retains only a minority shareholding.

A good agreement should state whether the company may continue using, modifying, licensing and selling the software after the founder leaves. It should also address return of repositories, passwords and confidential business records. An IP dispute must not be resolved by unauthorised disabling of production systems.

Tax and valuation questions

Transferring software to a company may have accounting and tax consequences. The parties should examine the consideration, valuation, capital or related-party treatment and any applicable registration or reporting obligations. Assigning valuable software in exchange for shares differs from granting a royalty-bearing licence.

The arrangement should be commercially coherent. Artificially labelling a large asset transfer as a nominal transaction can create later tax, valuation and shareholder disputes. The founder and company should obtain suitable professional advice where the technology has significant value.

Practical example of a pre-incorporation SaaS

Suppose two developers create a subscription platform before establishing a private company. One owns the original backend code, the other supplied design work and both used third-party libraries. After incorporation, the startup begins charging customers but never obtains written contributor assignments. An investor later requests evidence that the company can transfer all necessary rights on an acquisition.

The founders may need to document the contributions, obtain valid transfers or licences and disclose dependencies before investment. The company's possession of the repository is not a substitute for a reliable chain of title. The issue should be corrected before relationships deteriorate.

Security, access and operational continuity

The company's own accounts should control production infrastructure, domain registrations and repositories wherever possible. Personal ownership of a founder's laptop or cloud subscription should not expose client data to loss when a dispute arises. Access permissions, backup procedures and administrative credentials are vital.

Ownership of copyright and control of systems are distinct but related concerns. A startup may possess strong licence rights yet still be vulnerable because only one founder knows the cloud password. Proper corporate governance should cover both legal title and practical operational resilience.

Opinion and recommended course

A founder can retain ownership of software created before incorporation, but a company intending to exploit it should have legally effective rights. Determine the genuine contributors and any prior employment claims, identify dependencies and choose a documented assignment or durable licence appropriate to the intended investment and operating model.

Before fundraising, assemble source records, contributor agreements, licences and an IP schedule. Reconcile the company's warranties with its actual rights and ensure that departure or change of control will not interrupt lawful use of essential technology. Investors should insist on a defensible chain of title, not merely the founder's statement that the code is 'ours'.

Principal authorities for verification: Copyright Ordinance, 1962, particularly first ownership and assignments; Contract Act, 1872; Companies Act, 2017 for capital and related-party matters; relevant employment and software development agreements; third-party software licences.