← All blog articles

Before You Write a Consulting Proposal, Confirm These Five Decisions

A buyer says, “Send us a proposal.” You could spend tomorrow building a beautiful document. Or you could first check whether you and the buyer mean the same project.

A useful proposal turns an understood assignment into a decision. When the assignment is still vague, extra pages tend to hide the questions that need answering.

Confirm the change the client wants

Ask what should work differently when the assignment ends. “Improve operations” gives you little basis for scope. “Give our service manager one agreed process for assigning incoming enquiries” is something you can discuss, deliver and review.

The answer should use the client’s language. Do not replace a modest operational need with a larger transformation because that sounds more impressive.

Resolve five decisions

Use this fictional example to prepare your own brief.

Decision Agreed position
Work to change Incoming service enquiries are assigned inconsistently
Deliverable One documented assignment process and a team walkthrough
People involved Service manager and two team leads
Review Team checks the process against five representative enquiries
Buying decision Operations director approves scope and fee; date still to confirm

The missing approval date matters. It may affect when you reserve time, but it does not require you to invent urgency.

Ask one question to close the gap: “When will the operations director review the scope and fee?” A short email can do that; another full discovery call is not always necessary.

Check the assumptions behind your fee

List what you need the client to supply: access to the relevant people, sample material, a reviewer and timely decisions. Put a reasonable boundary around the work.

For the example, you might include one process, one workshop and one round of consolidated corrections. Adding a second department would need a separate scope discussion. That is clearer than writing “all support included” and discovering later that each stakeholder expects a different service.

Salesforce’s guide to discovery calls is useful background on understanding a prospect before presenting a solution. The readiness card above is an original working tool for the next step: making an assignment quoteable.

Write for the decision-maker

Put the work, deliverables, assumptions, review method and commercial terms near the front. A reader should be able to explain what they are buying without searching your credentials section.

A good opening might be: “We will document and test the service-enquiry assignment process with your team, then hand over the agreed procedure and a walkthrough.” You can support it with experience that is relevant and verifiable.

Choose the right next action

If these decisions are clear, write the proposal. If the client needs substantial analysis to define the work, consider a separately scoped diagnostic. If the task does not match what you can deliver, say so before quoting.

For the earlier research stage, use the target-account list guide. It helps you choose where to start conversations; it cannot answer the project decisions that only the buyer can make.