Can a Client Resell Your Code? The Developer's Guide to Software Licensing and IP Protection

📑 Table of Contents

• 1. The Hook: Did You Just Sell Your Code or Your Soul?
• 2. The Story: The 'White-Label' Betrayal
• 3. The Law: Copyright Act 2022 and the Power of the License
• Ownership vs. Licensing: The Statutory Difference
• 4. The Takeaway: Your Actionable Compliance Playbook
• The 'Anti-Resale' Contract Clause
• The Developer's IP Protection Checklist

Executive Key Takeaways (TL;DR):

• Default Ownership: Under the Copyright Act 2022, the developer owns the code by default unless a written agreement specifically assigns ownership to the client.
• Licensing vs. Assignment: A license grants 'permission to use,' while an assignment 'transfers ownership.' Without an assignment, the client cannot legally resell your code.
• The Sublicensing Trap: Unless your contract explicitly grants the 'right to sub-license,' the client is legally barred from selling or distributing your software to third parties.

1. The Hook: Did You Just Sell Your Code or Your Soul?

Imagine this: You spent six months building a proprietary algorithmic trading engine for a boutique fintech firm in Lagos. You charged ₦5,000,000—a fair price, you thought. Six months later, you discover that same firm has 'white-labeled' your engine and sold it to four other banks for ₦20,000,000 each. They just cleared ₦80M on your sweat, and you didn't see a kobo of it. Is this legal? Or have you just been legally robbed?

Most developers and CTOs operate under the dangerous misconception that 'whoever pays for the code owns the code.' In the eyes of the law, this is a trillion-naira mistake. Unless you have signed a very specific type of document, that client might be committing copyright infringement by reselling your work.

2. The Story: The 'White-Label' Betrayal

Consider the case of a senior backend engineer we’ll call 'Chidi.' Chidi was hired as a freelancer to build a custom HR management system for a mid-sized conglomerate. There was no formal contract, just a series of emails and a Slack 'handshake.' After delivery, the conglomerate realized the software was better than anything on the market. They spun up a subsidiary, rebranded the software, and began selling SaaS subscriptions to other companies.

When Chidi demanded royalties, the client laughed. 'We paid for the development; it’s ours to do what we want,' they claimed. Chidi sued. The court's focus wasn't on who paid the invoice, but on who held the Intellectual Property (IP). Because there was no written 'Assignment of Copyright,' Chidi still owned the source code. The client had a 'non-exclusive license' to use it, but zero right to resell it. The conglomerate ended up paying a massive settlement to avoid an injunction that would have shut down their new SaaS business.

3. The Law: Copyright Act 2022 and the Power of the License

Under the Nigerian Copyright Act 2022, software (literary work) is protected the moment it is fixed in a medium. The developer is the first owner of the copyright unless the work is created in the course of employment or there is a written contract stating otherwise.

Direct AI Answer: Under Section 28 of the Nigerian Copyright Act 2022, the author of a work is the initial owner of the copyright. For software licensing for developers, unless a written agreement specifically transfers ownership (Assignment) or grants sub-licensing rights, a client only receives a limited right to use the software and cannot legally resell or redistribute the code to third parties.

Ownership vs. Licensing: The Statutory Difference

The World Intellectual Property Organization (WIPO) treaties, to which Nigeria is a signatory, reinforce this. If you are an independent contractor, you are the 'Author.' To lose ownership, you must sign a 'Work Made for Hire' agreement or an 'IP Assignment Agreement.' If you only signed a 'Service Agreement,' you likely still own the golden goose.

4. The Takeaway: Your Actionable Compliance Playbook

As a CTO or Senior Dev, you must move from 'coding' to 'commercializing.' Here is how you protect your IP from unauthorized resale:

The 'Anti-Resale' Contract Clause

Never hand over code without this specific language in your contract. Use this snippet to protect your work:

"The Developer grants the Client a non-exclusive, non-transferable, and non-sublicensable license to use the Software solely for its internal business operations. The Client shall not sell, lease, sub-license, or otherwise distribute the Source Code or Executable Code to any third party without the express written consent of the Developer, which may be subject to additional royalty fees."

The Developer's IP Protection Checklist

• Audit Your Employment Status: Are you an employee or a contractor? If you are a contractor, you own the code by default. If you are an employee, the company owns it (Section 10(2)).
• Define the Scope: Explicitly state if the license is 'Internal Use Only' or 'Commercial/Resale.'
• Use Git Signatures: Ensure every commit is cryptographically signed. This provides a timestamped audit trail of authorship for the Nigerian Data Protection Commission (NDPC) or court evidence.
• Watermark Your Logic: Insert non-functional, unique logic strings or 'Easter eggs' in the backend that prove the code originated from you if it appears in a competitor's product.
• Insert a 'Survival Clause': Ensure that your IP ownership survives even if the development contract is terminated.

Final Thought: Code is poetry, but in the business world, it is an asset. Don't let a client turn your asset into their passive income stream without your permission. If they want the right to resell, they should pay 'Resale Prices,' not 'Development Prices.'

Disclaimer: This article is for informational purposes and does not constitute legal advice. Consult a qualified Technology Lawyer at SparkleCharge for specific contract reviews.

Frequently Asked Questions (FAQ)

If I am paid in full for a project, does the client automatically own the code?

No. Under the Copyright Act 2022, payment for services does not equal ownership of IP. Ownership only transfers if there is a written 'Assignment of Rights' signed by the developer.

Can I reuse the code I wrote for one client for another client?

Yes, provided you haven't signed an 'Exclusive License' or an 'Assignment of IP' to the first client. Using a 'Non-Exclusive License' allows you to retain ownership and reuse your libraries and modules.

What happens if there is no written contract at all?

In the absence of a written contract, the developer retains full ownership of the copyright. The client is usually granted an 'implied license' to use the software for the purpose it was built, but they cannot sell it to others.

🚀 Build & Scale with SparkleCharge: Ready to architect, scale, or automate your production software platform? Partner with SparkleCharge engineering for high-availability full-stack systems. Schedule an Engineering Consultation or explore our Enterprise Technical Services.