The gap that surfaces during due diligence, and the five-step path to closing it while it’s still cheap.
Intellectual property is the main asset in most tech businesses, and it’s the one founders leave undocumented for years on the assumption that paying for something means owning it.
We asked Dommisse Attorneys senior associate Jacques Stemmet, who runs the firm’s IP and trademark practice, what founders should actually have in place.
How to actually own your venture’s IP
1. Get written assignments from everyone who touched your code
Start with the most common gap. Under SA law the developer who wrote your code owns it unless they’ve validly assigned it to you, and paying invoices doesn’t transfer ownership. The clause has to say “hereby assigns” rather than “will assign,” and it needs a moral-rights waiver alongside it so you can freely modify the work.
2. Work out what you own of the AI output
The same question, one generation newer. A prompt alone doesn’t make the output yours in South Africa; ownership follows human input and originality, and there’s no local case law yet to give you certainty. Put real human work into anything you intend to defend, keep some evidence of it, and read the terms of every tool your team builds with.
3. Decide between a patent and a trade secret
Once you own it, choose how to protect it. A patent buys roughly 20 years of exclusivity in exchange for publishing exactly how your thing works; a trade secret lasts indefinitely but protects only against theft, not anybody who reverse-engineers it. Let the business model choose: patent what ships and can be taken apart, keep secret what nobody outside ever sees.
4. Register the trademark on your brand
Registering a company at CIPC does not protect your brand, and founders usually learn that when a competitor launches under a confusingly similar name. Search the register before you commit to a name, protect the word mark first, and file in the classes that match what you actually do. South Africa isn’t in the Madrid Protocol, so international protection is a country-by-country job.
5. Stop your team leaking it into free AI tools
All of the above can be undone quietly by someone pasting source code or client data into a consumer AI tool that trains on it. A trade secret is protected only while you take reasonable steps to keep it secret, and in SA, client data in a prompt can be a POPIA problem too. Route sensitive work through enterprise tiers and write a one-page usage policy your team will actually follow.
The big payoff
Work through the five and you can prove you own what you say you own, which is exactly what a buyer or investor checks first. Do it now, while contractors are still friendly and the stakes are low, rather than during due diligence when everyone suddenly understands how much leverage they hold.
Want the full playbook?
These five steps are drawn from What You Own vs What You Think You Own, Jacques’s full masterclass inside the Founder Collab, which walks through the whole system for proving what your business owns:
The full IP Control Stack: the five layers that decide whether your ownership holds up
Why one weak layer can undermine everything above it
Employee and prior-employer traps that quietly compromise your code
Open-source licence traps that can compromise proprietary work
What “good enough” IP hygiene looks like at pre-seed, seed and growth stage
You’ll also get access to 40+ other masterclasses from SA founders and operators on sales, fundraising, UX, paid media and more inside The Founder Collab.
Get more SA tech and business news, tips and business-building workflows and subscribe to The Open Letter.



