IP Assignment vs Licence in NZ: What Founders Need

Hiring a contractor to build your app, design your brand, write your course content or develop a prototype can create valuable intellectual property from day one. The risk is that founders often pay invoices without checking whether they have actually bought the IP, only have permission to use it, or have nothing clear in writing.

Common mistakes include assuming payment equals ownership, using a vague contractor agreement, ignoring pre-existing tools or templates, and forgetting that subcontractors may have contributed to the work. Those gaps can affect fundraising, resale, franchising, product launches and your ability to stop someone else from reusing the same work.

The practical decision is whether you need an IP assignment, which transfers ownership, or an IP licence, which gives permission to use IP on agreed terms. The right structure depends on the asset, the contractor relationship, your budget and how central the work is to your business model.

Assignment or Licence Decision Checklist

An assignment is usually best when the work is core to your business, while a licence can be enough when you only need limited commercial use.

For founders, the IP assignment vs licence decision in New Zealand is less about legal theory and more about control. A custom algorithm, brand identity or product design may need to sit fully inside your company. A stock image, plugin, training template or specialist methodology may be perfectly workable under licence.

Use these questions before the contractor starts work, not after the final invoice is paid:

• How central is the work? If the asset is your product, brand or main revenue generator, ownership is usually safer.
• Will investors, buyers or partners expect clean ownership? Fundraising and due diligence often involve checking that the company owns its core IP.
• Does the contractor need to reuse any part of the work? Designers, developers and content creators often rely on reusable methods, code libraries, templates or style systems.
• Are there third-party materials involved? Open source code, fonts, images, music, datasets and plugins may come with their own licence limits.
• Will the work be changed, sublicensed or commercialised internationally? Broad commercial plans usually require broader IP rights.
• Is confidentiality just as important as ownership? Trade secrets, product roadmaps and customer data need confidentiality and privacy controls as well as IP wording.

A helpful way to frame the decision is to separate new project IP, pre-existing IP and third-party IP. New project IP is created specifically for you. Pre-existing IP is what the contractor already had before the project, such as code frameworks, design templates or a teaching method. Third-party IP belongs to someone else, such as a software library, licensed font or stock image.

Many disputes happen because the contract simply says the client owns the deliverables. That may not clearly deal with the contractor's existing tools or the third-party assets embedded in the final work. A better contract says what is assigned, what is licensed, what remains with the contractor, and what the contractor is allowed to reuse.

How Contractor IP Ownership Works in New Zealand

New Zealand law does not treat every contractor-created asset in the same way, so written IP terms are the safest source of certainty.

Contractor intellectual property ownership in NZ often depends on the type of IP, the nature of the work, who created it, and what the contract says. The Copyright Act 1994 is especially relevant for software, design, written content, photographs, videos, sound recordings and other creative materials.

For employees, the employer will often own copyright in work created in the course of employment, unless the employment contract says otherwise. Contractors are different. A contractor is not automatically treated like an employee just because you pay them, give them a brief or approve their work.

New Zealand copyright law has specific rules for some commissioned works. In some cases, the person who commissions and pays for certain works may be the first owner of copyright, subject to any agreement to the contrary. However, founders should be cautious about relying on these default rules. They may not cover every type of deliverable, may not deal with pre-existing IP, may not solve overseas contractor issues, and may not capture subcontractor agreement gaps or contributions.

For example, a brand project might include a logo, illustrations, written brand guidelines, strategy documents, fonts and mockups. Different parts of that package may have different ownership positions. A software build might include custom code, open source libraries, the developer's standard components, database design, user interface copy and documentation.

Other forms of IP have their own rules. A registered trade mark is dealt with through IPONZ processes, and the owner should match the business that actually controls the brand. Patents, registered designs and domain names also need separate treatment. Copyright ownership language alone will not automatically update a trade mark record, domain account or product registration.

Confidential information is different again. A product roadmap, customer list, pricing model or unpublished recipe may be commercially valuable even if copyright is not the main issue. You protect that information through confidentiality obligations, access controls, return or deletion duties, and clear restrictions on use.

