You have built a product that works, but your contract might not. Many South African tech entrepreneurs assume a free template, or an international agreement with the serial numbers filed off, gives them cover. Then a dispute hits and the document falls apart. A proper software licence agreement is not paperwork you file away. It is the commercial instrument that defines what you are actually selling and protects the asset you have spent years building.
What a Software Licence Agreement Actually Covers
Under South African law, a software licence agreement governs usage rights. It does not transfer ownership of the underlying code. You keep full title to your intellectual property while granting the user a specific permission to install and use the program within boundaries you set.
That distinction matters because selling access is not the same as selling goods. When you licence software, you set strict limits on how the licensee may use, modify, copy or distribute your work, without ever giving up your copyright. A well-drafted agreement typically separates two kinds of permission: a non-exclusive, non-transferable right to install and use the software for the licensee’s own purposes, and, where relevant, a broader non-exclusive, non-transferable licence for commercial use. Whether that permission is revocable, or irrevocable except in the event of termination, is a decision you need to make deliberately rather than leave to boilerplate wording — an inconsistency here is exactly the kind of thing a court or an unhappy licensee will seize on later.
Without that clarity, users may assume they own the customisations they asked for, or think they can resell your platform to third parties. Your contract has to rule out those assumptions in writing, or you end up arguing about them in court.
Essential Clauses in Every Software Licence Agreement
Vague terms are the main reason licences fail when tested in local courts. Draft with precision, not optimism. Commercial lawyer Nicolene Schoeman-Louw notes that software licences drafted without South African context often contain unenforceable limitation of liability clauses, which leaves SMEs exposed the moment a dispute starts.
Scope of Use and Restrictions
Your licence must state exactly who may use the software, on how many devices, and for what business purpose. Leave it vague and users will read broad permissions in their own favour, not yours.
Restrictions should rule out copying, distributing, modifying or creating derivative works without authorisation; reverse engineering, decompiling or disassembling beyond what the law allows; and transferring, leasing or sub-licensing without your prior written consent. Put these prohibitions in the opening sections, and you protect your market position from day one. It’s worth testing the restrictions against how the software will actually be used in practice — backups, integrations, contractor access, or use by affiliates — so you’re not accidentally prohibiting something you meant to allow, or leaving a gap for something you didn’t.
Payment Terms and Renewals
Revenue leaks out of poorly structured payment clauses: no allowance for late fees, currency swings, or automatic renewal mechanics. Your agreement needs to say whether fees are once-off or recurring, when invoices go out, and what happens when payment arrives late. In practice, this usually comes down to a straightforward choice: a fixed monthly amount invoiced and payable by a set date each month, or a price based on an accepted quotation followed by an invoice. Pick one mechanism and complete it properly rather than leaving both options half-filled in.
South African contract law requires certainty on price and payment timing for an agreement to hold up. If your renewal terms lean on phrases like “reasonable notice” instead of a fixed number of days, you are building risk into your own collections process. A durational licence that runs indefinitely until either side gives a fixed notice period — commonly 30 days in writing — is easier to administer than one with no defined exit mechanism at all.
Termination and Consequences
Every solid software licence agreement needs a clear exit that survives the end of the relationship. Spell out which breaches trigger immediate termination, which ones get a cure period first, and what the licensee must do (stop use, destroy copies) once the licence ends. A common structure gives the defaulting party a set window — often 10 business days after written demand — to remedy a curable breach before the other side can cancel or claim specific performance and damages. Insolvency-type events (liquidation, business rescue, a proposed arrangement with creditors) and a licensee’s prohibited use of the software are usually carved out as grounds for immediate, summary cancellation.
Post-termination survival clauses keep confidentiality, indemnification and IP ownership binding even after the user stops paying. Skip these, and a former client can keep using your technology for free.
Protecting Intellectual Property Under South African Law
Your code is your most valuable asset. Plenty of founders erode their ownership of it through careless drafting. Keeping IP ownership separate from the usage rights you grant takes deliberate wording, with no room for a court to read it the other way.
Ownership vs Licensing Rights
State plainly that the software, and all rights, title and interest in it — including intellectual property rights — remain the licensor’s exclusive property throughout the term and after it ends. A licence does not transfer copyright, but loose wording can read like an assignment of rights you never meant to give away. It’s also worth placing a duty on the licensee to notify you promptly if they become aware of any infringement of your rights, so you’re not relying on catching it yourself.
Address feedback too. Without a clause assigning user suggestions to you, a user could later claim joint ownership of improvements their input inspired. One line closes that gap before it turns into a sticking point in acquisition talks.
Handling Derivative Works
Custom development is where ownership lines blur fastest if the licence doesn’t define them. If a client pays you to modify your core product for their needs, the contract has to say whether those modifications belong to you or to them.
Under South African copyright principles, the author of a derivative work usually owns the new elements, unless the parties agreed otherwise in writing. Without that agreement in place beforehand, a big client could effectively block you from rolling those improvements out to anyone else.
Before you share source code or discuss bespoke features, secure a non-disclosure agreement to protect your IP during negotiations.
Common Risks of Generic or Free Software Licences
International templates fail South African SMEs because they weren’t built for our legal framework. A standard US-sourced software licence typically lacks POPIA-compliant data processing terms, which creates immediate regulatory risk for any South African business handling customer information.
These generic documents reference foreign statutes, GDPR, DMCA, that carry no authority in Johannesburg or Cape Town. Rely on one and your limitation of liability caps may be void under our Consumer Protection Act. Your dispute resolution clause might even force you into expensive foreign arbitration, rather than a locally workable process — such as short internal consultation between named representatives, followed, if unresolved, by arbitration under the Arbitration Act 42 of 1965 and AFSA’s rules, with interim relief still available through the courts.
Fixing a broken contract after a breach costs far more than getting a locally drafted one from the start. Legal exposure compounds fast once your foundational document can’t survive scrutiny in a South African court.
Ensuring POPIA Compliance in Your Licence
Software that processes personal information triggers mandatory data protection duties under current South African law. Your licence needs to work alongside your POPIA privacy policy, allocating responsibility for data security, breach notification and cross-border transfers between you and the licensee.
Ignore these provisions and both parties are exposed to Information Regulator penalties, no matter how strong the rest of your contract is. You cannot contract out of a statutory obligation, but you can define who does what, so nobody’s pointing fingers when a data incident happens.
In practice, the licensee’s data obligations should require compliance with the Protection of Personal Information Act 4 of 2013 (or an applicable international equivalent), processing personal information only for the purposes of the agreement and on your instructions, controlling third-party access, putting reasonable technical and organisational safeguards in place, giving immediate notice of any possible breach or irregularity, and returning or destroying the information at your option once it’s no longer needed. These duties should expressly survive termination, and a breach of them should be treated as material rather than incidental.
When to Use a Software Licence vs Other Tech Contracts
Get the transaction type wrong and you’re unprotected in an audit or a dispute, because different instruments do different jobs. Knowing when to use a software licence agreement instead of something else closes gaps in your legal cover before they open.
Outsourcing and Development Scenarios
Hiring developers to build software for you? A licence is the wrong instrument. You need a development agreement that assigns all resulting IP to your business the moment it’s created, rather than one that merely permits use of someone else’s work.
If instead you engage contractors to maintain existing software, make sure their access sits under licensing terms that restrict copying and distribution. Confuse an employment relationship with a licensing arrangement and you create tax and labour risk on top of your IP exposure.
Your website’s public-facing rules matter too. Pair your software licence with a terms and conditions template to govern general platform access.
Practical Details Founders Often Overlook
A few administrative points separate a licence that holds up from one that quietly fails when tested:
- Notices and domicilium addresses. Parties typically elect physical addresses on the face of the agreement for formal notices. A change of address usually only takes effect after a set number of calendar days’ notice — commonly seven — so update this promptly if either party moves.
- Written variation only. Amendments, additions, deletions and waivers should only be valid if made in writing and signed by both parties. Treat verbal agreements to change terms as unenforceable, however reasonable they seemed at the time.
- Indemnity scope. Consider clearly what the licensee indemnifies you against — commonly loss of or damage to property, loss of profits, or inability to operate arising from the licensee’s negligence or wilful conduct — and whether you need a cap, exclusions or a defined claims procedure rather than an open-ended allocation of risk.
- Confidentiality carve-outs. Standard exceptions cover information that is already public, later becomes public through no fault of the receiving party, was received lawfully from another source, or must be disclosed by law or court order. Make sure these exceptions are drawn narrowly enough to still protect what matters.
Getting Your Agreement Right Without Law Firm Fees
Professional-grade protection is within reach, and you need it for sustainable growth. Traditional law firm billing just prices most SMEs out of it. Contracts4Biz gives you access to over 48 lawyer-drafted contract templates built specifically for South African law, covering the full range of SME tech agreements.
Our platform lets you customise, download and sign a legally sound software licence in minutes, without the legal fees that used to put this out of reach for small businesses. You answer plain-language questions about your situation, and the system generates a document built for South African jurisdiction, rather than one you’re adapting from foreign boilerplate.
You get every clause structured by a commercial lawyer, at a predictable cost, fast. You should not have to choose between affordability and enforceability to build your tech business properly.
Secure your intellectual property today: browse our contract templates to protect your software.
