Response structure: build to the scorecard
The buyer evaluates every response against a set of criteria, some stated in the RFP and some implicit. A winning proposal is built to that scorecard, in the buyer's language and order, not shaped like your standard pitch.
Answer what they asked, in their order
The single highest-leverage discipline: answer every question the RFP asks, fully, in the order they asked it. Evaluators often score section by section against a checklist; a response that reorders or skips questions loses points mechanically, before anyone judges the quality of the idea.
- Map every question and requirement in the RFP to a section of your response. Nothing unanswered.
- Keep their numbering and their wording. If they call it "audience verification", do not answer under "brand safety".
- Answer the question actually asked, not the one you wish they had asked. A strong answer to an adjacent question still scores zero on the one they wrote down.
Lead each section with the criterion it satisfies
Open each section by naming the buyer's need it addresses, then deliver. The evaluator should never have to hunt for where you answered their requirement. Put the answer first and the supporting narrative second, not the reverse.
Start from a clean canonical template
Always build from a clean, current template, never from a previous deal's response. Reusing the last proposal is the most common self-inflicted wound in RFP work:
- It drags in the wrong client's logos, screenshots, and case numbers, which a sharp evaluator notices immediately and reads as carelessness.
- It carries stale pricing and claims you may no longer stand behind.
- It anchors the new response to the old deal's structure instead of this buyer's questions.
Keep one maintained master template per response type. Start there every time, and pull in proof assets deliberately, matched to this buyer.
The proposal deadline sits at the top
Record the submission deadline at the very top of the working file, above the engagement or flight dates the RFP also lists. These are different dates and they get confused constantly: the flight dates say when the work would run; the deadline says when the proposal is due. Missing the second because you tracked the first loses the deal with a great response sitting finished on your drive.
Proof, matched not carpeted
Include proof, but matched to this buyer's situation, not every case study you own. One or two relevant, verifiable proof points beat a stack of loosely related ones (the same restraint the case-study discipline calls for). Anchor claims to real, defensible numbers; an evaluator who catches one inflated figure discounts the whole proposal.
A workable section order
Adapt to the RFP's own structure, but a reliable default when they do not prescribe one:
- A short executive summary that restates their objective in their words and names your angle.
- A point-by-point response to their requirements, in their order.
- The approach or solution, led by the criteria it satisfies.
- Proof matched to their situation.
- Pricing, exactly as they asked it to be presented.
- Team, timeline, and next steps.
If they gave a required format, theirs wins over this one, every time.