Once a proposal is accepted, it's rewritten into a Statement of Work (SOW), the document the entire engagement is managed against from then on. It's the most important document you'll produce in the whole engagement, because almost every dispute that damages a client relationship traces back to something the SOW did or didn't say. A complete SOW carries:
| Component | What it pins down | Why it matters later |
|---|---|---|
| Deliverables | The specific artifacts the client will receive (a diagnostic report, a market-entry recommendation, a workshop) | The reference list every scope-creep test (see scope creep) is run against |
| In-scope / out-of-scope | What is explicitly included and explicitly excluded | Excludes are as important as includes — silence is not an exclusion |
| Assumptions & dependencies | What the client must provide (data access, stakeholder time, a decision by a date) | When a client dependency slips, the timeline and fee are allowed to move — but only if this section exists |
| Timeline & milestones | Phases and the dates or triggers between them | The pacing skeleton the workplan (see the workplan and the weekly rhythm) is built from |
| Fee & payment terms | The commercial structure, schedule, and what triggers an invoice | Prevents the awkward "wait, when do we pay you" conversation |
| Change control | How a scope change is proposed, priced, and approved | The clause that makes the scope-creep discipline enforceable, not just a norm |
| Governance | Who signs off on what, and the meeting cadence (steering committee, weekly check-ins) | Sets the rhythm CN7.02 will later teach you to run |
Advertisement
How does a statement of work differ from a proposal?
Keep the proposal and the SOW sharply apart, because beginners often blur them. The proposal persuades and the SOW commits. A proposal can be aspirational, even a little bit of a sales document, without lying. A SOW can't. It's the document a court, a client's procurement team or, far more often, an aggrieved client three months from now will reread. Everything that follows in the engagement, from the fee build to the scope-creep test and the workplan, is downstream of what the SOW says. So write it precisely, before the relationship gets busy and informal. It pays for itself the first time a client asks for "just one more thing."
{
"skill": "Drafting a first-pass proposal outline and a matching SOW skeleton from scoping-call notes",
"use": "Have a chat assistant turn rough notes from a client scoping conversation into a structured proposal outline (situation, complication, objective, approach, team, timeline, fee) and a matching SOW skeleton (deliverables, in/out-of-scope, assumptions, change-control clause) as a fast first draft you then rewrite in your own judgment — never a document you send unedited.",
"tools": ["Chat assistants — Claude, ChatGPT, Gemini", "A word processor's built-in AI drafting add-in"],
"prompt": "Here are my rough notes from a scoping call, industry and situation only, no real client specifics: <NOTES>. Draft a one-page proposal outline with these sections: Situation, Complication, Objective, Approach (3-4 workstreams, each with a one-line day-one hypothesis), Team, Timeline, Fee & commercial terms. Then draft a matching SOW skeleton with explicit in-scope and out-of-scope bullets and a change-control clause. Flag anything you had to guess.",
"verify": "Every scope boundary, deliverable, and fee figure the draft invents must be checked against what you actually agreed on the call — a fluent draft can quietly widen or narrow scope in a way that reads fine but does not match reality. Trace every commercial term back to your own notes before anything goes to the client (Guardrail #1 Trace and #2 Match, applied to a proposal instead of a filing).",
"diy": "You must already know what a good proposal argues and what a SOW must contain (this section) well enough to catch a draft that omits the change-control clause or invents a scope boundary nobody discussed. AI drafts the skeleton; you own the commercial commitment.",
"market": "IN"
}