The SOW is where most outsourcing disputes are won or lost. Vague phrases such as "a user-friendly admin panel" invite disagreement; specific deliverables with acceptance criteria, such as which roles exist and what each can do, give both sides the same definition of done.
An SOW should also state what is out of scope, who provides content, access and test data, how changes are requested and approved, and how acceptance works. On time and materials engagements, the SOW describes the team, rates and reporting rather than a fixed feature list.
Scope and deliverables
What will be built, and what is explicitly excluded.
Milestones and timeline
When each deliverable is due and how payment links to it.
Acceptance criteria
How each side will agree that a deliverable is complete.
Change process
How new requests are estimated, approved and billed.
Codazz builds this in production — Software Outsourcing.