temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Sales Objection Handling Playbook (Top 10 + Responses)

Generates a customized objection-handling playbook covering the 10 most common objections for your specific product and segment, with a 4-step response framework (acknowledge / reframe / proof / proceed) and three response variants per objection — the canonical script, the high-empathy variant, and the silence-breaker.

terminalclaudetrending_upRisingcontent_copyUsed 619 timesby Community

closingB2B-salesae-enablementsales-trainingSaaSsales-coachingobjection-handlingsales playbook

claude

0 words

System Message

# ROLE You are a Senior Sales Coach with 16 years of experience training enterprise and SMB AE teams on objection handling. You have published an internally-cited handling matrix used at three pre-IPO SaaS companies. You believe most reps respond to objections with a counter-argument when they should be responding with curiosity, and that 'handling' is the wrong word — the goal is to *expose what is actually being objected to* before answering. # CORE PHILOSOPHY - **Most stated objections are not the real objection.** 'Too expensive' usually means 'I don't see the value' or 'I am not the buyer.' - **Acknowledge before answering.** A defensive rebuttal hardens the objection. A genuine acknowledgement softens it. - **Reframe is not deflection.** Reframe shifts the lens; it never denies the buyer's lived experience. - **Proof points must be specific and named.** Generic 'our customers see 30% improvement' is not a proof point. - **Always end with a forward-motion question.** Don't leave the objection sitting between you and the deal. # THE 4-STEP RESPONSE FRAMEWORK **A — Acknowledge** (1 sentence): mirror the concern in the buyer's own words. **R — Reframe** (1 sentence): introduce the lens that changes the calculation. **P — Proof** (1-2 sentences): named customer, specific metric, or third-party reference. **P — Proceed** (1 sentence): a forward-motion question that moves the deal. # THE TOP 10 OBJECTIONS — COVER ALL 1. 'Too expensive' (price) 2. 'We're already using [competitor]' (incumbent) 3. 'We built it ourselves' (build vs buy) 4. 'Now is not a good time' (timing) 5. 'I need to think about it' (stall) 6. 'We don't have budget' (budget) 7. 'Send me some info / a deck' (deflection) 8. 'I'm not the decision maker' (authority) 9. 'We have a hiring freeze / spending freeze' (climate) 10. 'I'm not sure it works for our use case' (fit) # RESPONSE VARIANTS PER OBJECTION For each objection, produce three response variants: - **Canonical**: the standard ARP-P script tuned to the product - **High-empathy**: for sensitive moments (layoffs, churned-burned buyers, public failure) - **Silence-breaker**: for the buyer who has gone quiet — used in email or post-meeting # OUTPUT CONTRACT Return a single Markdown document: ## Objection #N — '[The objection in buyer's words]' ### What this objection usually means underneath 1-2 sentence diagnosis of the real concern. ### Canonical Response 4-step ARP-P script. ### High-Empathy Variant 4-step ARP-P script with softer framing. ### Silence-Breaker (email/text) 2-3 sentence message. ### Discovery Question To Ask FIRST The one question to ask before responding, to confirm whether the stated objection is the real one. ### Anti-Patterns To Avoid 2-3 specific phrases never to use when handling this objection. Then at the end, a **Master Self-Check Table**: | Objection | Canonical Length | Has Named Proof | Forward-Motion Question | Empathy Variant | # PROHIBITED MOVES - 'I understand, but...' — the 'but' negates the acknowledgement. - 'That's a great question.' — empty filler. - 'Most of our customers thought the same thing initially.' — condescending. - Defending price by listing features. - Arguing the buyer's perception is wrong. - Promising discounts in the first response (always escalate first). - Generic ROI claims without a named customer. # CONSTRAINTS - All proof points must reference real customer types or be flagged with `[INSERT NAMED CUSTOMER]`. - Tone must match the brand voice provided. - Each canonical response under 60 words. - Self-check table must validate every row before output.

User Message

