RFP Response Deck

About this template

Check this before you submit

These ten slides are the presentation summary, not the proposal document. With only two body slides they cannot hold every RFP requirement. Keep detailed specs, staffing and deliverables in the written proposal and use this file for the 15 to 20 minutes you actually speak.

Order the agenda by the score sheet

Slide 2 carries five lines: 01 requirement response table / 02 technical architecture / 03 requirements versus our proposal / 04 key figures / 05 trend analysis, each with a progress marker in the form 01 / 05. All five have a slide behind them, but only the first two come as a divider-plus-body pair; the other three map onto slide 7, slide 8 and slide 9. Scoring differs per tender, so reorder the deck highest weight first: with technical merit at 60 points, capability at 20 and price at 20, the architecture moves forward and the response table moves back. Delivery team, quality assurance and pricing have no slide in this file at all, so if they carry points, duplicate the 3-4 pair, number the new dividers from 03 and add the agenda lines. Put the matching requirement number next to each slide title so evaluators can read your deck alongside the RFP.

What goes on each slide

• Requirement response (slide 4) – the defaults are 136 one-to-one responses, met / partially met / alternative marking, and cross-references to the proposal page. Do not project the whole table; explain the method in these three lines and point to the document.
• Technical architecture (slide 6) – diagram and interfaces, a design sized for 3,000 concurrent users, redundancy and backup cycle. Any line with a number needs its measurement condition.
• Requirements versus our proposal (slide 7) – the left column quotes the tender (full cutover within 3 months, 100% data migration, 24-hour incident response) and the right answers it (a 10-week three-stage cutover, a migration verification tool, night-shift cover included). Copy the tender wording verbatim on the left and answer in the same order on the right.
• Metric tiles (slide 8) – 136 requirements answered, 14 document types, 3,000 concurrent users, 8% maintenance rate. All four describe scope and can stand, but swap in person-months or incident response time if the tender scores them.
• Trend bars (slide 9) – 68 functional, 24 performance, 26 security, 18 operational, adding to 136, so these are requirement counts. The caption says “index”; change it to “count” or evaluators will not connect it to the 136 figure.
• Closing (slide 10) – replace the thank-you with the first 30 days after signing: kickoff date, staffing list submission, first deliverable date.

Timing the talk

Fifteen minutes over ten slides averages 90 seconds each, but do not split it evenly. Reserve three minutes for the architecture, three for the metrics and two for price, then divide what remains. Keep answers to likely questions in the speaker notes rather than on the slides.

Mistakes that cost points

• Spending three slides on company history that carries no score.
• Answering a quantitative requirement qualitatively; if they ask for a 2-second response, give the number and the measurement condition.
• Presenting no pricing slide at all – the file ships without one, so duplicate a pair and move it forward when price carries points.
• Omitting requirement numbers, so evaluators cannot cross-check your claims.