Reference

Templates and checklists

Part of the Proposal Sow Writing skill · loaded on demand from SKILL.md

Read this when producing any of the documents below. Placeholders in square brackets are permitted here and nowhere in a worked example or client document. Delete any section that would not change the client's decision.

1. Buyer map and qualification sheet

Client: [name] | Revenue: [ ] | Sector: [ ] | Trigger event: [what changed and when]
Economic buyer (signs): [name, role, what they are measured on]
Sponsor (owns the engagement day to day): [ ]
Mobilizer (sceptic with standing who can drive consensus): [ ]
Talkers (friendly, informative, cannot mobilise): [ ]
Blockers and their reason: [ ]
Procurement role: [none / reviews / runs RFP] | Competing bidders: [ ]
What the client believes the problem is: [their words]
What they have tried: [ ]
Our hypothesis about the problem: [one sentence]
What they believe that is probably wrong: [one sentence]
Budget signal: [ ] | Decision date: [ ] | Win probability: [ ] percent
Pursue: yes / no. If yes, the advance we want from the first meeting: [ ]

2. Discovery record (one per meeting)

Meeting [n] | Date | Attendees and roles | Format | Duration
Situation facts confirmed (only those not available elsewhere):
- [ ]
Problems surfaced (client's words, attributed by role):
- "[ ]" ([role])
Implications (cost, who else affected, consequence of delay; client's numbers):
- [problem] -> [consequence], "[client's number]"
Explicit needs stated (verbatim, with number and time frame):
- "[ ]"
Insight candidates (what they do not know that we might):
- [ ]
Advance obtained (who does what by when):
- [ ]
Open questions for the next meeting:
- [ ]

3. Insight statement

Write it as one paragraph, then test it.

[Client] believes [current framing]. [Data point 1, from the client's own figures]. [Data point 2, benchmark or pattern]. [The reframe: what the problem actually is]. [Value at stake, as a range, with the basis]. [Why this leads to a different engagement than the one they asked for].

Tests: at least two numbers; at least one is the client's own; a competitor could not truthfully say it; if true, it changes what the client should buy.

4. Proposal (insight-led)

Eight to twelve pages. Order matters: the client reads the insight before the credentials.

[Firm]. Proposal to [Client]: [title that names the outcome, not the method]. [Date]. Prepared for [names, roles].

### 1. Your situation and what we found
[Two paragraphs: the situation as the client sees it, then the insight statement. A table of levers with today / target / annual value if the reframe is quantitative. One sentence on what companies that acted on this have done.]

### 2. Objectives
In your words:
1. [Explicit need 1, with number and time frame]
2. [Explicit need 2]
3. [Explicit need 3]

### 3. Approach
[Duration], [n] phases, a steering committee decision at the end of each.
Phase 1, [name] (weeks [ ]). [What is done. The key questions answered.] Gate: [decision the steering committee makes].
Phase 2, [name] (weeks [ ]). [ ] Gate: [ ].
Phase 3, [name] (weeks [ ]). [ ] Gate: [ ].

### 4. Deliverables
| Decision enabled | Artefact | When |
|---|---|---|
| [ ] | [ ] | Week [ ] |

### 5. Team
[Name, role. One sentence on why this person, tied to a workstream. Time commitment.]
From [Client] we ask for: [sponsor; steering members; counterpart with time allocation; data; access].

### 6. Timeline
Kick-off [date]. Gates [dates]. Cadence: [steering committee at gates; weekly working session].

### 7. Fees
Option A, [model]: [amount] for [scope], payable [schedule tied to gates]. Expenses [policy and cap].
Option B (if offered), [model]: [ ].
[One sentence relating the fee to the value at stake.] [One sentence on how scope changes are handled.]

### 8. Why [Firm]
[One page at most: the two or three facts that make this firm the right one for this problem. References.]

### 9. Next steps
We propose to meet on [date] with [names] to [decision], and to sign the statement of work by [date] so that the team can start on [date].

5. Statement of work, with clause notes

The notes after each clause say what it protects against and what to check. Remove the notes before sending.

Statement of Work between [Firm] ("[Firm]") and [Client] ("[Client]"), under the Master Services Agreement dated [ ]. Effective [date].

1. Background and objectives
[Two sentences of background; the objectives from the proposal, incorporated by reference or restated.]
Note: objectives must be the client's explicit needs. If they drift here, the whole SOW drifts.

2. Scope
In scope: [units of analysis, sites, business units, time periods, levers].
Out of scope: [the things the client is most likely to ask for later, named specifically].
Any out-of-scope item may be added by change order under clause 11.
Note: write the out-of-scope list from the discovery records: every "while you're here" you heard belongs on it.

3. Approach and phases
[As in the proposal.] Each phase ends with a steering committee at which [Client] may continue, redirect or stop. If [Client] stops at a gate, fees for completed phases are payable and fees for subsequent phases are not.
Note: this clause is what makes the fee divisible; without it a stop is a dispute.

4. Deliverables and acceptance
[Table as in the proposal.] [Client] will accept in writing or state specific deficiencies within [5] business days; a deliverable not rejected in writing within [5] business days is accepted. [Firm] will remedy stated deficiencies within the phase's scope at no charge.
Note: deemed acceptance protects the payment schedule; the remedy sentence protects the client.

5. Team and substitution
[Named team.] [Firm] will not replace [partner, engagement manager] without [Client]'s consent, not unreasonably withheld; others may be substituted with equivalent experience on [5] business days' notice.
Note: the client is buying named judgment; say whose.

6. Timeline
[Dates.] Dates move day for day with delays caused by [Client]'s obligations under clause 9 not being met; [Firm] will notify [Client] within [2] business days of any such delay.
Note: the notification duty is what makes the day-for-day clause enforceable in practice.

7. Fees and payment
[Model and amount.] Invoiced [schedule tied to gates]. Payment within [30] days of invoice.
Note: the signing instalment should cover mobilisation cost for the first phase.

8. Expenses
[At cost / included / fixed percentage], capped at [amount] without prior written approval, invoiced monthly with receipts.

9. Assumptions and [Client] obligations
(a) [data by date]; (b) [system access]; (c) [named counterpart and time allocation from week n]; (d) [interviewee availability within n days]; (e) [steering committee decisions at the meeting or within n days]; (f) [pilot sites and participation].
Where an assumption is not met, the effect on timeline and fee is handled under clause 11.
Note: each item here corresponds to days in the economics sheet. If you cannot say which days depend on it, either the assumption or the estimate is wrong.

10. Governance
Steering committee: [names; chair; sponsor]. Working session: [weekly; who]. Escalation: [engagement manager to sponsor within n day; partner to economic buyer within n days].

11. Change control
Either party may request a change to scope, timeline or team. [Firm] will log the request within [2] business days and provide effort (days by role), fee at [standard / contracted] rates ([rates listed]), and effect on timeline. Requests under [n] consultant-days may be approved by the sponsor; larger requests require steering committee approval. No change work begins before written approval. Approved changes are recorded in a change order appended to this SOW.
Note: the four questions the clause must answer: who requests, who sizes and at what rates, who approves and at what threshold, what happens to the timeline.

12. Confidentiality and intellectual property
As in the MSA. [Firm]'s methods, tools and templates remain [Firm]'s property; [Client] receives a perpetual licence to use them internally. Deliverables specific to [Client] are [Client]'s property on payment.

13. Termination
[Client] may terminate at any gate on written notice, paying fees for completed phases and expenses to date. Either party may terminate for material breach on [15] days' notice if uncured. On termination [Firm] delivers all work in progress.

Signatures.

Leave liability caps, indemnities, insurance, governing law and dispute resolution to the MSA.

6. Engagement economics worksheet

Engagement type (brains / grey hair / procedure): [ ]
Firm parameters: margin floor [ ] percent | target [ ] percent | billable days per year used for loaded cost [ ]

### Weekly staffing grid (days)
| Role (name) | W1 | W2 | ... | Wn | Total |
|---|---|---|---|---|---|
| Partner | | | | | |
| Engagement manager | | | | | |
| Consultant | | | | | |
| Analyst | | | | | |
| Contingency (rate basis, phase) | | | | | |
| Total | | | | | |

### By role
| Role | Rate/day | Cost/day | Days | Fee at rack | Cost |
|---|---|---|---|---|---|
| ... | | | | | |
| Total | | | [ ] | [ ] | [ ] |

### By phase
| Phase | Days by role | Days | Fee at rack | Cost |
|---|---|---|---|---|
| ... | | | | |

### Price
| Anchor | Value | Basis |
|---|---|---|
| Cost floor | [cost / (1 - floor)] | |
| Target-margin price | [cost / (1 - target)] | |
| Rack reference | [days x rate] | |
| Value ceiling | [fraction x annual value at stake] | |
| Client budget signal | [ ] | |

Proposed fee: [ ] | Model: [ ] | Discount to rack: [ ] percent
Contribution: [fee - cost] | Margin: [ ] percent | Fee as share of annual value: [ ] percent
Payment schedule: [instalments tied to gates; must sum to fee]
Sensitivity: one-week slip in [most uncertain phase] adds [days] and [cost]; margin becomes [ ] percent.
Reconciliation: role total days = phase total days = grid total; role fee = phase fee; instalments sum to fee. [confirmed]

7. Fee-model decision table

QuestionIf yesIf no
Is the scope well-defined and has the firm done this before?Fixed fee by phaseTime and materials with a cap for phase 1; fix later phases at the gate
Is the outcome measurable, attributable and baselined before signing?A success component is possible (fixed base must cover cost)No success component; use value-based pricing of a fixed fee if value is sizeable
Does the client want budget certainty?Fixed feeTime and materials
Is the value at stake large relative to effort (brains engagement)?Price toward the value ceilingPrice near the rack reference
Is this ongoing access rather than a project?Retainer with stated inclusionsProject fee

8. Change order

Change order [CO-nn] | Date raised | Raised by
Requested change (what and why now):
Effect on scope (clause 2 amended: in / out):
Effort: [role] [days] at [rate] = [fee]; total [fee]
Effect on timeline and gates:
Effect on assumptions and client obligations:
Effect on engagement economics: fee [ ], cost [ ], contribution [ ], margin [ ] percent
Decision: approved / declined / deferred | By | Date

9. Pre-submission checklist

  • Page one teaches the client something, with at least two numbers, one of them theirs.
  • A competitor could not truthfully write the insight paragraph.
  • Each objective quotes an explicit need from a discovery record.
  • Deliverables are decisions enabled, artefacts in brackets.
  • Every phase ends with a gate and the payment schedule has an instalment at each gate.
  • Economics reconcile by role, by phase and by instalment.
  • Margin after contingency is at or above the firm floor.
  • Fee is stated as a share of annual value at stake and the share is defensible.
  • Every SOW assumption maps to days in the economics sheet.
  • Change control names who requests, who sizes at what rates, who approves at what threshold, and what happens to the timeline.
  • Partner days are budgeted at real cost.
  • Why-us section is after the fees and one page or less.
  • Next steps name a date, a meeting and the decision-makers.
  • Nothing in the SOW contradicts the proposal.
  • No seats, licences, plans, per-month pricing or go-live: if present, this is a product sale and is a product sale, not an engagement.
  • Storyline through executive-communication if the proposal is over eight pages.