Pilot Agreements in New Zealand: How to Structure a Commercial Trial

A pilot can be a smart way to test a product, service, software platform or new commercial arrangement before either side commits to a long term deal. The problem is that many founders treat a trial like a handshake exercise, then get stuck arguing over who owns the data, whether the customer has to pay, what happens if the pilot works, or who is responsible when something goes wrong.

Common mistakes are signing the other side’s standard terms without reading the liability clauses, relying on verbal promises about a later rollout, and leaving the scope so vague that the pilot quietly turns into business as usual. Those gaps can get expensive fast, especially when the pilot involves confidential information, customer data, technical integration or a discount in exchange for feedback.

A well drafted pilot agreement gives both sides a clear testing period, defined deliverables, fair risk allocation and an agreed path at the end of the trial. This guide explains how a pilot agreement works in New Zealand, what to include before you sign, and where businesses most often get caught out.

Overview

A pilot agreement is a short form commercial contract used to test a product or service in a real business setting for a limited time. It should say exactly what is being trialled, what success looks like, who carries the risk during the test, and what happens when the pilot ends.

• Define the pilot scope, term, sites, users and technical requirements.
• Set clear pricing, discounts, expenses and payment timing, even if the trial is partly free.
• Deal with confidential information, intellectual property, data ownership and privacy obligations.
• State service levels carefully so the trial does not create broader ongoing obligations than intended.
• Include termination rights, handover steps, return of equipment and what happens after expiry.
• Make sure marketing statements and trial results are handled in a way that does not create misleading expectations.

What Pilot Agreement Means For New Zealand Businesses

A pilot agreement is usually the bridge between early sales conversations and a full commercial contract. For a New Zealand business, it can reduce risk on both sides, but only if the document reflects the reality of the trial.

In practice, a pilot agreement is often used where one party wants proof before committing. That might be a software company trialling its platform with an enterprise customer, a hardware supplier installing devices at one location, or a service provider testing a new process for a fixed period.

Why businesses use a pilot agreement

The main value is clarity. A pilot lets the parties test performance, rollout effort, customer response and internal fit without locking themselves into a long term arrangement too early.

For suppliers, a pilot can help convert a cautious prospect into a signed customer. For customers, it can lower the risk of buying something that does not work in their environment.

That said, a pilot is still a contract. Even where the commercial trial is informal in tone, legal obligations can arise once services are provided, equipment is installed, or business information is shared.

When a pilot agreement is the right document

A pilot agreement usually makes sense where the trial is temporary, limited in scope and designed to evaluate a future relationship. It is especially useful before you sign a long form master services agreement, supply agreement or licensing deal.

It is often the right fit where the arrangement includes:

• a fixed trial period, such as 30, 60 or 90 days
• a limited user group, location or business unit
• special trial pricing or waived fees
• evaluation criteria or reporting obligations
• installation, testing or support obligations that are different from normal operations

If the deal is already fully commercial and ongoing, a pilot agreement alone may be too light. In that case, the parties may need a fuller contract from the start, or a pilot agreement that sits alongside core terms for supply, licensing or services.

How New Zealand law affects commercial trials

New Zealand contract law generally allows businesses to agree their own terms, but the wording matters. Courts usually look at what the parties actually agreed, not what one side says it expected later.

That is why founders get caught when they rely on an email promise that the pilot will “roll into” a 12 month deal if things go well. Unless the contract clearly sets out conversion terms, pricing and triggers, there may be no automatic right to ongoing work.

Other New Zealand legal rules may also be relevant depending on the pilot. If services are supplied to a consumer or consumer-like user, the Consumer Guarantees Act may affect rights and remedies. If your pilot marketing makes claims about performance, the Fair Trading Act can become relevant. If personal information is collected, shared or analysed during the trial, the Privacy Act 2020 needs attention.

Industry-specific requirements can also matter. A fintech pilot, health tech trial, education platform test or pilot involving physical devices in regulated premises may need extra checks before you sign. The key point is that calling something a “pilot” does not switch off ordinary legal obligations.

Legal Issues To Check Before You Sign

