Proposal writing: a practical guide

Most teams lose proposals before anyone reads the good part.

Proposal writing is the process of turning a stated requirement into a structured document that a buyer can evaluate, compare, and act on. That middle word carries more weight than it looks. Depending on what you are writing, your reader is either a single person you need to persuade or a review panel working through a scoring grid, and those two jobs produce very different documents.

Almost every guide on this subject treats proposal writing as an exercise in persuasive writing. That is half the picture. According to Loopio's 2026 RFP Response Trends and Benchmarks Report, which analyzed data from more than 1,500 response teams, only 13% of teams attribute their losses to proposal quality. Price and competition take the blame instead. That number is not evidence that quality is irrelevant. It is evidence that most teams never find out, because a document that misses a requirement gets filtered out long before quality is ever assessed.

Here is how to write proposals that survive that filter.

What is proposal writing?

Proposal writing is the discipline of creating a document that responds to a defined need and asks the reader to make a decision: award a contract, approve a budget, or sign an agreement. In a business context, it covers everything from a three-page sales proposal sent after a discovery call to a formal RFP response assembled by a bid team over four weeks.

Three characteristics separate a proposal from other business writing:

• It responds to something. A proposal always answers a need that already exists, whether the buyer published it formally or mentioned it on a call. You are never starting from a blank page, even when it feels that way.
• It is read comparatively. Your document sits next to two, five, or twelve others. Anything that makes yours harder to compare works against you.
• It commits you. Scope, price, timeline, and terms become contractual the moment the buyer accepts. This is why proposal writing sits closer to legal and finance than to marketing copy.

This guide focuses on business and commercial proposals. Grant writing and academic research proposals share the same skeleton, but they follow funder-specific rules that deserve their own treatment.

The 7 types of proposals, and which one you are actually writing

The single most useful thing you can do before writing a word is identify which type of proposal you are producing. The type determines your structure, your tone, your length, and above all whether your document will be persuaded or scored.

Persuaded or scored: the distinction that changes everything

Look at the "Evaluated how" column above and a line appears.

Persuaded proposals (business, sales, unsolicited) are read by a person or a small buying group. They have no formal grid. Your job is to make the reader see the value, feel confident, and say yes. Writing style, narrative, and design carry real weight here. If you are working on this side of the line, our guide on how to write a sales proposal with AI covers the practical workflow.

Scored proposals (RFP responses, tenders, technical submissions, grants) are read by an evaluation committee against published criteria, often with points allocated per section. Your job changes completely. You are not trying to be memorable. You are trying to make every point on the grid easy to award. An evaluator who has to hunt for your answer to requirement 4.3.2 will simply give you a lower score and move on.

Most teams write scored proposals as if they were persuaded proposals. That is the single most expensive habit in the discipline.

What goes into a proposal? The standard anatomy

Nearly every business proposal, across every industry, is built from the same set of components. What varies is which ones are mandatory and how much space each one gets.

You do not need every section every time. A sales proposal for a €15,000 engagement does not need a risk register. A public sector tender response almost certainly does. Looking at real sales proposal examples is usually faster than theorizing about which sections to keep.

Your executive summary is not a summary

This is the most misused section in proposal writing. An executive summary is not a condensed version of the document that follows. It is a standalone argument for why the buyer should choose you, written for the person who will read nothing else.

A working executive summary does four things in under a page:

1. Restates the buyer's problem in the buyer's own words, not yours
2. States your solution in one plain sentence
3. Gives the two or three reasons you are the right choice, with evidence attached
4. Names the commercial outcome: cost, timeline, and what happens next

Write it last, when you actually know what the proposal says. Then put it first.

How long should a proposal be?

Long enough to answer every requirement, short enough that nothing is padding. In practice, useful ranges look like this:

• Sales proposal: 3 to 8 pages. Beyond that, you are usually compensating for a weak discovery call.
• Business or consulting proposal: 8 to 20 pages, depending on scope complexity.
• RFP or tender response: dictated by the solicitation. If a page limit is stated, treat it as a hard rule. Exceeding it is one of the most common causes of disqualification before evaluation even begins.

Length is never the goal. Coverage is. A ten-page document that addresses all fifteen requirements beats a forty-page document that addresses eleven of them beautifully.

The proposal writing process, step by step

Strong proposals are the output of a process, not a writing session. Here is the sequence used by most professional bid teams, condensed into six steps.

How do you build win themes?

