What a good project brief / SOW should include
Timeline, milestones, payment structure, change-request process — a template for buyers and founders.
The short answer
A good brief describes outcomes; a good SOW (Statement of Work) describes deliverables, timeline, payments, and how changes are handled. Both should be written before build starts — verbal agreements cause the disputes you are trying to avoid.
Use the template sections below in a doc or Notion page. Send to 2–3 agencies for comparable quotes.
Project brief — what to include
Copy this structure:
- 1. Background — Company, industry, what prompted this project now.
- 2. Goals — 2–3 measurable outcomes (leads, bookings, operational time saved).
- 3. Audience — Who uses the site/app; geography; languages.
- 4. Scope overview — Website, web app, e-commerce, AI, integrations — high level.
- 5. Must-have features — Non-negotiable list.
- 6. Nice-to-have / Phase 2 — Explicitly out of v1 unless budget allows.
- 7. Design direction — References, brand assets, tone.
- 8. Content — Who provides copy, photos, translations.
- 9. Integrations — CRM, payments, WhatsApp, ERP, analytics.
- 10. Timeline — Hard deadlines and why.
- 11. Budget range — Rough band so agencies respond realistically.
- 12. Success criteria — How you will judge launch in 90 days.
SOW — what the agency should put in writing
Your signed SOW or contract should cover:
- Parties and project name — Legal entities, contacts.
- Deliverables — Page list, features, platforms (responsive, browsers).
- Exclusions — What is explicitly not included.
- Milestones — Discovery, design approval, dev, content, UAT, launch dates.
- Acceptance criteria — What “done” means per milestone.
- Payment schedule — e.g. 30% kickoff, 30% design sign-off, 30% pre-launch, 10% post-launch.
- Revision policy — Number of design/dev rounds included.
- Change request process — How extras are quoted and approved.
- IP and handover — Code repo, credentials, file formats at completion.
- Warranty period — Bug fixes included for X days post-launch.
- Support/retainer — Optional ongoing terms.
- Termination — Notice, payment for work completed, handover on exit.
Example milestone table
Typical website project — adjust for your scope:
- Week 1–2 — Discovery + sitemap + wireframes. Payment: 30%.
- Week 3–4 — Visual design + client approval. Payment: 20%.
- Week 5–8 — Development + content integration. Payment: 30%.
- Week 9 — QA, fixes, training. Payment: 10%.
- Week 10 — Launch + 14-day warranty. Payment: 10%.
Change requests — keep it boring
All changes after signed SOW go through a simple log: description, impact on time/cost, written approval from both sides. No approval, no build. This protects you and the agency.
Gaps that cause disputes
- “Responsive” assumed but not stated.
- Content entry — 10 pages assumed, you have 40.
- Hosting/domain — who registers, who pays renewal.
- SEO — basic setup vs ongoing campaign confused.
- Training — one hour assumed, team needs half day.
- Third-party fees — plugins, APIs, WhatsApp BSP not mentioned.
Next steps
Draft your brief using section 1, send to agencies, compare SOWs side by side — not only total price.
Our proposals follow this structure by default. Ask any vendor that does not.
Need help with this?
We build what this guide describes.
Tell us about your business and timeline — honest scope and quote, usually within one business day.
Contact Zulo Labs