Respond to an RFP
Surface the 3 deciding questions — don't treat RFPs as flat lists.
by @whitney · recommended tool Claude · 0 unlocks
0
You'll need
CLAUDE SKILLS
docx
CONNECTORS
Google Drive
EXAMPLES · WHAT THIS PROMPT PRODUCES
Sample output
**RFP Response — Acme Logistics: Managed Cloud Migration (draft answers)** **Q1. Describe your experience migrating monolithic .NET apps to AWS.** We've delivered 30+ .NET-to-AWS migrations, including three at large logistics firms. Standard path: containerize on ECS/Fargate, replatform SQL Server to RDS, and stage cutover behind a strangler-fig pattern to avoid a big-bang risk window. **Q2. What is your approach to zero-downtime cutover?** Blue/green deployments with weighted DNS, read-replica promotion, and a tested rollback runbook. We rehearse cutover in a staging mirror before production. *Gap flag:* We'd need to confirm whether your WMS vendor supports parallel-run mode — this materially affects the downtime window. **Q3. Describe your security and compliance posture.** SOC 2 Type II; encryption at rest and in transit; least-privilege IAM. *Clarify:* Does Acme require FedRAMP, or is SOC 2 sufficient? **"We'd need to clarify" questions** - Current SQL Server version + total DB size? - Is the WMS COTS or custom? - Hard compliance requirements beyond SOC 2? **The 3 questions that most determine win/loss** 1. **Downtime tolerance** — drives architecture and price more than anything else. 2. **WMS parallel-run support** — gates the cutover strategy. 3. **Budget ceiling vs. timeline** — tells us whether to propose phased or all-at-once.
PRICE HISTORY0 cr · current
PROMPT TEMPLATE · v1.0.0
I'll paste an RFP and our company profile. For each question: draft a specific answer using our real capabilities, flag gaps, and write the "we'd need to clarify" questions. Consistent tone across all answers. Surface the 3 questions that most determine win/loss.
RESULTS · WHAT PEOPLE GOT
0Sign in to show colleagues what this case produced.
No results posted yet. Used this case? Show colleagues what it produced.
DISCUSSION
0 commentsSign in to join the conversation.
No comments yet — be the first.
MORE LIKE THIS