RFP Response

Read and respond to RFPs, RFIs, and security questionnaires. AI parses requirements, generates Salesforce-specific responses, flags risk areas, and produces a compliance response matrix.

Skill Details

Install this skill

Versionv1.0.0AuthorJorge ArteagaLicenseMITSections13

Works with

Claude CodeCursorWindsurf

When This Skill Owns the TaskWorkflow

Required Context to Gather FirstWorkflow

Before responding to an RFP, ask for or infer:

RFP document or key sections — What are they asking? Share the requirements.

Salesforce products in scope — Which clouds are we proposing?

Submission deadline — When is this due? Is it realistic to respond well?

Bid/no-bid decision — Has someone qualified this as worth pursuing?

Known relationships — Do we know anyone at the organization? Is there a preferred vendor?

Win themes — What are our 2-3 strategic advantages in this bid?

Subject matter experts — What internal resources (product, security, legal) do we need?

WorkflowWorkflow

Bid/No-Bid Assessment — Apply the qualifier table before writing a word.

Parse the RFP — Categorize requirements into sections (functional, technical, security, commercial).

Set the win themes — Identify 2-3 strategic messages that run through every answer.

Draft responses — For each requirement, apply the STAR format (Situation, Task, Action, Result).

Flag risk items — Mark requirements where Salesforce doesn't fully comply or needs to caveat.

Handle "no" gracefully — For gaps, apply the "bridge" strategy rather than a flat no.

Build the response matrix — Compile all responses with compliance indicators.

Review before submitting — Apply the scoring rubric; fix anything below 80%.

Core Frameworks

Bid/No-Bid Qualifier

Score each criterion 0-2. Total below 8 = consider no-bid.

Total Score:

10-12: Pursue aggressively
6-9: Pursue with resource caps
Below 6: No-bid; write a respectful decline

Response Formatting Rules

Every RFP response should follow these rules:

Mirror the requirement language — Use the same terminology they used in the requirement.

Lead with compliance — Start with "Yes" or "Salesforce fully supports..." before explanation.

Prove it, don't just say it — Every capability claim needs evidence (Salesforce documentation URL, customer reference, or named feature).

Right-size the response — Match length to question importance. "Do you support SSO?" = 2 sentences. "Describe your data governance approach" = 2 paragraphs.

Avoid generic marketing language — "Salesforce is the world's #1 CRM" does not answer the question.

The STAR Response Format

For narrative/functional requirements:

Code

SITUATION: Briefly set the context for Salesforce's capability in this area.
TASK: What specific capability or function addresses this requirement?
ACTION: How does the feature work? (Brief mechanics, not a manual)
RESULT: What outcome can the customer expect? Include a reference if possible.

Handling Gaps: The Bridge Strategy

When Salesforce doesn't fully meet a requirement, never write "No" without a bridge:

Code

Structure:
"While Salesforce [what it does or doesn't do natively], customers achieve
[requirement outcome] by [alternative approach / configuration / partner solution / roadmap].
[Customer reference] is an example of this approach."

Compliance indicator: "Partial" or "Via Partner" rather than "No"

Example:

Requirement: "Does the system support real-time bidirectional sync with SAP S/4HANA?"

Response: "While Salesforce does not ship a native SAP S/4HANA connector, real-time bidirectional sync is achieved through Salesforce's MuleSoft integration platform or certified AppExchange ISV connectors, including [MuleSoft Accelerator for SAP / Jitterbit / SnapLogic]. These are production deployments trusted by over [X] Salesforce customers with SAP environments."

Security Questionnaire Quick Reference

Common security questions and Salesforce's standard responses:

Output FormatTemplate

RFP Response Matrix

MARKDOWN

# RFP Response Matrix — [RFP Name]
**Issuer:** [Company] | **Due:** [Date] | **SE:** [Name] | **AE:** [Name]

## Win Themes
1. [Win Theme 1 — the strategic message that runs through all responses]
2. [Win Theme 2]
3. [Win Theme 3]

## Response Summary

| Req # | Requirement Summary | Compliance | Response Status |
|-------|---------------------|------------|----------------|
| [X] | [Brief description] | Full / Partial / No / Via Partner | Draft / Complete / Review |

## Detailed Responses

### Section [X]: [Section Name]

**Requirement [X.1]:** [Full requirement text]
**Compliance:** [Full / Partial / No / Via Partner / On Roadmap]
**Response:**
[STAR-format response]
**References:** [Link, customer name, or doc]

---

## Risk Register

| Req # | Risk Description | Severity | Bridge Strategy |
|-------|-----------------|---------|----------------|
| [X] | [What we can't do or caveating] | H/M/L | [Alternative approach] |

## Recommended Appendices
- [ ] Company overview (1 page)
- [ ] Implementation methodology
- [ ] Customer references (3 minimum; in same industry preferred)
- [ ] Security documentation (SOC 2, ISO certifications)
- [ ] Pricing / commercial proposal

Anti-PatternsReference

Scoring Rubric (100 Points)Reference

Cross-Skill IntegrationReference

Task	This Skill	Defer To
Respond to RFP/RFI requirements	Yes	—
Assess whether to bid	Yes	—
Answer security questionnaires (SIG, CAIQ)	Yes	—
Flag risks and "no" strategies	Yes	—
Design the proposed solution architecture	No	sf-se-whiteboard
Build a proactive business case without an RFP	No	sf-se-proof-of-value
Write the presentation for the orals/demo phase	No	sf-se-presentation
Criterion	0	1	2
Relationship	No contacts; cold RFP	One contact, limited access	Champion or exec sponsor inside
Technical Fit	Core requirements are gaps	Mostly fits; 2-3 gaps	Strong fit; Salesforce is purpose-built for this
Competitive Position	Likely incumbent is not Salesforce	Level playing field	We have advantages; they've seen Salesforce
Strategic Value	Small deal; no logo value	Average deal	Marquee customer; strategic industry
Win Probability	Below 20%	20-50%	Above 50%
Resources Available	No SE/PS capacity	Stretched	Dedicated pursuit team available
Question Area	Salesforce Position
Data residency	Salesforce supports data residency in EU, US, APAC, and others via Hyperforce
Encryption at rest	AES-256 encryption at rest for all data
Encryption in transit	TLS 1.2/1.3 for all data in transit
SOC 2 Type II	Yes — available at trust.salesforce.com
ISO 27001	Yes — Salesforce is ISO 27001 certified
GDPR compliance	Salesforce acts as a data processor; DPA available
Penetration testing	Annual third-party pen tests; customer pen testing allowed with permission
Uptime SLA	99.9% for production environments
MFA enforcement	Mandatory MFA available; can be enforced org-wide
Audit logs	Event Monitoring add-on provides full audit trail
Anti-Pattern	Why It Fails	Fix
Responding to every RFP that comes in	Low-quality responses consume SE time with little return	Always do the bid/no-bid assessment first
Writing generic responses that don't address the specific requirement	Evaluators notice; scores drop	Mirror the requirement's exact language; answer what was asked
Saying "No" without a bridge	Eliminates Salesforce from consideration for a solvable gap	Always provide an alternative path: partner, configuration, or roadmap
Copying from the last RFP verbatim	Dates, customer names, and context mismatch; looks careless	Reuse structure, not specific answers — always refresh with current evidence
Overpromising on roadmap items	"Coming soon" responses create legal and relationship risk if features don't ship	Only reference roadmap items that are publicly announced; caveat clearly
Skipping the win themes	Responses are a list of facts with no strategic thread	Define 2-3 win themes before writing anything; thread them through every answer
Long responses to simple binary questions	Evaluators have hundreds of questions to read; oversized answers waste their time	Match response length to question complexity
Category	Points	Pass Criteria
Compliance Coverage	25	Every requirement has a compliance indicator and a response
Response Quality	25	Responses are specific, evidence-backed, and mirror requirement language
Risk Handling	20	All gaps have a bridge strategy; no flat "No" responses
Win Theme Consistency	15	Win themes appear throughout the narrative responses
Completeness	15	All requested appendices (references, security docs) are assembled
Skill	When to Use It
sf-se-whiteboard	Design the solution architecture that the RFP proposes
sf-se-architecture-review	Use to develop the technical response section
sf-se-proof-of-value	Add ROI and business case data to the value proposition section
sf-se-presentation	Build the orals / demo presentation that follows the written RFP
sf-se-competitive	Craft win themes that position Salesforce vs. the likely shortlist