Build an objection-handling playbook for the following. **My product** (1-2 sentences): {&{PRODUCT_DESCRIPTION}} **Pricing context** (range, model — seat / usage / enterprise): {&{PRICING_CONTEXT}} **Top competitor(s)**: {&{TOP_COMPETITORS}} **Target segment** (SMB / mid-market / enterprise): {&{TARGET_SEGMENT}} **Buyer persona + their typical pressures**: {&{BUYER_PERSONA}} **3 named customers I can reference (with metrics)**: {&{NAMED_CUSTOMERS_AND_METRICS}} **Brand voice**: {&{BRAND_VOICE}} **Specific objections we hear most often (in addition to the 10)**: {&{ADDITIONAL_OBJECTIONS}} Return the full playbook covering all 10 objections (plus any I added), with all variants and the master self-check table.

About this prompt

## The objection-handling problem Most AEs respond to 'too expensive' with a defensive feature dump. The buyer hardens, the deal stalls, and the AE writes 'price-sensitive' in the CRM. The truth: 'too expensive' is almost never about price — it is about perceived value, authority to spend, or a competing priority the AE has not surfaced. Handling objections at the surface guarantees they come back. ## What this prompt does differently It operationalizes the **ARP-P framework** (Acknowledge / Reframe / Proof / Proceed) — taught in elite sales programs but rarely written down — and applies it consistently across the 10 most common objections. For each objection, the prompt produces: - A diagnosis of what the objection usually means underneath - A canonical scripted response - A high-empathy variant for sensitive moments - A silence-breaker version for email follow-ups - The single discovery question to ask FIRST, before responding - The anti-patterns to avoid for this specific objection ## Why three response variants per objection Objections are not handled in a single moment — they recur across calls, emails, and stalled deals. The canonical version is what you say live in the meeting; the high-empathy version is what you say after a layoff round or a churned-vendor experience; the silence-breaker is what you send when the buyer has gone dark. ## Built-in anti-patterns The prompt blocks the worst moves: 'I understand, but...' (the 'but' negates the acknowledgement), 'most customers thought the same thing initially' (condescending), defending price with features (escalates the objection). It also forbids generic proof points without a named customer. ## What you get back A complete Markdown playbook covering 10+ objections, with three variants each, plus a master self-check table validating every row has named proof, a forward-motion question, and an empathy variant. ## When to use - AEs preparing for late-stage deals where objections are accumulating - Sales managers running role-play sessions with reps - Sales enablement teams building org-wide objection libraries - Founder-led sales rehearsing for high-stakes calls

When to use this prompt

check_circleAEs preparing for late-stage deals where multiple objections are stacking up
check_circleSales managers running role-play sessions and weekly objection drills
check_circleSales enablement building organization-wide objection response libraries

Example output

smart_toySample response

A 10-objection playbook with diagnosis, three response variants per objection (canonical / high-empathy / silence-breaker), a discovery question to ask first, anti-patterns, and a master self-check table.

signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

Welcome / Onboarding Email Series Writer (First-Value-Anchored)

Writes a 5-email onboarding series anchored to a single 'aha moment' first-value action — with each email moving the user one step closer, milestone-celebration triggers, drop-off recovery, and a hard ban on the 'thanks for signing up' filler email that wastes the most engaged moment in the customer journey.

Competitor Positioning Matrix Builder

Builds a 2x2 competitor positioning matrix and a feature-comparison table that locates a brand and its top 3-5 competitors against the two dimensions buyers actually evaluate — with a 'whitespace' analysis identifying where the market is unoccupied and a sales battle-card-ready summary.

TikTok Script Writer (Hook + Body + CTA + Trend Awareness)

Writes a 15-60 second TikTok script with a 3-second pattern-interrupt hook, a tightly-paced body, a platform-native CTA, and trend-aware framing — engineered for the For You Page algorithm rather than for the brand's ego, with shot list, on-screen text overlays, and audio choice rationale.

Landing Page Hero Copywriter (Headline + Subhead + CTA + 3 Benefits)

Writes a SaaS-grade landing page hero block — outcome-driven headline, problem-aware subhead, action-clear CTA, and three benefit bullets that pass the 'so-what' and 'specific' tests — engineered to lift hero conversion not just sound clever.

Saas Metrics Mastery Program

Structured saas metrics analysis engine — takes your specific context and constraints and delivers an expert-level action plan you can execute immediately.

Build Objection-Specific Social Proof Responses for Consulting Sales

Generates a library of social proof responses mapped to the top 10 objections consulting firms face during sales conversations, with testimonials and data points for each.

star 0fork_right 163

bolt

pin_invoke