The RFP Response Checklist — How to Write Proposals That Win

Winning an RFP is not a writing problem. It is a thinking problem, dressed up as a writing problem.

Most losing responses make the same mistakes. They treat the RFP like a form to fill in. They copy-paste from last quarter's proposal. They price against a generic hourly rate. They submit the night before. Here is the checklist we run every response against.

Before you decide to respond

Not every RFP is worth your time. Before you commit a senior person for two weeks, run a short go/no-go:

• Incumbent advantage. Is there a vendor already doing the work? How strong is their position?
• Evaluation criteria. Are we genuinely competitive on the top three weighted criteria, or are we chasing?
• Access. Can we have a conversation with the buyer before submission, or is this a pure paper exercise?
• Strategic fit. Is this a client we want on our logo slide for the next three years?

If two of those are soft, decline politely and spend the time on something you can win.

Decode the brief before you write anything

A good proposal answers the brief behind the brief. Pull the RFP apart:

1. What is the stated objective?
2. What is the real objective (you will usually find this in a throwaway line in the background section)?
3. What are the must-haves — the things you will be eliminated on if you miss them?
4. What are the tiebreakers — the nice-to-haves that will decide between two equal bids?
5. Who will read it (technical reviewer? procurement? board?) and in what order?

If possible, write a one-page "brief of the brief" and align your team before drafting.

Find your win theme

A win theme is the single sentence the reader should take away about why you are the right pick. Every section, every graphic, every price point should reinforce it. Weak win themes sound like "we are experienced and passionate." Strong ones sound like:

"You need this done in 10 weeks, in three countries, without slowing down the program. We have shipped exactly this, twice, and our delivery lead is free starting Monday."

Pick one. Make everything in the proposal point at it.

Structure: lead with the client, not yourself

A common mistake: Section 1 is "About Us." Reviewers skim it. A better structure:

• Section 1: Your understanding of the problem, better than the RFP stated it.
• Section 2: The approach (tied to the win theme).
• Section 3: The team and why this team specifically.
• Section 4: Relevant proof — case studies directly tied to the ask.
• Section 5: Plan, timeline, risks.
• Section 6: Commercials.

Put the client's logo, challenge and world at the front. Yours goes behind it.

Pricing: commercial narrative beats a line item

A price table with no story gets compared on unit cost against the cheapest bid. A *commercial narrative* frames the price inside value. Three moves that work:

1. Option A / B / C. Give the buyer a choice. Most will pick B.
2. Show what you are not charging for. Warranty, reviews, onboarding — make them visible even when free.
3. Tie fees to outcomes where possible. Not everything is a fixed fee; some of it is a success fee or a milestone structure.

The 48-hour rule

The last 48 hours always take longer than you think. Lock your content 48 hours before submission. Use that window for:

• Compliance check against the evaluation grid.
• Red-team by someone outside the writing team.
• Cover page, signatures, certifications, annexes.
• A final read-through for tone and consistency.

Submit 2–6 hours before the deadline, not 10 minutes before. Portals crash.

After submission: learn every time

Whether you win or lose, ask for a debrief. Record what worked and what did not. Feed it back into your proposal library so the next response starts at 70%, not 0%.

Got an RFP on the desk? Brief us — we run RFP response sprints with a fixed fee and a turnaround as fast as a week.