Free Discovery Call Roleplay Prompt
Short answer: Practice discovery with an adaptive buyer persona that reveals information only when earned.
BEFORE YOU COPY
Bring the context. Skip the blank page.
Collect account context, stakeholders, buyer language, stage, decision process, evidence from calls or artifacts, risks, next-step constraints, and the exact sales moment the output must improve. The prompt separates facts from assumptions, compares viable paths, and produces the promised artifact instead of generic advice.
- Add contextProvide your company, buyer, motion, constraints, and decision.
- Run the workflowPaste the free prompt into ChatGPT, Claude, or Codex.
- Inspect the artifactReview assumptions, risks, actions, and the quality check.
FULL PROMPT · FREE FOREVER
Copy the full GTM workflow.
No account or email required. Copy it into ChatGPT, Claude, or Codex, add your context, and make the decision in front of you.
Copy the prompt
## StackSwap execution contract
You are running a StackSwap operator workflow. Your job is to turn the user's real context into a decision-ready GTM artifact, not a generic explanation.
1. Start by extracting the objective, audience, motion, constraints, available evidence, decision, and definition of success.
2. If a missing fact would materially change the answer, ask up to 3 precise questions. Otherwise state reasonable assumptions and proceed.
3. Separate supplied facts, assumptions, unknowns, and recommendations. Never invent customer evidence, performance claims, market data, or proof.
4. Use the workflow below as the default operating method, adapting it to the user's context. Explain important trade-offs briefly.
5. Produce the promised artifact first. Make it copy-ready, specific enough to run, and structured for the user's actual team or buyer.
6. Include the evidence used, the verification or inspection loop, the main failure modes, and what would change the recommendation.
7. End with: Assumptions; Risks or failure modes; First 3 actions with owner and timing; and a short quality check showing what would make this artifact trustworthy.
### Output contract
Every workflow must make its output observable. Name the artifact, its required fields, the evidence or inputs behind each important claim, and the acceptance check that determines whether it is usable. If the workflow is a decision, show the viable alternatives, criteria, recommendation, runner-up, reversibility, and stop/continue rule. If the workflow is a copy-ready asset, include the final asset before commentary.
### Evidence and verification
Use the user's evidence first. Label sourced facts, assumptions, estimates, and recommendations. Prefer a small test, review, calculation, or comparison that can falsify the recommendation. Never treat an AI assertion as verification.
### Follow-on behavior
Name the next useful workflow only when it follows from the current artifact. Link the handoff to a concrete decision, missing evidence, or unresolved risk; do not recommend a generic tour of the library.
### Cross-platform behavior
This prompt is designed to work in ordinary chat, Claude, and Codex. Do not depend on hidden system instructions, a specific model, slash commands, or unavailable tools. If tools or files are available, use them only when they improve evidence quality; otherwise complete the workflow from the provided context.
---
---
name: discovery-roleplay
description: "Run a realistic discovery roleplay with a buyer context, hidden information, scoring rubric, and evidence-based debrief."
allowed-tools: Read Write WebSearch WebFetch
metadata: { author: Nick French / StackSwap, version: '1.0', product: Operator Playbook }
---
# Discovery Call Roleplay
Practice the decision, uncertainty, and buyer behavior, not a friendly script.
## When to use it
Use for onboarding, certification, new segment practice, or a specific discovery weakness. Do not use it as an improv game with no scoring or debrief.
## Inputs to collect
Collect segment, persona, trigger, stage, hidden context, business problem, alternatives, objections, success criteria, timebox, and difficulty.
## Method
1. Create a buyer brief with facts the buyer volunteers, facts they reveal only when asked, and red herrings.
2. Define the rep objective, must-learn signals, disqualifiers, and next-step threshold.
3. Run the roleplay without coaching during the call.
4. Score listening, problem depth, impact, qualification, relevance, control, and next step.
5. Debrief with evidence, one repeat, one change, and a rerun condition.
## Output
Produce the roleplay brief, buyer persona, hidden information, scoring rubric, facilitator guide, debrief, coaching actions, and certification result.
## Verification and failure modes
Use the same rubric across reps and preserve call evidence. Guard against scripted buyers, generous scoring, feature dumping, and roleplay behavior that does not transfer to live calls.
## Quality gate
The participant must demonstrate buyer understanding and a justified next step, not merely complete the script.Free forever. No email gate.
Was this prompt useful?
Thumbs up if it helped. Thumbs down if it needs work.
THE PROMPT IS THE START
Want an independent read on the real project?
Start the free discovery QA audit. Show StackSwap what your builder already knows, then get a focused next move.
QUESTIONS
About this free prompt
What does this discovery call roleplay prompt help with?
Practice discovery with an adaptive buyer persona that reveals information only when earned.
Who should use this discovery call roleplay prompt?
This free GTM prompt is for B2B SaaS founders, GTM leaders, and RevOps operators who need a useful first draft without starting from a blank page.
What should I add before running this discovery call roleplay prompt?
Add your company, buyer, GTM motion, constraints, and the decision you need to make. Better context produces a more specific artifact and makes weak assumptions easier to spot.
What output does this discovery call roleplay prompt produce?
Roleplay setup, buyer profile, scoring rubric, and debrief. The workflow is designed to produce that artifact instead of generic GTM advice.
Can I use this discovery call roleplay prompt in ChatGPT, Claude, or Codex?
Yes. The workflow is designed for ordinary chat, Claude, and Codex, with platform-specific formats available to copy for free.
How do I get a better result from this discovery call roleplay prompt?
Include real customer language, current numbers, and hard constraints, then inspect the assumptions and risks in the result. Treat the first output as a decision artifact to improve, not an unquestionable answer.