rfp-response
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseRFP Response
RFP响应
Transform complex RFP requirements into winning proposals through systematic analysis, compliant structure, and compelling differentiation.
通过系统化分析、合规结构设计和差异化亮点打造,将复杂的RFP需求转化为成功的提案。
When to Use This Skill
何时使用此技能
- Responding to formal RFPs/RFIs
- Creating proposal templates
- Developing win themes
- Compliance matrix creation
- Executive summary writing
- 响应正式的RFP/RFI
- 创建提案模板
- 开发制胜主题
- 制作合规矩阵
- 撰写执行摘要
Methodology Foundation
方法论基础
Based on Shipley Associates Proposal Management and APMP best practices, combining:
- Capture management principles
- Compliance-first structuring
- Win theme development
- Evaluation-driven writing
基于Shipley Associates Proposal Management和APMP最佳实践,结合:
- 商机捕获管理原则
- 合规优先的结构设计
- 制胜主题开发
- 以评估为导向的写作
What Claude Does vs What You Decide
Claude的工作 vs 你的决策
| Claude Does | You Decide |
|---|---|
| Analyzes requirements | Bid/no-bid decision |
| Creates compliance matrix | Pricing strategy |
| Structures sections | Resource allocation |
| Drafts content | Win themes priority |
| Identifies gaps | Go/no-go approval |
| Claude的工作 | 你的决策 |
|---|---|
| 分析需求 | 投标/不投标决策 |
| 创建合规矩阵 | 定价策略 |
| 构建章节结构 | 资源分配 |
| 撰写内容草稿 | 制胜主题优先级 |
| 识别需求缺口 | 批准是否推进 |
Instructions
操作指南
Step 1: RFP Analysis
步骤1:RFP分析
Initial Assessment:
| Element | What to Extract |
|---|---|
| Issuer | Organization, contact |
| Due Date | Submission deadline |
| Budget | Stated or estimated |
| Scope | Core requirements |
| Evaluation | Criteria and weights |
| Format | Page limits, structure |
Bid/No-Bid Factors:
| Factor | Score 1-5 |
|---|---|
| Solution fit | |
| Relationship strength | |
| Competitive position | |
| Resource availability | |
| Strategic value | |
| Win probability |
初始评估:
| 要素 | 提取内容 |
|---|---|
| 发布方 | 机构、联系人 |
| 截止日期 | 提交截止时间 |
| 预算 | 明确说明或预估金额 |
| 范围 | 核心需求 |
| 评估标准 | 评分项及权重 |
| 格式要求 | 页数限制、文档结构 |
投标/不投标考量因素:
| 因素 | 评分1-5 |
|---|---|
| 解决方案匹配度 | |
| 客户关系强度 | |
| 竞争地位 | |
| 资源可用性 | |
| 战略价值 | |
| 中标概率 |
Step 2: Compliance Matrix
步骤2:合规矩阵
Requirement Tracking:
| Req # | Requirement | Response Section | Status | Owner |
|---|---|---|---|---|
| 1.1 | Description | 3.2 | Draft | Name |
| 1.2 | Description | 3.3 | Review | Name |
Compliance Levels:
- Compliant (C) - Fully meets requirement
- Partial (P) - Meets with explanation
- Non-Compliant (NC) - Does not meet
- Exception (E) - Propose alternative
需求跟踪:
| 需求编号 | 需求内容 | 响应章节 | 状态 | 负责人 |
|---|---|---|---|---|
| 1.1 | 需求描述 | 3.2 | 草稿 | 姓名 |
| 1.2 | 需求描述 | 3.3 | 审核中 | 姓名 |
合规等级:
- 合规(C)- 完全满足需求
- 部分合规(P)- 满足但需说明
- 不合规(NC)- 不满足需求
- 例外(E)- 提议替代方案
Step 3: Win Theme Development
步骤3:制胜主题开发
Theme Framework:
| Theme | Evidence | Differentiator | Evaluator Benefit |
|---|---|---|---|
| Theme 1 | Proof point | Why unique | What they gain |
Theme Formula:
[Feature] + [Evidence] = [Benefit to Evaluator]
Example: "Our dedicated success team (feature) +
98% retention rate (evidence) =
lower risk of implementation failure (benefit)"主题框架:
| 主题 | 证据 | 差异化亮点 | 评估方收益 |
|---|---|---|---|
| 主题1 | 证明点 | 独特性所在 | 评估方可获得的价值 |
主题公式:
[功能] + [证据] = [评估方收益]
示例:"我们专属的成功团队(功能) +
98%的客户留存率(证据) =
更低的实施失败风险(收益)"Step 4: Section Writing
步骤4:章节撰写
Structure per Section:
- Theme statement (opening sentence)
- Understanding (their need)
- Approach (your solution)
- Evidence (proof it works)
- Benefit (why it matters to them)
Ghost Competitors:
- Address competitor weaknesses indirectly
- Never name competitors
- Position your strength against their weakness
单章节结构:
- 主题陈述(开篇句)
- 需求理解(客户的需求)
- 解决方案(我方的方案)
- 证据支撑(方案有效性证明)
- 价值体现(对客户的重要性)
隐性竞争对手应对策略:
- 间接提及竞争对手的弱点
- 绝不指名道姓
- 用我方优势对标对方弱点
Step 5: Executive Summary
步骤5:执行摘要
Executive Summary Formula:
| Section | Length | Content |
|---|---|---|
| Hook | 1-2 sentences | Their biggest challenge |
| Understanding | 1 paragraph | Prove you get it |
| Solution | 1-2 paragraphs | Your approach |
| Why Us | 1 paragraph | Differentiation |
| CTA | 1-2 sentences | Clear next step |
执行摘要公式:
| 部分 | 篇幅 | 内容 |
|---|---|---|
| 切入点 | 1-2句话 | 客户面临的最大挑战 |
| 需求理解 | 1段 | 证明我方理解客户需求 |
| 解决方案 | 1-2段 | 我方的实施路径 |
| 选择我方的理由 | 1段 | 差异化优势 |
| 行动号召 | 1-2句话 | 明确的下一步计划 |
Examples
示例
Example 1: Full RFP Response Structure
示例1:完整RFP响应结构
Input:
Help me respond to this RFP:
- Client: City of Springfield
- Need: New CRM system for citizen services
- Budget: $500K
- Timeline: 18-month implementation
- Evaluation: 40% technical, 30% price, 20% experience, 10% referencesOutput:
undefined输入:
Help me respond to this RFP:
- Client: City of Springfield
- Need: New CRM system for citizen services
- Budget: $500K
- Timeline: 18-month implementation
- Evaluation: 40% technical, 30% price, 20% experience, 10% references输出:
undefinedRFP Response Plan: City of Springfield CRM
RFP Response Plan: City of Springfield CRM
Win Themes
Win Themes
| Theme | Evidence | Application |
|---|---|---|
| Government Expertise | 47 municipal deployments | Use throughout |
| Citizen-Centric | 4.8/5 satisfaction score | Technical sections |
| On-Time Delivery | 94% on-schedule rate | Timeline section |
| Theme | Evidence | Application |
|---|---|---|
| Government Expertise | 47 municipal deployments | Use throughout |
| Citizen-Centric | 4.8/5 satisfaction score | Technical sections |
| On-Time Delivery | 94% on-schedule rate | Timeline section |
Compliance Matrix (Sample)
Compliance Matrix (Sample)
| Req # | Requirement | Section | Status | Win Theme |
|---|---|---|---|---|
| 2.1 | Multi-channel citizen intake | 4.1 | C | Citizen-Centric |
| 2.2 | Integration with existing 311 | 4.2 | C | Gov Expertise |
| 2.3 | Mobile app for citizens | 4.3 | C | Citizen-Centric |
| 2.4 | Real-time reporting dashboard | 4.4 | C | Gov Expertise |
| 2.5 | ADA compliance | 4.5 | C | Citizen-Centric |
| Req # | Requirement | Section | Status | Win Theme |
|---|---|---|---|---|
| 2.1 | Multi-channel citizen intake | 4.1 | C | Citizen-Centric |
| 2.2 | Integration with existing 311 | 4.2 | C | Gov Expertise |
| 2.3 | Mobile app for citizens | 4.3 | C | Citizen-Centric |
| 2.4 | Real-time reporting dashboard | 4.4 | C | Gov Expertise |
| 2.5 | ADA compliance | 4.5 | C | Citizen-Centric |
Executive Summary (Draft)
Executive Summary (Draft)
THE CHALLENGE
Springfield's 200,000 citizens deserve modern, responsive government services. Your current system, built 15 years ago, creates delays and frustration for both citizens and staff.
OUR UNDERSTANDING
Springfield needs more than a CRM upgrade—you need a citizen experience transformation. Based on our analysis of your RFP and conversations with your team, your priorities are:
- Reducing citizen wait times from 10+ minutes to under 2
- Enabling true omnichannel service (phone, web, mobile, in-person)
- Providing leadership with real-time visibility into service delivery
- Ensuring full ADA and accessibility compliance
OUR SOLUTION
CivicConnect, our purpose-built municipal CRM, addresses these exact needs. Unlike generic CRMs adapted for government, CivicConnect was designed from day one for citizen services.
Key capabilities:
- Unified citizen profile across all channels
- AI-assisted routing reducing resolution time by 40%
- Real-time dashboards built for elected officials and department heads
- Native accessibility exceeding WCAG 2.1 AA standards
WHY [COMPANY]
With 47 successful municipal deployments, including [Similar City] and [Another City], we understand government's unique requirements. Our 94% on-schedule delivery rate and 98% client retention demonstrate our commitment to partnership, not just projects.
NEXT STEPS
We propose a discovery workshop with your team to validate requirements and refine the implementation approach. This investment in upfront alignment is how we achieve our 94% on-time rate.
THE CHALLENGE
Springfield's 200,000 citizens deserve modern, responsive government services. Your current system, built 15 years ago, creates delays and frustration for both citizens and staff.
OUR UNDERSTANDING
Springfield needs more than a CRM upgrade—you need a citizen experience transformation. Based on our analysis of your RFP and conversations with your team, your priorities are:
- Reducing citizen wait times from 10+ minutes to under 2
- Enabling true omnichannel service (phone, web, mobile, in-person)
- Providing leadership with real-time visibility into service delivery
- Ensuring full ADA and accessibility compliance
OUR SOLUTION
CivicConnect, our purpose-built municipal CRM, addresses these exact needs. Unlike generic CRMs adapted for government, CivicConnect was designed from day one for citizen services.
Key capabilities:
- Unified citizen profile across all channels
- AI-assisted routing reducing resolution time by 40%
- Real-time dashboards built for elected officials and department heads
- Native accessibility exceeding WCAG 2.1 AA standards
WHY [COMPANY]
With 47 successful municipal deployments, including [Similar City] and [Another City], we understand government's unique requirements. Our 94% on-schedule delivery rate and 98% client retention demonstrate our commitment to partnership, not just projects.
NEXT STEPS
We propose a discovery workshop with your team to validate requirements and refine the implementation approach. This investment in upfront alignment is how we achieve our 94% on-time rate.
Section 4.1: Multi-Channel Citizen Intake (Draft)
Section 4.1: Multi-Channel Citizen Intake (Draft)
CivicConnect's unified intake system transforms how Springfield citizens access services.
Understanding the Need: Springfield citizens currently experience fragmented service—phone callers repeat information to multiple departments, online submissions disappear into queues, and walk-in visitors wait while staff search for context. This frustration is avoidable.
Our Approach: CivicConnect provides true omnichannel intake with a single citizen record:
| Channel | Capability | Citizen Benefit |
|---|---|---|
| Phone | CTI integration, screen pop | Staff see full history instantly |
| Web | Smart forms, auto-routing | Right department first time |
| Mobile | GPS-enabled reporting | Location auto-populated |
| In-Person | Queue management, kiosk | Reduced wait times |
| NLP categorization | Faster routing |
Evidence: When [Similar City] implemented this approach, they saw:
- 62% reduction in repeat contacts
- 3.2-minute average resolution (from 10.4 minutes)
- 89% citizen satisfaction (from 67%)
Benefit to Springfield: Citizens get answers faster, staff spend time solving problems rather than gathering information, and leadership sees exactly where bottlenecks occur.
CivicConnect's unified intake system transforms how Springfield citizens access services.
Understanding the Need: Springfield citizens currently experience fragmented service—phone callers repeat information to multiple departments, online submissions disappear into queues, and walk-in visitors wait while staff search for context. This frustration is avoidable.
Our Approach: CivicConnect provides true omnichannel intake with a single citizen record:
| Channel | Capability | Citizen Benefit |
|---|---|---|
| Phone | CTI integration, screen pop | Staff see full history instantly |
| Web | Smart forms, auto-routing | Right department first time |
| Mobile | GPS-enabled reporting | Location auto-populated |
| In-Person | Queue management, kiosk | Reduced wait times |
| NLP categorization | Faster routing |
Evidence: When [Similar City] implemented this approach, they saw:
- 62% reduction in repeat contacts
- 3.2-minute average resolution (from 10.4 minutes)
- 89% citizen satisfaction (from 67%)
Benefit to Springfield: Citizens get answers faster, staff spend time solving problems rather than gathering information, and leadership sees exactly where bottlenecks occur.
Evaluation Strategy
Evaluation Strategy
| Criteria | Weight | Our Strength | Strategy |
|---|---|---|---|
| Technical | 40% | Strong | Lead with gov-specific features |
| Price | 30% | Competitive | Emphasize TCO, not just license |
| Experience | 20% | Very Strong | Heavy use of case studies |
| References | 10% | Strong | Prep 3 referenceable clients |
Ghosting Competitors:
- Generic CRM vendors: Emphasize "purpose-built for government"
- Low-cost options: Focus on "total cost of ownership" and implementation risk
- Larger vendors: Highlight "dedicated government team" and responsiveness
undefined| Criteria | Weight | Our Strength | Strategy |
|---|---|---|---|
| Technical | 40% | Strong | Lead with gov-specific features |
| Price | 30% | Competitive | Emphasize TCO, not just license |
| Experience | 20% | Very Strong | Heavy use of case studies |
| References | 10% | Strong | Prep 3 referenceable clients |
Ghosting Competitors:
- Generic CRM vendors: Emphasize "purpose-built for government"
- Low-cost options: Focus on "total cost of ownership" and implementation risk
- Larger vendors: Highlight "dedicated government team" and responsiveness
undefinedExample 2: Quick Compliance Check
示例2:快速合规检查
Input:
Quick compliance check for these requirements:
1. Must support 500 concurrent users
2. 99.9% uptime SLA required
3. Data must remain in US
4. SOC 2 Type II certification
5. Integration with SalesforceOutput:
undefined输入:
Quick compliance check for these requirements:
1. Must support 500 concurrent users
2. 99.9% uptime SLA required
3. Data must remain in US
4. SOC 2 Type II certification
5. Integration with Salesforce输出:
undefinedCompliance Quick Check
Compliance Quick Check
| Req | Requirement | Status | Notes |
|---|---|---|---|
| 1 | 500 concurrent users | C | Supports 2,000+ |
| 2 | 99.9% uptime SLA | C | Standard tier includes |
| 3 | US data residency | C | AWS US-East only |
| 4 | SOC 2 Type II | C | Current certification |
| 5 | Salesforce integration | P | Requires middleware |
| Req | Requirement | Status | Notes |
|---|---|---|---|
| 1 | 500 concurrent users | C | Supports 2,000+ |
| 2 | 99.9% uptime SLA | C | Standard tier includes |
| 3 | US data residency | C | AWS US-East only |
| 4 | SOC 2 Type II | C | Current certification |
| 5 | Salesforce integration | P | Requires middleware |
Action Required
Action Required
Requirement 5 (Salesforce):
- Status: Partial compliance
- Gap: No native connector
- Solution: MuleSoft integration (additional $15K)
- Response language: "Integration achieved through certified MuleSoft connector, providing real-time bi-directional sync"
Requirement 5 (Salesforce):
- Status: Partial compliance
- Gap: No native connector
- Solution: MuleSoft integration (additional $15K)
- Response language: "Integration achieved through certified MuleSoft connector, providing real-time bi-directional sync"
Recommended Response Approach
Recommended Response Approach
Full compliance on 4/5 requirements. For #5, lead with capability, mention integration approach, include cost in pricing section. Do not highlight as limitation.
undefinedFull compliance on 4/5 requirements. For #5, lead with capability, mention integration approach, include cost in pricing section. Do not highlight as limitation.
undefinedSkill Boundaries
技能边界
What This Skill Does Well
此技能擅长的工作
- Structuring compliant responses
- Developing win themes
- Creating evaluation-aligned content
- Identifying compliance gaps
- 构建合规的响应文件
- 开发制胜主题
- 创建与评估标准对齐的内容
- 识别合规缺口
What This Skill Cannot Do
此技能无法完成的工作
- Know competitor pricing
- Access proprietary client info
- Guarantee win probability
- Replace subject matter experts
- 了解竞争对手的定价
- 访问客户的专有信息
- 保证中标概率
- 替代领域专家
When to Escalate to Human
何时需转交人工处理
- Bid/no-bid decisions
- Pricing strategy
- Executive approval
- Reference coordination
- 投标/不投标决策
- 定价策略制定
- 高管审批
- 客户推荐协调
Iteration Guide
迭代指南
Follow-up Prompts:
- "Draft the implementation timeline section"
- "How should we address [specific weakness]?"
- "Create a ghost competitor strategy for [competitor type]"
- "Write the pricing justification narrative"
后续提示示例:
- "撰写实施时间线章节"
- "我们应如何应对[特定劣势]?"
- "针对[竞争对手类型]制定隐性应对策略"
- "撰写定价合理性说明"
References
参考资料
- Shipley Associates Proposal Guide
- APMP Body of Knowledge
- Government RFP Best Practices
- Federal Acquisition Regulations (for gov RFPs)
- Shipley Associates Proposal Guide
- APMP Body of Knowledge
- 政府RFP最佳实践
- 联邦采购条例(适用于政府RFP)
Related Skills
相关技能
- - Post-award contracts
contract-review - - Oral presentations
sales-pitch-dunford - - Win strategy
competitive-analysis
- - 授标后合同处理
contract-review - - 口头演示
sales-pitch-dunford - - 中标策略
competitive-analysis
Skill Metadata
技能元数据
- Domain: Legal / Sales
- Complexity: Advanced
- Mode: cyborg
- Time to Value: 2-8 hours per response
- Prerequisites: RFP document, solution knowledge
- 领域: 法律 / 销售
- 复杂度: 高级
- 模式: 人机协作
- 价值实现时间: 每份响应需2-8小时
- 前置条件: RFP文档、解决方案相关知识