All setups
SalesSetupAI-generated

Discovery Call Prep

A question plan and agenda for your next discovery call

What it is

A question plan and agenda for your next discovery call

Produces a structured discovery agenda — opening, discovery questions, value hypothesis, next steps — tailored to the prospect company, role, and your sales methodology. Run it 30 minutes before the call and walk in with a plan, not a blank page.

What you'll get

Custom instructionsCompiled from your answers, editable before you export.
Discovery call reference cardA reference card Claude uses to sharpen discovery questions and hypotheses for your specific product and ideal customer.
Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.

Try it on

Discovery prep for a CFO at a logistics companyscenario · built in
Claude should produce a four-phase discovery agenda for the CFO at Hargrove Logistics. Questions must be framed using the configured methodology and tied to a CFO's concerns: cost visibility, budget control, and financial reporting across regions. The expansion to new countries should inform the discovery questions. Critical questions must be marked clearly.
Discovery prep for a VP of Engineeringscenario · built in
Claude should build a structured discovery agenda for a VP of Engineering at Cascade Software. Questions should surface engineering bottlenecks, tooling pain, and team velocity concerns. The agenda should fit within a 30-minute call window and end with a concrete next-step proposal.

Compiled preview

You prepare a structured discovery call plan for {{productName}}. Prospect company: {{prospectCompany}} Prospect role: {{prospectRole}} Sales methodology: {{salesMethodology}} {{#if knownContext}} Context you already have on this prospect: {{knownContext}} {{/if}} Rules: 1. Structure the agenda in four phases: opening (rapport + agenda-setting), discovery questions, value hypothesis, next steps. 2. Frame all discovery questions using {{salesMethodology}} — tie each question to a specific dimension of that framework; do not quote the framework name mechanically. 3. Include 3–5 questions per phase; mark the two most critical with an asterisk. 4. Never invent details about {{prospectCompany}