The legal detail in a pilot agreement should match the real commercial risks of the trial. If the arrangement touches live systems, customer data, physical sites or business critical processes, a one page trial letter is rarely enough.

Scope and deliverables

The agreement should say exactly what is being tested and what is not included. This is where founders often get caught, because broad sales language creates expectations that the pilot was never designed to meet.

The scope should cover:

• the product, service or solution being trialled
• the sites, departments, users or devices included
• implementation steps and who is responsible for them
• support hours, response times and maintenance windows
• any exclusions, assumptions or customer dependencies

If customisation, integration or onboarding work is required, spell it out. Otherwise, one side may treat those tasks as included while the other sees them as extra chargeable work.

Term and evaluation period

A pilot agreement should have a clear start date and end date. Open ended trials create confusion, especially where the supplier keeps providing services after the initial test period ends.

You should also set the review process. For example, the contract can state when meetings happen, who signs off on the evaluation, and whether either party can extend the pilot by written agreement.

If the parties want a future rollout to be negotiated later, say that clearly. Do not imply a guaranteed next phase unless you are prepared to commit to it.

Fees, discounts and costs

Even a “free” trial needs pricing language. The agreement should state whether fees are waived, reduced or deferred, and who pays for implementation, travel, equipment, third party licences, shipping or removal costs.

The commercial terms should address:

• whether the pilot fee is refundable or non-refundable
• whether trial pricing applies only during the pilot term
• whether the customer must pay if usage exceeds agreed limits
• whether any future rollout pricing has been agreed, or is still subject to negotiation

This point matters because businesses often give discounted pilot rates expecting a later full rollout, then discover the customer treats the trial price as the benchmark for the long term deal.

Intellectual property and feedback

Ownership should be explicit. In most pilots, each party keeps ownership of its pre-existing intellectual property, while new feedback and learnings are dealt with in a tailored way.

You may want the agreement to cover:

• who owns software, documentation, processes, data models and reports created before the pilot
• who owns any custom work created during the pilot
• whether the supplier can use feedback, suggestions and test results to improve its product
• whether the customer can keep using pilot materials after the trial ends

If the pilot involves branding, testimonials, logos or case studies, include express consent rules. Do not assume that positive feedback can be used in marketing.

Confidentiality, privacy and data use

Many pilot projects involve access to sensitive operational information. The agreement should protect confidential information and explain what happens to data during and after the trial.

Where personal information is involved, check whether either party is collecting, storing, accessing or processing information about identifiable individuals. If so, the contract should align with the Privacy Act 2020 and the actual data flows in the pilot.

Key questions include:

• what categories of data will be shared or accessed
• whether personal information is involved
• where the data will be stored, including any offshore providers
• how long the data will be retained
• what security standards and access controls apply
• what happens to the data when the pilot ends

If the supplier is processing data on the customer’s behalf, the pilot agreement may need data processing style obligations. That can include instructions on use, security, incident reporting and deletion or return of information.

Liability, warranties and risk allocation

A pilot agreement should not leave liability to chance. The right position depends on the value and risk of the trial, but both sides should understand who bears loss if the pilot fails, causes disruption or creates a claim from a third party.

Typical clauses deal with:

• limits on total liability
• exclusions for indirect or consequential loss
• indemnities for certain third party claims
• warranties about authority, compliance and performance
• allocation of risk for damage to equipment or site access issues

Before you accept the provider’s standard terms, check whether the liability cap is realistic. A cap set at the pilot fee may be too low in some cases. On the other hand, a supplier may not want to take enterprise-level risk for a small paid trial.

Termination and exit

The agreement should make ending the pilot straightforward. Trials often stop early because the product is not a fit, internal priorities change, or technical integration proves harder than expected.

The exit section should cover:

• termination for convenience, if either party wants flexibility
• termination for breach, insolvency or security concerns
• notice periods
• return or removal of equipment
• handover of data, reports and materials
• final fees and expense reconciliation

This is especially important where physical hardware has been installed at the customer’s premises or staff have been trained around the pilot workflow.

Conversion to a full commercial deal

