Black Friday10% off any legal service

SaaS Statement Of Work Template For Custom Builds

byAlex Solo10 min read

Mei runs a Wellington SaaS company that helps gyms manage bookings and memberships. A new client signs up, then asks for a Xero integration, a custom reporting dashboard and a member migration from an old system. Everyone is excited, so work starts quickly.

Four weeks later, the client says the dashboard is missing three reports they assumed were included. Mei's developer says those reports were never scoped. The invoice is due, but the client doesn't want to pay until the extra work is finished.

This is exactly where a clear SaaS statement of work can save you a lot of stress. It turns a promising project into a shared plan, so your team and your client know what is included, what isn't, when payment is due and how changes will be handled.

What Is A SaaS Statement Of Work?

A SaaS statement of work, often called an SOW, is a project document that sets out the exact implementation, integration or custom development work you'll do for a client.

It usually sits under a broader SaaS agreement, master services agreement, software development agreement or implementation agreement. The main agreement covers the bigger legal relationship, while the SOW deals with the practical details of a particular project.

For example, your main SaaS contract might cover:

  • access to your platform
  • subscription fees and payment terms
  • support and service levels
  • privacy and data protection
  • liability limits
  • termination rights

Your SOW then covers the specific build or implementation, such as:

  • what features, integrations or configuration work you'll deliver
  • what data the client must provide
  • the project timeline and milestones
  • how testing and sign-off will work
  • what counts as out-of-scope work
  • how extra work will be quoted and approved

The SOW shouldn't replace your main contract. Instead, it should work with it. If the two documents say different things, your contract should explain which one wins. That small detail can avoid big arguments later.

For a New Zealand software business, a clear SOW also helps support your position if questions come up under the Fair Trading Act 1986. You don't want sales conversations, proposals or project documents to overpromise what your system or team will deliver.

Do You Need A Separate SOW For Custom Software Work?

Yes, if you're doing implementation, integration or custom build work, you should usually use a separate SOW because the project details change from client to client.

A standard SaaS subscription is often repeatable. Custom work isn't. Even if two clients ask for a CRM integration, their data fields, approval process, legacy systems and internal team capacity may be very different.

A separate SOW is especially useful when you're doing any of the following:

  • custom software development
  • API integrations
  • data migration
  • onboarding and implementation
  • workflow configuration
  • bespoke reporting or dashboards
  • training or change management
  • proof-of-concept or pilot projects

Without a written SOW, you may struggle to show where the agreed work ended and where extra work began. That can make it harder to recover unpaid invoices, manage a delayed project or push back on a client who keeps expanding the brief.

It's also helpful for your team. Developers, product managers and customer success staff can all work from the same source of truth, rather than relying on sales notes or Slack messages.

You don't need a 40-page document for every project. For a small implementation, your SOW might be short. For a high-value custom build, it should be much more detailed. The point is to match the document to the risk, complexity and value of the work.

What Should A SaaS Statement Of Work Template Include?

A SaaS statement of work template should include the project scope, deliverables, timeline, fees, testing process, assumptions, dependencies, change request process and IP position.

Templates can be a useful starting point, but they often miss the details that actually cause problems in software projects. Before you use one with a client, it's worth having it reviewed and tailored to how your business sells, builds, tests and supports software.

SaaS SOW Fill-In Outline

