Back to Blog
Nov 17, 2026Startup guide

Developer, Agency or Employee? How Technology Companies Should Structure IP Ownership

Every technology company makes a sourcing decision long before it makes a legal one. A founder needs a mobile app built, so she hires a freelancer she met through a referral. A Series A company needs to scale its engineering team quickly, so it signs with an agency in Nairobi. A growth-stage fintech brings its core platform in-house and starts hiring senior engineers in Lagos, Accra and Cape Town. Each of these decisions is driven by speed, cost and talent availability. Each also determines, often without anyone noticing, who will own the code.

The legal default differs depending on who writes the code and under what arrangement. A company that applies the same assumptions to an employee, a contractor and an agency will get at least two of them wrong. This article explains how ownership works under each model, where the traps sit in African and cross-border arrangements, and how to structure each relationship so that the company ends up with what it is paying for.

Why the engagement model matters

Copyright in software belongs, in the first instance, to its author. Most African copyright statutes then carve out particular relationships where ownership shifts to someone else, most commonly employment. The carve-outs are narrower than founders tend to assume, and they rarely extend to independent contractors or agencies.

The practical result is a sliding scale. Employees are the relationship where the company is most likely to own the work by default, though even there the default is not something to rely on. Freelancers are where the company is least likely to own the work without a written assignment. Agencies sit in between, usually assigning some things and licensing others, depending entirely on what their contract says.

Employees: the safest default, but not automatic

Many jurisdictions give employers ownership of works created by employees in the course of their employment. South Africa’s Copyright Act, for example, vests ownership of works made in the course of employment under a contract of service in the employer, absent agreement to the contrary. Nigeria’s Patents and Designs Act contains a similar principle for inventions made in the course of employment, subject to the employee’s entitlement to fair remuneration in certain circumstances.

For copyright in software, however, a company should not rely on the statute alone. There are three reasons.

First, the statutory rule only applies to work done “in the course of employment.” An engineer who builds a tool over a weekend on her own laptop, which the company later adopts, may argue that the work fell outside her duties. A product manager who writes code, although he was hired to manage a roadmap, can make a similar argument.

Second, classification is not always clear. As we have seen in disputes before the National Industrial Court of Nigeria, people engaged as “consultants” or on “trial arrangements” can be found to be employees in substance, and people described as employees can sometimes be found to be something else. If the ownership position depends on classification, it is only as strong as the classification.

Third, investors and acquirers do not want to run a statutory analysis on every engineer. They want to see a present assignment of IP in every employment contract.

What the employment contract should say:

  • A present assignment: the employee “hereby assigns” all intellectual property created in the course of, or in connection with, the employment. An agreement to assign in the future is weaker and depends on further action.
  • A broad scope that covers work outside working hours or on personal devices if it relates to the company’s business or uses its confidential information.
  • A waiver of moral rights to the extent the governing law permits.
  • An obligation to disclose inventions and cooperate with registrations, with a power of attorney if the employee is unavailable.
  • A schedule where the employee lists any pre-existing IP they are bringing in, so that it is either excluded deliberately or licensed to the company.

Freelancers and independent contractors: ownership only by agreement

When a company engages an independent developer, the developer owns what they write unless they assign it. That is the most common source of IP gaps we see in diligence on African startups.

The freelance relationship also tends to be informal. Engagement happens through a referral, a quick scope on WhatsApp and payment by bank transfer. There may be no written contract at all, or a contract that covers deliverables and fees but says nothing about IP. Global freelancing platforms sometimes include assignment provisions in their terms, but those terms vary, may not cover work delivered outside the platform, and are rarely checked by the company.

How to structure a freelance engagement:

  • Use a written agreement with a present assignment of all IP in the deliverables, signed before work starts.
  • Tie the final payment to delivery of source code and signed confirmation of assignment, rather than the other way round. Leverage disappears once the last invoice is paid.
  • Require the code to be committed to a repository the company controls, from the first day.
  • Address the developer’s pre-existing tools and libraries expressly. If they are used, the company needs a perpetual, irrevocable, transferable licence to them.
  • Be careful with classification. If a “freelancer” works full-time, takes direction like an employee and is integrated into the team, the arrangement may be employment in substance, which brings labour law obligations. The IP assignment should be drafted so that it holds whichever way the relationship is characterised.

Agencies: assignment of foreground, licence of background

Development agencies are a fixture of the African technology ecosystem, both local agencies in Lagos, Nairobi and Kigali, and offshore agencies in Eastern Europe and South Asia that serve African clients. Agencies bring speed and capacity, but their business model depends on reusing code across clients.

As a result, agency contracts typically distinguish between:

  • Foreground IP: code written specifically for the client, which is assigned on payment; and
  • Background IP: the agency’s frameworks, libraries, components and know-how, which the agency keeps and licenses to the client.

This is reasonable, but it creates real exposure if the licence is weak. A company should check whether the background licence is perpetual and irrevocable, whether it survives termination of the agency relationship and any fee dispute, whether it can be transferred on a sale of the company or assigned within the group, and whether it permits modification and sublicensing. An agency that can terminate the background licence for non-payment has, in practice, retained a veto over the company’s product.

Offshore agencies raise additional questions. Is the agency using subcontractors, and have the subcontractors assigned their rights to the agency so that the agency can pass them on? What law governs the contract, and would an assignment be recognised and enforceable in the agency’s home jurisdiction? Does the agency’s country impose any restrictions on exporting software or technology? These are not theoretical concerns for companies working with agencies in jurisdictions where enforcement is slow or contested.

Equity-for-code arrangements

Early-stage African startups frequently pay developers partly or wholly in equity. A senior engineer might build the first version in exchange for a percentage of the company, with no salary and no written employment contract.

These arrangements combine two separate questions that should be documented separately: the IP assignment and the equity grant. A developer who receives shares but never signs an assignment has become a shareholder and remains the owner of the code. If the relationship breaks down, the company is negotiating with a shareholder who also holds the rights in its core product. The equity should vest over time and the IP should be assigned at the start, not on vesting.

Cross-border hiring and employer-of-record models

Remote hiring across African markets has made employer-of-record arrangements common. Under these models, a third party legally employs the engineer in their home country and seconds them to the company. The engineer’s employment contract is with the employer of record, not with the company, so any statutory employer ownership rule favours the employer of record.

Companies using these models should confirm that the employer-of-record contract assigns all IP created by the seconded staff to the company, and that the engineer’s own contract with the employer of record contains a matching assignment. Without both links in the chain, the company may own nothing directly.

Matching the model to the stage

Each model has a place, and the right structure depends on what the company is building and where it is going.

  • Pre-seed and seed: Freelancers and small agencies are common. The priority is clean written assignments and code in company-controlled repositories, because the first institutional investor will check.
  • Series A: Core product work should be moving in-house or to agencies on terms that assign foreground IP and give strong, transferable licences to background IP. Founders should have signed confirmatory assignments.
  • Growth and pre-exit: The company should be able to show a complete chain of title for every material component, an IP register, and consistent employment templates across every jurisdiction where it hires.

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