How to write a proposal that wins in 2026

A proposal is not a brochure. It is a decision document. Somebody has a problem, a budget they are not entirely sure about, and two or three other documents open in another tab. Your job is to make saying yes the easiest thing they do that week. In 2026 that has become harder for a boring reason: buyers skim. They read the first screen, the price, and the timeline, and only then decide whether the rest deserves attention.

Write the first screen for a skimmer

The opening of your proposal should restate the client's situation in their own words, name the outcome they asked for, and give one sentence on how you will get there. No company history, no mission statement, no stock photography. If a reader stops after twenty seconds, they should still be able to repeat your offer to a colleague. A useful test: delete your logo and the client's name from the first paragraph. If the text could belong to any other project, it is too generic to win anything.

Mirror the brief before you propose anything

Clients buy from the vendor who understood them, not the vendor who described themselves best. Before your scope section, write a short block called Goals or What we heard. List three to five statements drawn directly from the call or the brief, including the awkward ones — the deadline tied to a trade show, the internal stakeholder who dislikes the current site, the fact that nobody has time to write copy. Naming constraints out loud is the cheapest trust you will ever buy, and it protects you later when scope pressure arrives.

Scope in outcomes, priced in phases

Long deliverable lists feel thorough to you and exhausting to the reader. Group the work into three or four phases, each with a name a non-specialist understands — Discovery, Design, Build, Launch — a plain description, and a duration. Then price the phases, not the hours. Phase pricing does two things at once: it gives the buyer a mental model of how the project moves, and it gives you a natural place to cut if the budget is tight. A client who cannot afford the full engagement can start at phase one instead of walking away.

Justify every number

The single most common reason a proposal stalls is a price that arrives without an explanation. Every line in your pricing table deserves one sentence of rationale: what is included, what drives the effort, what the client gets at the end. This is not defensive writing. It is the material your contact will use to defend the spend internally, in a meeting you will never attend. Give them the sentence, and your proposal keeps selling when you are not in the room.

Be explicit about what is not included

An exclusions block reads as confidence, not as hedging. Copywriting, translations, photography, third-party licences, hosting, ongoing maintenance: say which of these are out of scope and roughly what they would cost as an add-on. Half of scope creep is not bad faith, it is an assumption nobody wrote down. The other half is a client who genuinely believed the number covered something it never did.

End with a next step, not a signature line

The last section should tell the reader precisely what happens if they say yes: a kick-off call in the first week, a deposit percentage, a start date that depends on when they reply. Deadlines that are honest — the fact that your calendar fills three weeks out — do more than any artificial urgency. And close with the smallest possible ask. Answering a short question is easier than committing to a project.

Speed is part of the offer

There is a practical reason to keep proposals tight: the faster one arrives, the more likely it lands while the conversation is still warm. A proposal that takes four days to write competes against three days of second thoughts. This is the whole reason Pitchscribe exists — the structure above is stable enough that a machine can draft it from your notes, so the hours you save go into the parts only you can do: judgement about scope, and a price you can defend.

A checklist before you send

Does the first paragraph name the client's outcome, not your services?

Is there a goals block quoting the brief?

Are phases named and dated, with a price per phase?

Does every price line carry a one-sentence rationale?

Are exclusions written down?

Is the next step a single, small action?

Six checks, about ten minutes. It is the cheapest improvement available to anyone who sends more than two proposals a month.