Engagement Leadership · Commercial wing
RFP/RFI Response War Room
SIMULATEDVerified Jul 2, 2026Decompose the ask, red-team the response against the RFP's own scoring, and make the call. The RFPs you decline fund the ones you win — bid/no-bid is a portfolio decision, not a reflex.
RFP excerpt
“Seeking a partner to deliver an AI-assisted disputes automation capability in a regulated environment. Must demonstrate proven RAG delivery, a named engagement manager, an AI governance framework, and a blended onshore/offshore model. 24-week fixed-price delivery with milestone acceptance.”
Compliance matrix · 80% covered
| Requirement | Owner | Evidence | Status |
|---|---|---|---|
| Proven RAG delivery in regulated finserv | Delivery lead | Disputes RAG case study | met |
| Named EM, 4+ yrs client-facing delivery | Staffing | EM profile + references | met |
| Data & AI governance framework | Governance | Risk-tiering + guardrails lab | met |
| Blended onshore/offshore model | Resourcing | Mobilization plan (draft) | partial |
| 24-week fixed price with milestones | Commercial | PERT estimate + change control | partial |
Bid / no-bid
BidRed-team scorecard · 82/100
Bid — and lead with the win themes
Steering-committee takeaway: The RFPs you decline fund the ones you win. Bid/no-bid is a portfolio decision, not a reflex.
Resume echo — $9M pipeline — the instrument of how a pipeline gets built, one qualified pursuit at a time.
How this is built
Coverage = mean of requirement status (met 1 · partial 0.5 · gap 0). Red-team = Σ(criterion weight × score) against the RFP's own evaluation scheme.
Bid rule: margin ≥ floor AND pursuit score (fit × win-prob × capacity) ≥ 35. The second sample is engineered to fail both — the honest answer is no-bid.
Stack: Next.js (static) + shared design system; client-side only.
Limitations: fit/win-prob/capacity are judgment inputs, not a CRM model; scoring is illustrative. It disciplines the qualify-and-decline decision, not the full proposal build.