Statements of Work, Done Right

Why the SOW Dictates Your Quality of Life

Statements of work (SOW) sit at the heart of consulting business development. Proposals and SOW documents are the lifeblood of winning and delivering work. What you put into a SOW will affect the quality of your life on the engagement. Do it well, and the project runs smoothly. Do it poorly, and you spend months untangling misunderstandings. For consultants, proposals and SOW documents operate at the consideration and trial stage of the purchase funnel. They convert interest into commitment. 1

Statements of Work Are Difficult to Do Well

Once your proposal is accepted, it is time to write the SOW. You might think this is largely a copy and paste exercise from the proposal. The answer is yes and no. You codify what you agreed during the pitch, but now you must also handle the parts you dislike. A good SOW is clear, descriptive, good-hearted, flexible and useful. It serves as guardrails and a metronome for the dance, not a checklist of obligations. SOW documents can be exhausting. Some run over 1,200 pages and try to do too much. A typical SOW contains background, approach, resources, timeline, expectations, metrics, pricing and deliverables. For professional services it is even more nuanced, because client satisfaction equals expectation minus perception, all of which is subjective. The challenge is authoring a document that keeps consultant and client in sync for the project duration. 2

SOW Documents Vary A Lot

Consulting spans industries, functions and problems, so SOW documents vary accordingly. It is naive to think one magic template covers every situation. Projects range from a one-person workshop to Accenture operating a call center. Energy capital investment, website restructuring, retail footprint rationalization, executive compensation benchmarking and mergers and acquisitions (M&A) IT due diligence have little in common. Collect examples. Get into the habit of gathering deliverables, proposals and SOW documents. There are definite similarities, and there is no reason to reinvent the wheel. Having the outline and headings can keep you out of trouble and ensure you forget nothing critical. The precise wording your firm uses to describe deliverable quality and pricing can be both legally smart and expedient.

What Makes a Good SOW

Here is a description, not a prescription. A good SOW sets project direction and provides guardrails so consultants and clients know who, what, when and why things need to get done. The how is where you gauge the client's savvy and personality, then provide just enough detail. You want to avoid ambiguity, but you also want to avoid legalism. A good SOW articulates a shared understanding. It is far better to argue, refine and complain before the project starts than afterwards. 3

A Good SOW Is a High-Level Recipe

Run a thought experiment. If you and your client counterpart both disappeared tomorrow, could your replacements carry on without you? Could they understand the situation, context and issues you are solving? Could they organize the work efficiently with little duplication? Could they agree on the high-level approach and fine-tune the details? Could they align on what success looks like, deliverable quality and timelines? Could they hold each side accountable with carrots and sticks? Following the food analogy, could they cook the dish? Would there be table service at the restaurant? These questions reveal whether your SOW is a working recipe or a fragile artifact.

Co-Author With the Client

When possible, get your client to meet you halfway. A scenario that works well starts with client rapport, credibility and time. Flush out symptoms and root causes through client conversations and meetings. Scaffold the main points and potential solutions, because consultants are good at this part. Have a point of view. For cost reduction, if your answer is generic, go home. Send meeting minutes to prospective clients and gather feedback. Get buy-in on level one, which covers what, who and so what. Then break that down into level two detail, which covers how and when. Fine tuning is needed throughout. Have the client be your co-author. From there, the question becomes positioning. What you have is what you have. At mid-career you know what products, services and insights you are good at. The task is mapping that to what already exists in your client's mind.

Are Pro-Bono SOW Documents Different

For pro-bono work, the main difference is the profit motive and remuneration. All other aspects remain the same, and perhaps more difficult, than for a for-profit corporation. Clients still want to know what is in it for them. They want to know what you will be doing and how much of their time is needed. They want to know how you work and whether you will be a pleasure or a gadfly. They want to know how many chances they get to redirect your work if it goes off track. They want to know the cost and whether you think it is fair. They want to know what is not included, so you do not disappoint them. Treat pro-bono SOW documents with the same discipline as paid engagements.

Collect, Co-Author and Deliver

Teaching management consulting this semester, I ask students to write a proposal for a fictitious company called Terrace Fitness within three weeks. The advice for new consultants is consistent. Collect SOW examples from your firm. Build a point of view before you write. Co-author with the client wherever possible. Aim for a high-level recipe that two strangers could follow. Avoid ambiguity, avoid legalism and argue the details before the project starts, not after. The SOW is the guardrail that turns a signed proposal into a delivered result.

Avoid the Two Failure Modes

Statements of work fail in two predictable ways. The first is over-specification, where every step is prescribed so tightly that the team cannot adapt when reality diverges from the plan. The second is under-specification, where vague language lets scope creep silently inflate the work. A good SOW threads between these by fixing outcomes, milestones and quality standards while leaving the team room to adjust the approach. When both sides can point to the same shared understanding of done, disagreements stay small and resolvable. The discipline is to specify enough to align and not so much that you strangle the work.

• 1A clear, well-structured SOW protects both consultant and client, prevents scope creep and defines deliverables, costs and timelines
• 2A consulting SOW template should capture scope, deliverables, key performance indicators and exit criteria in one place
• 3A statement of work should define the project scope, deliverables, timeline and success criteria so both parties share one understanding