Writing a consulting proposal and statement of work clients sign

A good consulting proposal does two jobs. It persuades the client that you understand their problem, and it sets out exactly what you will and will not do. The first job wins the work. The second protects both sides when the project gets busy and memories differ.

This guide covers what to put in a proposal and statement of work, how to choose between the main fee models, and how to handle the changes that every engagement brings. It is practical guidance, not legal advice. For contract terms such as liability, payment disputes and intellectual property, have a qualified adviser review your template.

Proposal and statement of work: what each does

The proposal is the persuasive document. It restates the client’s situation, explains your approach and makes the case for hiring you. The statement of work (SOW) is the operational document. It describes the work, the deliverables and the terms in enough detail that someone who missed every meeting could tell whether you delivered.

Small engagements often combine the two into one signed document. Larger clients usually sign a master services agreement once, then a separate SOW for each project. Either way, the content below needs to appear somewhere both parties have agreed to.

The seven parts clients look for

Wikipedia’s summary of a statement of work lists the usual contents: purpose, scope, location, period of performance, deliverables schedule, applicable standards, acceptance criteria, special requirements, and contract type and payment schedule. For consulting, these group into seven parts.

1. Objectives: the question you will answer or the result you will help achieve, in the client’s own terms. Tie it to a decision or a business measure.
2. Scope: the activities you will carry out, with an explicit list of exclusions. “Out of scope: website changes, staff consultation, implementation” saves arguments later.
3. Deliverables: each thing you will hand over, its format, and its acceptance criteria. Wikipedia’s summary recommends objective criteria where possible, so “a board paper of no more than ten pages with a recommended option” beats “a strategy”.
4. Assumptions and client responsibilities: what you are relying on: data supplied by a date, named people available for interviews, one round of consolidated feedback. If an assumption fails, it triggers change control.
5. Timeline: start and end dates, milestones, and the review time the client needs at each one.
6. Fees and payment terms: the fee model, the amount, expenses, invoicing dates and payment terms.
7. Change control: how either side requests a change, how it is priced, and who can approve it.

Choosing a fee model

The fee model decides who carries the risk if the work takes longer than expected. Choose it deliberately rather than by habit.

The time and materials entry on Wikipedia notes the model is used when a project’s size cannot be estimated accurately or requirements are likely to change. It also describes a guaranteed maximum price, a cap that limits what the client can be charged. Offering a cap is a common way to make day rates easier for a client to approve.

Value-based pricing sets price by perceived value rather than cost. The Wikipedia article on value-based pricing lists its drawbacks too: value is hard to pin down, communicate and quantify. Alan Weiss argues for it in Value-Based Fees, aimed at solo consultants and boutique firms. It works when you and the client can agree what the result is worth before you start.

A retainer is a prepaid arrangement that keeps a professional available for future needs, paid once or on a recurring basis. State what the retainer covers, how quickly you will respond, and whether unused time rolls over, expires or is refunded.

Change control that keeps the relationship intact

Scope creep is the gradual, uncontrolled growth of a project’s scope, usually after it has started. Wikipedia’s summary links it to poorly defined or poorly controlled scope, and notes that many small changes can add up to significant extra work. It also warns against accepting changes just to please the client, since some belong in a follow-up project.

A light change process is enough for most consulting work:

1. Either side raises a change in writing, even a short email.
2. You assess the effect on time, cost and other deliverables.
3. You offer options: add it for a fee, swap it for something already in scope, or defer it.
4. The named approver on the client side agrees in writing before the work starts.

Raise changes early and calmly. A change request is simply the agreed way to keep the project honest.

An example (illustration only)

A regional bakery chain with eight shops wants to know whether to open a ninth site or invest in wholesale.

• Objective: recommend one growth option to the owners’ meeting on a set date, with a three-year profit estimate for each.
• Scope: market review, customer survey, financial model, two workshops. Out of scope: property search, recruitment, implementation.
• Deliverables: survey summary; financial model in a spreadsheet the finance manager can update; a decision paper of no more than eight pages.
• Assumptions: sales data by shop supplied in week one; one round of consolidated feedback on the draft paper.
• Fee: fixed fee in two instalments, half at kick-off and half on acceptance of the decision paper. Additional workshops at a stated day rate.
• Change control: changes agreed by email with the managing director before work begins.

Midway through, the owners ask for a third option, a café concept. Under the change clause, the consultant prices it as an add-on with a one-week extension. The owners decline and keep the original scope, which takes five minutes instead of a dispute.

Common mistakes

• Describing activities without deliverables, so nobody can say when the work is finished.
• Leaving out exclusions because they feel negative.
• Hiding assumptions. If the client’s data arrives three weeks late, the timeline needs a written basis for moving.
• Choosing a fixed fee for work you have never scoped before.
• Vague retainers with no response times or limits.
• Agreeing changes verbally in a meeting and never writing them down.

When to use which approach

Use a short combined proposal and SOW for small, well-understood projects. Use a separate SOW under a master agreement when a client will buy several pieces of work. If the problem is still unclear, propose a short, paid diagnostic first and price the main project once you know what it involves. That gives the client a low-risk start and gives you the information to price the rest properly.