IP Assignment Clauses for New Zealand Healthtech Startups

If you are building a healthtech startup in New Zealand, your intellectual property can be your most valuable asset, but it is also one of the easiest things to lose through a badly drafted contract. Founders often assume that paying a developer means the code belongs to the company, that a contractor's standard terms are harmless, or that a broad assignment clause will automatically capture everything created for the business. Those assumptions can create serious problems when you raise capital, partner with a clinic, or try to commercialise software, data tools, diagnostics, or medical devices.

An IP assignment clause decides who owns the rights in what is being created. In healthtech, that can cover software, algorithms, clinical workflows, device designs, datasets, documentation, branding, know-how, and future improvements. The right wording matters before you sign a contract, before you accept the provider's standard terms, and before you rely on a verbal promise about ownership. This guide explains what an IP assignment clause means for New Zealand healthtech businesses, the legal issues to check, the mistakes founders commonly make, and the practical points to sort out before any agreement is signed.

Overview

An IP assignment clause is the part of a contract that transfers intellectual property from one party to another. For New Zealand healthtech startups, it needs to do more than say ownership changes hands. It should clearly identify what IP is being assigned, when the assignment takes effect, what rights are excluded, and how confidential information, moral rights, privacy obligations, and future improvements are handled.

• Confirm exactly what intellectual property is covered, including code, designs, documentation, inventions, databases, models, and know-how.
• Check whether the clause assigns existing IP, newly created IP, future IP, or all three.
• Make sure the agreement states when ownership transfers, for example on creation, on payment, or on signature.
• Review any carve-outs for pre-existing tools, third party materials, open source components, or background IP.
• Match the clause with confidentiality, privacy, data use, and information security obligations.
• Check whether contractors, employees, founders, universities, or clinical partners also need separate assignment documents.
• Look at moral rights consents, assistance obligations, and signing requirements for future filings or registrations.
• Make sure the clause works with the commercial deal, especially if one party only needs a licence rather than full ownership.

What IP Assignment Clause Healthtech Startups Means For New Zealand Businesses

An IP assignment clause decides whether your company actually owns the healthtech product it is paying to build. That ownership question affects fundraising, due diligence, licensing, collaborations, and exit value.

Healthtech founders usually deal with more moving parts than a standard software startup. You might have software developers, product designers, clinicians, researchers, data scientists, and universities all contributing to the same product. If ownership is not mapped properly, your company can end up with a patchwork of rights instead of a clean asset.

What counts as IP in a healthtech startup?

For a healthtech business, intellectual property often goes well beyond a logo or a brand name. Depending on the product, the relevant IP can include:

• source code and object code for apps, platforms, and embedded systems
• algorithms, machine learning models, and model training methods
• user interface designs, workflows, and technical specifications
• medical device designs, prototypes, circuitry, and manufacturing files
• clinical content, educational materials, and treatment support tools
• databases, structured datasets, and data labelling frameworks
• process documents, playbooks, and internal know-how
• patentable inventions, confidential methods, and trade secrets
• trade marks, product names, and branded assets

Not all of these rights are protected in the same way, and not all should always be assigned. That is why the wording in the clause matters.

Why healthtech deals need more care

Healthtech products often sit at the intersection of IP, privacy, and regulation. A software vendor may contribute code, a clinician may create treatment content, and a research institution may claim rights in study outputs. At the same time, the product may rely on patient information, de-identified datasets, and confidential clinical processes.

The result is that an assignment clause cannot be read in isolation. It needs to fit with the rest of the contract and with the actual working relationship between the parties.

This is where founders often get caught. They focus on price, delivery dates, and product milestones, but do not pin down who owns the resulting IP, who can reuse it, and whether future versions are also covered.

Assignment versus licence

A full assignment transfers ownership. A licence gives permission to use IP while ownership stays with the original owner.

That distinction matters because not every healthtech arrangement should involve a full assignment. For example, a contractor may assign bespoke code developed specifically for your product, but keep ownership of its pre-existing development tools. A clinical partner may license certain content to your company without assigning all of its underlying material.

Before you sign, ask what the company actually needs:

• full ownership of newly created product IP
• a broad licence to use background tools or frameworks
• permission to modify and commercialise deliverables
• exclusive or non-exclusive rights in particular markets or fields of use

A clause that grabs too much can stall negotiations. A clause that says too little can leave your company without enough rights to operate.

