Most Nigerian service businesses believe they only need one document with a client: a contract. Singular. One agreement that covers everything — what's being built, what it costs, when it's due, what happens if something goes wrong. It feels efficient. Why sign four documents when one will do?
In Part 1, we looked at the documents that protect a business at the founding stage — from founder agreements and IP assignments to contractor agreements and NDAs. Once the business starts taking on clients, however, the paperwork changes. The question is no longer simply who owns what; it becomes how the commercial relationship itself is structured.
That belief is wrong for any business that expects to work with the same client more than once, and it's wrong in a specific, expensive way. Here's the actual problem: a single all-in-one contract forces you to renegotiate your entire relationship — payment terms, liability, confidentiality, IP ownership — every single time you take on new work with a returning client. We've watched agencies burn two weeks re-drafting boilerplate for a client they've already worked with three times, because nobody separated "the rules of how we work together" from "what we're building this time."
The fix is splitting the relationship into layers, and it's one of the more useful shifts a growing Nigerian service business — an agency, a consultancy, a dev shop — can make to how it operates.
The first layer is the Master Service Agreement. This is where the boring, recurring terms live: payment timelines, confidentiality obligations, who owns what gets built, how disputes get handled, what happens if either side wants out. You negotiate this once, at the start of a client relationship, and it governs everything that comes after. It's not glamorous, but it's the document that saves you from having a lawyer argue about payment terms every time a client wants a second project.
The second layer is the Statement of Work, and this is where most of the actual friction in Nigerian client work lives. An SOW sits under the MSA and covers one specific engagement — the deliverables, the timeline, the price, the milestones. If the MSA is the constitution, the SOW is the specific law passed under it. The reason this split matters isn't legal elegance — it's that scope disputes are the single most common source of unpaid invoices and soured client relationships in this industry, and a proper SOW is what actually prevents them. When "build us a website" isn't broken into phases with defined deliverables and dates, you end up in the position every Nigerian developer knows too well: the client keeps adding "small" requests, the project keeps expanding, and there's no document anyone can point to that says where the original scope actually ended.
If you only ever do one-off work for a client — a single project, no expectation of repeat business — you don't need the MSA/SOW split at all. That's where a Professional Service Agreement does the job on its own: parties, term, scope, and payment amount, all in one document, built for a relationship that isn't going to recur. Using an MSA for a client you'll likely never work with again is over-engineering. Using a single PSA for a client you work with six times a year is under-engineering. Knowing which situation you're in is the actual skill here, not memorizing which document is "correct."
The fourth document in this stage sits slightly apart from the other three: the advisor agreement. This becomes relevant the moment a startup founder brings someone on to guide the business — a more experienced operator, a technical mentor, someone with industry connections — usually in exchange for a small equity stake rather than cash. The mistake founders make here isn't skipping the agreement entirely; it's being vague about what the advisor is actually expected to do in exchange for equity they didn't have to earn through sweat or capital. An advisor agreement that just says "advises the company" without defining scope — how many hours, what kind of input, for how long — sets up a dispute eighteen months later when the founder feels the advisor vanished, and the advisor feels they're still owed the full grant. The same logic that governs founder vesting should govern advisor equity: it should vest over time based on actual involvement, not get granted upfront on the assumption of future help that may or may not materialize.
One more thing worth building into any of these documents, and something Nigerian businesses under-use: a dispute resolution clause that points to mediation or arbitration before court. Nigeria's court system is not fast, and litigation over a contract dispute can drag well beyond the point where either party still cares about winning. The Arbitration and Mediation Act 2023 formally recognizes mediation as a valid, enforceable dispute resolution route, and a simple clause — mediate first, arbitrate if that fails, litigate only as a last resort — costs nothing to include and can save both sides months if things go wrong. While the Act supports this route, whether it's faster or cheaper in a specific dispute depends on the arbitrator, the dispute's complexity, and both parties' willingness to cooperate — it is not a guarantee of a fast outcome.
None of this requires treating every client relationship like a legal minefield. It requires knowing which of these documents your specific relationship calls for, and — more importantly — putting the recurring terms and the project-specific terms in separate places, so the second project with a client takes an afternoon to set up instead of two weeks.
In Part 3, we move into an area that becomes increasingly important as a business grows: customer data. We look at the Nigeria Data Protection Act 2023, Data Processing Agreements, third-party processors and the compliance obligations that many Nigerian businesses mistake for a purely European or American concern.
