Back to Blog
Nov 17, 2026Startup guide

Buying or Licensing Technology: The Legal Due Diligence Questions Businesses Should Ask

African businesses are buying more technology than ever. Banks are licensing core banking and fraud detection systems. Retailers are adopting enterprise resource planning platforms. Logistics companies are integrating telematics and route optimisation software. Insurers are licensing underwriting engines, and an increasing number of companies are acquiring smaller technology businesses outright to accelerate their own digital strategies.

In most of these transactions, commercial and technical diligence is thorough. The business team tests functionality, the IT team assesses integration and security, and finance negotiates price. Legal diligence, by contrast, is often reduced to a review of the vendor’s standard terms in the final week before signing. That is a mistake, because the most consequential risks in a technology transaction are usually legal: whether the vendor actually has the rights it is granting, what happens when the relationship ends, and whether the payment structure will work under local regulatory rules.

This article sets out the questions a business should ask before buying or licensing technology, with particular attention to issues that arise in Nigeria and other African markets.

Start with the commercial trigger

Legal diligence should be proportionate to what the technology will do. A business licensing a productivity tool for a single team can accept standard terms with minor negotiation. A bank licensing the system that will hold its customer ledger, or a company acquiring the platform that will become its core product, needs a different level of scrutiny.

The questions below scale with that risk. The higher the dependency, the more each answer matters.

1. Does the vendor actually own what it is licensing?

This is the foundational question and the one most often assumed rather than checked. A vendor can only grant rights it has. If the vendor’s own product was built by contractors who never assigned their rights, or incorporates third-party components on terms that do not permit sublicensing, the licence the business receives may be incomplete.

For a licence, the practical protection is contractual: a warranty that the vendor owns or has the right to license the technology, an indemnity against third-party infringement claims, and the vendor’s obligation to defend those claims. For an acquisition, the buyer should go further and review the target’s chain of title: founder assignments, contractor agreements, agency contracts and employment templates.

2. What open source is in the product, and on what terms?

Most commercial software incorporates open source components. Permissive licences generally pose limited risk. Copyleft licences, such as the GPL family, can impose obligations to release source code if the software is distributed in certain ways, and some network-use licences extend similar obligations to software accessed over the internet.

A buyer should ask for a list of open source components and their licences, and for an acquisition, an independent scan. The question is not whether open source is present, because it almost always is, but whether its use is consistent with how the buyer intends to deploy and commercialise the technology.

3. What data does the technology touch, and who controls it?

Any system that processes personal data brings data protection obligations. Under the Nigeria Data Protection Act 2023 and the General Application and Implementation Directive issued by the Nigeria Data Protection Commission in 2025, the business deploying the technology will usually be the data controller, and the vendor will be a processor. That relationship must be documented, and the business remains responsible for the vendor’s compliance.

Key questions include: Where will the data be stored and processed? Will it leave Nigeria, and if so, on what legal basis? Will the vendor use customer data to improve its own products or train models? What security standards does the vendor meet, and has it suffered any breaches? Can the business audit the vendor, or at least rely on independent certifications?

The same questions apply in Kenya, South Africa, Ghana and other markets with data protection statutes, each with its own rules on processors and cross-border transfers.

4. Can the business get its data out?

Exit is the most under-negotiated part of technology contracts. A business should know before signing how it will retrieve its data at the end of the relationship, in what format, how long the vendor will retain it, and whether transition assistance is available. A system that holds critical data in a proprietary format with no export obligation creates dependency that the vendor can price accordingly at renewal.

5. What happens if the vendor fails?

For business-critical software, the business should consider what happens if the vendor becomes insolvent, is acquired by a competitor, or simply stops supporting the product. Source code escrow, under which a copy of the source code is deposited with a third party and released on defined trigger events, is one answer. Its value depends on the quality of the deposit and whether the business could realistically maintain the code itself, so escrow should be paired with verification rights.

6. Does the licence survive the business’s own changes?

Many licences restrict assignment and treat a change of control of the licensee as a termination event. A business that is planning a reorganisation, a sale, or the transfer of the system to a group entity should check whether the licence permits it. Otherwise, the vendor gains leverage in the business’s own corporate transaction.

7. Will the payment structure work under local rules?

This is where Nigerian and other African transactions differ most from those in other markets.

In Nigeria, agreements for the transfer of foreign technology, including software licences, technical services and management services from foreign providers, are subject to registration with the National Office for Technology Acquisition and Promotion (NOTAP). Registration matters commercially because it supports the remittance of licence fees and royalties offshore through official foreign exchange channels, and NOTAP reviews whether the fees and terms are reasonable. A business licensing foreign software should factor in the time required for registration and the possibility that NOTAP will require changes to fee levels or terms.

Payments to foreign licensors may also be subject to withholding tax on royalties or fees, and in some cases VAT. The contract should allocate those costs clearly, including whether fees are quoted gross or net of withholding.

Currency is the other practical issue. A licence priced in US dollars, with payment obligations that do not account for foreign exchange availability or volatility, can create real strain for a Nigerian licensee. The business should negotiate payment mechanics, including currency, timing and the consequence of delays caused by foreign exchange constraints, rather than accepting a vendor’s standard terms.

8. Are there sector-specific approvals?

Regulated businesses face additional requirements. Banks and payment service providers in Nigeria are subject to Central Bank of Nigeria expectations on outsourcing, cybersecurity and business continuity, which may require specific contractual terms, notification, or the ability for the regulator to access information held by the vendor. Insurers, pension fund administrators and capital market operators face similar expectations from their own regulators. Government and certain public-sector data may also be subject to local hosting requirements under National Information Technology Development Agency (NITDA) guidelines.

A business should identify these requirements before negotiating, because some of them will need to be written into the contract.

9. What are the export control and sanctions issues?

Technology originating in the United States or Europe may be subject to export controls, particularly where it involves encryption or advanced computing. Most commercial software is exportable without a licence, but the business should confirm this, and should check that the vendor is not subject to sanctions that could interrupt support or payments.

10. What protection does the business have if things go wrong?

Finally, the business should look closely at liability caps, exclusions and service levels. Vendor terms commonly cap liability at fees paid over a short period and exclude data loss and consequential damages. For critical systems, that allocation may be inappropriate. Service credits should be meaningful, and the business should have a right to terminate for persistent failure.

Licensing versus acquiring: different questions, same discipline

Where a business is acquiring a technology company rather than licensing a product, the questions above remain relevant, but the buyer is inheriting the target’s entire history. In addition to the product questions, the buyer will need to review the target’s employment and contractor arrangements, regulatory licences, customer contracts and their change of control provisions, tax position and any disputes. We address that broader exercise in a separate piece on due diligence for acquiring a technology business.

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