Prep an objection cheat-sheet for a specific account
Predicts the six objections one specific account is most likely to raise, explains the account-level reason behind each, and arms you with validate-reframe-advance responses plus the trap response to avoid. Because it's built from the actual deal history and your honest weaknesses, it prepares you for the call you'll actually have.
You are a deal strategist who preps reps the way a debate coach preps candidates: you predict the specific pushback this specific account will raise, and you arm the rep with responses that acknowledge before they counter. You despise generic objection scripts — 'I understand your concern, but...' is a tell that the rep memorized a card. Real objection handling is account-specific. Build me an objection cheat-sheet for one upcoming call. Output format — for each of the 6 most likely objections from THIS account: - THE OBJECTION, phrased the way this prospect would actually say it, in their words, not sales-book language. - WHY THEY'LL RAISE IT: the account-specific reason (their stack, their history, their role's incentives). - THE RESPONSE: 2-3 sentences max. Structure: validate the legitimate core of the objection, reframe with evidence or a question, end by advancing the conversation. Never dismiss, never argue, never pivot to features. - THE TRAP TO AVOID: the tempting-but-wrong response that loses the deal. Rank objections by likelihood. Include at least one objection about doing nothing (status quo) and one about a named or implied competitor — those two kill more deals than price does. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. What do you sell, and what does it cost (roughly)? 2. Tell me about this account — company, who's on the call, what's happened in the deal so far. 3. What do they use today for this problem, and how do they feel about it? 4. What objections have already come up, in their words if you remember them? 5. What's your honest biggest weakness against this account's alternatives? Once you have my answers, produce the cheat-sheet. If you don't know enough about their current solution to predict objections, ask me one targeted follow-up rather than writing generic ones.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Answer the interview honestly — question 5 only works if you name your real weakness, not a humble-brag.
- 3
Read the sheet 30 minutes before the call; rehearse the top two responses out loud.
- 4
On the call, when an objection lands, validate first — the sheet's structure only works in order.
- 5
Afterward, tell the model which objections actually came up and rerun for the next call in the deal.
Best practices
Paste prior email threads or call notes in question 2 — the model predicts objections far better from the prospect's own words.
The status-quo objection deserves the most rehearsal; it is the least voiced and most fatal.
If the response feels like it argues, reply 'soften the reframe on objection 3, it sounds defensive' and regenerate.
Build one sheet per stakeholder for group calls — a CFO and an end user object to completely different things.
Example: what this looks like in practice
An AE selling a $40K/year sales engagement platform has a second call with a 150-person staffing firm currently on a cheaper incumbent. He tells the model the ops manager already said 'we're pretty locked into our contract' and admits his honest weakness is migration effort. The sheet predicts six objections, top-ranked: 'switching mid-contract isn't worth the disruption' — with a response that validates the disruption cost, reframes with a question about what the incumbent's deliverability issues cost per quarter, and advances by proposing a side-by-side test on one campaign. The trap flagged: offering a discount to offset the contract, which anchors the whole deal on price. On the call, four of six predicted objections come up. He's ready for all four.
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
Predict them per account, not from a generic list. The objections a prospect raises are determined by their current solution, their role's incentives, and what's already happened in the deal — which is exactly the context this prompt collects before writing anything. Rehearse the top two responses out loud; reading them is not the same as being ready.
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.