What to include in a consulting proposal, section by section

You have a call on Tuesday, a budget signal, and a blank document. The client asked for a proposal by Friday. You know the work, you have done it before, and the thing that is stopping you is not the thinking. It is deciding what actually goes in the document and what gets cut.

Most consulting proposals fail for one of two reasons. They are too long, so the client reads the first page and the price. Or they are too short in the wrong place, so the client cannot tell whether you understood the problem, and they go with someone who sounded more certain.

Here is the structure that does the work, in the order it should appear.

Start with what you understood, in their words

This section goes first and it does more work than everything after it combined. Not because it is persuasive, but because it is the section the client reads to decide whether you were listening.

Write it as a description of their situation, not yours. The test is simple: if the client could have written this paragraph themselves, you have got it right. If it could have been sent to any of the other firms they spoke to, you have written a template.

Include:

• The problem as they described it, using their vocabulary. If they said "our quoting is a mess", do not upgrade it to "opportunities for process optimisation".
• The constraint they mentioned. Budget cycle, a system that cannot be replaced this year, a person who has to sign off, a deadline tied to an event.
• What they said success looks like. If they did not say, write what you inferred and mark it as an assumption to confirm.
• What is out of scope, stated plainly. This is the part most proposals skip and the part that prevents the argument in month three.

A useful discipline: write this section before you write anything else, and do not let it exceed a page. If you cannot fit their situation on one page, you did not understand it well enough to price the work.

One more thing about this section. It is the only part of the proposal that is genuinely hard to fake. Anyone can list deliverables. Only someone who was in the conversation can describe the constraint the client mentioned in passing.

The approach: what you will do, in what order

This is where most proposals turn into a list of activities. Resist that. The client does not want to buy activities, they want to buy a sequence that ends with the problem solved.

Write it as phases, and for each phase give three things: what happens, what the client gets at the end of it, and what you need from them to start it.

The third one matters more than people expect. Consulting work stalls when the client's side is not ready, and a proposal that names its dependencies up front is a proposal that does not need an awkward email in week two. "We need read access to the CRM and one hour with the sales lead before phase two begins" is a sentence that protects both parties.

Keep the phases to three or four. If you have seven, you have either scoped too much or you are describing tasks rather than phases. Merge them.

Be specific about what you will not do. "We will not implement the changes in your systems; we will hand over a plan your team can execute" is a boundary that prevents a scope conversation later. It also makes the price make sense.

Priced options, not a single number

A single price invites a yes or no. Two or three options invite a conversation about which one, and that conversation is the one you want to be having.

The structure that works:

• A core option. The work as you would scope it if you were being careful. This is your recommendation and you should say so.
• A reduced option. Less scope, clearly less. Fewer phases, narrower question, or a shorter engagement. It exists so the client has a way to say yes when the core number is above the line.
• An expanded option. More scope, usually including something the client mentioned but did not ask for. It exists to anchor the middle option and occasionally to be chosen.

Each option needs its own scope statement, its own timeline, and its own price. An option that is just the core option with a different number is not an option, it is a discount with extra steps.

On the arithmetic: show how the price is built. Days, rates, expenses, and what is excluded. A total that appears without a build is a total the client has to take on faith, and faith is in short supply when they are comparing three firms.

If you are offering a deposit or staged payments, say so here rather than in a follow-up email. Payment terms are part of the offer, not an administrative detail.

The team: who does the work, and how much of it

The client is not buying your firm, they are buying the people who will be in the room. Name them. Give each person one line: what they have done that is relevant to this problem, and what their role is on this engagement.

If a senior person is selling the work and a junior person is doing it, say so. Clients find out anyway, and finding out later costs more than saying it now. "The engagement is led by X, with Y doing the analysis and Z available for review at each phase gate" is honest and it is also reassuring, because it tells the client the work is structured.

If you are a solo consultant, this section is short and that is fine. Say what you have done that is close to this problem, and say what you will do when you hit something outside your experience. Nobody expects one person to know everything. They do expect to be told.

Risks and assumptions: the section that makes you look serious

