Free template
A specification you can accept against.
The structure we use for a Statement of Work, as a template you can fill in. Each section is written so that every line can be tested on the day the work is delivered.
Inside the template
Eleven sections, one page each at most.
- Purpose. The problem this solves and how the work is done today.
- Users and roles. Who uses it and what each role may see or change.
- Platforms. Where it runs.
- What users can do, with acceptance criteria. One line per task, each with a test you can run.
- Data the software keeps. The records, who owns them and who may see them.
- Integrations. What goes in, what comes out, who holds the account.
- Out of scope for this block. What will not be built now.
- Timing and constraints. Deadlines, languages, hosting and devices.
- How the work will be accepted. Who tests, against what, and what happens if an item fails.
- Agreed in writing before work starts. Costs outside the hourly rate, and ownership.
- Open questions. Anything not yet decided.
Prefer to answer questions? The specification starter builds a first draft from your answers.
Related
From specification to acceptance
ProcessHow a block is acceptedEach item in the specification is tested by QA, then by you, before any invoice.GuidesGuides on specifications and scopeHow to write lines that can be tested, and what to leave for a later block.Free callWalk through your draft with usA free 30 minute call to go over the specification and size the first block.
Start with a conversation
Tell us what you want built. We will tell you plainly whether it fits.
The first conversation is free. You get a rough size in hours, the tier that suits the work, and what a first 150 hour block would cover.
Or get a ballpark proposal in two minutes