Getting a website built is exciting - it’s often the moment your business starts to feel “real”. But it can also be one of the easiest places for misunderstandings (and cost blowouts) to creep in.
A Website Development Agreement is the contract that sets out what your developer is building, how much it will cost, when it will be delivered, and who owns what at the end. In other words, it’s the document that helps keep your website project on track and your business protected from day one.
This article is updated to reflect the kinds of website builds we commonly see now (from Shopify and WordPress sites to custom builds, integrations, and ongoing support) and the legal risks NZ businesses are facing in modern online trading.
What Is A Website Development Agreement (And What Does It Actually Do)?
A Website Development Agreement is a legally binding contract between you (the client/business owner) and the person or agency building your website (the developer).
It’s different from a simple quote or email thread because it pulls everything into one place and makes it enforceable. If something goes wrong, it gives you a clear reference point for:
- What was promised (features, pages, integrations, functionality)
- How changes are handled (scope changes, extra fees, timeframes)
- Who owns the deliverables (code, design files, content, licences)
- What happens if there are delays (and who is responsible)
- What happens if the relationship ends early (handover, termination, payment)
Even when you have a great developer, having the agreement in place helps you avoid the classic “we thought you meant…” problem.
Is A Quote Or Email Chain Enough?
Sometimes a quote plus email acceptance can form a contract in New Zealand, especially if it’s clear and both parties intend to be bound. But in practice, quotes and email threads often:
- don’t clearly define what “done” looks like
- don’t deal with IP ownership (a big one)
- don’t cover testing, acceptance, or bug fixes properly
- don’t set out how ongoing support will work
- leave you stuck when there’s a dispute about scope or payment
If you’re investing meaningful time or money into a website, a proper agreement is usually the smarter move.
When Do You Definitely Need One?
Not every website project needs a 30-page contract - but there are some clear scenarios where a Website Development Agreement is a must-have.
You should strongly consider having one in place if:
- The project cost is significant (especially if you’re paying in milestones or deposits).
- Your website is revenue-critical (ecommerce, bookings, subscriptions, paid leads).
- You’re building custom functionality (integrations with CRMs, payment gateways, accounting software, inventory systems, membership portals).
- You’re relying on third-party platforms (Shopify apps, WordPress plugins, API integrations) and need clarity on what’s included.
- You need the website by a specific date (launch, promotion, opening date, campaign).
- You’re providing confidential info (customer lists, business processes, admin access, pricing, supplier details).
- You want to own the site (not be locked into one agency forever).
Even for smaller builds, having the basics covered (scope, fees, timelines, IP, and handover) can save a lot of stress later.
A Common Scenario We See
Imagine you hire a developer to build a “simple” site. Halfway through, you realise you need:
- online booking
- an email marketing integration
- automated invoices
- SEO setup
- a mobile performance fix
Without a contract that explains how variations work, your original quote can become meaningless - and you can end up with a website you can’t launch without paying a lot more than you expected.
What Should A Website Development Agreement Include?
A well-drafted Website Development Agreement should reflect how web projects actually work - including changes, iterations, content delays, and testing.
Here are the key clauses and schedules you’ll usually want to include.
1. Scope Of Work (The “What”)
This is where you clearly describe what the developer will deliver. Ideally, the agreement will include a detailed scope or statement of work that covers:
- number of pages and page types (home, about, service pages, product pages, blog)
- design approach (template-based vs custom)
- required functionality (forms, ecommerce, booking, membership, portal access)
- integrations (payment providers, accounting software, marketing tools)
- hosting and domain responsibilities (who sets them up, who pays)
- content responsibilities (who writes copy, who supplies images, who uploads products)
If scope is vague, disputes are more likely - because “website build” can mean very different things to different people.
2. Timeframes, Milestones, And Client Responsibilities
Web projects commonly stall because the business owner can’t provide content or approvals quickly enough - and then everyone disagrees about who caused the delay.
A good agreement will set out:
- milestone dates (design, first build, testing, launch)
- review and approval timeframes
- what you must provide (logos, brand guidelines, images, copy, product lists)
- what happens if approvals are delayed
This isn’t about blaming anyone - it’s about keeping expectations realistic and the project moving.
3. Fees, Deposits, And Variations
This section should clearly cover:
- total price or pricing model (fixed fee vs time-based)
- deposit amount
- milestone payments
- what triggers an extra charge (scope changes, extra revisions, new features)
- what happens if you pause or cancel the project
Variation clauses are especially important because it’s normal for your requirements to evolve as you see the website take shape.
4. Intellectual Property (IP) Ownership
This is one of the biggest reasons to use a proper Website Development Agreement.
Without clear IP terms, you may not automatically own:
- the website code
- custom designs and visual assets
- copywriting and content created by the developer
- graphics, icons, or templates
Your agreement should clarify what you own once you’ve paid, what the developer retains (for example, reusable tools or pre-existing code), and what third-party licences apply (such as themes and plugins).
If your brand is a key business asset, it’s also worth thinking about trade mark protection early - for example, your business name, logo, or tagline. If that’s on your radar, Trade Mark protection can help you avoid copycats as you grow.
5. Testing, Acceptance, And Bug Fixes
What counts as “finished”? That’s where acceptance criteria come in.
Your agreement can include:
- what browsers/devices must be supported
- what “bugs” are included in fixes (and for how long after launch)
- how you’ll report issues
- what issues are outside scope (new features vs genuine defects)
This avoids the awkward situation where you think you’ve paid for a functioning website, but the developer thinks the build is complete and any changes are extra.
6. Hosting, Access, Admin Rights, And Handover
At the end of the project, you should be able to run your website without being “held hostage” by ongoing access issues.
A good agreement will clearly cover:
- who owns/controls the domain name
- who controls hosting accounts
- handover of admin logins (CMS, plugin accounts, analytics, email)
- delivery of key files (backups, design files where relevant)
This is also where you can include obligations around basic training (e.g. how to update products or publish blog posts).
7. Confidentiality And Data Security
Your developer may access sensitive business information - including admin access, customer enquiries, payment system settings, and marketing accounts.
Confidentiality terms help ensure that:
- your commercial information isn’t shared
- your logins are handled securely
- data is only used for the project
If confidentiality is particularly important (for example, you’re building something innovative or working with customer datasets), you may also consider a separate Non-Disclosure Agreement before the project begins.
What Other Legal Issues Come With Launching A Website In New Zealand?
Building the website is one thing. Operating it legally is another.
If your website is customer-facing (especially if you sell online or collect personal information), you’ll want to make sure your legal foundations are set up properly.
Consumer Law And Online Sales
If you sell products or services to consumers in New Zealand, you’ll need to make sure your website doesn’t mislead customers and that your sales practices are compliant.
Two key laws to keep in mind are:
- Fair Trading Act 1986 (you can’t mislead customers in advertising, pricing, or claims).
- Consumer Guarantees Act 1993 (consumers have automatic guarantees for certain purchases, and you can’t contract out of them in most consumer situations).
This isn’t just a legal issue - it affects how you present pricing, refunds, delivery timeframes, and product descriptions.
Many businesses use website Website Terms And Conditions (or ecommerce terms) to clearly explain things like payment, shipping, refunds, cancellations, and liability limits (where allowed).
Privacy Law And Customer Data
If your website collects personal information (like names, emails, phone numbers, addresses, or payment details), the Privacy Act 2020 will likely apply.
Even if you’re “just collecting enquiries”, you should think about:
- what information you collect and why
- where it’s stored (and who can access it)
- whether you use third-party tools (analytics, email marketing platforms, CRMs)
- how people can request access or correction of their information
In most cases, having a clear Privacy Policy on your site is a practical step that helps you be transparent and build trust with customers.
Ongoing Support And Maintenance (Don’t Leave This As A Handshake)
Websites aren’t “set and forget”. You might need ongoing work like:
- security patches
- plugin updates
- bug fixes
- content updates
- performance improvements
If the developer will provide ongoing support, it’s worth capturing that in writing too - sometimes as part of the Website Development Agreement, and sometimes in a separate ongoing services arrangement (with clear response times, fees, and what’s included).
Should You Use A Contractor Agreement Or A Website Development Agreement?
This is a common question, especially when you’re hiring a freelance developer.
A Website Development Agreement is usually project-specific and focused on deliverables, IP ownership, timelines, and launch.
A Contractor Agreement is broader and can cover a longer working relationship, including confidentiality, IP, invoicing, and expectations about how the contractor works with you.
If you’re engaging a freelancer and want to make sure the relationship is set up properly (including that they’re genuinely an independent contractor and not an employee), it may make sense to use (or pair it with) a Contractor Agreement.
And if your website project is being managed as part of broader marketing services (SEO, ads, branding, ongoing campaigns), you might also want a more comprehensive services arrangement - so that the website is only one part of the overall scope.
What If I’m Using A Website Agency?
Agencies often have their own standard terms. Sometimes they’re solid. Sometimes they’re heavily one-sided (for example, limiting their responsibility for delays while still requiring you to pay on time, or keeping ownership of key assets).
Before signing, make sure you understand:
- whether you’ll own the website when it’s complete
- whether you can move the site to another provider later
- what happens if you terminate early
- whether ongoing hosting/support is mandatory
If you’re unsure, it’s usually worth getting the terms reviewed - it’s far cheaper than trying to unwind a messy arrangement later.
Key Takeaways
- A Website Development Agreement helps protect you by clearly setting out scope, timelines, costs, IP ownership, and what happens if the project changes or ends early.
- Quotes and email chains can be too vague for website builds, especially when you add integrations, ecommerce, or custom functionality.
- Clear IP terms are essential so you actually own what you pay for (and aren’t locked into a developer or agency).
- Your website also needs to operate legally, including compliance with consumer law (like the Fair Trading Act 1986 and Consumer Guarantees Act 1993) and privacy obligations under the Privacy Act 2020.
- If you’re hiring a freelancer, you may also need a Contractor Agreement to properly structure the relationship and protect your business.
- Legal documents should be tailored to your actual website project - a generic template can easily miss the details that matter.
If you’d like help putting the right Website Development Agreement in place (or reviewing one you’ve been given), reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.