Most consultants leave this out because it feels like talking the client out of buying. It does the opposite. A proposal that names what could go wrong is a proposal written by someone who has done this before.

List the three or four things that would most plausibly derail the work, and for each one say what you will do about it. Keep it concrete:

• Assumption: the data in the current system is complete enough to analyse. If it is not: we add a two-week data clean-up phase, priced separately.
• Risk: the decision-maker changes mid-engagement. Mitigation: we document decisions at each phase gate so the work survives a handover.
• Dependency: your team needs to make someone available for two hours a week. If that slips: the timeline moves by the same amount.

This section is also where you say what you are not. If the work touches regulated activity, say that you are not providing legal advice and that a qualified adviser should review the output. If the client needs a notarised signature on anything, that needs a notary, not a consulting firm with a PDF tool.

One next step, not a menu

End with a single action. Not "let us know your thoughts". Not "happy to jump on a call to discuss". One thing, with a date attached.

"If this looks right, reply to confirm and I will send the engagement letter and an invoice for the deposit, with a start date of the 14th" is a next step. It is easy to say yes to, it does not require the client to work out what happens next, and it puts a date in the diary.

If you want to offer a call, make the call the next step and propose two specific times. A menu of options is a decision the client has to make. A single next step is a decision they can make in one reply.

Length is what kills a proposal

Everything above fits in four to six pages. That is not a constraint imposed by taste, it is a constraint imposed by how proposals are read.

The client is reading this on a phone, between meetings, probably after reading two others. The first page decides whether they read the second. A twenty-page proposal with a strong first page is a five-page proposal with fifteen pages of material that will never be read, and the fifteen pages make the price look bigger because they make the work look more complicated than it is.

Where length creeps in:

• Company history. Nobody buys your founding story. One line at most, and only if it is directly relevant to this problem.
• Methodology diagrams. If you have a proprietary framework, name it in a sentence. The diagram is for the pitch meeting.
• Biographies. One line per person, as above. A paragraph per person is a paragraph nobody reads.
• Case studies without numbers. If you cannot say what the outcome was, the case study is a story, and stories take up space without doing work. There are no published benchmarks here to lean on, so describe the shape of the problem you solved rather than implying a result you cannot evidence.
• Terms and conditions. Put them in the engagement letter, not the proposal.

The honest test: read your proposal and delete every sentence that does not either describe the client's situation, describe what you will do, say what it costs, or say what happens next. What is left is the proposal. What you deleted was reassurance for you, not information for them.

Where software helps, and where it does not

If you write proposals regularly, the drafting is where the time goes, and it is the part with the least thinking in it. The situation section is different every time. The approach, the team, the risk language and the payment terms are largely the same document with different nouns.

That is the case for generating the document rather than assembling it from a template gallery. With DocuDeal, you describe the deal in a sentence and the AI drafts the proposal, then asks you the questions it cannot infer: who the client is, what the phases are, what the options are priced at. You review rather than write. Prices are computed from your own rate card by code, not by the model, so the total is arithmetic rather than a guess, and anything it cannot source is flagged for you to confirm before it goes out.

It goes out as a link rather than an attachment. The client opens it on a phone, no account, no download, and you can see which sections they spent time on. That is the part that changes the follow-up: instead of asking whether they have had a chance to look, you know they spent four minutes on the pricing page and nothing on the team page, and the follow-up writes itself. Everything you send a client accumulates on one page automatically, so the proposal, the engagement letter and the invoice live at the same link.

Two things to be clear about. DocuDeal is not legal advice and does not guarantee a document is enforceable anywhere, so if your engagement needs a lawyer's review, get one. And if your proposals are genuinely bespoke every time, with a different structure for every client, a drafting tool saves you less than it costs. The case for it is repetition: same shape, different deal.

On price: every plan has unlimited users, including the free one. A team of ten costs $0 on Free and $149 on Pro. The meter is documents per month, never people. What changes by plan is volume, and from Pro upward, team roles and approvals and sending from your own email address.

The rule to apply before you send

Read your proposal and find the sentence that describes the client's problem in their own words. If it is not on the first page, move it there. If it is not in the document at all, you have written a brochure, and the price is the only thing the client will remember.