A win theme is a short statement of why you are the right choice for this specific buyer, repeated consistently across the document. It sits at the intersection of three things: something the buyer said matters to them, something you can prove you do well, and something your competitors cannot easily claim.

Two or three win themes per proposal is the right number. They belong in the executive summary, in the opening line of each major section, and in the conclusion. Rephrase them rather than copy them, so the repetition reads as consistency rather than filler.

What is a compliance matrix?

A compliance matrix is a table that maps every requirement in the solicitation to the exact section of your response where it is answered. It is one column of requirements, one column of section references, and one column confirming the requirement is met.

For scored proposals, it is the highest-leverage document you can build. It does two jobs at once: it stops your own team from missing a requirement, and it lets the evaluator find your answers instantly. Where the buyer allows it, include the matrix in your submission rather than keeping it internal.

Who writes the proposal?

Almost no proposal is written by one person, and this is where most of the friction lives. In a typical mid-market B2B team, four roles are involved.

• The account executive or sales rep owns the deal context: what the client actually said, what the pricing looks like, what was promised on the call.
• The pre-sales engineer or solutions consultant owns the technical answer: architecture, methodology, integrations, feasibility.
• The bid or proposal manager owns the process: deadlines, compliance, structure, and the review calendar. On smaller teams, this role does not exist and the work quietly lands on the account executive.
• Subject matter experts own the specialist sections: security, legal, finance, delivery.

The Association of Proposal Management Professionals (APMP) exists precisely because coordinating those four roles under deadline is a discipline in itself. The recurring failure point is rarely writing ability. It is that the deal context sits in one person's head, the technical content sits in a folder from a previous bid, and nobody has time to reconcile them before the deadline.

That reconciliation problem is what modern proposal tooling is genuinely trying to solve, and it is worth being precise about what tooling can and cannot do.

Can you use ChatGPT to write a proposal?

You can, and it will help with parts of the job. Generic AI assistants are good at producing a first draft, rewriting a clumsy paragraph, adjusting tone, and expanding a technical explanation. For a short, low-stakes proposal, that may be enough.

The limits show up fast on anything that gets scored. A general-purpose chatbot has no access to your deal context, no memory of what you promised in previous bids, no awareness of the evaluation grid, and no way to enforce your brand or your document structure. It produces plausible prose that reads well and answers nothing specific. Evaluators recognize it immediately, because it is the same prose they read in the four other submissions.

The distinction is not "AI or no AI." It is whether the AI has access to the things that make your proposal yours. Daoud Chami, Data Science and AI Manager at CBTW, put the requirement well when describing why the team selected Cobl: the platform is designed for documents that follow an internal grammar, such as RFPs, technical memos, HR templates, and reports, and it helps generate complex content while keeping full control at every stage.

That is the practical test. Purpose-built proposal AI connects to your CRM, your past responses, and your brand assets, then generates against a structure you control. Cobl works this way, using specialized agents for layout, brand compliance, and quality control rather than a single generic model. If you want the mechanics, we broke them down in how an AI proposal generator works.

One caveat applies regardless of the tool. AI systems make mistakes, and a proposal is a contractual document. Human review before submission is not optional, and no serious proposal team treats it as such.

Common proposal writing mistakes

• Skimming the instructions. Page limits, formatting rules, mandatory forms, and submission windows are eliminatory. Read the solicitation twice before writing once.
• Answering the question you wish they had asked. If requirement 3.2 asks about your escalation process, describe your escalation process. Do not pivot to your service philosophy.
• Writing the executive summary last and treating it as a formality. It is the section most likely to be read in full and the one most likely to be rushed.
• Reusing a previous proposal without re-contextualizing it. Content reuse is efficient and correct. Leaving another client's name in paragraph nine is not. This is the most common self-inflicted loss.
• Reviewing with one pair of eyes. A compliance reviewer and a content reviewer look for different things. One person cannot do both well at midnight.
• Assuming price is why you lost. It is the easiest explanation and the least actionable. Our breakdown of what actually closes deals covers what the data says instead.

Write proposals your evaluator can score

Good proposal writing is less about writing well than about making a decision easy for someone who is short on time and reading you against a competitor. Identify which type of proposal you are producing, structure it so every requirement is trivially easy to find, build two or three win themes and hold them consistently, and review with fresh eyes before you submit.

The mechanical work of assembling that document is where teams lose the hours they should be spending on strategy. That is the part worth automating.

Try Cobl for free and generate your next proposal from the context you already have. Get started here.