Full SKILL.md

Proposal Sow Writing

Writes insight-led proposals and statements of work for advisory engagements and checks their economics — buyer map, SPIN discovery, a commercial insight that reframes the problem, phased scope with decision gates, team pyramid and cost sheet, fee-model choice and three-anchor pricing, the proposal, the SOW clause by clause, and change control. Use whenever a client conversation, RFP or inbound request must become an advisory proposal, or someone must scope, phase, staff or price an engagement, or the user says "write a proposal", "draft the SOW", "how should we scope this", "what should we charge", "fixed fee or T&M", "they want a success fee", "build the engagement budget", "prep me for the scoping meeting", "we need a change order". Not for product or software-implementation sales, or for the analysis itself (problem-framing, value-driver-modeling).

Discovery before insight, insight before scope, scope before price, price before prose. Reversing the order produces a beautiful document for an engagement the firm cannot afford to deliver. SPIN (Rackham), Challenger insight selling (Dixon and Adamson), Maister's pyramid and fee-model reasoning are in references/frameworks.md; the question bank by stage and function is in references/spin-question-bank.md.

When not to use

  • Product, subscription or implementation with seats, plans and go-live: not an advisory engagement.
  • The analysis itself: problem-framing, value-driver-modeling; this skill sells and scopes them.
  • The formatted file: docx, pptx after the content exists.

Inputs

Ask for, or infer and label "assumed": the client (name, size, sector, trigger event: new CEO, missed budget, board question, regulatory deadline); buyer map (economic buyer, sponsor, mobilizer, blockers, procurement); what the client believes the problem is, in their words, and what they have tried; discovery notes, transcripts, RFP text; rate card, loaded daily cost by role, target margin, availability of named people; competitive situation (sole-source, shortlist, open RFP); constraints (deadline, budget signals, procurement rules, currency).

Ask one round of questions if the client, the buyer or the rate card is missing. Otherwise proceed with every assumed number marked "assumed" in the economics sheet.

Workflow

  1. Qualify and prepare (references/templates.md §1). Buyer map; find the mobilizer (sceptical, asks hard questions, has standing to drive consensus); friendly contacts who cannot mobilise are where deals die. One-sentence hypothesis about the problem and one-sentence guess at what the client believes that is probably wrong. List facts already known. Decide to pursue with a stated win probability. Test: what does the client currently believe that your work would change?

  2. Discovery with SPIN (references/templates.md §2). Situation questions few (homework done); problem questions until three or four real dissatisfactions surface; implication questions most (what each problem costs, who else it affects, a year of delay); need-payoff questions so the client states the value in their own numbers. End every meeting with an advance (dated next meeting with a decision-maker, data access, agreement to review a draft scope), never a continuation ("send us something"). Done when three to five explicit needs each carry a client-supplied number and an advance is on the calendar.

  3. Commercial insight (references/templates.md §3). One paragraph with at least two numbers that reframes the problem (client thought X, evidence suggests Y), is grounded in data the client recognises, and leads to a capability rivals lack. Test: could a rival say the same? Then it is content marketing. Would the client buy the same engagement without it? Then it is decoration. Structure: warmer, reframe, rational drowning, emotional impact, a new way, your solution.

  4. Scope. At most three objectives, each traceable to an explicit need. Key questions (from problem-framing if run). Phases ending in decision gates where the client can stop, redirect or continue, with fees divisible at the same points. Deliverables named as decisions enabled with the artefact in brackets ("pricing architecture decision (deck and rule book)"). Explicit out-of-scope list. Client obligations with dates. Done when a delivery team could build it and the client could tell when to stop paying.

  5. Staff and cost (references/templates.md §6). Work backward from workstreams: consultant-days per workstream per phase, then roles. Pyramid: partner about a day a week (more in week one and the last week), engagement manager full-time, consultants and analysts on workstreams; as junior as the work permits (brains engagements senior-heavy, procedure engagements leveraged). Weekly staffing grid, days and cost by role, rack-rate fee, contingency, on one sheet that reconciles. Test: whose days are on the critical path, and what does a week's slip cost?

  6. Fee model and price (references/templates.md §7). Choose by scope certainty and outcome measurability; the question is who bears the risk the work runs long. T&M with cap: client bears; uncertain scope, diagnostics. Fixed fee by phase: firm bears; defined deliverables, done before. Retainer: shared; standing access. Value or success fee with fixed base: shared, weighted to firm; outcome measurable, attributable, baseline agreed before signing; avoid when several initiatives touch the metric or the client controls the levers. Two rules regardless: the fixed component covers delivery cost; under fixed fee the firm owns estimation risk, so contingency and change control matter most. Price against three anchors: floor (cost / (1 − minimum margin)), reference (rack rate), ceiling (defensible share of value at stake, typically well under 10%). State the price three ways: margin, share of value, discount to rack. Test: if the client asks for 20% off, what scope comes out? "Nothing" means the price was padded.

  7. Proposal (references/templates.md §4). Page one: the situation as the client sees it and the insight that reframes it. Then objectives in the client's words; approach and phases with gates; deliverables; team with a sentence per person tied to a workstream; timeline; fees and payment schedule with what changes if scope changes; why this firm, one page, after the fees; next steps as a dated advance with a named decision-maker. Tailor by reader: CFO in margin and cash, operations in throughput and headcount, CEO in the decision. Eight to twelve pages. Run executive-communication on the storyline. Test: would the client learn something from page one alone?

  8. SOW (references/templates.md §5). Clause by clause, each preventing a named failure, else cut it: background and objectives (drift); scope in and out (the unpriced third site); phases with gates (cannot stop sensibly); deliverables and acceptance with deemed acceptance after fixed business days (endless revisions); team and substitution (the selling partner disappears); timeline and dependencies (client delay charged to the firm); fees, schedule, expenses (cash lag; signing instalment covers mobilisation); assumptions and client obligations (data in week four); governance (decisions with no forum); change control (silent scope growth); confidentiality and IP; termination and wind-down (stopped mid-phase unbilled). Every SOW assumption has a line in the economics sheet. Legal boilerplate goes to the MSA. Test: a third pilot site in week six: who decides, what does it cost?

  9. Close and keep the scope. Pre-wire with the mobilizer; present live before sending; ask for the decision date in the room. Negotiate scope for price, never price alone ("that number removes the second pilot site, which moves the roll-out decision three months"). Every scope request is a change-control event within 48 hours: log, size, price, steering committee. Done when SOW signed, kick-off dated, change log opened day one.

