Alex is a co-founder of Sprintlaw. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.
Do you really need a contract for a trial software pilot? Yes, in most cases you do - even if the pilot is unpaid, short, or being run with a friendly first customer.
A pilot can feel lighter than a full SaaS rollout. You might be testing features, proving ROI, or giving a customer limited access before they commit. But the moment you give access to your platform, customer data, internal systems, confidential information or your product roadmap can come into play.
The good news is that a software pilot agreement in NZ doesn't have to be long or complicated. It just needs to make the trial clear, controlled and safe, often through a tailored pilot agreement, while you work out whether the full deal should go ahead.
Do I Need A Software Pilot Agreement In NZ?
Yes, you should usually have a written software pilot agreement before access is granted. A pilot agreement sets the rules for the trial period before you've agreed the full SaaS contract.
This matters because pilots often sit in an awkward middle ground. You're not just having a sales conversation anymore, but you may not be ready to sign a full master services agreement or SaaS subscription agreement either.
A pilot agreement can deal with questions like:
- who gets access to the software and for how long
- whether the pilot is paid, unpaid or discounted
- what data can be uploaded, used, exported or deleted
- whether support, onboarding, implementation services or custom setup is included
- who owns feedback, improvements and any new IP
- what happens if the customer wants to go live after the pilot
Without a written agreement, you may end up relying on emails, sales decks and meeting notes. Those can help, but they often leave gaps. For example, one person may think the pilot includes integrations and unlimited support, while the other thinks it only covers sandbox access.
If you're the SaaS provider, a pilot agreement helps you protect your product, limit your exposure and keep the trial commercially sensible. If you're the customer, it helps you confirm what you're getting before you let a new tool near your team, data or systems.
Is A Pilot Agreement Different From A SaaS Agreement?
Yes, a pilot agreement is usually shorter and more limited than a full SaaS agreement because it's designed for testing, not long-term use.
A full SaaS agreement normally covers ongoing subscription terms, service levels, renewals, billing cycles, acceptable use, data processing, liability, support, security, termination and other long-term issues. It assumes the software is being used as part of your business operations.
A pilot project contract is different. It usually focuses on a defined test period, limited users, limited data and a clear outcome. It might say that the customer can only use the software to evaluate whether it meets agreed use cases, not to run their whole business.
Common Pilot Structures
Your pilot might be set up as:
- an unpaid proof of concept: the customer gets limited access to test technical fit or internal interest
- a paid pilot: the customer pays a setup fee, monthly fee or fixed trial fee
- a discounted early customer pilot: access is cheaper because the customer is helping you test features or provide feedback
- a pre-go-live implementation trial: the customer has committed in principle, but wants a staged rollout before the full subscription starts
The right document depends on the structure. A free template may not pick up the difference between a sandbox demo and a paid pilot involving live customer data. That's why pilot documents work best when they're tailored to how your software is actually being used.
What Should A Proof Of Concept Agreement Cover?
A proof of concept agreement should cover the test scope, access rights, data handling, IP ownership, fees and what happens at the end of the trial.
Here is a practical outline you can use as a starting point. This isn't a finished legal document, and you should have it tailored before you use it, but it shows the clauses you should be thinking about.
- Parties: write the correct legal names, NZBNs where relevant, and contact details for notices.
- Pilot Purpose: describe what the trial is designed to test, such as user adoption, technical integration, API access or reporting accuracy.
- Pilot Period: state the start date, end date and any extension process.
- Access And Users: list who can use the software, user limits, admin rights and login controls.
- Fees And Payment: set out any setup fee, monthly fee, invoice timing, GST treatment and what happens if payment is late.
- Data Access: explain what data can be uploaded, who can access it, where it may be hosted and when it will be returned or deleted.
- Privacy And Security: cover privacy responsibilities, security standards, breach notification and any customer policies you need to follow.
- IP And Feedback: confirm who owns the software, customer materials, feedback, custom work and pilot learnings.
- Confidentiality: protect product information, pricing, business information and customer data.
- Support And Service Levels: state what support is included and whether uptime targets apply during the pilot.
- Limitations And Exclusions: set practical limits on liability, warranties, production use and consequential loss.
- End Of Pilot: explain whether access ends, data is exported, the full SaaS agreement starts, or the parties agree a new contract.
If the pilot is business-to-business, you may also need to think about the Consumer Guarantees Act 1993. In some B2B contracts, businesses can contract out of certain guarantees where both parties are in trade and the contract meets the legal requirements, including that it's fair and reasonable. That wording needs care.
How Should You Deal With Data, Privacy And Security?
You should deal with data, privacy and security clearly before any real customer or staff data is uploaded. For many software pilots, this is the highest-risk part of the arrangement.
Under the Privacy Act 2020, personal information needs to be collected, used, stored and disclosed in line with the Information Privacy Principles. If there's a notifiable privacy breach, the Privacy Commissioner and affected people may need to be notified.
Your pilot agreement should explain:
- what categories of data can be used in the pilot
- whether live data, dummy data or de-identified data is required
- who can access the data within each organisation
- whether data will be stored in New Zealand or overseas
- what security measures apply, such as MFA, encryption or access logs
- what happens if there's a suspected data breach
- how data will be returned, deleted or retained after the pilot
Say you run a HR SaaS platform and a customer wants to test it with 25 employees for 60 days. If they upload names, job titles, leave balances and performance notes, you're handling personal information. Your pilot agreement should say whether that information can be used for product improvement, whether your support team can access it, and when it will be deleted after the trial.
As the provider, don't promise more than your systems can actually deliver. If you can't guarantee New Zealand-only hosting, don't say you can. If you're the customer, check whether your own privacy notice and internal policies let you use personal information in the pilot.
Who Owns The IP In A SaaS Pilot?
The SaaS provider usually keeps ownership of the software, while the customer keeps ownership of its own data, materials and business information. The tricky part is feedback, configurations and new features.
In New Zealand, copyright protection arises automatically for original software code and other qualifying works. Trade marks can be registered through IPONZ to protect brand names and logos, but a pilot agreement won't register those rights for you. What it can do is make sure the trial doesn't accidentally blur ownership.
Your IP clause should cover:
- background IP: what each party already owns before the pilot starts
- customer data: confirming the customer keeps ownership of its uploaded data
- feedback: whether the provider can freely use suggestions, bug reports, ideas and product improvements
- custom work: who owns any integrations, scripts, workflows or reports created during the pilot
- licence rights: what limited rights each party gets to use the other's IP during the pilot
- marketing rights: whether the provider can name the customer in case studies or sales materials
For example, Aroha runs a Wellington-based inventory SaaS business. She offers a paid pilot to a retailer for $2,000 setup plus $500 per month for two months. During the trial, the retailer suggests a new reporting dashboard and Aroha's team builds it into the platform.
If the agreement says feedback and product improvements belong to Aroha, she can usually reuse that dashboard for other customers. If the agreement is silent, the retailer may later argue the dashboard was built specifically for them. That's the sort of uncertainty you want to avoid early.
What Should Happen At The End Of The Pilot?
The agreement should spell out what happens when the pilot ends, because this is where many trials get messy.
A strong end-of-pilot clause can save awkward conversations later. It should set out whether the pilot automatically stops, converts to a paid subscription, rolls into a separate SaaS agreement, or needs written approval before anything continues.
Common End-Of-Pilot Options
- Hard stop: access ends on a set date unless both sides sign a new agreement.
- Extension: the pilot can be extended for a set period, usually in writing.
- Conversion: the customer can move to a full SaaS subscription on agreed pricing and terms.
- Go-live gate: the parties complete security, onboarding, data migration or procurement steps before full use starts.
If you want an automatic conversion, make it very clear. For example, your agreement might say a 60-day pilot costs $3,000 plus GST, and if the customer doesn't cancel at least 10 business days before the end date, a 12-month subscription starts at $900 plus GST per month. That can be commercially useful, but it needs to be easy to understand and consistent with the Fair Trading Act 1986, which prohibits misleading or deceptive conduct.
If you're the customer, be careful about automatic renewal or conversion wording. You don't want a small trial turning into a 12-month commitment just because no one diarised the end date.
You should also cover data export. If the customer doesn't proceed, will they receive a CSV export, API export, data licence rights, or no export because the data was only dummy data? Spell it out.
Can I Use Software Trial Terms And Conditions Instead?
Sometimes, yes, but standard software trial terms and conditions may not be enough for a serious pilot involving data, integrations, fees or go-live planning.
Website terms can work well for simple self-serve trials where users click to accept limited access. For example, a 14-day trial of a project management tool with no live business data and no custom setup might be covered by well-drafted trial terms.
A separate signed pilot agreement is usually better where:
- the customer is paying for the pilot
- you're giving admin or production-like access
- live customer, employee or patient data will be uploaded
- there's an integration with the customer's systems
- your team will do onboarding, configuration or custom work
- success criteria or go-live obligations need to be agreed
- the customer has procurement, security or privacy requirements
You can also use both. Your pilot agreement can say it overrides your standard trial terms if there's a conflict, while your standard terms continue to cover everyday platform rules like acceptable use and account security.
As a provider, be careful with sales promises. If your deck says the software will reduce admin time by 40%, or your emails say integration will take one week, those statements can become part of the commercial story. Under the Fair Trading Act 1986, claims should be accurate and not likely to mislead. If the pilot is testing whether a result is achievable, say that clearly.
Key Takeaways
- A software pilot agreement is usually worth having before you grant access, even for a short or unpaid trial.
- The agreement should cover scope, timing, fees, data, privacy, IP, confidentiality, support and end-of-pilot options.
- Privacy needs careful handling under the Privacy Act 2020, especially if live customer or staff data is used.
- IP clauses should clearly separate your software, the customer's data, feedback and any custom work created during the pilot.
- Go-live and conversion terms should be clear so a trial doesn't accidentally become a bigger commitment than either side expected.
- Templates can be a useful starting point, but pilot agreements work best when they're tailored to your product, data flows and commercial plan.
If you'd like help with your software pilot agreements, trial terms, data and privacy clauses or SaaS contract pathway, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.
Get your customer-facing terms right
What should your privacy and online terms cover?
If you collect customer data, sell online or run marketing campaigns, your public terms and privacy documents should match the real customer journey.