Here is a practical outline you can use when preparing your own custom software SOW. Treat this as a drafting checklist, not as a finished legal document.

  1. Parties And Project Name: Write the legal names of your business and the client, plus a clear project title.
  2. Background: Briefly explain the business problem, the client's goals and how the project connects to your SaaS platform.
  3. Scope Of Work: Describe the configuration, development, integration, migration, training or implementation services agreement details you'll provide.
  4. Deliverables: List each deliverable separately, with enough detail to tell whether it has been completed.
  5. Out-Of-Scope Items: State what isn't included, such as new modules, unsupported systems, data cleansing or extra reports.
  6. Milestones And Timeline: Set out key dates, project stages and what must happen before the next stage begins.
  7. Client Dependencies: List what the client must provide, such as test data, system access, approvals and subject matter experts.
  8. Fees And Payment: Explain fixed fees, time-based fees, milestone payments, expenses and when invoices are due.
  9. Acceptance Testing: Set out how testing works, who signs off, what counts as a defect and when acceptance is deemed to occur.
  10. Change Requests: Explain how changes are requested, costed, approved and added to the timeline.
  11. IP Ownership And Licensing: State who owns existing IP, custom code, configurations, documentation and reusable tools.
  12. Data, Privacy And Security: Cover any personal information, access controls, security terms, test environments and data handling rules.
  13. Support And Handover: Explain what support is included after go-live and what moves into your usual SaaS support process.
  14. Order Of Priority: Say how the SOW interacts with your SaaS agreement or master services agreement if there's an inconsistency.

If your project involves personal information, the Privacy Act 2020 is likely to matter. For example, if you're migrating customer records or employee data, your SOW should match your privacy policy and data processing commitments.

How Do You Stop Scope Creep In A Software Development Scope Of Work?

You stop scope creep by defining the deliverables clearly, listing what's excluded and requiring written approval before extra work starts.

Scope creep usually happens gradually. A client asks for a small wording change. Then an extra field. Then a new report. Then the project has doubled in size, but the fee and timeline haven't changed.

Your SOW should make it easy to say, politely and confidently, yes, we can do that as a change request.

Worked Example

Say Tane runs a SaaS company in Auckland that provides inventory software to wholesalers. He agrees to build a custom dashboard for a client for a fixed fee of $18,000 plus GST, with delivery in 6 weeks.

The SOW says the dashboard will include:

  • 5 sales reports
  • 1 inventory ageing report
  • CSV export
  • 2 rounds of feedback on the dashboard layout

It also says that additional reports are out of scope and must be approved through a change request.

In week 4, the client asks for 4 new supplier performance reports. Tane's team estimates this will take 24 extra hours and push the go-live date by 8 business days. Because the SOW is clear, Tane can send a change request stating the added cost, extra time and revised milestone date. The client can then approve it, reduce the request or leave it for a later phase.

Without that SOW, Tane may feel pressured to absorb the extra work to keep the client happy. That can hurt your margins and your team's workload.

Practical Scope Controls To Include

  • Detailed deliverables: Avoid vague descriptions like custom dashboard. Say what screens, reports, fields or workflows are included.
  • Assumptions: State what you're relying on, such as the client's API being available and documented.
  • Exclusions: Name common extras that aren't included, such as data cleansing, third-party licence fees or legacy system fixes.
  • Approval limits: Say who can approve changes on the client's side.
  • Written change requests: Don't start extra work based only on a phone call.

How Should Acceptance Testing And Milestones Work?

Acceptance testing and milestones should give your client a fair chance to test the work, while protecting you from endless review cycles.

For custom SaaS projects, payment is often tied to milestones. That can work well, but only if each milestone is objectively described.

A strong milestone clause might cover:

  • what you must deliver at each stage
  • what the client must review
  • how long the client has to test or respond
  • what happens if the client doesn't respond
  • what counts as a defect compared with a change request
  • when the next invoice can be issued

For example, your SOW might give the client 5 business days to test a staging version after you notify them that a milestone is ready. If they report a genuine defect within that period, you fix it. If they ask for a new feature, it goes through the change request process. If they don't respond within the review period, the milestone is treated as accepted.

Be careful with the word bug. Not every client complaint is a bug. A useful SOW separates:

  • Defects: The deliverable doesn't meet the agreed specification.
  • Changes: The client wants something different or additional.
  • Third-party issues: A delay or failure caused by another system, vendor or API.
  • Client delays: The client hasn't provided data, approvals or access needed for the work.

