A consulting proposal has two jobs that pull in opposite directions. It has to sell the engagement, which argues for confidence and narrative. And it has to define the engagement precisely enough that, in week three, when the client asks for “one more thing,” both sides can point at a page. The structure below does both, and the order matters: the selling happens in the first two sections, the defining in the next five, and the last one turns the document into a start date.
It's the structure behind our consulting proposal template. The running example is Meridian Advisory proposing an operations assessment to Caldwell, a manufacturer whose COO wants to know where throughput is going.
The eight sections, in order
1. Situation and objectives
The engagement's why, in the client's terms. What they told you is happening, and the outcomes that would make this money well spent. Three objectives at most, each specific enough to be checked at the end.
A roadmap leadership can fund. A prioritised 12-month improvement plan with cost, effort, and expected impact for each initiative.
Quick wins inside the engagement. At least two improvements implemented during the assessment itself, not just recommended.
What it prevents: the end-of-engagement conversation where the client says “this isn't what we needed.” If the objectives are theirs and written down, that conversation happens now, when it's cheap.
2. Approach
How you think about this problem, and the shape of the work. Enough to show the client you have a method; not so much that you've given away the assessment for free. Two or three paragraphs. This is the section that differentiates you from the other two firms proposing, and it's the one most consultants either skip or bloat into a methodology whitepaper.
3. Scope and deliverables
What's included, phase by phase, and what each phase hands over. Written so both sides can point at it later. The deliverable is a noun: a report, a model, a workshop, a prioritised list. “Ongoing support” is not a deliverable.
Include what's explicitly out of scope. One short list. It feels awkward to write and it's the most valuable paragraph in the document six weeks from now.
4. Milestones and timeline
Dated milestones with clear acceptance points. This is the skeleton the engagement hangs on: the client can see when they get what, and you can see when you get paid. Build the client's review windows in, because their delays are the usual delays, and a timeline that doesn't account for them is a timeline you'll miss.
5. Team
Who is doing the work, and why them for this. In consulting, the people are the product, so this section earns its place. Keep it to the people who will actually be on the engagement, with one line each on relevant experience. The partner who sold it and will never appear again does not go here.
6. Assumptions and dependencies
What you're counting on the client for: data access by a date, a named sponsor, plant visits, decisions within a week of being asked. The section that prevents the awkward week-three conversation, because it turns “we're waiting on you” from a complaint into a reference to page six.
7. Investment by phase
Pricing mapped to the phases, so cost tracks visibly to deliverables. Easier to approve, because the CFO can see what each dollar buys, and harder to whittle, because cutting the price means cutting a phase, and you've made that trade-off visible.
- Fixed fee by phase is the default for defined-scope work. The client knows the total; you carry the risk of your own estimate.
- Time and materials with a cap when the scope genuinely can't be known upfront. State the cap and what happens when it's reached.
- Retainer for ongoing advisory. Monthly, with what's included and what isn't.
Whichever model, show it after the scope, never before. A number on page two gets judged before the reader knows what it buys.
8. Acceptance and next steps
How the engagement starts, and what “done” means for each phase. The signature line, the kickoff date, and the specific next step you agreed on the call. Ends with a date, not a question.
How long
Four to eight pages for a typical engagement. The sponsor reads the objectives and the investment; the person who has to live with the engagement reads scope, milestones, and assumptions. Write for both: a tight front, a precise middle. A twenty-page proposal signals that you bill by the page.
The mistakes
- Leading with credentials. The firm history, the client logos, the partner bios, before the client's problem appears. Credentials belong in section five, one line each.
- Vague deliverables. “Strategic recommendations” is not a thing you can hand over.
- Pricing as one number. One number invites one negotiation: lower. Pricing by phase invites a different one: which phase.
- No assumptions section. Every delay becomes your fault.
- Objectives in your words. If the client doesn't recognise their own problem in section one, nothing after it lands.
Building it from the conversation
Everything in sections one, three, and six came from the scoping call: the COO's objectives, what he said the plants could provide, what he couldn't promise. That's the raw material, and it's usually sitting in your notetaker's summary. Veew drafts the eight sections above from the deal record and those call notes, in your brand, with investment by phase as line items, and delivers it as a trackable link with a matching PDF. The consulting proposal template is the live example; consultants covers how firms use it. We build it, so calibrate. The structure stands on its own.