Form a pre-call pain hypothesis before your discovery call
Turns raw account research into a ranked, falsifiable pain hypothesis with an opener that positions you as informed rather than interrogating, plus validation questions and an explicit qualify-out signal. It replaces 45 minutes of unfocused pre-call reading with a brief you can act on in the first five minutes of the call.
You are a strategic account researcher who preps enterprise reps before big calls. Your core belief: reps who walk in with a testable hypothesis run peer-level conversations; reps who walk in to 'learn about the business' run interrogations. A hypothesis can be wrong — that's fine, prospects love correcting a smart guess far more than answering a blank-slate question. Build me a pre-call pain hypothesis for one account. Output format: 1. PRIMARY HYPOTHESIS: The single most likely problem this company has that my product solves, in two sentences, with the evidence trail (what signal suggests it — hiring, stack, stage, industry pattern). 2. TWO SECONDARY HYPOTHESES: Ranked, one sentence each, with evidence. 3. THE OPENER: One sentence I can say in the first five minutes that states the primary hypothesis as an informed guess and invites correction. Format: 'Companies like yours at this stage usually hit X — is that what's happening, or is it something else?' 4. THREE VALIDATION QUESTIONS: Questions that confirm or kill the primary hypothesis fast. 5. THE KILL SIGNAL: What answer would tell me this account has no real pain and I should qualify out. Rules: hypotheses must be falsifiable and specific — 'they struggle with efficiency' is banned. Every hypothesis must trace to evidence I gave you or a named industry pattern, never invented facts about the company. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. What does your product solve, and what does the problem cost customers who have it? 2. Paste what you know about the account — website copy, LinkedIn, job posts, funding news, tech stack, anything. 3. Who is the call with — role and seniority? 4. What did your last three closed-won customers have in common right before they bought? Once you have my answers, produce the hypothesis brief. If my account research is thin, tell me the two highest-signal things to go find first.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Gather 5 minutes of raw material first: the account's site, the contact's LinkedIn, recent job posts or news.
- 3
Answer the interview — question 4 is the secret weapon; closed-won patterns sharpen every hypothesis.
- 4
Open the call with the hypothesis opener and let the prospect confirm or correct you.
- 5
After the call, note whether the primary hypothesis held — feed that back next time to improve the model's priors.
Best practices
Being wrong is productive — a corrected hypothesis gets prospects explaining their real problem unprompted.
If you run this at volume, pull the account signals from Clay and batch several accounts in one chat.
Watch for the kill signal honestly; the brief only saves time if you actually qualify out when it fires.
Job postings are the highest-signal input — a company hiring three SDRs has different pain than one hiring a RevOps lead.
Example: what this looks like in practice
An AE at a data-quality vendor has a call with the Head of Marketing Ops at a 200-person fintech. She pastes the company's careers page (hiring a lifecycle marketer and a Salesforce admin), a recent Series B announcement, and the contact's LinkedIn. The brief comes back: primary hypothesis is that post-funding lead volume is outpacing their routing and dedupe rules, evidenced by the admin hire; the kill signal is 'if they say lead volume is flat, qualify out.' She opens with the hypothesis line. The prospect laughs and says 'it's worse than that' and spends twelve minutes describing the mess. The demo she books is scoped entirely around routing, and the deal closes in five weeks.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Collect signals, not trivia: recent job postings, funding stage, tech stack, and the contact's own posts. Then convert them into a testable hypothesis about the pain your product solves — that's the step most reps skip and the one this prompt automates. Ten minutes of signal-gathering plus this brief beats an hour of reading their About page.
More discovery calls & demos prompts
Build a discovery question bank tailored to one persona
Generates a 15-question discovery bank built around one persona's actual responsibilities and failure modes, organized by call stage, with listening notes on what strong and weak answers sound like. Beats generic question lists because the interview forces your product, competitor, and deal-death context into every question.
Write a post-discovery summary email that mirrors their words
Produces a sub-180-word summary email built on the prospect's verbatim phrases, with impact-paired bullets, an invitation to correct you, and next steps with your commitments listed first. Mirroring their language proves you listened in a way no template can, and the email becomes the artifact your champion forwards internally.
Build a demo storyline from your discovery notes
Converts raw discovery notes or a transcript into a three-act demo storyline that opens on the prospect's problem in their own words, sequences scenes by deal importance, tells you what NOT to show, and scripts the close. It's the difference between a feature tour and a demo the champion replays internally.