Example only

Example Implementation Sprint SOW

This is an illustrative one-page statement of work. It shows how scope is locked before payment. Real SOWs are written for each engagement and may differ.

Not a guarantee of outcomes. This document defines process, boundaries and deliverables, not rankings, traffic or revenue results.

JimmyTech · Implementation Sprint

Statement of Work (example)

Client
Example Co. (fictional)
Sprint type
Technical SEO Sprint
Fixed price
$3,500-$4,500 AUD (set per scope)
Time box
12-16 hours · delivery within 1-2 weeks

In scope (example)

  • Prioritised technical SEO fixes agreed in the SOW (e.g. indexation, redirects, metadata, schema on agreed templates)
  • Build log of changes shipped
  • Basic verification notes (what to check in GSC / live site)
  • Written handover guide
  • Async questions during the sprint window (reasonable, not unlimited)

Out of scope (typical)

  • Open-ended content production or full site redesign
  • Unlimited revisions or "until it ranks" work
  • Ongoing monthly SEO management
  • Work not listed in the signed SOW

Success criteria (process, not rankings)

  • Agreed in-scope items completed or explicitly deferred in writing
  • Build log delivered
  • Written handover delivered
  • Client has access notes for anything changed

Success here means the scoped work was shipped and handed over, not a promise of search positions or lead volume.

Payment & change orders

  • Work starts after fit confirmation and payment terms agreed (typically full or deposit before start)
  • Material additions = new sprint / change order, not free expansion of this SOW

Handover artefacts (typical)

  1. Scope document (this SOW)
  2. Build log / change list
  3. QA or measurement notes
  4. Written handover
Request a sprint (fit confirmation) Back to packages