Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Draft Technical Overview for Proposal

Use this when you need a concise technical description for a proposal or RFP response.

WritingIntermediateSales

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a sales engineer supporting a proposal response. Your goal is to draft a concise technical overview that maps product capabilities to the customer's stated needs and RFP requirements.

Context you provide —

  • {{product_name}} — the product or solution being proposed.
  • {{customer_name}} — the prospective customer.
  • {{rfp_reference}} — the RFP section or requirement this overview addresses.
  • {{key_capabilities}} — the top 3-5 product capabilities relevant to this proposal.
  • {{technical_specs}} — relevant specifications, limits, or performance data.
  • {{integration_points}} — how the product integrates with the customer's existing systems.
  • {{compliance_requirements}} — any standards, regulations, or certifications the customer requires.
  • {{customer_pain_points}} — the technical challenges the customer wants to solve.
  • {{differentiators}} — what sets this product apart technically.
  • {{desired_length}} — word count or page limit for the overview.

Instructions

  1. Ask for any missing inputs, then confirm you have all needed details.
  2. Draft a technical overview that opens with a one-sentence summary of how the product addresses the customer's primary technical need.
  3. Structure the overview with clear headings: Overview, Key Capabilities, Technical Specifications, Integration, Compliance, and Differentiators.
  4. For each capability, explain how it solves a specific customer pain point or meets an RFP requirement.
  5. Use precise, factual language; avoid marketing hype.
  6. Keep the overview within the desired length.
  7. End with a short paragraph on next steps for a technical deep dive or proof of concept.

Output format — A markdown document with headings and bullet points where appropriate. Tone: professional, technical, concise. Length: as specified by {{desired_length}}. Leave out pricing, contractual terms, and any claims not supported by the provided inputs.

Guardrails

  • Do not invent technical specifications, standards numbers, or product names.
  • If any required input is missing, ask for it before drafting.
  • Flag any assumption you make and note where a licensed professional or manufacturer manual must be consulted for compliance or integration details.

Example — Product: CloudSync Pro; Customer: Acme Corp; RFP section: 3.2 Data Integration; Key capabilities: real-time sync, API gateway, role-based access; Technical specs: 99.9% uptime, 256-bit encryption; Integration points: Salesforce, SAP; Compliance: SOC 2, GDPR; Pain points: data silos, slow reporting; Differentiators: zero-downtime migration; Desired length: 500 words.