Who should sign?

The company that wants to own the IP must make sure the person or entity creating it has authority to assign it. In practice, that may include:

• founders who developed the initial product before the company was incorporated
• employees creating code, content, inventions, or technical improvements
• independent contractors and development agencies
• advisers or consultants contributing technical materials
• universities, research bodies, or spinout entities involved in R&D
• clinical partners contributing protocols, datasets, or specialist content

If the chain of ownership is broken at any point, investors and buyers will notice. That problem is much easier to fix early than during due diligence.

Legal Issues To Check Before You Sign

The safest approach is to treat an IP assignment clause as a commercial ownership map, not a boilerplate paragraph. Before you sign a contract, the clause should answer who owns what, when, on what terms, and with what limits.

1. Define the assigned IP properly

General wording like "all intellectual property" can be too vague if the parties later disagree about what was actually created. Healthtech agreements should identify the deliverables and the categories of IP clearly.

Where the project is technical or collaborative, the contract should list the materials or outputs covered, such as:

• software code and updates
• wireframes, technical architecture, and design files
• device specifications and prototype materials
• clinical content and workflow documents
• data schemas, taxonomies, and training materials
• reports, manuals, and implementation documents

2. Separate background IP from project IP

Most suppliers, developers, and researchers bring pre-existing materials into a project. Those may include libraries, templates, models, processes, or proprietary tools they used before working with your company.

The contract should spell out:

• what background IP each party keeps
• whether the startup gets a licence to use that background IP
• whether that licence is perpetual, transferable, sublicensable, or limited
• whether the company can use the deliverables without ongoing dependence on the supplier

This point is especially important if your product will be sold to healthcare providers who expect long term continuity and support.

3. Check when the assignment takes effect

Ownership can transfer on creation, on execution of the agreement, on delivery, or once payment is made. Each option creates different risks.

If assignment only happens after full payment, the supplier may retain ownership during development. If assignment only applies to accepted deliverables, drafts or partial work may sit outside the transfer. Before you rely on a verbal promise, make sure the timing is express and commercially workable.

4. Deal with future improvements and derivative works

Healthtech products often change quickly after pilot testing, customer feedback, or regulatory review. A narrow clause may assign version 1, but not later improvements, refinements, or derivative works.

That is a common source of dispute where a developer continues supporting the product after launch or where a research collaboration produces follow-on material. The contract should address whether future developments are:

• automatically assigned to the company
• included only if paid for under the project
• owned by the creator but licensed back
• subject to a separate negotiation

5. Match the clause with confidentiality and privacy obligations

An assignment clause may give ownership of certain outputs, but that does not override confidentiality obligations or privacy law. In New Zealand, healthtech businesses often handle personal information or health information, so the Privacy Act 2020 and related data protection issues are highly relevant.

If a dataset, analysis, or tool is built using personal information, the contract should align IP ownership with:

• who controls the data
• what consents or permissions apply to use of the data
• whether de-identification has occurred and on what basis
• what security measures are required
• what each party can retain after the project ends

Owning a software product does not necessarily mean you can freely use all underlying data in any way you like.

6. Consider moral rights and further assurance obligations

Some agreements also need the creator to consent to certain acts relating to moral rights, or to sign further documents needed to perfect ownership, registrations, or enforcement. That can matter where copyright works, design materials, or patent filings are involved.

If the business may later file for protection, transfer rights internationally, or sell the company, founders should make sure the agreement includes a practical obligation for the creator to assist.

7. Watch for conflicts with employment and contractor arrangements

Employee-created IP and contractor-created IP are not always treated the same way in practice, and the contract structure matters. Founders often assume standard engagement terms are enough, but the safest course is to make ownership clear in each employment agreement, contractor agreement, and founder document.

For a New Zealand startup, that can mean checking whether:

• the founder built the product before incorporation and needs to assign it to the company
• the employment agreement covers inventions, code, and confidential information created in the role
• contractors have signed written assignments rather than relying on invoices or emails
• agency terms conflict with the company's own ownership position

8. Make sure the clause fits the deal with customers and partners

Your company may want to own the product IP but only license it to clinics, pharmacies, insurers, or research partners. If your upstream development contracts are messy, downstream customer promises can become risky.

Before you sign a commercial contract, check that your ownership position supports what you are promising about exclusivity, use rights, customisation, and support.

