Claude Prompt for Discovery & Objection Handling
Create pre- and mid-demo questions the rep asks when demoing AI coding assistant to VP of People.
Read the guide
Cold email, renewal, and cross-sell playbooks built from real agency workflows.
More prompts for Discovery & Objection Handling.
A full 30-minute discovery call talk track with opening, question flow, value drop, and clean close — tailored to your product and persona.
Turn a supportive prospect into a true internal champion who actively sells on your behalf when you're not in the room.
Handle the 'too expensive' objection by reframing value, uncovering the real concern, and protecting your price anchor.
Build a qualification question bank to assess fit when a Head of FP&A is evaluating customer support helpdesk.
Create pre- and mid-demo questions the rep asks when demoing BI and analytics tool to Head of IT.
Create pre- and mid-demo questions the rep asks when demoing HR information system to CIO.
You are an expert Solutions Consultant with deep expertise in product demo.
Design the pre-demo and in-demo question set the rep uses when running a demo of AI coding assistant for a VP of People in personal-finance.
**Pain hypothesis:** territory coverage is uneven
**Value prop:** give reps 4 extra selling hours per week
**Tone:** data-driven and analytical
## 1. Pre-Demo Re-Discovery (5 questions)
Questions asked in the first 5 minutes of the demo call to confirm what was uncovered in discovery is still true. For each question:
- The question
- What you're listening for
- What to do if the answer contradicts your earlier notes
## 2. Demo Narrative Arc
Structure the demo around 3 customer moments that map to the confirmed pain. Each moment:
- Title (outcome-focused, not feature-focused)
- Opening sentence that frames the moment
- Feature / workflow to show (3-5 minutes)
- Transition question to the next moment
## 3. In-Demo Engagement Questions
10 questions the rep sprinkles through the demo to keep it conversational rather than a feature monologue:
- Confirmation ("does this match how your team works today?")
- Impact ("what would your week look like if this happened automatically?")
- Priority ("where does this rank against the other workflows you're trying to fix?")
- Objection surface ("what's missing here for you?")
## 4. Live Objection Responses
Short in-demo responses to five likely objections:
- "Can it integrate with [legacy tool]?"
- "What about permissions and roles?"
- "How secure is our data?"
- "This looks more complex than we need"
- "Is there a lighter-weight version?"
## 5. Demo Close
A 2-minute close that summarizes what was shown in the buyer's language, quantifies impact, and secures a specific next step.
## 6. Post-Demo Recap Email
A 100-word recap email including a single clear CTA and 3 assets to share. Leave placeholders clearly marked.
Structure as a playbook with: Overview, Prerequisites, Step-by-step Plays, Metrics to Track, and Troubleshooting Guide.Replace the bracketed placeholders with your own context before running the prompt:
[legacy tool]— fill in your specific legacy tool.