Service Agreements for New Zealand Web Design Agencies

If you run a web design agency in New Zealand, a vague proposal and a few emails are not enough protection once the project gets messy.

The common problems are predictable: clients assume unlimited revisions are included, agencies start work before deposits are paid, and ownership of website files, code, or content is left unclear until the relationship breaks down. Another frequent mistake is relying on verbal promises about timing, scope, or ongoing support, then finding those promises are hard to prove later.

A well-drafted service agreement for web design agency work sets the commercial rules before the project begins. It tells both sides what is being delivered, when payments are due, who owns what, and what happens if the scope changes or the client goes quiet. If you are reviewing your own contract or about to sign a client's standard terms, this guide explains the main clauses to check, the legal issues that matter in New Zealand, and the mistakes that most often lead to fee disputes and project blowouts.

Overview

A service agreement for a web design agency should do more than describe the work. It should allocate risk, set payment triggers, define ownership of deliverables, and deal with practical project issues such as delays, revisions, third party tools, privacy, and post-launch support.

The strongest agreements are usually the ones that match the agency's actual workflow, rather than generic templates copied from another industry.

• define the scope of services, deliverables, exclusions, milestones, and revision limits
• set clear pricing, deposits, payment dates, late payment rights, and change request processes
• state who owns the website design, code, content, licences, and pre-existing intellectual property
• cover client responsibilities, including approvals, content supply, access details, and delay consequences
• address privacy, confidentiality, third party platforms, hosting, and subcontractor use where relevant
• limit liability sensibly and explain termination rights, suspension rights, and handover obligations

What Service Agreements Cover

A good web design contract should spell out the real working arrangement, not just the headline service. Before you sign a contract, the key question is whether the agreement reflects how the project will actually run from discovery through to handover and support.

Scope of work

The scope clause is where most project disputes begin or end. If the description of services is too broad, the client may expect strategy, copywriting, SEO, branding, integrations, testing, training, and ongoing maintenance for the same fixed price.

Your agreement should describe the work in plain terms and separate included items from excluded items. This often includes:

• discovery or strategy sessions
• design concepts and page layouts
• development and build work
• content population
• basic testing
• launch assistance
• maintenance or support, if any

It also helps to expressly say what is not included. For example, a standard website package may exclude copywriting, photography, advanced SEO, third party integrations, custom app development, accessibility auditing, or ongoing security monitoring unless quoted separately.

Deliverables and milestones

The agreement should identify what the client will receive and when. That might be wireframes, design mock-ups, a staging site, final code, training material, or a launch checklist.

Milestones matter because they tie approvals and payments to specific stages. Without them, agencies often keep working while the client delays sign-off, then disputes the invoice because the project does not feel finished.

Useful milestone drafting usually covers:

• when each stage starts
• what counts as completion of that stage
• how long the client has to review and approve
• what happens if the client does not respond in time
• whether approval is deemed after a set period

Fees, deposits, and variations

Your pricing clause should answer the practical money questions before work begins. If you offer fixed fee projects, the agreement should still explain what happens when the scope changes.

Many web design agencies in New Zealand require an upfront deposit before booking work into the schedule. That reduces the risk of unpaid pre-production time and gives a clear signal that the project is confirmed.

A payment clause often covers:

• deposit amount and when it is due
• progress payments tied to milestones
• final payment before launch or file release
• what counts as a variation
• hourly rates or separate fees for out-of-scope work
• late payment consequences, including interest or suspension of work if appropriate

This is where founders often get caught. A client says, “Can we just add one more page?” or “Can you connect one more platform?” Individually those requests sound minor, but together they can wipe out the project's margin unless the agreement gives you a clean variation process.

Client responsibilities

A web design project stalls quickly if the client does not provide content, approvals, access credentials, or technical information on time. Your agreement should say what the client must supply and when.

That can include:

• brand assets and style guides
• website copy and images
• logins for domains, hosting, or CMS tools
• timely feedback and approvals
• confirmation that they have rights to use supplied content

You should also deal with the effect of delay. If the client misses deadlines, the agency may need the right to extend timeframes, reallocate resources, pause the project, or charge recommencement fees.

Intellectual property and licences

Ownership is one of the most important parts of a service agreement for web design agency work. Before you rely on a verbal promise, make sure the contract clearly distinguishes between new project deliverables, third party components, and the agency's pre-existing materials.

