What Is A Research And Development Agreement? (2026 Updated)

Research and development (R&D) is exciting - it’s where new products, improved processes, software features, and “we’ve-never-done-this-before” ideas come to life.

But the legal side of R&D can get complicated quickly. Who owns what gets created? What happens if the project scope changes? Can one party use the results for other clients? What if confidential information leaks?

That’s where a Research and Development Agreement comes in. It’s the contract that sets the ground rules before you invest time, money, and IP into building something new together. This update reflects current, practical expectations around IP, confidentiality, data handling, and commercialisation.

Below, we’ll break down what an R&D agreement is, when you’ll need one in New Zealand, what it usually includes, and the common traps to avoid so you’re protected from day one.

What Is A Research And Development Agreement?

A Research and Development Agreement (often called an “R&D agreement”) is a contract between two or more parties who are collaborating to develop something new or improved.

It’s commonly used where:

• one party funds or sponsors the R&D (or contributes resources); and/or
• one party performs the R&D (like a developer, lab, university, engineer, or specialist team); and
• both parties need clarity on the deliverables, ownership, confidentiality, and the right to use the outcomes.

In plain terms: an R&D agreement is how you turn “let’s build this together” into a legally workable plan that reduces misunderstandings and protects what matters - especially intellectual property (IP).

How Is An R&D Agreement Different From A Normal Service Agreement?

A regular services contract is often about delivering a known outcome (e.g. “build a website by X date”). R&D is different because the outcome may be uncertain, experimental, iterative, and dependent on testing.

That means an R&D agreement tends to go deeper on:

• how “success” is measured (and what happens if success isn’t achievable);
• who owns background IP vs newly created IP;
• publication and confidentiality controls (particularly in research environments); and
• commercialisation rights (who can sell it, licence it, or take it to market).

If your relationship is more like “ongoing development and experimentation” than “a standard deliverable,” an R&D agreement is usually the safer fit.

When Do You Need A Research And Development Agreement?

If you’re collaborating with someone to develop new IP - or even potentially new IP - it’s worth putting an R&D agreement in place early.

Common scenarios we see in New Zealand include:

• Startups and founders developing a prototype with an external engineer or dev team.
• Manufacturers working with product designers to create new formulations, components, or processes.
• Tech companies partnering with research institutions or contractors to test and validate a new concept.
• Joint ventures where two businesses combine expertise and resources to create something neither could do alone.
• Grant-funded projects where reporting, milestones, and IP obligations need to be crystal clear.

Early Conversations Aren’t “Too Early” For A Contract

A lot of R&D collaborations start informally - a few meetings, a shared idea, maybe a spreadsheet budget, and someone begins work.

The problem is that early-stage work is often when the most valuable IP is created, and when parties make assumptions like:

• “We paid for it, so we own it.”
• “We created it, so we own it.”
• “We’re partners, so we both own it.”

Those assumptions don’t always align - and if the relationship sours later, it can be expensive to untangle. Getting an agreement in place upfront is usually far cheaper than trying to fix it later.

What Should A Research And Development Agreement Include?

There’s no one-size-fits-all R&D agreement, because the “right” terms depend on how your project is funded, who is contributing what, and what each party needs to do with the outcomes.

That said, a strong R&D agreement usually covers the key issues below.

1. Parties, Purpose, And Project Scope

This section sets the scene: who’s involved, what you’re trying to develop, and the boundaries of the project.

Because R&D can shift as you test and learn, it’s common to include:

• a high-level description of the objective;
• a detailed scope in a schedule (which can be updated);
• assumptions and dependencies (e.g. you need access to a site, sample data, a lab, a third-party API); and
• a change control process when scope inevitably changes.

This is also where you can align expectations about what the R&D is not (for example, “not a guarantee of commercial viability” or “not regulatory approval”).

2. Milestones, Deliverables, And Acceptance Criteria

Even if the project is experimental, it’s still helpful to define checkpoints. This is especially important when one party is funding the work and needs confidence the project is progressing.

Milestones can include things like:

• prototype version releases;
• lab test results or pilot trials;
• documentation and technical reports;
• handover of source code or design files; and
• review and sign-off steps.

Where appropriate, you can include acceptance testing or “go/no-go” decision points, so neither party is locked into endless spend without a clear pathway forward.

3. Fees, Funding, And Expenses

R&D agreements should be very clear about money, including:

• fixed fees vs time-based billing;
• who pays for materials, equipment, and third-party costs;
• how expenses must be approved;
• invoicing timing and payment terms; and
• what happens if the project is paused or terminated.

