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.
Yes, you usually should have a contract for a paid trial project - even if the work is small, friendly or only meant to test the waters.
The slightly trickier part is choosing the right kind of contract. A paid pilot or proof of concept often sits in the middle: it's more serious than an informal test, but not quite a full long-term customer agreement yet.
That gap is where misunderstandings tend to happen. Who owns the work? What exactly are you delivering? Can the customer use the results if they don't continue? What happens if the pilot works and they want to roll it out properly?
A short, tailored service agreement for the trial project can keep things simple while still protecting the value you're creating.
Do I Need A Written Agreement For A Paid Pilot?
Yes, if money is changing hands or you're sharing valuable information, you should put the pilot in writing before work starts.
A paid pilot is usually designed to prove whether your product, service or method works for a particular customer. That means both sides are taking on some commercial risk. You might be giving early access to technology, building a customised workflow, reviewing confidential data or spending time on strategy that the customer could later use.
A written agreement helps you avoid awkward conversations later about:
- Scope: what you're doing, what you're not doing and how many revisions or meetings are included.
- Fees: the price, payment timing, GST treatment and what happens if the customer wants extra work.
- Intellectual property: who owns the materials, reports, software, code, designs, learnings or improvements.
- Confidentiality: what information needs to stay private during and after the pilot.
- Next steps: whether either side gets a right to continue, negotiate or move into a larger contract.
Without a written agreement, you may still have a contract based on emails, messages or conversations. The problem is that it's much harder to prove the details if memories differ later. A short agreement gives everyone a shared reference point from day one.
Is A Trial Project Agreement Different From A Full Customer Contract?
Yes, it can be different because a trial project agreement is usually narrower, shorter and focused on testing a specific outcome.
A full customer contract often covers ongoing supply, service levels, renewals, account management, detailed support obligations, longer liability settings and termination rights. A pilot agreement usually doesn't need all of that. It should be practical and proportionate to the size of the project.
That said, a paid trial shouldn't be so casual that it misses the big-ticket issues. If your pilot involves access to customer systems, business data, pre-release software, designs, brand materials or sensitive commercial information, a one-page email may not be enough.
When A Short Pilot Agreement Usually Works
A shorter agreement may be enough where:
- the pilot has a clear start and end date
- the deliverables are limited and easy to describe
- the fee is modest compared with your usual projects
- neither side is committing to a long-term relationship yet
- you don't need complex service levels or implementation obligations
When You May Need Something More Detailed
You may need a more detailed agreement if the pilot involves:
- integrating with the customer's live systems
- handling personal information under the Privacy Act 2020
- creating new software, code, training materials or branding assets
- giving the customer access to your confidential methodology
- using the customer's logo or results in marketing
- a clear pathway into a larger roll-out if the trial succeeds
The goal isn't to overcomplicate the deal. It's to match the document to the real risk and value of the work.
What Should A Paid Trial Project Contract Include?
A paid trial project contract should clearly set out the commercial deal, the boundaries of the pilot and what each side can do with the results.
You don't need a 30-page contract for every proof of concept. But you do need enough detail that a person who wasn't in the sales calls could read it and understand what has been agreed.
Fill-In Outline For A Trial Project Agreement
Here is a practical outline you can use to plan the agreement. This isn't a finished legal document, and a lawyer should tailor it before you use it.
- Parties: write the correct legal names, NZBNs if available and contact details for notices.
- Purpose: describe what the pilot is testing and what success is meant to show.
- Scope Of Work: list the deliverables, tasks, meetings, access needed and anything excluded.
- Timeline: set the start date, end date, milestones and any dependency on the customer providing information.
- Fees And Payment: state the amount, whether GST is included or added, invoice timing and payment due date.
- Changes: explain how extra work, extra users or extended timing will be approved and charged.
- Intellectual Property: say who owns existing IP, new materials, improvements, outputs and any licence to use them.
- Confidentiality: cover business information, pricing, methods, data and results shared during the pilot.
- Privacy And Data: set rules for personal information, security, access, deletion and breach handling if data is involved.
- Customer Responsibilities: list what the customer must provide, such as data, access, feedback or staff time.
- Use Of Results: say whether either side can publish case studies, testimonials or performance numbers.
- Next-Step Rights: explain whether the pilot leads to an option, proposal, preferred pricing or no obligation to continue.
- End Of Pilot: set out what happens to access, materials, unpaid fees and confidential information when the trial ends.
Templates can be a useful starting point, but they often miss the clauses that matter most for your business model. A software pilot, consulting pilot and product testing arrangement may all need different wording.
Who Owns The IP In A Proof Of Concept?
It depends on what the contract says, so your agreement should be very clear about IP ownership and use rights.
Under New Zealand copyright law, copyright often sits with the person or business that creates the work, unless there's an assignment or another rule applies. Trade marks are dealt with separately through IPONZ registration and brand use rights. For practical purposes, don't rely on assumptions about who owns what.
In a paid pilot, there are usually a few different types of IP to separate:
- Your background IP: the tools, templates, software, know-how, frameworks or methods you already had before the pilot.
- The customer's background IP: their brand, data, systems, content, customer information or internal processes.
- New project materials: reports, dashboards, designs, code, training materials, recommendations or prototypes created during the pilot.
- Improvements and learnings: updates to your product, new features, methods or insights developed while running the trial.
For example, say Aria runs a Wellington SaaS startup. She agrees to a 6-week paid pilot with a retailer for $4,500 plus GST. During the pilot, she configures her existing platform, builds two custom reports and improves her onboarding workflow after seeing how the retailer's team uses the tool.
A sensible IP clause might say Aria keeps ownership of her platform, methods and general improvements, while the retailer gets a limited licence to use the custom reports for the pilot and any agreed roll-out. If the retailer wants to own particular deliverables outright, that should be priced and documented upfront.
This matters because IP is often the most valuable part of a pilot. If the wording is vague, you may accidentally give away more than you intended or make it harder to reuse your own improvements with future customers.
What About Confidentiality, Privacy And Customer Data?
Yes, you should cover confidentiality and privacy if the pilot involves business information, personal information or access to systems.
A pilot can feel low-risk because it's temporary, but the information shared during a trial can be highly sensitive. You might receive customer lists, pricing, sales data, employee information, login access, product roadmaps or internal performance data.
Your agreement should say:
- what counts as confidential information
- who can access it within your business
- what you can use it for
- how long confidentiality obligations last
- whether information must be returned or deleted at the end
- whether you can mention the customer publicly
If personal information is involved, the Privacy Act 2020 becomes relevant. You should think about why you're collecting the information, how you'll keep it secure, whether you'll use any offshore tools or subcontractors and what you'll do if there's a privacy breach.
If the pilot involves consumer-facing claims, marketing results or performance promises, the Fair Trading Act 1986 also matters. Don't overstate what the pilot will achieve. If you say your platform will reduce admin time by 40%, you need a reasonable basis for that claim.
For some business-to-business contracts, you may also deal with the Consumer Guarantees Act 1993, including whether certain guarantees are being contracted out of where the law allows. This wording needs care, especially if your customer might use the goods or services in a way that isn't purely business use.
How Should Fees, Timing And Next-Step Rights Work?
Your contract should make the money, timing and post-pilot pathway specific, because these are the points that often cause friction.
Start with fees. State whether the price is fixed, hourly, milestone-based or partly credited against a future customer contract. In New Zealand, be clear whether amounts are inclusive or exclusive of GST, which is currently 15%. If you're GST-registered and quoting business customers, many agreements say fees are plus GST, but the wording should match how you invoice.
You should also say when invoices are issued and when they're due. For example:
- $2,000 plus GST on signing
- $2,500 plus GST after delivery of the pilot report
- payment due 7 days after each invoice
- extra workshops charged only if approved in writing
Next, deal with timing. If the pilot depends on the customer giving you access, data or feedback, say so. This protects you if the customer delays the project but still expects the original deadline.
Finally, think carefully about next-step rights. You might include:
- No obligation to continue: either side can walk away after the pilot.
- First right to negotiate: both sides agree to discuss a full roll-out before the customer uses a competitor.
- Pre-agreed pricing: the full contract price or discount is locked in for a set period.
- Conversion credit: part of the pilot fee is credited against a larger contract if signed within a certain time.
- Limited use after expiry: the customer must stop using trial access or outputs unless a new agreement is signed.
If you're an individual consultant, or you're engaging an individual to help deliver the pilot, also watch the contractor versus employee issue. Under the Employment Relations Act 2000 and the 2026 contractor gateway test changes, a written contractor agreement can help, but labels alone won't fix a working arrangement that functions like employment. Get tailored advice if the person will work under your direction, use your tools and be closely integrated into your business.
How Much Does A Paid Pilot Agreement Cost?
The cost depends on how tailored the agreement needs to be, the value of the pilot and the risk areas it needs to cover.
A free template is usually the cheapest option, but it can be risky if it doesn't match your actual pilot. Many templates are built for general service agreements and don't deal properly with proof-of-concept issues like limited use of results, product access, trial data, conversion rights or IP in improvements.
An online fixed-fee legal service can be a good middle option if you want a tailored agreement without hourly billing uncertainty. You should expect the scope to be clear before work starts, including what document will be prepared, how many rounds of changes are included and whether the legal team will explain the key clauses to you.
A traditional firm billing by the hour may suit more complex pilots, especially if the customer is a large organisation with its own procurement process, cyber security requirements or detailed contract mark-ups. The trade-off is that the final cost can be harder to predict.
What drives the cost most is usually:
- how technical or regulated your service is
- whether personal information or sensitive data is involved
- whether new IP will be created
- whether the customer wants ownership of deliverables
- whether you need standard terms you can reuse for future pilots
- how much negotiation is expected
For many startups and consultants, the best approach is a short pilot agreement that can be adapted for repeat use, with room to add a simple statement of work or service level agreement for each new customer.
Key Takeaways
- A paid trial project should usually have a written contract, even if the pilot is small or friendly.
- A pilot agreement can be shorter than a full customer contract, but it still needs to cover scope, fees, IP, confidentiality and next steps.
- Be clear about who owns existing IP, new deliverables and improvements developed during the proof of concept.
- If customer data or personal information is involved, build in privacy, security and deletion obligations from the start.
- Fees should spell out GST, invoice timing, payment due dates and how extra work will be approved.
- Templates can help you plan, but a tailored agreement is safer when the pilot involves valuable IP, data or a possible roll-out.
If you'd like help with your paid pilot agreement, proof-of-concept terms, IP clauses or customer data protections, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.