In practice, the agreement often needs to separate:

• pre-existing agency intellectual property, such as frameworks, tools, templates, methods, and reusable code
• third party assets, such as plugins, fonts, stock images, themes, and software licences
• client-owned materials, such as logos, content, and brand elements supplied by the client
• new deliverables created specifically for the project

Some agencies assign ownership of final custom deliverables once all fees are paid. Others keep ownership of underlying systems and grant the client a licence to use them. Either model can work, but the contract needs to say so clearly.

It should also deal with what happens if the client stops paying. Many agencies provide that ownership or licence rights do not pass until invoices are paid in full.

Support, maintenance, and hosting

Clients often assume the agency will keep fixing issues after launch unless the agreement says otherwise. The contract should distinguish between initial build work and ongoing support.

If you offer maintenance or hosting, set out the service level in realistic terms. Cover response times, update windows, backup arrangements, client responsibilities, and any exclusions for third party outages or security incidents outside your control.

Legal Issues To Check Before You Sign

Before you accept the provider's standard terms, make sure the legal settings match the risk of the project. The main issues are consumer law style service obligations, truthful marketing, privacy compliance, intellectual property rights, subcontracting risk, and workable liability limits.

Fair Trading and service promises

Your proposals, sales calls, and contract terms should line up. In New Zealand, businesses need to avoid misleading or deceptive conduct and false or unsubstantiated claims under the Fair Trading Act 1986.

For a web design agency, that means being careful with statements about results, timelines, technical capability, or performance outcomes. Promises such as guaranteed rankings, guaranteed conversions, or “fully custom” design should only be used if they are accurate and supportable.

The service agreement should not contradict what was sold. If your quote says launch in four weeks but the contract gives you broad timing flexibility because the client must provide content, that dependency should be made clear upfront as well.

Consumer Guarantees Act and B2B contracting out

Some web design work supplied to business clients may allow contracting out of the Consumer Guarantees Act 1993, but only in certain business-to-business situations and only if the drafting is done properly. If you are dealing with a client who is acquiring services for business purposes, your agreement may include a clause that the parties contract out of that Act to the extent permitted by law.

That point matters because agencies often assume a limitation clause solves everything, when it may not if the surrounding wording is not suitable or the client is not actually acquiring the services for business use. The right drafting depends on the client and project context.

If your agency works with consumers as well as businesses, your contract set should reflect that difference rather than using one form for every job.

Privacy obligations

Privacy issues often arise earlier than agencies expect. If you collect enquiry form data, install analytics, set up email marketing tools, or access customer databases during a build, privacy obligations can become relevant under the Privacy Act 2020.

Your service agreement should say enough about data handling to avoid confusion, especially where the agency may access personal information on the client's systems or through the website being built. Depending on the work, useful clauses may cover:

• what personal information the agency may access
• who is responsible for collection notices and website privacy disclosures or a privacy notice
• how credentials and data will be stored and protected
• whether subcontractors or offshore tools are used
• what happens to data at the end of the engagement

If the agency is building forms, booking systems, or e-commerce features, the broader privacy position should be reviewed alongside the service agreement.

Third party platforms and supplier terms

Most websites depend on external providers. That may include hosting companies, payment gateways, domain registrars, plugin developers, design tool vendors, and cloud platforms.

Your contract should make clear that the agency is not responsible for the terms, outages, licensing restrictions, or service changes imposed by those providers, except to the extent you have expressly agreed to manage them. It should also state whether the client or the agency is entering into those third party contracts.

This is especially important where subscriptions renew automatically or where a third party licence is only valid while the agency continues to manage it.

Subcontractors and contractor status

Many agencies use freelance developers, designers, SEO specialists, or copywriters. Your client agreement should allow subcontracting if that is part of your delivery model.

Separately, your arrangements with those freelancers should confirm that intellectual property is assigned or appropriately licensed to the agency, confidentiality is protected, and the relationship is structured correctly. The client contract cannot fix a gap in your contractor agreement or other contractor paperwork.

Liability limits and indemnities

Liability clauses should be realistic and balanced. The goal is not to avoid every possible responsibility, but to stop a modest project turning into an open-ended claim if the client loses revenue or a third party tool fails.

Many agency agreements deal with:

• caps on liability, often linked to fees paid
• exclusions for indirect or consequential loss
• limits on liability for third party software or services
• client indemnities where the client supplies infringing or unlawful content
• time limits for bringing claims