This is also where you can address whether any funding is contingent on milestones being met, and what reporting the funding party is entitled to receive.

4. Confidentiality And Information Handling

In R&D, you’re usually sharing sensitive information - product concepts, trade secrets, datasets, business strategies, and early-stage inventions.

Confidentiality clauses are standard, but the best R&D agreements also get practical about:

• what counts as confidential information (including verbal disclosures);
• how confidential information may be used (and what “purpose” means);
• who can access it (e.g. employees, subcontractors, advisors);
• security requirements (especially where data is shared digitally); and
• returning or destroying information at the end of the project.

In many collaborations, a separate Non-Disclosure Agreement is used during early discussions, and the R&D agreement then becomes the “main contract” once you commit to the project.

5. Intellectual Property (Background IP vs New IP)

This is the section that most often causes disputes - and the one you want to get right before real work begins.

R&D agreements usually separate IP into two buckets:

• Background IP: what each party already owned (or developed) before the project starts, including tools, code libraries, know-how, designs, and methods.
• Project IP (Foreground IP): what gets created during the project, including inventions, prototypes, reports, code, designs, and improvements.

Then the agreement sets rules around:

• who owns the project IP (one party, shared ownership, or allocation by category);
• whether each party gets a licence to use the other’s IP (and on what terms);
• restrictions on re-use (e.g. the developer can’t re-use your bespoke design for another client); and
• who owns improvements to background IP (this often surprises people).

If you’re building software or commercial products, it can also be relevant to document IP ownership and licensing separately through an IP Assignment or an IP Licence, depending on the commercial deal.

6. Commercialisation Rights

Creating IP is one thing - using it commercially is another.

Your agreement should be clear on questions like:

• Who can sell the end product?
• Can either party licence the IP to third parties?
• Are there field-of-use limits (e.g. you can use it in healthcare, but not in education)?
• Are there territory limits (NZ only, worldwide, etc.)?
• Are there royalties or revenue share arrangements?

Where commercialisation is the key goal, it’s also common to include terms about branding, marketing approvals, and use of each party’s name or logo.

7. Warranties, Risk, And Limitation Of Liability

R&D carries risk by nature. Some experiments fail. Some prototypes don’t scale. Some results can’t be replicated.

That’s why the agreement should be upfront about warranties and liability - for example:

• what is and isn’t guaranteed (often, the developer warrants it will perform services with reasonable care and skill, not that it will achieve a commercial breakthrough);
• how liability is capped (e.g. at the fees paid);
• excluded losses (like loss of profit); and
• insurance expectations.

These clauses can be sensitive, but they’re also essential for risk management - particularly if the R&D is part of a larger supply chain or regulated product development process.

8. Term, Termination, And Exit Plan

One of the most practical parts of an R&D agreement is what happens if things don’t go to plan.

Your agreement should cover:

• how long the agreement runs for;
• termination rights (for convenience vs for breach);
• handover obligations (e.g. returning data, delivering work-in-progress);
• final payments and expense reconciliation; and
• what happens to IP created up to termination.

If one party is doing the work and the other is paying, you’ll often want the right to “step in” and secure the outputs created to date - otherwise you can end up paying for work you can’t use.

Key Legal Issues To Watch In New Zealand R&D Deals

R&D agreements can look “standard” on the surface, but a few NZ-specific legal issues regularly come up in practice.

Confidential Information And Trade Secrets

If you’re relying on confidentiality to protect a competitive edge, your contract needs to do the heavy lifting.

That means clear confidentiality obligations, but also practical controls (like limiting access) and making sure subcontractors are bound too. If you’re serious about protecting know-how, it’s also worth thinking about internal processes - not just the contract.

Privacy And Data (If You’re Using Personal Information)

Many R&D projects involve data - sometimes customer datasets, user testing results, or health-related information.

If personal information is involved, you’ll need to consider your obligations under the Privacy Act 2020. The agreement should clearly cover:

• what data is shared and why;
• who is responsible for storage and security;
• whether data can be transferred overseas (and what safeguards apply); and
• what happens if there’s a privacy incident or data breach.

It’s also a good time to make sure your external-facing documents match what you’re actually doing - for example, having a fit-for-purpose Privacy Policy if your business collects customer information as part of testing, pilots, or ongoing product development.

Consumer And Marketing Claims (When You Start Selling)

Even if your R&D phase is “behind the scenes,” commercialisation often comes with advertising, early sales, beta programs, or pilot customers.