A pilot agreement should say clearly whether there is any obligation to move to a broader contract after the trial. Most pilots do not automatically convert, and that is often the safer position unless all major commercial terms have already been settled.

If the parties do want a conversion mechanism, the contract should identify the trigger and the key economics. Leaving that point vague can lead to disputes over whether the pilot was only exploratory or effectively a commitment to proceed.

Common Mistakes With Pilot Agreement

The biggest mistake is treating a pilot as too small to need proper legal drafting. Pilot disputes usually come from unclear expectations, not bad intent.

Using vague success criteria

If success is described in loose language like “satisfactory performance” or “positive results”, the parties may disagree later about whether the pilot worked. Set measurable criteria where possible.

That might include uptime targets, usage levels, processing speeds, reduction in manual work, customer adoption rates or completion of agreed milestones. The right criteria depend on the product and the customer’s business context.

Letting the trial drift beyond the end date

Many commercial trials quietly continue after expiry. The supplier keeps servicing the account, the customer keeps using the product, and nobody signs a longer term contract.

That creates uncertainty around payment, support, liability and termination. If the pilot has value, either extend it in writing or move to a full agreement.

Relying on verbal promises about rollout

Founders often invest heavily in a pilot on the assumption that the customer will buy at scale if the test succeeds. Unless the contract says so, there may be no obligation to expand, purchase minimum volumes or sign a longer term deal.

Before you spend money on setup, check whether the customer has actually committed to anything beyond the trial period.

Ignoring data and privacy issues

Businesses sometimes treat trial data as low risk because the arrangement is temporary. That is a mistake. Personal information can still trigger privacy obligations even in a short pilot.

It also matters whether the supplier can use pilot data to train systems, improve analytics or produce benchmark reports. If that use is intended, say so clearly and ensure it matches the parties’ privacy position.

Copying a standard services agreement without adapting it

A long form supply contract may be too heavy for a pilot, but a generic services template can also be the wrong fit. Pilots need clauses that deal with testing, evaluation, trial pricing and expiry.

The right document is usually a tailored middle ground. It should be short enough to sign quickly, but specific enough to prevent predictable disputes.

Forgetting practical site and access issues

If the pilot involves on-site work, equipment installation or access to the customer’s premises, practical details need to be documented. Otherwise, disputes can arise over access times, health and safety responsibilities, insurance obligations and damage to property.

Where third party vendors or subcontractors are involved, the agreement should also say who manages them and who is responsible for their conduct.

FAQs

Is a pilot agreement legally binding in New Zealand?

Yes, if the usual elements of a contract are present and the terms show an intention to create legal obligations. Calling it a pilot, trial or proof of concept does not make it non-binding.

Should a pilot agreement be free?

Not necessarily. Some pilots are unpaid, some are discounted, and some are fully paid. The better question is whether the pricing reflects the work, risk and resources involved, and whether the contract states the commercial position clearly.

Who owns data generated during the pilot?

That depends on the contract. The agreement should say who owns raw data, reports, analytics, derived insights and feedback, and what each party can do with them after the pilot ends.

Can a pilot agreement automatically convert into a long term contract?

It can, but only if the agreement says so with enough detail to be workable. Many businesses prefer the pilot to end automatically unless a separate full agreement or service agreement is signed.

Do we need a separate privacy clause for a software pilot?

If the pilot involves personal information, yes, privacy terms should be addressed properly. The clause should reflect who controls the information, how it is used, where it is stored and what happens if there is a privacy incident.

Key Takeaways

• A pilot agreement is a binding commercial contract, not just a trial arrangement based on goodwill.
• The contract should clearly define the scope, term, pricing, evaluation criteria and exit process.
• Data use, confidentiality, intellectual property and privacy issues need careful drafting, especially for software and technology pilots.
• Risk allocation matters even in a short trial, so review liability caps, warranties, indemnities and termination rights before you sign.
• Do not rely on verbal promises about a future rollout. If conversion to a longer term deal matters, put the trigger and key terms in writing.
• If you are reviewing or negotiating a pilot agreement and want help with contract review, scope and pricing terms, privacy and data clauses, liability caps, or termination rights, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.