Back to Blog
Nov 17, 2026Startup guide

Your Product Is Built: Who Actually Owns the Intellectual Property?

Most founders only ask who owns their product when someone else asks first. The question usually arrives in a data room request list, phrased politely: “Please provide evidence of the Company’s ownership of all intellectual property used in the business, including assignments from all founders, employees and contractors.” It is at that moment, often weeks before a term sheet is meant to close, that a company discovers the gap between building a product and owning one.

The gap is wider than most teams expect. In our experience advising technology companies across Nigeria and the wider continent, the product that investors are valuing is frequently held, in strict legal terms, by a patchwork of people: a co-founder who wrote the first version before the company was incorporated, a freelance developer paid through a payments platform, an offshore agency that built the mobile app, and a former CTO who left on unfriendly terms. Each of them may have a claim, and none of those claims disappears simply because the company paid for the work or because everyone “understood” the product belonged to the business.

This article sets out where ownership problems actually come from, why they surface at the worst possible time, and what a company should do before a financing, acquisition or major partnership forces the issue.

Ownership is a document, not a feeling

The starting point under most African copyright regimes, including Nigeria’s Copyright Act 2022, is that the author of a work is its first owner. Software is protected as a literary work. That means the person who writes the code owns the copyright in it unless something displaces that default: a statutory rule that applies to the particular relationship, or a valid written assignment.

Two consequences follow, and both catch companies out.

First, payment is not ownership. A company that pays a developer to build its platform has bought the developer’s time and, at best, an implied licence to use what was delivered. It has not necessarily bought the copyright. An implied licence may be enough to keep the lights on, but it is not enough for an investor who needs to know that the company can sell, license, pledge or defend the code without anyone else’s permission.

Second, assignments of copyright must be in writing and signed by or on behalf of the person transferring the rights. A WhatsApp message saying “the code is yours” or an invoice marked “full ownership transferred” may not meet that standard. The safer view, and the one sophisticated investors will apply, is that if there is no signed assignment, the company should assume it does not own the work.

The five places ownership usually leaks

1. Pre-incorporation work by founders: Many Nigerian and pan-African startups begin as side projects. The founders build a prototype in the evenings, test it with friends, then incorporate a company, sometimes a Delaware parent with a Nigerian operating subsidiary, once traction appears. The prototype, and often much of the code that still runs in production, was written before the company existed. Unless each founder has assigned that pre-existing work to the company, it remains theirs personally. This becomes acute when a founder leaves, because the departing founder may hold rights in the very code the company depends on.

2. Freelancers and contractors: Freelancers engaged directly or through global marketplaces are the most common source of ownership gaps. Some platform terms of service include IP assignment language between client and freelancer, but the scope varies and the company rarely checks. Where a contractor was engaged informally, there is usually nothing in writing at all.

3. Development agencies: Agencies, whether in Lagos, Nairobi, Kyiv or Bangalore, typically build on their own pre-existing frameworks, libraries and templates. Their standard contracts often assign only the “deliverables” while keeping the underlying toolkit, which is licensed to the client. That is commercially reasonable, but it means part of the product’s foundation is licensed, not owned, and the licence terms matter: Is it perpetual? Transferable on a sale of the company? Can it be terminated if fees are disputed?

4. Employees: Founders often assume that anything an employee creates belongs to the company automatically. The position is less tidy than that. Employer ownership of works made in the course of employment depends on the particular statute and the facts, including whether the work was actually made in the course of the employee’s duties. A well-drafted employment contract with a present assignment of intellectual property removes the argument. A poorly drafted one, or one copied from a services template, can create it.

5. The infrastructure around the code: Ownership questions are not limited to source code. Domain names registered in a founder’s personal name, app store developer accounts opened with a founder’s email, cloud accounts paid on a personal card, social media handles and trademarks filed by an early employee are all assets the company may believe it owns but cannot prove it controls.

Why it surfaces at the worst moment

Ownership gaps are rarely discovered through litigation. They are discovered through diligence, and diligence happens at moments when the company has the least leverage to fix them.

When an investor or acquirer identifies a gap, the company must go back to the person who holds the rights and ask them to sign. If that person is a current employee or a friendly former contractor, this is an administrative exercise. If it is a departed co-founder, an agency with an unpaid invoice, or a former CTO who feels under-compensated, the request becomes a negotiation, and the counterparty now knows that a financing depends on their signature.

We have seen confirmatory assignments that cost a company a fraction of the round in cash or equity simply because the request was made in the middle of a transaction rather than six months earlier. We have also seen investors respond to unresolved gaps by insisting on specific indemnities from founders, escrow arrangements, or conditions precedent that delay closing.

Cross-border structures add a second layer

For African technology companies with offshore holding structures, ownership has a geographic dimension. Investors in a Delaware or Mauritius parent will usually expect the parent to own the core intellectual property, or at least to control it through an intra-group licence. If the code was written by Nigerian employees of a Nigerian subsidiary, the IP may sit with the subsidiary, and moving it upstream is not merely a paperwork exercise.

A transfer or licence from a Nigerian entity to a foreign parent, or from a foreign parent back into Nigeria, can engage the National Office for Technology Acquisition and Promotion (NOTAP) regime, which requires registration of technology transfer agreements and is relevant to whether royalty and licence fee payments can be remitted offshore through official channels. It also engages transfer pricing rules, because intra-group IP arrangements must reflect arm’s length terms, and withholding tax on royalties. Structuring the IP position early, and documenting it consistently with the tax position, avoids a later choice between an expensive restructuring and an uncomfortable disclosure to investors.

Newer questions: open source and AI-generated code

Two developments are changing what “ownership” means in practice.

The first is open source. Almost every modern product incorporates open source components. That is not a problem in itself, but some licences, particularly copyleft licences such as the GPL family, can require a company to make its own source code available if it distributes software that incorporates the licensed component in particular ways. Investors increasingly ask for a software bill of materials or an open source scan, and a company that cannot produce one will face questions.

The second is AI-assisted development. Developers now use coding assistants routinely. Copyright law across most jurisdictions is built around human authorship, and the extent to which machine-generated output attracts protection is unsettled. For most companies the practical risk today is not that their code is unprotected, but that they cannot say which parts were generated, under what tool terms, and whether those terms allow commercial use. Companies should have a policy on approved tools and keep a record of their use for core components.

What to do before anyone asks

The fix is not complicated, but it requires discipline and should be done before a transaction starts.

  • Build an IP register: List the core components of the product, who wrote them, when, and under what arrangement. Include domains, accounts, trademarks and key third-party licences.
  • Paper the founders: Every founder should sign a confirmatory assignment of all IP they created relating to the business, including work done before incorporation.
  • Paper the contractors and agencies: Obtain signed assignments from every contractor whose work remains in the product. For agencies, confirm the scope of the assignment and the terms of any licence to their background tools, including whether it survives a change of control.
  • Fix the employment template: Use a present assignment (“hereby assigns”), cover all IP created in the course of or in connection with employment, include a waiver of moral rights where the law allows, and require cooperation with future filings.
  • Align the group structure: Decide which entity should own the IP, document intra-group licences or transfers, and address NOTAP registration and tax treatment.
  • Run an open source review: Identify copyleft exposure and address it before an investor’s technical diligence does.
  • Move the infrastructure: Transfer domains, app store accounts, cloud accounts and trademarks into the company’s name.

Add a Comment

Your email address will not be published.

We'd love to help you!

Let us know the needs of your business, and we will pinpoint the best-suited solution to fulfill them.

Services


Copyright 2026 Vazi Legal Business Attorneys. All Rights Reserved. | Privacy Policy

LinkedInXInstagram