A founder we spoke with a while back — building a fintech tool out of Lagos — paid a contract developer roughly ₦2.5 million over four months to build the core of his product. No written agreement beyond a WhatsApp conversation and a few bank transfers. When the relationship soured and he brought in a new developer, the original one refused to hand over the codebase. His argument: he was never actually asked to sign anything giving up ownership, so the code was still his.
He wasn't bluffing. Under Nigeria's Copyright Act 2022, copyright in a work made by an independent contractor initially vests in the author unless the contract says otherwise. Paying someone to build something is not the same as owning what they built. Ownership only transfers if there's a written agreement that says so. This founder had assumed the money did the legal work. It didn't.
This is the trap that catches most first-time founders across Nigeria and the wider region — not fraud, not bad developers, just a quiet assumption that a business relationship automatically comes with legal protection. It doesn't. And the documents that would have protected him aren't complicated or expensive. They're just usually signed after something has already gone wrong instead of before.
The founding-stage documents, and why they exist
There are five documents that matter before your business has made a single sale: a founder agreement, contractor agreements, employment agreements, NDAs, and IP assignment agreements. Each one solves a different failure mode, and it's worth understanding what actually breaks without them, because the paperwork itself is boring — the consequences aren't.
Founder agreements exist because co-founder relationships don't fail at the beginning, they fail in the middle. Everyone agrees on equity splits when the company is worth nothing. The disagreement shows up eighteen months later, when one founder has been grinding full-time and the other has drifted into a side hustle, and both still hold their original equity because nobody wrote down what happens if someone checks out. A founder agreement with a vesting schedule — equity earned over time rather than granted all at once — solves this cleanly. If someone leaves in year one, they walk away with a small slice, not the 40%, for example, they were promised on day one. This single clause prevents more Nigerian startup breakups than any other piece of paper we've seen.
Contractor agreements and employment agreements both exist to answer the same underlying question — who owns the work — but for different categories of people. This is where the misclassification problem shows up: many early-stage Nigerian founders bring people on as "contractors" to avoid the cost and complexity of formal employment, when the actual working relationship — fixed hours, exclusive availability, supervision — looks much more like employment. That distinction matters legally, and getting it wrong can create tax and labour exposure down the line. But even setting misclassification aside, the more immediate risk is the one our fintech founder hit: without an explicit written clause assigning IP to the company, a contractor in Nigeria retains ownership of what they build, by default. An employment contract doesn't automatically fix this either — the law's treatment of private-sector employee-created work is less settled than most founders assume. Since the Copyright Act doesn't explicitly address private-sector employees, courts may need to infer where ownership sits based on the purpose of employment and the nature of the work if there's no written agreement. That ambiguity is exactly why you don't want to be relying on inference when a dispute lands in court. You want it written down.
NDAs solve a narrower but still real problem: the moment you have to talk about your idea with someone who isn't yet inside the company — a potential developer, an advisor, an investor doing early diligence. Nigerian founders are often torn between two bad instincts here. Either they're paranoid and make everyone sign an NDA before a first coffee meeting, which mostly just signals inexperience and slows nothing down usefully, or they're completely open and share their entire technical roadmap with a stranger because "the idea isn't the hard part anyway." Both instincts miss the point. NDAs aren't there to protect an idea — ideas are cheap and rarely stolen wholesale. They're there to protect specific, sensitive information: your customer list, your unit economics, your actual technical architecture. Use them when you're about to share something concrete, not as a reflexive gate before every conversation.
IP assignment agreements are the document that ties the other four together, and they're the one founders skip most often because it feels redundant — surely the contractor agreement or employment contract already covers this? Sometimes it does, if it was drafted properly. But a huge number of Nigerian founding teams are working off templates pulled from the internet — often US-drafted, referencing "work made for hire" doctrine that doesn't map cleanly onto Nigerian copyright law. The safer approach, especially with contractors, is a standalone IP assignment clause or document that explicitly and irrevocably transfers ownership of anything created for the company, with no ambiguity about timing or scope. This is the document that would have saved our fintech founder his ₦2.5 million and four months.
What this actually costs you to get right
None of this requires a retainer with a big law firm in year one. A founder agreement, a contractor template with an IP clause built in, and a one-page NDA can be drafted once, reviewed by a lawyer for a modest fixed fee, and reused for every hire and every conversation going forward. The real cost isn't money. It's the discipline of doing it before you need it — because by the time you need it, as our fintech founder discovered, the leverage has already shifted to the other side of the table.
If there's one habit worth building into how you run the company from day one, it's this: nobody starts working, contracting, or advising until something is signed. Not because you distrust the people you're bringing in, but because clarity now is what keeps the relationship intact later, when the stakes are higher and memories of what was "obviously agreed" get conveniently fuzzy.
In Part 2 of this series, we move from the documents that protect the company internally to the contracts that govern its relationships with clients and vendors — including Master Service Agreements, Statements of Work and Professional Service Agreements.