This approach keeps testing practical. It also helps your accounts team, because milestone acceptance can trigger invoicing without needing a fresh debate each time.

Who Owns The IP In Custom SaaS Development?

It depends on what your contract says, so your SOW should be clear about what the client owns, what you keep and what the client is licensed to use.

IP is a big issue in custom SaaS work because you're often building on your own platform, codebase, libraries, processes and know-how. If the SOW simply says the client owns all IP in the deliverables, you may accidentally give away more than you intended.

A more practical approach is to separate different types of IP:

  • Your pre-existing IP: Your SaaS platform, source code, tools, templates, frameworks, documentation and internal know-how.
  • Client materials: The client's data, logos, brand assets, content and business materials.
  • Project deliverables: Configurations, custom reports, workflows or code created for the project.
  • Reusable improvements: Ideas, fixes, features or learnings you may want to use for other clients.

Many SaaS providers keep ownership of the platform and reusable development work, then give the client a licence to use the deliverables as part of the SaaS service. That may be the right model for your business, but it depends on what you're selling and what the client is paying for.

Copyright will usually be relevant to software code and documentation. Trade marks may also matter if you're using your product name, logo or client branding. In New Zealand, trade mark registrations are handled through IPONZ. Your SOW doesn't need to become an IP textbook, but it should avoid uncertainty about who can use what after the project ends.

If your client is asking for ownership of custom code, source code access or an exclusive feature, get tailored advice before agreeing. Those commitments can affect your product roadmap and your ability to serve other clients.

Your SaaS implementation agreement should cover the wider legal relationship, while the SOW covers the project details.

If you're using a master agreement or SaaS terms plus SOW model, make sure the two documents fit together. The SOW shouldn't quietly override important protections in your main terms unless you mean it to.

For New Zealand SaaS providers, the main agreement will often deal with:

  • Payment terms: Subscription fees, implementation fees, GST, late payment consequences and suspension rights.
  • Consumer and business law: How the Consumer Guarantees Act 1993 and Fair Trading Act 1986 apply, especially if any client could be treated as a consumer or small trade customer.
  • Privacy: Responsibilities under the Privacy Act 2020, including how personal information is collected, used, stored and disclosed.
  • Confidentiality: How each party protects business, technical and customer information.
  • Security: Access controls, user permissions, audit logs, hosting and incident processes.
  • Service levels and support: Uptime commitments, support channels, response targets and exclusions.
  • Liability limits: Caps, exclusions and carve-outs that match the risk of the project.
  • Termination: When either party can end the contract and what happens to data, access and unpaid fees.

Your SOW can then refer back to those terms instead of repeating them. For example, the SOW might say all data migration work is subject to the security and privacy obligations in the main agreement.

If you work with contractors to deliver implementation services, make sure your contractor agreements line up too. From 2026, changes to the Employment Relations Act 2000 include a contractor gateway test for certain working arrangements. If your delivery model relies heavily on contractors, it's worth checking that your contracts and day-to-day practices are consistent.

Key Takeaways

  • A SaaS statement of work sets out the practical project details for implementation, integration or custom development work.
  • Your SOW should work alongside your SaaS agreement or master services agreement, not replace it.
  • Clear deliverables, exclusions, milestones and acceptance testing are the best tools for managing scope creep.
  • Change requests should be written, costed and approved before extra work starts.
  • IP ownership needs careful drafting so you don't accidentally give away your platform, reusable code or product improvements.
  • Privacy, data security and fair trading obligations should be reflected in your project documents, especially where personal information or client data is involved.

If you'd like help with your SaaS statement of work, implementation agreements, change request process or IP and privacy terms, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.

Drafted by Taylor, Sprintlaw's AI, and overseen by Alex Solo. How we write

Protect your brand

What intellectual property should you protect?

If a name, logo, design or other creative work matters to the business, check who owns it, what permissions you need and whether clearance or registration is appropriate.

Alex Solo
Alex SoloCo-Founder

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.

Protect your brand

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.