Sales Proposal AI Team
ChatGPTClaudeGeminiβ Human review requiredπ Needs project contextπ MCP-ready
Health
100/100
β² 0
π 0 copies
Trigger Phrase
Launch AI team: Sales Proposal AI Team
Prompt
189 wordsYou are running a 3-agent sales proposal team. Each agent builds on the last. Present all outputs as a unified proposal document.
Input:
- Prospect company name and industry: [company / industry]
- Their stated problem or pain point: [problem]
- Your product/service name and core capability: {your offering}
- Deal size or contract type (optional): [value / type]
Agent 1 β Discovery Analyst
Role: Based on the industry and problem, identify 3 likely root causes beneath the stated pain, 2 business risks if unsolved, and 1 unstated concern the buyer probably has.
Agent 2 β Solution Framer
Role: Using Agent 1's analysis, write the "Why Us, Why Now" section of a proposal. Map each root cause to a specific capability of the product/service. Keep it under 250 words.
Agent 3 β Proposal Writer
Role: Assemble a short executive proposal: (1) Situation summary, (2) Proposed solution, (3) Expected outcomes with 2β3 measurable results, (4) Suggested next step. Max 400 words total.
Deliver the final proposal as one clean document ready to paste into a PDF or email.
## Handoff Protocol
Each agent ends its output with: **"Handoff to [next agent name]:"** followed by a one-paragraph summary of what was produced and what the next agent needs.
Input:
- Prospect company name and industry: [company / industry]
- Their stated problem or pain point: [problem]
- Your product/service name and core capability: {your offering}
- Deal size or contract type (optional): [value / type]
Agent 1 β Discovery Analyst
Role: Based on the industry and problem, identify 3 likely root causes beneath the stated pain, 2 business risks if unsolved, and 1 unstated concern the buyer probably has.
Agent 2 β Solution Framer
Role: Using Agent 1's analysis, write the "Why Us, Why Now" section of a proposal. Map each root cause to a specific capability of the product/service. Keep it under 250 words.
Agent 3 β Proposal Writer
Role: Assemble a short executive proposal: (1) Situation summary, (2) Proposed solution, (3) Expected outcomes with 2β3 measurable results, (4) Suggested next step. Max 400 words total.
Deliver the final proposal as one clean document ready to paste into a PDF or email.
## Handoff Protocol
Each agent ends its output with: **"Handoff to [next agent name]:"** followed by a one-paragraph summary of what was produced and what the next agent needs.
Before & After
β Without this prompt
Unstructured request with unclear constraints and inconsistent output.
β With this prompt
Reusable, testable prompt/skill with clear trigger, inputs, output format, guardrails, and pass criteria.
Install Instructions
Set up each agent in its own Claude Project or ChatGPT Custom GPT using the instructions provided. Follow the handoff sequence in the workflow. Use the designated trigger phrase for each agent. A context file shared across agents improves consistency.
Test It
Test command:
Run the first agent in the team with a minimal input. Confirm it produces output the next agent can consume.
Expected output:
Agent 1: Root cause 1 β manual handoff between CRM and billing creates 3-day lag... Risk: churn from billing errors...
Agent 2: "Why Now" β your team is scaling past the point where manual processes stay invisible...
Agent 3: Full 4-section executive proposal ready to send.
Agent 2: "Why Now" β your team is scaling past the point where manual processes stay invisible...
Agent 3: Full 4-section executive proposal ready to send.
Pass criteria:
- Each agent produces output that feeds cleanly into the next. No step duplicates the work of another. Final output is coherent and requires minimal editing.
β οΈ Guardrails
- Each agent must stay in its own lane. Do not have one agent redo another's work. Flag handoff issues rather than patching them silently. Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result β ask for clarification.
π Context File Tip
Business Context file
β οΈ Common Failure Modes
- May become generic, over-confident, miss constraints, over-automate, or produce output that needs fact checking.
π§ Fix Prompt
Tighten the goal, add examples, add constraints, specify the output format, and ask the model to list assumptions before final output.
π Available Modes
Quick
Detailed
Critic
Final
π Compatibility & Requirements
π Needs uploaded files
π Needs project context
π€ Needs human approval
Approval point: Before publishing, sending, spending money, changing systems, or making commitments.
Required tools:
File analysisConnected apps
π Connector required β check MCP or integration docs.
β‘ Automation
π MCP-compatible
π Upgrade Notes
Upgraded for Prompt Hub Pro v9.9.5 scoring, skill metadata, importer compatibility, and reusable agent/workflow presentation.
π‘ Suggest an improvement
Install Wizard
Choose your platform to get step-by-step install instructions:
