A statement of work written for the team who will live with the work, and one written for the person who approves the spend, are different documents. The work might be identical. The argument is not.
Practitioners buy capability. They want to know what you will do, who will do it, and whether their team can absorb it. Approvers buy a case. They want to know what is at risk, what it is worth, and what happens on the timeline they are already committed to. A document written for the first audience reads as vague to the second.
The three questions
Every investment committee asks the same three things about a services spend, in the same order. If your document does not answer them in that order, someone has to reconstruct the argument for you in a meeting you are not in.
| Question | Where it belongs | What fails |
|---|---|---|
| What is broken? | Complication | Qualitative pain with no figure |
| What does it cost us? | Complication | Cost stated as a risk, not a number |
| What do we get? | Resolution | Services listed instead of outcomes scoped |
Notice that two of the three live in the complication. Most proposals spend their length on the resolution, which is the part the buyer has the least trouble believing.
Situation: earn the room in four bullets
The situation section is not background. It is proof that you understood the business well enough to be worth reading further. Four bullets is usually enough, and each one should carry a number, a named entity or a date.
A situation written for an approver names the business case explicitly. If the company is consolidating a fragmented market, or defending a contract renewal, say so and say what is riding on it. That sentence signals you know what the engagement is really measured against.
Complication: quantify or lose the argument
This is where most documents thin out. “The team is struggling with consistency” is a sentence a buyer cannot act on. It has no size, so it cannot be compared to the fee.
A useful proposal makes the evidence and the decision easier to review. Illustrative example
That principle is useful because it converts. Use figures from the buyer's confirmed discovery record, with a source and owner for every number. Do not substitute an invented benchmark or anonymous success story.
Three things to quantify every time
- Attainment against a benchmark. Use a sourced internal or external benchmark, and label it clearly when it is not the buyer's own data.
- Time-to-productivity. Ramp expressed in months, multiplied by planned headcount, converts directly into deferred capacity.
- The forecast delta. If the current trajectory misses the plan the business is held to, name the number and name the meeting where it surfaces.
Resolution: scope, not a service list
A service list says what your firm does. A scope says what will exist at the end that does not exist now. The difference shows up immediately in procurement, because a scope can be accepted or rejected item by item and a service list cannot.
Structure each workstream with the same six fields, every time:
- Scope: what is included, stated as artefacts
- Impact: which complication this addresses, by name
- Deliverables: the specific documents, systems or programs produced
- Options: alternative depths, priced separately
- Risk of inaction: what happens if this workstream is cut
- Adoption plan: who owns it internally once you leave
The adoption plan is the one most firms omit and the one approvers read most carefully. They have funded initiatives that died on handover before.
Risk of inaction, per workstream
Attaching a risk of inaction to every workstream changes the negotiation. Without it, cutting scope is a discount conversation: the client asks what you can take out, you take something out, the fee drops. With it, cutting scope is a documented decision the client makes with the consequence written down next to it.
It also protects you. When the engagement lands and the problem you flagged materialises in the area that was cut, the conversation is already on the record.
The checklist
Before the document goes out, check it against these. Any single failure is usually enough to send a buyer back to their own analyst rather than to you.
- Every situation bullet carries a number, a named entity or a date
- The complication states a figure for the cost of the current state
- The business case is named explicitly, not implied
- Every workstream has a risk of inaction
- Every workstream has a named internal owner after handover
- The timeline references the client's fiscal calendar, not yours
- Nothing in the document is unsourced from discovery
The last one is the one that compounds. A document where every claim traces back to something the client said is a document the client cannot argue with, because they are the source. That is a structural advantage, and it is available to anyone willing to work from the transcript rather than from memory.