Seven Sections of a Consulting Proposal That Gets a Yes

The call went well. The client told you what was going wrong, you could see how to help, and they finished with "send me something." You spent a Sunday on twelve pages and sent them on Monday. Nine days later, a polite note says they have decided to wait.

The thinking in those pages was probably sound. The trouble is that the document asked too much of its reader. The client had to find their own problem in it, work out what they were buying, and explain it to someone who was never on the call.

A consulting proposal has one job: to make a decision easy. Here are the seven sections that do that, in the order a client wants to read them, with a template to copy.

Get your answers before you start writing

Before you agree to send anything, make sure you can answer these questions:

• What happens if nothing changes in the next six months?
• What would a good result look like, and how would they measure it?
• Who else has a say, and what do they care about?
• When do they need to decide, and why then?
• What range of budget did they have in mind?

If you have gaps, ask for fifteen more minutes. If they would rather not name a budget, offer a range yourself and ask whether it feels right. It is far better to learn that now than from silence later.

The seven sections at a glance

Each section answers one question the client is asking.

Open with their situation, not your firm

Use the client's own words from the call, including the numbers and the reason it matters now.

Instead of this:

Founded in 2011, we are a leading advisory firm with deep experience in operational excellence.

Write this:

Your team of twelve spends most of every Friday rebuilding the same client report by hand. Two people left this year, and you told us a third is close. You want that day back before the busy season starts in March.

The test: could this paragraph go to another client with only the name changed? If so, rewrite it.

Describe the result, then the work

Say what will be different, in terms the client can check. "The Friday report takes under an hour" is a result. "Improved reporting processes" is not.

Then set out the work in phases, and name what the client receives from each one. A deliverable is something they can hold, such as a map or a plan. "Stakeholder alignment" is not.

Phase 1, weeks 1 and 2: We interview the five people who touch the report and map every step. You get a one-page map and a list of what to cut.

Close with a helpful line about what sits outside the project:

Team training and new software are outside this proposal. If either becomes useful, we can quote for it separately.

Keep the proof short and relevant

One similar project and what changed is usually enough, in two or three sentences. Keep it true, and check that the earlier client is happy to be mentioned, or describe them without a name. Put this after the work: by then, the client has a reason to care.

Offer options, and recommend one

Fees read better once the client has seen the result. Two or three options also change the question from "yes or no?" to "which one?", and let a client with a tight budget say yes to something smaller. Make them differ in real scope, not in padding:

Then say which one you recommend and why. Below the table, state when you will invoice and what would change the fee.

Write for the person you never met

The reader who says yes may be someone you have not spoken to. Proposify's State of Proposals 2026, based on 742,137 proposals sent through its software, says close rates jump by 20% when more than one stakeholder views a proposal. Winning proposals averaged 11 pages against 13 for losing ones, and were viewed 12 times on average against 8.

That is one vendor's data about its own customers, and cutting two pages will not win a deal by itself. It is still a useful reminder that your proposal has to make sense without you in the room.

• Replace "as discussed" with what was actually discussed.
• Spell out abbreviations your contact uses but their finance lead may not.
• Open it on your phone, where a busy reader may see it first.

End with one action and one date

Do not close with "let me know your thoughts." Ask for one thing, by one date, and say what happens next. If the proposal will also serve as your contract, have a lawyer check the wording first.

Better still, book a short call to go through it together. If you hear nothing by the date you set, a short follow-up is enough: "Is the timing still right, or has something changed? A no is fine too, it helps me plan."

A template you can copy

One last read before it goes out

• The opening could only have been written for this client
• The result is something the client can check
• Every phase names a deliverable
• Proof is short, true and relevant
• Two or three real options, with one recommended
• It makes sense to someone who missed the call
• One clear action and one date

Where Pagyra fits

We are building Pagyra so a proposal can be one page your client can open, pass along and act on. Write it on a clean page, set out your options in a table that adds up, and share it by link: anyone your client sends it to reads it on their phone in about a second, with no account or app. You can see how many times the link was opened (never who), and you can invite clients free to read and comment on the exact line they have a question about. On Pro, you can set an expiry date to match the one on your proposal, and send it for signature from the document itself, with a signed copy and certificate of completion emailed to each signer. Pagyra is open now: sign up here, or open the example document to see what your clients would see.