Contractors may also handle personal information, especially in app development, marketing, HR, health, education or marketplace projects. The Privacy Act 2020 can apply where personal information is collected, used, stored or disclosed. Your contractor agreement should match your privacy policy and operational practices, especially where data is shared with offshore tools or service providers.

The cleanest position is usually a written contractor agreement signed before work begins. It should identify who owns new IP, what rights are licensed back or retained, how third-party materials are approved, whether moral rights are waived where appropriate, and what happens when the engagement ends.

When an IP Assignment Makes Commercial Sense

An IP assignment makes sense when your business needs full ownership, long-term control and a clean chain of title.

An assignment transfers ownership of the relevant IP from the contractor to your business. In practice, an IP assignment agreement in NZ should be in writing, signed by the right parties, and specific enough to capture the relevant assets. It can be included in a contractor agreement or signed as a separate document.

Assignments are common when a founder is paying for work that forms the backbone of the business. If a SaaS company hires a developer to build proprietary platform features, a licence may not be enough. If a food brand pays a designer for its core visual identity and packaging system, the company may need ownership to register, enforce and evolve the brand.

Assignment is often the better structure for:

• Custom software that forms your product, including source code, documentation, user interface elements and database structures created for the business.
• Brand identity assets, such as logos, icons, custom illustrations, packaging artwork and campaign concepts intended to represent the business long term.
• Product development work, including CAD files, prototypes, technical drawings, manufacturing specifications and industrial design concepts.
• Investor-sensitive IP, where a future investor or buyer will expect evidence that the company owns the assets it depends on.
• Content libraries that will be resold or licensed, such as paid course materials, templates, publications, training manuals or digital products.

Assignment gives the business more freedom. You can modify the work, commercialise it, appoint new suppliers, prevent reuse, sell the asset, licence it to others, and include it in a business sale. It also reduces the risk of being locked into one contractor because only they have the rights needed to maintain or develop the work.

The main downside is cost and negotiation. Contractors may charge more for a full assignment, particularly if the work draws on their specialist methods or reusable components. A senior developer may not want to assign a code library they use across multiple clients. A designer may not want to give up their entire design system, mood board library or creative process.

A practical middle ground is to assign the bespoke project IP while carving out the contractor's pre-existing IP. For example, your company owns the finished app interface, custom features and product documentation, while the developer retains ownership of their generic coding framework. Your company then receives a broad licence to use that framework as embedded in the final product.

A good assignment clause should deal with timing. Some agreements transfer IP immediately on creation. Others transfer only once fees are paid in full. From a founder's perspective, paying for milestones without receiving usable IP can create risk, especially if the relationship breaks down before launch. From a contractor's perspective, holding assignment until payment is a way to manage credit risk.

Assignments should also handle moral rights for creative works. Moral rights are personal rights of creators, such as the right to be identified as author and to object to derogatory treatment in certain circumstances. They are not the same as copyright ownership. Where lawful and appropriate, the contract may include consents or waivers so your business can edit, adapt and commercialise the work without needing repeated approvals.

For registered IP, assignments may require extra steps. If a contractor or founder holds a trade mark, design or other registrable right personally, the business may need written transfer documents and updates to the relevant register. The Companies Office, NZBN records and IPONZ records do different jobs, so having a company name or NZBN does not prove ownership of every brand or asset.

When an IP Licence Is the Better Fit

A licence is often better when you need permission to use the work, but the contractor reasonably needs to keep ownership.

A licence does not transfer ownership. It gives your business specified rights to use the IP. A copyright licence contractor arrangement might allow you to use, reproduce, modify, display, host or distribute a work, depending on the wording. The licence can be narrow or broad, free or paid, exclusive or non-exclusive, time-limited or perpetual.

Licensing can be commercially sensible when the contractor's value comes from reusable know-how. A marketing consultant may have campaign templates. A software developer may use standard modules. A trainer or tutor may have a methodology used across many clients. A photographer may license images for defined campaign use rather than selling all rights outright.

A licence may be the better structure for:

• Standard tools or templates that the contractor uses across multiple clients.
• Non-core content, such as a one-off blog series, event photography or internal training slides.
• Specialist methodologies, where the value lies in the contractor's repeatable process rather than a bespoke deliverable.
• Third-party materials, where assignment is not possible because the contractor does not own the underlying asset.
• Lower-budget projects, where the founder only needs defined commercial use rather than full ownership.

