You can have a sharp product, a decent pitch deck, and a name your team loves, then still lose the lot because someone else filed first. That's the annoying part of intellectual property protection, it's rarely about talent, and usually about timing, paperwork, and not being sloppy. I've watched founders spend months polishing a brand, only to find the register already crowded, or worse, their contractor walked away with the working guts of the product.
The fix isn't glamorous. It's a mix of early filing, boring contracts, and a clear call on what gets published and what stays locked up. For New Zealand founders, that call matters even more because rights are territorial, and local protection doesn't appear by magic just because you've launched overseas or shipped to Australia. The basic legal frame sits in the Patents Act 2013, Trade Marks Act 2002, and Copyright Act 1994, with IPONZ handling the practical gateway for patents, trade marks, and designs.
You know what? The founders who sleep easiest aren't the ones with the fanciest idea. They're the ones who treated IP like a real asset on day one.
A founder I'd bet you've met, maybe even been, has this story. The brand is live, customers are signing up, and then a letter lands saying the name is already spoken for. That's not bad luck. That's a missed search, a missed filing, and a painful lesson in how unforgiving the register can be.
Intellectual property protection is territorial. If you've protected something overseas, that doesn't automatically carry into New Zealand. The reverse is true too. Local filing matters because IPONZ is the operational gatekeeper here, and if you skip that step, you're basically hoping the market will be kind. It won't.
That's the trap for software and app founders. They think the product launch is the milestone. It isn't. The first real milestone is making sure the brand, invention, or design is defensible where you trade. WIPO's 2024 filing picture shows just how crowded the field has become, with 3.7 million patent applications worldwide and trademark activity holding at 15.2 million class counts WIPO. When filings are that dense, local slackness gets expensive fast.
For a clean founder-level primer on the broader terrain, RNC Group's founder's IP guide is worth a look. It's not NZ-specific, but it's a useful reminder that IP is a system, not a slogan.
Practical rule: if the name, shape, or technical edge matters to the business, treat filing as part of launch, not a legal tidy-up later.
The lesson is simple. A brand name you love, a feature your dev team built, or a product category you want to own has no protection just because you made it first in your own head. The register doesn't care about vibes. It cares about what was filed, when, and where.
Most founders do not need a lecture on legal theory. They need to know which asset sits in which bucket, and whether they should file or just keep clean records. That is the useful bit.
Copyright is automatic for original software code in New Zealand, but it protects the expression of the code, not the idea behind it. Your onboarding flow, your written copy, and your source code are covered, but the underlying method or know-how is not protected just because you wrote it down. Founders building SaaS products miss this all the time. They assume the whole product is wrapped up by default. It is not.
Trademarks protect the source sign, the part customers see. That is your product name, logo, slogan, packaging, and the brand layer that stops confusion in the market. WIPO's plain-language explanation of trademarks matches that point, and Tulane University's IP explainer makes the practical point that the main job is keeping competitors from using confusingly similar signs WIPO, Tulane University. For naming work, logo and branding guidance is useful because good branding without registrability is just expensive decoration.
Patents cover a genuine technical invention, not a vague product idea. If your recommendation engine or system architecture solves a technical problem in a novel way, that may be worth talking to a patent attorney about. If it is just a standard stack with a fresh wrapper, save your money.
Trade secrets cover the material you do not want to publish, like a data pipeline, prompts, model weights, or internal implementation details. In New Zealand, that route is often stronger for commercially sensitive software know-how, provided you keep it secret.
| IP Type | What It Protects | Automatic? | Typical NZ Cost | Typical AU Cost | Duration |
|---|---|---|---|---|---|
| Copyright | Original code, text, and expression | Yes | No filing fee | No filing fee | Long, but tied to the work |
| Trademark | Brand name, logo, slogan, packaging | No | Filing costs apply | Filing costs apply | Renewable if maintained |
| Patent | Novel technical invention | No | Attorney and filing costs apply | Attorney and filing costs apply | Limited term |
| Trade Secret | Confidential know-how and data | No | Policy and contract cost | Policy and contract cost | As long as secrecy holds |
If your business is more build-heavy than brand-heavy, the internal structure of the product matters a lot. This developer-focused page is a handy reminder that code, architecture, and delivery work all sit in different legal buckets.
Short version: copyright is automatic, trademarks need filing, patents need real invention, trade secrets need discipline.
A founder who starts with the filing form is already behind. Start with the business problem instead. What are you trying to stop, someone using your name, copying your technical method, or cloning the look and feel of the product? Those are different threats, and they need different IP answers.
Start with a search on the IPONZ and IP Australia registers. If a mark is too close to an existing one, do not talk yourself into filing anyway. Pick something more distinctive. Generic names cause trouble, and a weak mark is harder to enforce later. If you are still shaping the brand, this NZ Apps branding resource is useful because good marks are usually chosen before filing, not cleaned up after refusal.
Then choose the right class or classes for the software product. That sounds tedious because it is tedious, and sloppy class selection is a common founder mistake. A SaaS platform and a mobile app can sit in different commercial uses, so the wording has to match what you sell. File the application, go through examination, and deal with objections or opposition if they come up.
A straightforward trade mark filing can often move in roughly 6 to 12 months, depending on the path and whether anyone objects. Self-filing is often cheaper than using an attorney from day one, which is why many early-stage teams file first and get advice only when the mark looks shaky. That is not penny-pinching. That is sensible capital discipline.
Patent work deserves a tighter filter. A software patent only makes sense when there is a real technical invention, not a feature list dressed up in technical language. If the product edge sits in a technical method, architecture, or machine process, speak to a specialist early. If the edge is brand, speed, or execution, a patent can become an expensive distraction.
Practical rule: file the trademark early, test patentability before you spend serious money, and do not let a lawyer push you toward a weak patent just because the paperwork feels busy.
For founders building across New Zealand and Australia, the filing route has to be planned properly. The Madrid Protocol can help with international trade mark coverage, and the Paris Convention priority period can matter when you file in more than one market. That is the unglamorous cross-border layer, but it stops founders from stepping on their own rake.
Founders often get overexcited. A patent sounds impressive. It feels like a moat. Sometimes it is. Often it's a costly way to publish what you should've kept private.
If your software has a novel technical mechanism, patenting may make sense. If your advantage is model behaviour, prompts, a training workflow, or a data pipeline, secrecy is often better. In New Zealand, trade secret + contract + access control is usually the stronger play for commercially sensitive know-how, because secrecy only works when the information stays secret and the business takes reasonable steps to protect it Data Protection Report.
That means you don't casually email the core logic around the company. You don't paste prompt libraries into open docs. You don't leave architecture notes in a shared folder that half the team can browse from the train. The product can still be clever and fast. It just needs a gate around the special sauce.
Founders keep asking what's protectable when AI touches the product. Fair question. The honest answer is that the code isn't the whole asset anymore. Model behaviour, internal prompts, data flows, and operating know-how can matter more than the source code itself. The catch is that patenting those pieces can force you to disclose what you'd rather keep hidden.
So ask three blunt questions before filing anything:
That's the trade-off. Patents buy public exclusivity, but they also publish. Trade secrets can last longer, but only if the company behaves like the information matters. Most early-stage teams are bad at that. Fixable, but bad.
Registration is useful, but it doesn't save you from messy people problems. Founders lose IP not because the law failed them, but because the paperwork and access discipline were half-built. That's where the damage starts.
Start with NDAs, but don't treat them like a magic charm. They need to be signed before disclosure, and they should describe the kind of material you're protecting. For a founder, that means code snippets, customer lists, product roadmaps, data schemas, and model details, not just some fluffy “confidential information” paragraph that nobody reads.
Then fix your employment and contractor agreements. If someone creates IP on company time, or under company direction, the agreement needs to assign that work to the company. Don't assume goodwill will do the job. It won't, especially once the relationship sours and everyone suddenly remembers they “meant to tidy up the paperwork later.”
Practical rule: if a contractor, employee, or advisor touches the product, the IP assignment clause should already be signed. Not next week. Not after launch.
Data licences matter too. If you hand over datasets to a partner or customer, spell out use rights, derivative-data ownership, modification limits, confidentiality duties, and the delivery format. Those terms decide whether the data gets reused, repackaged, or commercialised by someone else.
Access control is not glamorous, but it's cheap and effective. Keep source repo access tight. Limit who can export customer data. Reduce admin rights on production systems. Store a central register of IP assets and list the owner for each one. That makes later disputes a lot less painful, because you can show what exists and who created it.
If you're collaborating with another product team, or building with a dev shop, this co-development resource is the sort of thing worth checking before you sign anything. Shared development is where ownership gets fuzzy fast.
The worst IP mistakes don't look dramatic at the time. They look small. A shortcut here, a rushed launch there, a “we'll sort it later” in Slack. Then a year or two passes, revenue shows up, and the cracks start to cost real money.
Generic names are trouble. If your brand sounds like every other tool in the category, you're making life harder for yourself from day one. It may feel safe because it sounds descriptive, but that's often exactly why it's weak.
No IP assignment clause is another classic. A contractor writes the code, the founder pays the invoice, and everyone assumes ownership is obvious. It's not. If there's no assignment clause, you may have to argue about ownership later, and that's a grim place to discover the gap.
Public repositories are a gift to everyone except you. A default-public GitHub org can expose source, issue history, and sometimes clues about your commercial logic. Keep it private unless there's a good reason not to.
Then there's the domain mistake. Owning a .nz or .com.au domain doesn't mean you own the brand. Domain registration and trademark rights are different animals, and founders mix them up all the time.
Design rights and UI protection get ignored too. If your app has a distinctive visual layout, don't assume the code alone covers the look and feel. And no, an NDA signature isn't theatre. If you never enforce it or even explain it, people treat it like paperwork confetti.
If a feature, brand, or design would sting to lose, stop assuming it's protected just because it exists.
The cure is usually boring: file early, assign rights cleanly, restrict access, and keep records. Boring is good. Boring saves lawsuits.
Owning a right is one thing. Using it is another. If you're not watching the market, you'll only notice infringement when the copycat already has customers.
For trademarks, pay attention once the mark is published. That's the window where opposition issues can surface. For domains, keep an eye on lookalikes and typo variants. For software clones, monitor app stores, landing pages, and GitHub-style copies. Most founders don't need a courtroom on speed dial. They need a system for noticing the problem early.
If a dispute starts, the first letter should be measured, not theatrical. A decent cease-and-desist note identifies the right, the problem, and the remedy you want. It doesn't rant. Overplay your hand and you can create new problems, including claims around groundless threats if you're careless.
For local domain and dispute routes, the .nz Domain Name Commission and the .au Dispute Resolution Policy are worth knowing because they can be cheaper and faster than jumping straight into full-blown litigation. That said, if the issue touches a patent, a serious trade mark dispute, or a threatened investor round, get advice fast. That's where Ciphar's note on lawyer-client confidentiality is a useful reminder, because candid advice only helps if the conversation stays protected.
Call a lawyer when the mark is close to launch, when a contractor relationship gets messy, when someone challenges ownership, or when a competitor starts acting like your product is theirs. Don't wait for the problem to become a public fight. By then, the advice is more expensive and the options are thinner.
The cheap move is to get the hard bits reviewed early. That's not over-lawyering. That's avoiding a dumb bill later.
Week 1: audit what you've already built, then file the key trade mark applications for the product name and any parent brand you're serious about.
Week 2: draft and sign IP assignment clauses for employees, contractors, and advisors. Don't leave this half-finished.
Week 3: review repo access, admin rights, and data export permissions. Trim the list. Then trim it again.
Week 4: classify trade secrets, write down who can see what, and set the protection rules around prompts, model behaviour, datasets, and internal architecture.
If money is tight, start with the free IPONZ search tools and a narrow filing strategy. Don't try to protect everything badly. Protect the bits that keep the business alive.
Do I need a patent before I pitch investors? No, but you do need to know whether your real edge is patentable or better kept secret.
Can I trademark a logo idea? Not really. You need a real mark you can file and use properly.
What if a competitor copies my UI? Check whether you've got design, copyright, contract, or trade dress issues, then get advice before sending angry emails.
How do I protect AI-generated assets under New Zealand law? Treat the model output, prompts, data pipeline, and internal know-how as separate assets. Some may fit copyright, some may not, and some are better handled as trade secrets.
If you're sitting on product, brand, or know-how that matters, stop treating IP like admin. Sort the filing, clean up the contracts, and lock the doors around the good stuff. If you want a place to start, NZ Apps has the regional context and company coverage to help you think about market positioning with a bit more backbone.
Add your NZ or Australian app or tech company to the NZ Apps directory and get discovered by founders and operators across the region.
Get ListedReach tech decision-makers across New Zealand and Australia. Sponsored and dofollow editorial links, permanent featured listings, and sponsored articles on a DA30+ .co.nz domain.
See Options