Discovery call guide prompt

When to use it

Use this when you need a discovery call guide and want a concrete starting point rather than generic advice. Replace the fictional details with your own confirmed facts before using the result in a real setting.

The prompt

## Role
Act as a consultative sales coach. Apply professional judgment while keeping your reasoning understandable to someone who is not a specialist.

## Context
LedgerLane offers invoice reconciliation software to regional distributors. A finance manager has booked a 30-minute exploratory call after downloading a guide. Pricing depends on invoice volume and required integrations, neither of which is known. The seller must learn the workflow before recommending a demonstration.

## Objective
Design a conversation that uncovers fit, business impact, and buying process without turning the call into an interrogation.

## Audience
The primary users are account executives. Make the deliverable usable in their day-to-day work, with enough explanation to support decisions but no unnecessary background lecture.

## Requirements
Allocate the 30 minutes across introduction, workflow, impact, decision process, and next steps. Include ten open questions, optional follow-ups, and examples of neutral transitions. Explain how to ask permission before discussing budget or sensitive operational information. Provide a note-taking template separating direct quotes, seller interpretations, and facts still to verify.

## Constraints
Do not assume the manager controls purchasing, invent product capabilities, or lead the buyer toward a predetermined pain point. Work only with the scenario and any material explicitly supplied. Label assumptions and distinguish proposed actions from confirmed facts.

## Tone & style
Be direct, thoughtful, and specific. Prefer plain English, concrete examples, and short paragraphs. Match the language to the intended reader rather than relying on jargon or generic motivational phrasing.

## Output format
Present the requested deliverable first, using descriptive headings and tables only where they improve usability. Keep supporting notes separate from copy intended for publication or direct use. Finish with a short checklist of outstanding decisions or verification steps.

## What to avoid
Avoid filler, unsupported certainty, and details invented to make the result seem more complete. Do not let a polished presentation conceal missing information or conflicting requirements.

## Success criteria
A seller can summarize the current process, the cost of inaction as described by the buyer, unresolved fit questions, and a mutually agreed next step. Check the result against the stated constraints before presenting it and correct any inconsistencies you find.

## Clarifying questions
Ask up to three focused questions only if missing information would materially change the result. Otherwise proceed with the fictional scenario, state any necessary assumptions briefly, and identify what a real user should confirm before relying on the output.

Why it works

• The scenario gives the model concrete facts and boundaries instead of asking it to invent a brief.
• The requirements specify the actual deliverables and the important edge cases for this task.
• The constraints make unsupported claims and unapproved commitments harder to slip into the result.
• The success criteria turn review into a practical check: a seller can summarize the current process, the cost of inaction as described by the buyer, unresolved fit questions, and a mutually agreed next step.

Make it yours

Build a tailored version with PromptDeck by replacing the fictional scenario with your own context, audience, and constraints. Keep the verification steps so the final result reflects what you actually know.