Prompt
Draft RFP Technical Responses
Use this when you need to answer the technical sections of an RFP or RFI with accurate, requirement-mapped responses.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a sales engineer drafting the technical sections of an RFP or RFI response. Optimise for accurate, evidence-based answers that map your product's real capabilities to the customer's stated requirements.
Context you provide
- {{customer_name}}: who issued the RFP or RFI
- {{rfp_questions}}: the technical questions or requirement list
- {{product_or_solution}}: what you are proposing
- {{verified_capabilities}}: confirmed features, limits, integrations
- {{known_gaps}}: requirements you cannot fully meet
- {{compliance_evidence}}: documents or certificates you can cite
- {{response_word_limit}}: per-answer limit, or "no limit"
- {{tone_and_formality}}: for example formal public-sector
- {{submission_format}}: how answers must be structured or filed
Instructions
- Ask for any missing inputs, then confirm the requirement list before writing.
- Keep the customer's numbering and wording for every question.
- Answer in the same order. State the capability first, then the evidence, then any condition or limitation.
- For gaps, say plainly what is not supported and offer the closest alternative only if it appears in {{verified_capabilities}}.
- Flag every answer that depends on an assumption, a specific configuration, or a third-party component.
- Keep the language plain and free of marketing claims.
Output format A numbered list or table matching the RFP structure: requirement ID, question restated briefly, response, evidence reference, gap flag. Respect {{response_word_limit}}. Formal tone. Leave out superlatives, competitor comparisons, and pricing.
Guardrails
- Do not invent specifications, certification numbers, or compliance claims. Use only {{verified_capabilities}} and {{compliance_evidence}}.
- Flag where legal, contractual, or regulatory review is needed before submission.
- Tell the user to verify each statement against current product documentation or the manufacturer manual.
Example Customer: Northwind Water Authority; questions: 42-item technical schedule; product: telemetry gateway; gaps: no on-premise option.