These clauses need careful drafting. If they are too aggressive or inconsistent with the rest of the agreement, they may create pushback in negotiations or be harder to rely on later.

Common Service Agreement Mistakes

Most web design contract problems come from ordinary commercial shortcuts. Before you sign, the main risk is not usually a rare legal technicality, it is a missing clause on scope, payment, ownership, or delay that creates avoidable confusion later.

Using a generic template

A generic services template often misses the features that make web design projects distinctive. It may not deal properly with revisions, staging sites, launch dependencies, third party tools, or handover of source files and credentials.

If your agreement reads like it was written for a consultant giving advice by the hour, it probably does not fit a design and development workflow.

Leaving scope too open

Agencies often write short descriptions like “design and build a five page website” and assume everyone has the same picture in mind. They rarely do.

The result is scope creep dressed up as ordinary feedback. Revision limits, page counts, functionality specifications, integration assumptions, and excluded work should be spelled out.

Not tying ownership to payment

One of the most expensive mistakes is handing over editable files, code repositories, or full access credentials before final payment is made. If the contract does not reserve ownership or licence transfer until payment, your leverage can disappear quickly.

The handover process should be linked to final invoice clearance, subject to any negotiated exceptions.

Ignoring client delay

Clients often pause for weeks while gathering content internally, then expect the original launch date to stand. If the agreement says nothing about delayed approvals or missing inputs, the agency can end up absorbing the scheduling cost.

A simple delay clause can save a lot of friction. It can allow revised timeframes, project pauses, milestone re-setting, and additional charges where the delay materially affects delivery.

Promising outcomes outside your control

Web agencies sometimes overpromise to win work. Search visibility, conversion rates, ad performance, and system uptime depend on many factors beyond design and development alone.

The contract should frame deliverables around the services you control. If you are not providing SEO, copywriting, hosting, cybersecurity management, or legal compliance advice, say so clearly.

Forgetting post-launch boundaries

The client's assumption after go-live may be that all future fixes are included. Your agreement should define any warranty period carefully and distinguish defects from new work, training issues, content edits, or third party compatibility problems.

If support is separate, the contract should say that clearly and set out how additional services will be quoted.

Relying on email threads instead of a signed contract

Email can help explain the project, but it is a poor substitute for a single signed agreement. Important details end up scattered across proposals, messages, call notes, and attachments, with room for conflicting interpretations.

A signed contract, plus a statement of work or proposal schedule where needed, is usually far easier to manage and enforce.

FAQs

Does a web design agency really need a written service agreement?

Yes. A written agreement helps define scope, payment, ownership, revision limits, and project timing. Without it, disputes usually turn on conflicting expectations rather than clear obligations.

Who owns the website once the project is finished?

That depends on the contract. Some agreements assign final custom deliverables to the client after full payment, while the agency keeps its pre-existing tools and reusable code. Others provide a licence instead of a full transfer.

Can a client demand unlimited revisions if the contract is silent?

If the agreement does not set revision limits, the position becomes much harder to manage. The client may argue that further changes are needed to complete the agreed work. Clear limits and variation clauses are much safer.

Should the agreement cover plugins, fonts, and other third party tools?

Yes. Those items often come with separate licence terms, renewal fees, and usage restrictions. Your contract should say who is responsible for selecting, paying for, and complying with those third party terms.

Can a web design agency limit its liability in New Zealand?

Often yes, but the drafting needs to be appropriate for the client and circumstances. Liability caps, exclusions, and Consumer Guarantees Act wording should be tailored carefully, especially where clients may not all be business customers.

Key Takeaways

• A service agreement for web design agency work should clearly define scope, deliverables, milestones, and what is excluded.
• Payment terms should cover deposits, progress billing, final payment, variations, and rights to pause work for non-payment.
• Intellectual property clauses should distinguish between agency materials, client content, third party assets, and final project deliverables.
• Client responsibilities matter, especially for content supply, approvals, platform access, and delay consequences.
• New Zealand agencies should check Fair Trading Act, Privacy Act, Consumer Guarantees Act, and third party platform issues before they sign.
• Common mistakes include generic templates, vague scope, weak ownership wording, and unclear post-launch support boundaries.
• If you are reviewing or negotiating a service agreement for web design agency work and want help with scope and variation clauses, intellectual property ownership, liability limits, and privacy terms, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.