Salsox

SOWs and RFPsAgreement

Software development statement of work (SOW) template

Define a software build precisely enough to deliver and accept it: the features in and out of scope, milestones, how each is tested and accepted, how changes are requested, and how fees follow the milestones.

Opens in the Salsox editor with 6 signing fields already placed for Supplier and Client. Add their emails and send. The free plan sends 3 documents a month.

Who signs

  • Supplier (you)
  • Client

Preview

Statement of Work SOW-07

Date: 24 October 2026 Supplier: Kernel and Co. Software Ltd Client: Harvest Grocers Inc.

This statement of work is issued under the Master Services Agreement dated 3 March 2026. If they conflict, the master agreement prevails, except where this SOW expressly says otherwise.

1. Objective

a mobile app for iOS and Android that lets customers order groceries for same-day pickup at any of the client's 14 stores.

2. Scope

In scope: customer accounts and sign-in; product search and browsing from the client's existing catalogue API; basket and checkout with card payment through the client's Stripe account; pickup slot selection; order status notifications; and an admin screen for store staff to mark orders ready.

Out of scope: delivery to customers' homes, loyalty points, changes to the catalogue API, and content entry.

3. Milestones and fees

MilestoneDeliverable, date and fee
1clickable prototype and approved designs, by 30 November 2026, EUR 18,000
2working beta in test app stores with all in-scope features, by 15 February 2027, EUR 54,000
3public launch in both app stores, by 31 March 2027, EUR 28,000

Each milestone fee is invoiced on acceptance of that milestone.

4. Acceptance

The Client will test each milestone against the scope within 10 business days of delivery, and either accept it or list the defects that stop it meeting the scope. The Supplier will fix listed defects and redeliver. A milestone is accepted when the Client confirms it, or when the acceptance period ends without a list of defects.

5. Client responsibilities

The Client will provide access to the catalogue API and a test Stripe account by 9 November 2026, a named product owner available for a weekly review, and app store developer accounts. Delays in these move the milestone dates by at least the same time.

6. Change requests

Either party may propose a change in writing. The Supplier will estimate its effect on fees and dates within 5 business days. A change takes effect only when both parties sign it.

7. Team

The Supplier will provide a delivery lead, two mobile engineers, a backend engineer and a designer. The Supplier may change team members with notice, keeping equivalent skills.

8. Warranty

For 60 days after launch, the Supplier will fix, at no charge, defects that stop the app working as described in the scope.

Signatures

For the Supplier: Signature · Supplier Date: Date · Supplier Name: Name · Supplier

For the Client: Signature · Client Date: Date · Client Name: Name · Client

These templates are general starting points, not legal advice. Laws differ between countries and states: check that a template suits your situation, or ask a lawyer, before you rely on it.

About the Software development statement of work (SOW) template

A statement of work turns "build us an app" into something that can be delivered, tested and paid for. It sits under a master services agreement, which covers the legal terms, and describes one project: what will be built, what will not, when each milestone is due, how the client checks it, and what it costs.

This template is built around acceptance, the step most often skipped. Each milestone has a set period for the client to test it against the scope, and silence after that period counts as acceptance, so a milestone cannot stay open indefinitely. Defects found in testing are fixed at no charge; new ideas go through a written change request with their cost and schedule impact before anyone starts work.

The out-of-scope list is as important as the in-scope one. Writing down what will not be built is the cheapest way to avoid disputes about what was promised.

Signers
2
Signing fields placed
6
Details to fill in
15

How to use this template

  1. Open it in Salsox

    Choose Use this template. Sign up free if you have no account; the template opens straight after.

  2. Fill in the details

    Type your details into each blank, or start from the sample to see how it reads. Save it as your own template to reuse it.

  3. Add signers and send

    The editor already has every signature, date and initials field in place. Add each signer's email and send; they sign on their phone, and everyone gets the sealed copy with its audit trail.

Used in

Questions

What is the difference between a SOW and a contract?

A master agreement sets the legal terms for the relationship, such as liability, ownership and payment terms. A SOW describes one specific project under it. One master agreement can have many SOWs.

What if the client wants a new feature mid-project?

It goes through the change request process in section 6: the supplier estimates the cost and schedule impact, and work starts only once both sides sign the change.

When is a milestone accepted?

When the client confirms it meets the scope, or when the acceptance period ends without the client reporting defects that stop it meeting the scope.

Related templates

See all templates

Send it for signature in minutes

Start from this template in Salsox: fill in the blanks, add your signers and send by email, WhatsApp or SMS. Signers sign one field at a time on their phone, and you can collect a payment in the same step.