Common Mistakes With IP Assignment Clause Healthtech Startups

The biggest mistake is assuming ownership is obvious because the startup paid for the work. In healthtech, that assumption can fail quickly once multiple contributors, datasets, and compliance obligations are involved.

Relying on generic templates

A generic services contract may use broad assignment language that does not deal properly with background IP, medical content, regulated workflows, or shared datasets. It may also ignore future improvements or leave too much room for dispute over reuse rights.

This becomes expensive when the relationship breaks down or an investor asks for proof of title to the core product.

Ignoring founder-created IP

Many startups start informally. A founder may build the first app version, draft clinical content, or create branding before the company exists. If that IP never gets formally assigned to the company, there may be a gap between what the business thinks it owns and what it can prove it owns.

That issue often surfaces before fundraising, sale discussions, or a major commercial partnership.

Missing contractor and agency ownership issues

External developers and specialist agencies commonly use their own standard terms. Those terms may say they keep ownership of code, frameworks, or deliverables while giving the startup only a limited licence.

Before you accept the provider's standard terms, check whether the licence is enough for your actual business model. If your plan includes sublicensing, white-labelling, integration into a regulated healthcare environment, or future sale of the platform, a narrow licence may not work.

Treating data rights as the same as IP rights

Founders sometimes talk about "owning the data" when the legal position is more complicated. Contractual rights over datasets, privacy obligations, confidentiality restrictions, and IP rights in databases or analytics outputs are related but not identical.

If a healthtech tool learns from patient or provider data, the agreement should not blur these separate issues. This is particularly important where hospitals, PHOs, clinics, or third party software providers are involved.

Failing to document collaborative development properly

Joint projects can create confusion about who owns new outputs, who can commercialise them, and whether one party can continue using them after the relationship ends. A short memorandum or vague scope document rarely solves those questions.

Healthtech collaborations with research bodies or clinical institutions often need more detailed contract drafting around:

• ownership of project results
• licensing back to the contributing party
• publication rights and confidentiality review
• use of patient-related information
• future research and commercialisation rights

Leaving the clause disconnected from the rest of the contract

An assignment clause can be undermined by inconsistent definitions, payment milestones, acceptance procedures, confidentiality terms, or termination rights elsewhere in the agreement. A contract should read as one coherent deal.

If one clause says ownership passes on payment, another says the supplier may reuse deliverables freely, and a third says the customer has exclusive rights, the parties are set up for dispute.

Forgetting due diligence readiness

Investors and acquirers usually ask for signed agreements showing how the company obtained its IP. If documents are missing, unsigned, or inconsistent, the company may be asked to fix them urgently or accept valuation pressure.

Good housekeeping means keeping signed copies, version control records, founder assignments, contractor agreements, and a simple IP register. That admin work is not glamorous, but it saves time and stress later.

FAQs

Does paying a developer mean my startup owns the code?

No. Payment alone does not reliably settle ownership. The contract should clearly state whether the code is assigned to your company or only licensed.

Should a healthtech startup always ask for a full IP assignment?

Not always. A full assignment is often appropriate for bespoke product IP, but some deals work better with a licence for pre-existing tools, frameworks, or third party materials.

Do founders need to assign IP to their own company?

Usually, yes, if the founder created the relevant IP personally before or outside the company relationship. A formal written assignment helps create a clean chain of title.

Can an IP assignment clause cover future improvements?

Yes, if it is drafted clearly. The agreement should say whether updates, modifications, derivative works, and later versions are included and when those rights transfer.

Why do privacy issues matter if the contract is about IP?

Because healthtech products often use personal or health information. Owning the software or output does not automatically give unrestricted rights to use the data behind it, so the contract should align IP rights with privacy and confidentiality obligations.

Key Takeaways

• An IP assignment clause determines whether your New Zealand healthtech startup actually owns the product, content, code, and other assets it is paying to create.
• The clause should clearly define the relevant IP, separate background IP from project IP, and state when ownership transfers.
• Healthtech agreements often need extra care around privacy, confidential information, clinical content, datasets, future improvements, and collaborative development.
• Founders should not assume payment, verbal assurances, or generic contractor terms are enough to secure ownership.
• Clean founder, employee, contractor, and partner documentation can make fundraising, commercial deals, and due diligence much smoother.

If you want help with contractor agreements, founder IP assignments, software development contracts, privacy and data use terms, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.