rfp-responder

---
name: rfp-responder
description: Use when an RFP, RFI, RFQ, or security questionnaire arrives and needs requirement parsing, a proof-point fit matrix, win-themes, a winrate estimate, and a bid/no-bid call.
category: Commercial
version: 1.0.0
tools: []
---

# rfp-responder

Structured RFP/RFI/RFQ response strategy for Bid Managers, Proposal Leads, Directors of Sales, and Sales Engineers. Parses buyer-dictated requirements, builds a Shipley-method proof-point matrix, articulates win-themes, and produces a winrate estimate that drives a bid/no-bid/partner-bid call. Surfaces GAP requirements explicitly — never invents claims.

## Purpose

Answer five questions at the response-strategy moment:

1. **What is this RFP actually asking?** — parse sections, tag every requirement MANDATORY / WEIGHTED / NICE-TO-HAVE, extract scoring criteria, surface deadlines and format constraints.
2. **What is our true fit?** — a proof-point matrix per requirement: STRONG / PARTIAL / GAP, each backed by a verifiable source (case study, certification, customer quote, technical attestation, benchmark).
3. **What is our win-theme strategy?** — Shipley method: 3-5 themes that ladder up across requirements, not generic value-prop bullets.
4. **What is our realistic winrate?** — a Shipley-derived factor model (fit, incumbent, relationship strength, decision-criteria alignment, late-entry, competitor count, deal size) producing an estimate with a confidence band.
5. **Should we bid?** — a deterministic verdict: BID / PARTNER-BID / NO-BID with the named factors driving the call.

GAPs are surfaced explicitly. Leadership decides whether to close them, partner around them, or no-bid. Claims are never invented.

## When to use

A 30+ page RFP/RFI/RFQ has landed with a 7-14 day response deadline; a security questionnaire (SIG, CAIQ, custom-buyer) needs structured Q&A, not prose; the team is preparing a bid/no-bid review and needs a defensible winrate estimate; Sales Engineering has a proof-point library but no system to map proofs to requirements; leadership wants fit % (STRONG/PARTIAL/GAP) before committing pursuit budget; or a late-entry opportunity needs an honest read on the relationship deficit.

Not for: free-form proposal narrative where you set the structure (route to proposal writing); contract redline after award (route to general counsel); marketing collateral; discount approval on the awarded deal (route to deal-desk); pricing-model design for a new product (route to pricing-strategist).

## Workflow

### Step 1 — Parse the RFP

Extract every requirement from the RFP text, tagged MANDATORY / WEIGHTED / NICE-TO-HAVE by cue words (must/shall = MANDATORY; should/weighted scoring numbers = WEIGHTED; may/preferred/desired = NICE-TO-HAVE). Capture section structure, disclosed scoring criteria, deadline, and submission format constraints.

### Step 2 — Score fit per requirement

Build a proof-point library (each proof tagged by type, verifiable source, and which requirements it covers) plus proposed win-themes. Produce the proof-point matrix per requirement — STRONG / PARTIAL / GAP — plus a GAP audit. Hard rule: GAP requirements are surfaced, never invented around; leadership decides whether to close, partner, or no-bid.

### Step 3 — Apply win-theme strategy

Shipley method: 3-5 themes spanning requirements, each answering "why us over the incumbent/competitor on the criteria the buyer named." A theme appearing in fewer than 2 requirements is decorative, not strategic, and gets flagged.

### Step 4 — Estimate winrate

Feed deal context (fit %, incumbent strength, relationship, decision-criteria alignment, late-entry, competitor count, deal size vs. average) into the Shipley-derived factor model. Output: estimate 0-100%, confidence band, factor breakdown, and BID / PARTNER-BID / NO-BID verdict. An estimate under 20% triggers an automatic no-bid recommendation.

### Step 5 — Decide

Take the parsed RFP, proof-point matrix, GAP audit, and winrate estimate into the go/no-go review. Leadership commits the pursuit budget, not this methodology.

## Reference canon

