投标响应策略_rfp-responder

以下为本文档的中文说明该技能用于应对RFP、RFI、RFQ、安全问卷、供应商问卷或提案请求提供结构化的响应策略。核心功能是帮助投标经理、提案负责人和销售总监在响应策略时刻回答五个关键问题。使用场景包括收到买方规定格式的多部分需求文档时需要评估是否投标、不投标或合作投标时需要制定基于证据的赢单策略时。五个核心问题包括RFP实际在问什么——解析章节、标记每个需求的优先级强制/加权/锦上添花、提取评分标准、截止日期和格式约束我们的真实匹配度如何——为每个需求建立证据点矩阵强匹配/部分匹配/缺口每个证据需有可验证的来源赢单主题策略是什么——采用Shipley方法制定3-5个贯穿需求的赢单主题真实赢单率是多少——基于Shipley因子模型评估匹配度、在位关系、关系强度、决策标准一致性缺口如何暴露——明确标识需求缺口绝不编造声明。该技能的核心原则是诚实和基于证据不编造能力和案例。rfp-responderPurposeHelp Bid Managers, Proposal Leads, and Directors of Sales answer five questions at the response-strategy moment:What is this RFP actually asking?(parse sections, tag every requirement MANDATORY / WEIGHTED / NICE-TO-HAVE, extract scoring criteria, surface deadlines and format constraints)What is our true fit?(proof-point matrix per requirement: STRONG / PARTIAL / GAP, each backed by a verifiable source — case study, certification, customer quote, technical attestation, benchmark)What is our win-theme strategy?(Shipley method: 3-5 themes that ladder up across requirements, not generic value-prop bullets)What is our realistic winrate?(Shipley-derived factor model: fit, incumbent, relationship strength, decision-criteria alignment, late-entry, competitor count, deal size — produces estimate confidence band)Should we bid?(deterministic verdict: BID / PARTNER-BID / NO-BID with named factors driving the call)The skill surfaces GAPs explicitly. Leadership decides whether to close them, partner around them, or no-bid.It never invents claims.When to useA 30 page RFP / RFI / RFQ has landed with a 7-14 day response deadlineA security questionnaire (SIG, CAIQ, custom-buyer) needs structured QA — not proseThe team is preparing a bid / no-bid review and needs a defensible winrate estimateSales Engineering has a proof-point library but no system to map proofs to requirementsLeadership wants to see fit % (STRONG / PARTIAL / GAP) before committing pursuit budgetA late-entry opportunity needs honest assessment of the relationship deficitDo not use for:Free-form proposal narrative authoring →business-growth/contract-and-proposal-writerContract redline AFTER award →c-level-advisor/general-counsel-advisorMarketing collateral / category content →marketing-skill/*Discount approval on the awarded deal →commercial/deal-deskPricing-model design for a new product →commercial/pricing-strategistWorkflowStep 1 — Parse the RFPDrop the RFP markdown / text intoscripts/rfp_parser.py. Output: structured JSON listing every requirement, tagged MANDATORY / WEIGHTED / NICE-TO-HAVE based on cue words (must / shall MANDATORY; should / weighted scoring numbers WEIGHTED; may / preferred / desired NICE-TO-HAVE). Captures section structure, scoring criteria if disclosed, deadline, submission format constraints.python scripts/rfp_parser.py--inputrfp.md--outputjsonparsed.jsonStep 2 — Score fit per requirementFillassets/rfp_intake_template.mdwith your proof-point library (each proof tagged with type verifiable source which requirement-tags it covers) and proposed win-themes. Feed parsed RFP intake intoscripts/response_drafter.py. Output: proof-point matrix per requirement with STRONG / PARTIAL / GAP, win-theme injection, GAP audit.python scripts/response_drafter.py--inputdraft_input.json--outputmarkdownmatrix.mdHard rule:GAP requirements are surfaced, never invented around. Leadership reads the GAP audit and decides: close the gap, partner-bid, or no-bid.Step 3 — Apply win-theme strategyShipley method: 3-5 themes that span requirements. Each theme answers “why us over the incumbent / competitor on the criteria the buyer named.”response_drafter.pyshows which themes thread through which requirements — a theme appearing in 2 requirements is decorative, not strategic, and gets flagged.Step 4 — Estimate winrateFeed deal context (fit %, incumbent strength, relationship, decision-criteria alignment, late-entry, competitor count, deal size vs. average) intoscripts/winrate_predictor.py. Output: Shipley-derived estimate 0-100% confidence band factor breakdown BID / PARTNER-BID / NO-BID verdict.python scripts/winrate_predictor.py--inputdeal_context.json--profileenterprise-software--outputmarkdownNo-bid threshold:estimate 20% triggers automatic no-bid recommendation.Step 5 — DecideTake parsed RFP proof-point matrix GAP audit winrate estimate into the go / no-go review. Skill does not commit pursuit budget — leadership does.Scriptsscripts/rfp_parser.py— section requirement extractor (regex cue-word heuristics, stdlib only)scripts/response_drafter.py— proof-point matrix win-theme injection GAP auditscripts/winrate_predictor.py— Shipley-derived factor model bid/no-bid verdict, industry-profile-tunedAll scripts: stdlib only (argparse, json, sys, pathlib, re, collections, statistics).--helpand--samplework on all three.Referencesreferences/shipley_method_canon.md— Shipley Proposal Guide v6, Shipley Capture Guide, APMP BoK, Tom Sant, Tom Searcy Henry DeVries, Strategic Proposals research, Larry Newmanreferences/rfp_strategy_canon.md— FAR, GSA, Forrester, Gartner, Bain, McKinsey, B2B International on RFP win-rates and buyer behaviorreferences/rfp_anti_patterns.md— Shipley failure modes, APMP cases, Strategic Proposals research, federal loss reviews, MIT Sloan, Bain commercial-discipline, GartnerAssumptionsThe RFP is the ground truth.If the buyer asked it, answer it — in the order they asked, in the format they specified. Re-organizing for narrative flow is for 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.“We’re the leader in X” is a marketing claim; “Your operations team reduces incident MTTR by 60% with the same headcount” is a win-theme. Shipley canon, not optional.Winrate estimates are directional.The model is a discipline tool to force honest pursuit-qualification — not an oracle. 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 security depth.Late entry is a structural disadvantage.Entering after the RFP issued, with no relationship history, drops base rate ~15%. The skill names this, doesn’t hide it.Anti-patternsInventing a proof point to fill a GAP.Hard rule violation. GAPs surface for leadership decision, not for prose-laundering. Seereferences/rfp_anti_patterns.md.Responding to every RFP.Without a qualified bid / no-bid gate, the team burns capacity on 20% winrate pursuits and loses the 50% pursuits to lack of focus. Bain commercial-discipline research.Generic response with no win-theme.A proposal that could be sent verbatim by any competitor is decorative. Shipley failure mode #1.Missing a mandatory disqualifier late.FedRAMP / HIPAA / ISO 27001 / SOC 2 / on-shore data residency caught on Day 12 of a 14-day response wasted pursuit. Parser surfaces these on Day 1.Answering the question YOU wanted asked.RFP responder discipline: answer what they asked, in their words, in their order. Re-framing belongs in cover letters, not in the compliance matrix.No compliance matrix.Every requirement should map to a response section page number. Evaluators score on a matrix; respondents who don’t provide one self-disqualify on traceability.Late-entry without acknowledging the relationship deficit.Entering cold against an incumbent with a 3-year relationship and no champion sub-20% winrate. Pretending otherwise wastes Sales Engineering capacity.Treating WEIGHTED requirements like MANDATORY.Score-weighted requirements reward depth on the high-weight items, not uniform mediocrity across all. Shipley capture method.Distinct frombusiness-growth/contract-and-proposal-writer— free-form narrative proposals where YOU set the structure (executive briefs, capability statements, unsolicited proposals). RFP-responder handlesbuyer-dictated structured QAwhere the buyer set the questions,sections, scoring criteria, and format. Different artifact, different decision logic.c-level-advisor/general-counsel-advisor— contract redline and IP/risk review AFTER award. RFP-responder operates BEFORE award, on the response strategy.marketing-skill/*— external marketing assets (web copy, content, ASO, SEO, brand voice) for many-to-many audiences. RFP-responder produces asingle-buyer artifactwith deterministic compliance requirements.commercial/deal-desk— per-deal discount routing on a closing opportunity. RFP-responder is pursuit-stage; deal-desk is close-stage.commercial/pricing-strategist— pricing-model design for a new product. RFP-responder consumes existing pricing as input to the commercial-terms section.Forcing-question library (Matt Pocock grill discipline)Walked one at a time before any script runs. Recommended answer canon citation per question. Never bundled.“What’s your STRONG / PARTIAL / GAP split on the MANDATORY requirements?”Recommended: STRONG ≥ 70% on MANDATORY before bidding. PARTIAL/GAP on any MANDATORY either close the gap pre-submission or no-bid.Canon: ShipleyProposal Guide v6— capture-management discipline, “Pgw (probability of win) is bounded by your weakest MANDATORY.”“Is there an incumbent, and how strong is their position?”Recommended: strong incumbent (3 years, no displacement event) drops base winrate ~30%. Don’t bid without a named displacement trigger.Canon: Forrester B2B-RFP research — incumbents win 70-80% of renewal RFPs absent a named failure event.“Did you enter the conversation before or after the RFP issued?”Recommended: late-entry (after RFP issued, no prior engagement) drops winrate ~15% and signals the RFP was scoped to someone else’s strengths.Canon: Tom Searcy Henry DeVriesHow to Win Big Business— “If you didn’t help write the RFP, you’re column fodder.”“What are your 3-5 win-themes, and does each thread through ≥2 requirements?”Recommended: themes that appear in only one requirement are decorative. Themes must ladder up across MANDATORY WEIGHTED sections.Canon: ShipleyCapture Guide— win-themes are the buyer-side answer to “why us” across the evaluation criteria, not seller-side feature lists.“For every claim in the response, can you name the verifiable source?”Recommended: every claim → case study / certification / customer reference / technical attestation / benchmark. Unsourced claims GAPs.Canon: APMP BoK — “Substantiation: every assertion in a proposal must be backed by evidence the evaluator can independently verify.”“What’s the bid / no-bid threshold you committed to BEFORE seeing this RFP?”Recommended: pre-committed threshold (e.g., winrate ≥ 25%, STRONG ≥ 70% on MANDATORY, named champion). Post-hoc rationalization is how teams end up bidding 5% pursuits.Canon: Bain RFP-win-rate studies — disciplined bid/no-bid gates lift win-rate from ~15% to ~35%.“What does the buyer’s evaluation team actually score on?”Recommended: if the RFP discloses scoring criteria, weight your response effort proportionally. If undisclosed, ask. If you can’t ask, that itself is a relationship-deficit signal.Canon: Strategic Proposals proposal-management research — evaluators score on the rubric they were given, not on your narrative.Walk depth-first. Lock 1-3 before opening 4-7. After all 7 are answered, invokerfp_parser.py→response_drafter.py→winrate_predictor.pyin sequence. If question 6 lands on “we don’t have a threshold,” set one now or no-bid.