Proposal outline: eight sections that answer the buyer's questions in order

A proposal fails for one of two reasons. Either it answers questions the buyer was not asking, or it answers the right questions in the wrong order, so the reader hits the price before they have any reason to care about it.

The fix is not better writing. It is putting the sections in the sequence the buyer's own thinking follows. A buyer reads a proposal asking, roughly in this order:

Write the document in that order and most of the work is already done.

One note before the outline: this page is an outline, not a downloadable or editable file. There is no template file to fill in. Copy the eight sections into your own document and write them in order.

What to take away

The outline

<figure class="inline-figure">
  <img src="/inline/proposal-templates-fig1-1280.webp" alt="Numbered list of the eight proposal sections in order (Proposal templates: the outline that follows the buyer's own questions)" loading="lazy" decoding="async" />
  <figcaption>The eight-section outline that follows the buyer's own questions, in the order they ask them. <a href="https://companyformtemplates.com/image-licence">Image: Company Form Templates</a></figcaption>
</figure>
   The situation in your words. What is happening, what it is
   costing you, what you have already tried.

   The approach in one paragraph, then the shape of the work.

 3.1 What is included: deliverable by deliverable
   3.2  What is not included
   3.3  What we need from you, and when

   Phases, milestones, who is involved, how you will see progress.

   The named people. Relevant experience only.

   The price, how it is structured, what triggers each payment.

   What this price assumes. What happens when an assumption
   turns out to be wrong.

   The single action you want, and the date this offer holds until.

Everything below explains what each section has to accomplish and how it commonly fails.

1. What we understand

This is the section that decides whether the rest gets read carefully. It is also the section most people skip in favor of describing themselves.

Write the buyer's situation back to them in the words they used. Not a flattering summary: a genuine restatement, including the awkward parts. If they told you the last attempt failed, say so. If there is internal disagreement about what the problem is, name it.

Failure mode: a paragraph of generic industry observation that could open any proposal to anyone. If you could send this section to a different prospect without editing it, delete it and write the real one. Funders enforce the same order by rule: the National Science Foundation's guidance for new proposers puts the problem and the approach ahead of the applicant's history.

Test: could the buyer forward this page to a colleague who was not in the meeting, and would that colleague recognize their own company?

2. What we propose

One paragraph, before any detail. What you will do, and what will be different afterwards.

Buyers read this paragraph and decide how much of the rest to read. Do not open with methodology. Open with the outcome and the shape of the route to it.

Failure mode: leading with your process name. Nobody has bought a process. They buy the state they will be in when it is done.

3. Scope

Three subsections, and the second two are the ones that protect you.

What is included. Deliverable by deliverable, each with something concrete: a form, a count, a format, a moment it appears. "Strategy support" is not a deliverable. "A written positioning document, reviewed with you in one session, revised once" is.

Filled example: one 12-page positioning document, delivered as PDF and editable DOCX, one 90-minute review session, and one revision round.

What is not included. This feels adversarial to write and is the single most valuable section in the document. It is not about refusing work: it is about naming the things a reasonable person might assume are covered. Ongoing maintenance after handover. Content the client has to supply. Third-party costs. Travel. Training beyond one session. Anything you would be annoyed to be asked for free.

Filled example: excluded are website copywriting, print production, image licensing, and support after the 30-day handover window.

What we need from you. Every project that slips slips partly on the client side. Name the inputs, the approvers, and the response time you are assuming. Do this here, and the conversation later is about a documented assumption instead of about blame.

Failure mode: an inclusions list so abstract that both sides can read it as agreeing with them. Write each line so that at the end of the job, you and the buyer would independently give the same answer to "was this delivered?"

4. How it runs

Phases, what appears at the end of each, and the decision the buyer makes at each boundary. This section quietly answers the question buyers rarely ask out loud: how much of my time will this take, and when will I know if it is going wrong?

Give real check-in points. A buyer who can see three moments where they get to look at progress and change direction is buying much less risk than one who sees a single delivery date.

If you commit to dates, tie them to a start trigger rather than the calendar: "week 3 from kick-off" rather than a specific date that will be wrong by the time they sign.

Failure mode: a timeline with no decision points, which reads as "give us the money and wait."

5. Who does the work

Names, and only the experience relevant to this job. Two or three lines each.

Buyers are checking one thing: whether the people they met are the people who will show up. If a senior name appears in the proposal and does not work on the project, say what their actual involvement is. Overstating it here is the fastest way to lose a second contract.

Failure mode: company boilerplate (founding year, client logos, awards), pasted in as a substitute for saying who does the work.

6. What it costs

Present price as a structure, not a number. The quote format has to put the total on the first screen.

Failure mode: a single number in a box with no structure around it, which forces the buyer to negotiate on the only variable they can see. Whether the structure was right shows up months later on your profit and loss form.

7. Assumptions and changes

Short, and worth its length several times over.

List the assumptions the price depends on, volume, access, existing system state, number of review rounds, availability of a decision-maker. Then state, in one or two sentences, what happens when one turns out to be wrong: who raises it, how the change is priced, and who approves it before work continues.

A change process agreed in advance is a normal conversation. The same conversation without it is a dispute.

8. Next step

One action. Not three.

Say exactly what you want the buyer to do (sign, reply to confirm, book the kick-off call), and who to contact. Give the offer an expiry date, because prices and availability genuinely do change, and because an open-ended proposal never gets a decision.

Failure mode: ending with "we look forward to hearing from you," which asks for nothing.

What to leave out

Proposals get longer because nobody is responsible for cutting them. These usually go:

Formatting and version control

Version and date on every page. Buyers circulate proposals internally, and two versions in a shared drive will be compared.

A stated validity date. It is the only polite way to create a deadline.

Send it in a form they can forward. Whoever you sent it to is not the only reader, and a business letter has to pass the same test.

Keep the file you sent. Not the ability to regenerate it: the actual document, so that when there is a question about what was agreed, you are both looking at the same object.

Number the sections. Someone will want to ask about "point 3.2," and giving them the vocabulary to do that speeds up every subsequent conversation.

A five-minute pass before sending

If you need a priced offer rather than a persuasive document, quotes and estimates is the shorter form for that job.

Common questions