Output

The insight paragraph first. Then, each once, by request:

  1. Buyer map and qualification sheet
  2. Discovery record with explicit needs and client-stated numbers
  3. Proposal (8–12 pages of content)
  4. Statement of work with clause notes
  5. Engagement economics sheet (staffing grid, cost, fee, contingency, price three ways)
  6. Fee-model decision with reasoning
  7. Change order template where a live engagement is drifting

No method vocabulary, framework authors, skill names or the worked example's client in the deliverable. No seats, licences, per-month pricing or go-live dates; if present, it is a product sale. Full example: references/worked-example.md.

Quality bar

Run silently; fix, do not report.

  1. Every objective traces to an explicit need with a client-supplied number.
  2. The insight fails the "could a rival say this" test.
  3. Every phase ends in a decision gate; fees divide at the gates.
  4. Deliverables are decisions enabled, with artefacts in brackets.
  5. Economics sheet reconciles; every assumed number is marked.
  6. Fixed component covers delivery cost; price stated three ways.
  7. Every SOW clause names the failure it prevents and traces to the sheet.
  8. Page one teaches; the last page is a dated advance.
  9. A 20% discount has a scope answer.
  10. No leaked method vocabulary.

Anti-patterns

  • Proposal written first, economics back-filled.
  • Situation questions that bore the client; implication questions skipped.
  • Meetings ending in "send us something".
  • Insight a rival could sign; page one restating the brief.
  • Deliverables as documents and workshops.
  • Success fee that puts delivery cost at risk.
  • Credentials front and long.
  • Scope growth absorbed silently.

Hand-offs

References

  1. Frameworks: the intellectual foundation of proposal and SOW writing

    4,786 w
    references/frameworks.md6 sub-sections
  2. SPIN question bank for advisory discovery

    1,556 w
    references/spin-question-bank.md7 sub-sections
  3. Templates and checklists

    2,191 w
    references/templates.md9 sub-sections
  4. Worked example: Wexford Industrial Supply, commercial margin recovery

    4,684 w
    references/worked-example.md8 sub-sections