- Shipley method: Shipley Proposal Guide v6, Shipley Capture Guide, APMP Body of Knowledge, Tom Sant, Tom Searcy + Henry DeVries, Strategic Proposals research, Larry Newman.
- RFP strategy: FAR, GSA, Forrester, Gartner, Bain, McKinsey, B2B International on RFP win-rates and buyer behavior.
- Anti-patterns: Shipley failure modes, APMP case studies, Strategic Proposals research, federal loss reviews, MIT Sloan, Bain commercial-discipline research, Gartner.

## Assumptions

The RFP is ground truth — answer what the buyer asked, in the order asked, in the format specified; re-organizing for narrative flow belongs in proposals, not RFPs. Proof points must be verifiable — a claim is only as strong as the case study, certification, customer reference, or technical attestation backing it; unsourced claims become GAPs. Win-themes are buyer-side, not seller-side ("your operations team reduces incident MTTR by 60% with the same headcount" is a win-theme; "we're the leader in X" is a marketing claim). Winrate estimates are directional, a discipline tool to force honest pursuit-qualification, with a confidence band always wider than the point estimate suggests. Industry profiles tune base rates — government RFPs reward compliance discipline, enterprise SaaS rewards reference accounts, healthcare rewards regulatory and security depth. Late entry is a structural disadvantage — entering after the RFP issued, with no relationship history, drops the base rate roughly 15%.

## Anti-patterns

Inventing a proof point to fill a GAP — a hard-rule violation; GAPs surface for a leadership decision, not for prose-laundering. Responding to every RFP without a qualified bid/no-bid gate — burns capacity on sub-20% winrate pursuits while losing the 50%+ pursuits to lack of focus. Generic responses with no win-theme — a proposal any competitor could send verbatim is decorative. Missing a mandatory disqualifier late (FedRAMP / HIPAA / ISO 27001 / SOC 2 / on-shore data residency caught on day 12 of a 14-day response wastes the pursuit) — surface these on day 1. Answering the question you wanted asked instead of the one that was asked. No compliance matrix mapping every requirement to a response section and page number — evaluators score on a matrix, and respondents without one self-disqualify on traceability. Late-entry pursuits that don't acknowledge the relationship deficit against an incumbent. Treating WEIGHTED requirements like MANDATORY — score-weighted items reward depth on the high-weight items, not uniform mediocrity across all.

## Forcing-question library

Walk one question at a time before any scoring runs. Lock 1-3 before opening 4-7.

1. What's your STRONG/PARTIAL/GAP split on the MANDATORY requirements? STRONG ≥ 70% before bidding; PARTIAL/GAP on any MANDATORY means close the gap pre-submission or no-bid. (Shipley *Proposal Guide v6* — "Pgw (probability of win) is bounded by your weakest MANDATORY.")
2. Is there an incumbent, and how strong is their position? A strong incumbent (3+ years, no displacement event) drops base winrate ~30% — don't bid without a named displacement trigger. (Forrester B2B-RFP research — incumbents win 70-80% of renewal RFPs absent a named failure event.)
3. Did you enter the conversation before or after the RFP issued? Late-entry drops winrate ~15% and signals the RFP was scoped to someone else's strengths. (Tom Searcy + Henry DeVries, *How to Win Big Business*.)
4. What are your 3-5 win-themes, and does each thread through ≥2 requirements? Themes in only one requirement are decorative. (Shipley *Capture Guide*.)
5. For every claim in the response, can you name the verifiable source? Case study / certification / customer reference / technical attestation / benchmark — unsourced claims are GAPs. (APMP BoK — substantiation is mandatory.)
6. What's the bid/no-bid threshold you committed to BEFORE seeing this RFP? A pre-committed threshold (e.g. winrate ≥ 25%, STRONG ≥ 70% on MANDATORY, named champion) beats post-hoc rationalization. (Bain RFP-win-rate studies — disciplined bid/no-bid gates lift win-rate from ~15% to ~35%.)
7. What does the buyer's evaluation team actually score on? Weight response effort to the disclosed rubric; if undisclosed, ask — and if you can't ask, that itself signals a relationship deficit. (Strategic Proposals research.)

After all 7 are answered, apply the RFP parser, then the response drafter, then the winrate predictor, in that sequence. If question 6 lands on "we don't have a threshold," set one now or no-bid.