The commercial strength of a licence depends on its terms. A weak licence might allow use only for one campaign, in New Zealand, for six months, with no right to edit. A stronger licence might be worldwide, perpetual, irrevocable, royalty-free, transferable to a buyer of the business, and broad enough to allow modifications, sublicensing and use across all media.

For software, the licence needs special care. You should know whether you receive source code or only object code, whether you can host the software yourself, whether you can appoint another developer, whether open source components are included, and whether there are restrictions on resale or integration with other products. If the software handles customer data, security and Privacy Act 2020 obligations also matter.

For design work, a licence should state exactly where and how the design can be used. Packaging, website, social media, paid ads, merchandise, pitch decks and trade show materials may all require different rights if the wording is narrow. If the design will become part of a trade mark application, an assignment is usually cleaner than a limited licence.

For content, founders should look closely at exclusivity and reuse. If a copywriter licences your landing page text but keeps ownership, can they reuse similar wording for a competitor? If a course creator licences training modules to your platform under a content licence, can you translate them, update them, bundle them, or keep selling them after the relationship ends?

For product development, licensing can be useful where a contractor contributes an existing component to your product. For example, an engineering consultant might license a testing methodology or standard part design while assigning the custom prototype documentation created for your product. This hybrid model can be fair and commercially realistic.

Licences should also deal with termination. If the contractor can terminate the licence easily, your business may lose access to an asset it relies on. For mission-critical assets, founders often seek a perpetual licence that cannot be revoked once fees are paid, even if the broader services relationship ends.

The biggest mistake is accepting the word licence without checking the rights. A licence can be powerful, but only if it covers the actual business plan. If you plan to scale, sell, franchise, white-label, raise capital or expand overseas, narrow permission may become a serious constraint.

FAQs

Who Owns Contractor Work in NZ if There Is No Written Agreement?

There is no single answer for every contractor project. New Zealand copyright law has default rules, including specific rules for some commissioned works, but the outcome can depend on the type of work, payment arrangement and surrounding facts. A written agreement is the safest way to confirm who owns contractor work in NZ.

Is Paying a Contractor Enough to Own the IP?

Payment alone may not give you all the rights you need. It may support an argument about commissioned work or implied permission, but it may not deal with pre-existing tools, third-party materials, moral rights, registered IP or future commercial uses. Clear assignment or licence wording is much safer.

Can a Contractor Keep Their Templates and Still Give My Business Rights?

Yes. A common structure is for the contractor to keep ownership of their pre-existing templates, methods or code libraries while giving your business a broad licence to use them as part of the final deliverables. The bespoke work created for your business can be assigned separately.

Should Software Developed by a Contractor Be Assigned or Licensed?

Core platform code is often best assigned to the business, especially for SaaS companies and tech startups. However, reusable modules, open source components and the developer's existing tools may be licensed instead. The agreement should separate these categories clearly.

Do I Need IP Terms if the Contractor Is Overseas?

Yes. Overseas contractors can create extra uncertainty around governing law, enforceability, tax handling, privacy, data access and subcontracting. A New Zealand business should still use clear IP terms and make sure the contract fits the actual working arrangement.

Key Takeaways

• An IP assignment transfers ownership, while an IP licence gives permission to use IP on agreed terms.
• Founders should not assume that paying a contractor automatically gives the company all IP rights needed for scaling, sale or fundraising.
• Assignment is usually best for core software, brand assets, product designs and commercial content libraries that drive business value.
• Licensing can work well for templates, tools, stock assets, methodologies and other materials the contractor needs to reuse.
• The best contractor agreements separate new project IP, pre-existing contractor IP and third-party IP, then deal with each category clearly.
• Software, design, content and product development projects often need a hybrid structure combining assignment, licence, confidentiality and privacy terms.

If you are engaging a contractor and want the IP position cleaned up before work starts, Sprintlaw can help with your contractor agreement, IP assignment wording, copyright licence terms and confidentiality protections. Contact us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.