RFP Response Builder

---
name: rfp-response-builder
description: Use when responding to a Request for Proposal (RFP) or Request for Information (RFI). Triggers on "respond to this RFP", "RFP response", "build an RFP", "RFI response", or pasted RFP requirements with your capabilities.
---

# RFP Response Builder

Build RFP responses that procurement evaluators can score. Most responses lose because they read like a brochure instead of mirroring the RFP's structure — evaluators have to hunt for answers, get frustrated, and score down. Mirror the structure exactly, then differentiate on substance.

## Required inputs

1. **The RFP itself** — full text or structured requirements
2. **RFP metadata** — issuing org, deadline, submission format, evaluation criteria, contact
3. **Your win themes** — 3-5 sentences on why YOU vs competitors
4. **Capabilities content** — service descriptions, methodologies, team bios
5. **Reference customers** — 3-5 with metrics, contact (with permission)
6. **Pricing model** — fixed / T&M / milestone-based, plus your numbers
7. **Compliance items** — security, certifications, insurance, MBE/WBE if relevant
8. **Disqualifiers** — anything in the RFP you cannot meet

If the RFP has a disqualifier you can't meet (mandatory cert, mandatory experience), surface it FIRST. Don't waste days writing a response that gets thrown out at intake.

## Document structure

Mirror the RFP exactly. Evaluators compare to a scoring rubric that matches the RFP's section numbering. If the RFP says Section 4 = Technical Approach, your Section 4 = Technical Approach.

```
[Cover sheet — your company, RFP number, date, contact]

## Cover letter (1 page)
- Salutation to specific buyer (named in RFP)
- 1 paragraph: we're submitting; we understand; we're qualified
- 1 paragraph: brief differentiator
- 1 paragraph: contact + thanks

## 1. Executive Summary (1-2 pages)
- The buyer's situation in their own words
- Our proposed approach in 3-5 bullets
- Why us (win themes)
- Investment headline (if pricing is in main doc)

## 2. Company Overview
- 1 page max. History, scale, focus, certifications.

## 3. Understanding of Requirements
- Restate the requirements; show we read them.

## 4-N. Response to Requirements
- ONE section per RFP requirement section, NUMBERED EXACTLY as RFP
- For each requirement: requirement quoted, response, evidence, deliverable

## N+1. Project Approach / Methodology
- Phased plan, milestones, governance

## N+2. Project Team
- Named team with roles and bios; org chart if useful

## N+3. References
- 3-5 references with: customer name, scope, outcome metrics, contact (with permission)

## N+4. Pricing
- Whatever format the RFP specified — line-item, summary, or per their template

## N+5. Implementation Timeline
- Gantt or table; tied to milestones in pricing

## N+6. Compliance Statements
- Security, insurance, certifications, MBE/WBE/SDVOSB if relevant
- Any exceptions / clarifications to the RFP terms

## Addendums
- Sample work products
- Resumes
- Insurance certificates
- Certifications
- Master agreement / Terms response
```

## Style & tone

- **python-docx** with Heading 1/2/3 mapped to RFP numbering. Or write markdown and convert via Pandoc.
- 11pt body. Margins 1 inch. Page numbers in footer.
- **Use the RFP's terminology verbatim.** If they say "Solution," don't say "Platform." Mirror their language.
- **Quote each requirement directly** before responding. "RFP Section 4.2.3 requires: '...' Our response: ..."
- Tables for compliance matrices. Bullet lists for response detail.
- Win themes embedded throughout, not concentrated in cover letter.

## Response writing per requirement

For each RFP requirement, structure the response as:

1. **Requirement** (quoted from RFP)
2. **Response** ("Yes, we will provide..." or "Yes, with the following clarification...")
3. **Approach / How** (the substantive answer)
4. **Evidence** (case study, metric, certification, sample)
5. **Differentiator** (why our approach is better than alternatives — but earn it; don't over-claim)

If the requirement is something you partially meet, say so explicitly. "We meet this with the following clarification: [...]." Hidden non-compliance is found in evaluation.

## Compliance matrix

Almost every enterprise RFP wants a compliance matrix. Build it.

| Req # | Requirement | Comply (Y/N/Partial) | Reference (section) | Notes |

This is often the single most-read artifact in the response. Get it right.

## Hard rules

- **Never invent reference customer names, certifications, or metrics.** Hallucinated references are RFP suicide.
- **Never copy-paste boilerplate that doesn't match the RFP's industry.** Healthcare RFPs need HIPAA language; financial services need SOC 2 specifics.
- **Always answer in the RFP's order.** Do not reorder for narrative flow.
- **Always submit in the requested format** (.docx, .pdf, portal upload). If pdf, generate from .docx so the procurement team can convert if needed.

## Common pitfalls

- **Marketing voice instead of compliance voice**: RFPs are scored, not read for vibes. Be direct, factual, complete.
- **Over-promising on scope**: "We'll do anything" responses get flagged as not credible.
- **Missing the addendum/exhibit checklist**: many RFPs require attachments (insurance, financials, MBE certs); missing one is auto-disqualification.
- **Ignoring the page limit**: if the RFP says 30 pages, 35 pages may be auto-cut. Cut yourself first.
- **Pricing buried**: some RFPs require pricing in a separate sealed doc. Read the submission instructions carefully.
- **Boilerplate not customized**: pasting last RFP's response with the customer name find-replaced — evaluators can tell.

## Output

The .docx response, plus:

```
RFP response summary:
- RFP: [number / name]
- Submission deadline: [date]
- Total pages: X (limit: Y)
- Compliance matrix: N items, M Yes / P Partial / Q No
- Pricing: [model + total]
- Open questions for the proposal manager:
  1. [item needing clarification before submission]
  2. [item needing clarification before submission]
```

If any disqualifier is unresolved, surface it as the FIRST item. Don't ship a response that gets thrown out at intake.