As you move toward market, make sure you don’t overpromise. The Fair Trading Act 1986 prohibits misleading or deceptive conduct, including around performance claims and representations about what a product can do.

It’s not just a legal issue - it’s a reputational one. A well-drafted agreement can also help control who can publish what, and when.

Common Mistakes With Research And Development Agreements (And How To Avoid Them)

R&D agreements are often signed in a rush - right when everyone is keen to start building. That’s exactly when important details can be missed.

Here are some common pitfalls we see (and how you can avoid them).

Mistake 1: Not Defining Background IP Properly

If the agreement doesn’t clearly list what each party is bringing in, it can blur the line between “existing tools” and “project outputs.”

How to avoid it: attach a schedule that describes key background IP (even at a high level). If you’re a developer or specialist provider, that can include pre-existing frameworks and methods you use across projects.

Mistake 2: Assuming Payment Automatically Means Ownership

This is one of the biggest misconceptions in commercial collaborations.

How to avoid it: put IP ownership and licensing in writing, clearly. If you’re paying for R&D because you want exclusive commercial rights, spell that out.

Mistake 3: Leaving Commercialisation “For Later”

It’s tempting to say, “We’ll figure out licensing or revenue share once we know it works.” But once it works, the bargaining position changes - and that’s when relationships can strain.

How to avoid it: even if you don’t know final pricing models, lock in the key commercial principles now (exclusive vs non-exclusive, revenue share approach, who can license to third parties, and decision-making controls).

Mistake 4: Using A Generic Template That Doesn’t Match The Project

R&D is nuanced. A generic template may miss the parts that matter most for your industry, your risk profile, and your commercial goals.

How to avoid it: treat the agreement as a key business asset. Having it properly drafted (or at least reviewed) can prevent costly disputes later - especially when the project becomes valuable.

Mistake 5: Forgetting The People Layer (Staff, Contractors, And Subcontractors)

Even if your organisation signs the R&D agreement, the actual work is often done by employees, contractors, or subcontractors.

How to avoid it: make sure your internal and external engagement documents align with the R&D deal. For example, you may need strong contractor terms or a clear Employment Contract so IP created by your team is properly captured and confidential information is protected.

How Do You Set Up Your R&D Collaboration For Success?

An R&D agreement is a big piece of the puzzle, but it works best when the rest of your legal foundations support it.

Here are a few practical steps that tend to make R&D collaborations smoother from day one.

Get Clear On Decision-Making And Governance

If two businesses are co-developing and co-owning outcomes, decide early:

• who approves changes in scope and budget;
• how disputes are handled (and how quickly);
• what happens if a party wants to exit; and
• who can make commercial decisions (licensing, pricing, partnerships).

For startups and growth companies, it’s also worth ensuring your internal ownership documents support what you’re signing externally - for example, a Shareholders Agreement can be important if the R&D outcomes are a core business asset and multiple owners are involved.

Make Sure Your Structure Matches Your Risk

If you’re entering a high-value R&D project (especially involving product liability, regulated areas, or significant investment), your business structure matters.

Sometimes it’s worth having a company structure in place (rather than contracting personally as a sole trader), and making sure your governance documents are robust, such as a Company Constitution.

This won’t remove all risk, but it can be part of a wider strategy to manage liability and clarify decision-making.

Consider How The R&D Agreement Fits With Other Contracts

R&D often sits alongside other legal documents, such as:

• a broader Service Agreement for ongoing support, maintenance, or implementation after the R&D phase;
• manufacturing or supply agreements if you move into production; and
• distribution or reseller arrangements as you go to market.

It can be overwhelming to map all of this out - but it’s much easier (and cheaper) to align documents early than to fix contradictions later.

Key Takeaways

• A research and development agreement sets the ground rules for R&D collaborations, including scope, milestones, funding, confidentiality, and what happens if the project changes direction.
• IP clauses are the heart of most R&D agreements - you should clearly separate background IP from project IP and spell out ownership and licensing rights in plain terms.
• Commercialisation should be addressed early, including who can sell or licence the outcomes, whether use is exclusive, and whether royalties or revenue share apply.
• If your R&D involves personal information, you’ll likely need to consider Privacy Act 2020 obligations and data security practices as part of the contract and your broader policies.
• R&D agreements should be tailored - generic templates often miss key details, especially around risk allocation, deliverables, and IP control.
• It’s smart to align your R&D agreement with your other legal foundations (like employment/contractor terms and internal ownership documents) so the project outputs are properly protected.

If you’d like help drafting or reviewing a Research and Development Agreement (or structuring an R&D collaboration so you’re protected from day one), you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.