Client Proposal, SOW & Contracting Playbook

The proposal sells the engagement — it's persuasive, references the client's specific situation, and doesn't need to be exhaustively precise. The SOW governs the engagement — it's the operational and legal reference both parties will point to if there's a dispute, so ambiguity there is expensive.

As detailed as the inclusions list, if not more. List every adjacent piece of work a reasonable client might assume is included — implementation support after a strategy phase, for example — and state explicitly whether it's in or out.

Use fixed fee when the scope and deliverables can be defined precisely and the client wants budget certainty; use time & materials when the work is exploratory or the scope will likely evolve based on early findings, and consider a capped T&M structure as a middle ground.

Frame it as protecting them as much as you — it prevents scope from expanding informally in ways that inflate the fee without a conversation. Most resistance disappears once you show the form takes minutes to complete and requires their explicit approval before any additional cost is incurred.

A template is fine for the SOW's operational content — scope, deliverables, fees — but the underlying Master Services Agreement covering liability, IP ownership, and termination should be reviewed by a lawyer at least once, then reused as boilerplate across engagements rather than redrafted each time.