Act as a consultative B2B seller helping me respond to a prospect objection. Write a response based only on the facts below; do not invent product capabilities, pricing, customer results, security claims, integrations, or deadlines. Prospect and deal context: [PROSPECT CONTEXT] Exact objection and where it appeared: [OBJECTION] Our verified offer, evidence, and limits: [VERIFIED FACTS] My desired next step: [DESIRED NEXT STEP] Channel and relationship stage: [CHANNEL AND STAGE] First, identify the objection type: budget, priority, authority, risk, fit, timing, incumbent, or another type. State the likely underlying concern in one sentence, distinguishing what the prospect explicitly said from an inference. Then produce: 1. A recommended reply in the requested channel, 90-150 words for email or 45-75 seconds for a call. Start by acknowledging the concern in the prospect's terms. Reframe only with relevant evidence. Ask one low-friction question or propose one concrete next step. 2. Two shorter alternative replies: one more direct and one more exploratory. 3. A private seller note with the discovery question I should ask next and the deal risk to record in CRM. Do not argue, pressure the prospect, use fake urgency, or turn an objection into a feature dump. If the evidence cannot answer the concern, say so plainly and recommend the honest next action, such as confirming with a specialist or sharing a relevant document. Before answering, check that every factual claim is supported by [VERIFIED FACTS] and that the requested next step matches the objection rather than skipping past it. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROSPECT CONTEXT] | Describe the buyer, their situation, current process, priorities, and any relevant prior conversation. | VP Operations at a 180-person logistics firm; uses spreadsheets and an incumbent routing tool; wants fewer late deliveries. |
| [OBJECTION] | Paste the prospect's exact words and note whether it came by email, call, or meeting. | Email after demo: 'This looks useful, but we cannot justify another $18k tool while our current contract runs through September.' |
| [VERIFIED FACTS] | List only approved product facts, pricing context, proof points, policies, and known limitations. | Annual price is $18,000 for up to 50 dispatchers; month-to-month pilot is not offered; implementation takes 3-4 weeks; customer case study shows a 12% drop in late deliveries but not guaranteed. |
| [DESIRED NEXT STEP] | State the specific action you want, such as a technical review, pricing call, or permission to follow up later. | Book a 20-minute call to map renewal timing and decide whether a September evaluation is worthwhile. |
| [CHANNEL AND STAGE] | Name the reply channel and where the deal is, such as post-demo email or discovery-call follow-up. | Email; completed demo, champion is engaged, economic buyer has not attended. |
How to use
- Paste the prospect's wording exactly, including any qualifiers such as 'not this quarter' or 'need to check with finance.'
- List only facts you could stand behind in a sales call; remove vague claims such as 'easy implementation.'
- Check the recommended reply for one meaningful next step, not a generic request to 'connect.'
- Follow up with: 'Make the exploratory version sound warmer but keep every claim within the verified facts.'
Variations
Call talk track
Use when you need to prepare for a live objection on a sales call.
Create a 60-second objection-handling talk track for a B2B sales call. Prospect context: [CONTEXT]. Objection: [EXACT OBJECTION]. Approved evidence and constraints: [FACTS]. Desired call outcome: [OUTCOME]. Give an acknowledge-reframe-question sequence, then three likely follow-up questions with truthful answers. Do not invent proof, discounts, or commitments. Check that the question earns the next step rather than pressures the buyer.
Pricing objection
Use when the prospect says the price, budget, or ROI is the issue.
Help me respond to a pricing objection without discounting by default. Buyer situation: [BUYER SITUATION]. Exact price concern: [OBJECTION]. Price, packaging, ROI evidence, and approval limits: [COMMERCIAL FACTS]. Next step: [NEXT STEP]. Write a 120-word email, a discovery question that tests whether price is the real blocker, and an internal note on when to involve sales leadership. Flag any ROI statement not supported by the facts.
Lost-deal follow-up
Use after a prospect chooses an incumbent or pauses the project.
Write a respectful follow-up after a prospect declined or delayed. Prospect context: [CONTEXT]. Their stated reason: [REASON]. Facts we can truthfully offer later: [RELEVANT FACTS]. Recontact timing and proposed action: [TIMING]. Produce a 100-word email that confirms their choice, leaves a useful door open, and asks no more than one question. Avoid guilt, urgency, and unsupported comparisons. Check that the timing respects what they said.
Tips
- Keep the prospect's exact language separate from your interpretation; “too expensive” can mean budget, proof, approval process, or low urgency.
- A useful objection response usually contains one piece of relevant evidence and one diagnostic question, not a catalog of capabilities.
- Do not offer a discount, custom commitment, security answer, or implementation date unless it is approved and documented.
- If an objection exposes a missing stakeholder, ask for a conversation with that stakeholder instead of asking the champion to relay your pitch.
FAQ
Should AI write the reply as if it knows why the prospect objected?
No. It can label a likely underlying concern, but the reply should acknowledge only what the prospect actually said and use a question to test the inference.
Can I use this for a cold email reply?
Yes. Set the channel to email and keep the desired next step small, such as permission to send a relevant example or a 15-minute conversation.