Prompts tagged "Objection handling"

Respond to the sales objection below with a confident, value-focused response. Objection: {{objection}} Product value: {{value_prop}}

Respond to the sales objection below with a confident, value-focused response. Objection: {{objection}} Product value: {{value_prop}}

Respond to the sales objection below with a confident, value-focused response. Objection: {{objection}} Product value: {{value_prop}}

Respond to the sales objection below with a confident, value-focused response. Objection: {{objection}} Product value: {{value_prop}}

Respond to the sales objection below with a confident, value-focused response. Objection: {{objection}} Product value: {{value_prop}}

Respond to the sales objection below with a confident, value-focused response. Objection: {{objection}} Product value: {{value_prop}}

Respond to the sales objection below with a confident, value-focused response. Objection: {{objection}} Product value: {{value_prop}}

Respond to the sales objection below with a confident, value-focused response. Objection: {{objection}} Product value: {{value_prop}}

You are a sales enablement specialist who builds objection handling libraries for sales teams. Help me create a comprehensive objection library for my team. OUR CONTEXT: - What we sell: [Product/service] - Target market: [Buyer personas] - Price point: [Range] - Main competitors: [List] - Common objections: [What you hear most] Create an objection response library: 1. OBJECTION CATEGORIZATION Organize objections by type: PRICE OBJECTIONS: - [Common objection 1] - [Common objection 2] - [Common objection 3] AUTHORITY OBJECTIONS: - [Common objection 1] - [Common objection 2] NEED OBJECTIONS: - [Common objection 1] - [Common objection 2] TIMING OBJECTIONS: - [Common objection 1] - [Common objection 2] COMPETITIVE OBJECTIONS: - [Common objection 1] - [Common objection 2] TRUST/RISK OBJECTIONS: - [Common objection 1] - [Common objection 2] 2. RESPONSE FRAMEWORK For EACH objection, provide: OBJECTION: '[The exact objection]' TYPE: [Price/Authority/Need/Timing/Competitive/Trust] WHAT THEY'RE REALLY SAYING: [Underlying concern or fear] RESPONSE STRUCTURE: Step 1 - Acknowledge: [Validate without agreeing] Step 2 - Clarify: [Question to understand deeper] Step 3 - Isolate: [Is this the only concern?] Step 4 - Reframe: [Shift perspective] Step 5 - Evidence: [Proof point] Step 6 - Bridge: [Move forward] WORD-FOR-WORD SCRIPT: '[Complete response ready to use]' PROOF POINTS TO USE: - [Case study, statistic, or testimonial] FOLLOW-UP QUESTION: '[Question to ask after response]' WHAT NOT TO SAY: - [Common mistakes reps make] 3. TOP 10 OBJECTIONS Focus on the most common: OBJECTION #1: 'Your price is too high' [Complete framework from section 2] OBJECTION #2: 'I need to think about it' [Complete framework] OBJECTION #3: 'We're happy with our current solution' [Complete framework] OBJECTION #4: 'Send me some information' [Complete framework] OBJECTION #5: 'I don't have the budget' [Complete framework] OBJECTION #6: 'We're not ready yet' [Complete framework] OBJECTION #7: 'Your competitor is cheaper' [Complete framework] OBJECTION #8: 'I need to talk to my team/boss' [Complete framework] OBJECTION #9: 'We can build this internally' [Complete framework] OBJECTION #10: 'This isn't a priority right now' [Complete framework] 4. OBJECTION PREVENTION How to address before they object: PREEMPTIVE FRAMING: - Price: [How to position value early] - Timing: [How to create urgency] - Competition: [How to differentiate upfront] SCRIPTS: '[Example of preemptive positioning]' 5. ADVANCED TECHNIQUES TECHNIQUE 1: The Boomerang - When to use: [Scenario] - How it works: [Turn objection into reason to buy] - Example: [Script] TECHNIQUE 2: Feel-Felt-Found - When to use: [Scenario] - How it works: [Empathy bridge] - Example: [Script] TECHNIQUE 3: The Takeaway - When to use: [Scenario] - How it works: [Remove pressure] - Example: [Script] TECHNIQUE 4: Question the Objection - When to use: [Scenario] - How it works: [Uncover real concern] - Example: [Script] 6. OBJECTION HANDLING BY BUYER TYPE ECONOMIC BUYER: - Most common objections: [List] - How to respond differently: [Approach] - Key messages: [What matters to them] TECHNICAL EVALUATOR: - Most common objections: [List] - How to respond differently: [Approach] - Key messages: [What matters to them] END USER: - Most common objections: [List] - How to respond differently: [Approach] - Key messages: [What matters to them] 7. ROLE-PLAY SCENARIOS SCENARIO 1: Price Objection Role-Play - Prospect says: '[Objection]' - You say: '[Response]' - Prospect pushes back: '[Follow-up objection]' - You say: '[Response]' SCENARIO 2: Competitive Objection Role-Play [Same structure] SCENARIO 3: Timing Objection Role-Play [Same structure] 8. PROOF POINT LIBRARY Organized by objection type: FOR PRICE OBJECTIONS: - ROI Case Study: [Example with numbers] - Total Cost Comparison: [TCO analysis] - Payback Period: [Timeline] FOR COMPETITIVE OBJECTIONS: - Win Story: [Customer who switched] - Comparison Data: [Head-to-head] - Analyst Validation: [Third-party proof] FOR RISK OBJECTIONS: - Customer Success Story: [Similar company] - Implementation Data: [Time to value] - Guarantee/SLA: [Risk mitigation] 9. TRAINING GUIDE How to train team on objection handling: WEEK 1: Understanding Objections - [Training module outline] WEEK 2: Response Frameworks - [Practice exercises] WEEK 3: Role-Play Practice - [Scenarios to run] WEEK 4: Real-World Application - [How to coach] 10. CONTINUOUS IMPROVEMENT How to evolve the library: - Capture new objections: [Process] - Share what works: [Team collaboration] - Update responses: [Frequency] - Track effectiveness: [Metrics] Provide as a complete objection library document.

You are a strategic sales consultant who helps buyers make build vs. buy decisions. I'm facing this objection: 'We can just build this internally.' CONTEXT: - What we sell: [Product/service description] - Their technical capability: [What you know about their eng team] - Their core business: [What they actually do] - Timeline they need it: [If discussed] Create a consultative framework to work through this objection: 1. DISCOVERY QUESTIONS FIRST Don't immediately counter - understand their thinking: - Why do they think building is better? - Have they built similar things before? - What's their true timeline and resource availability? - Questions to ask: [Provide 5-7 specific questions] 2. TOTAL COST OF OWNERSHIP ANALYSIS Help them calculate true cost: - Initial build cost (engineering time) - Ongoing maintenance and updates - Opportunity cost (what else could eng team build) - Time to market vs. buying - Provide framework: [Build simple calculator] 3. RISK FACTORS Highlight non-obvious risks: - Technical debt and maintenance burden - Feature parity and staying current - Compliance and security requirements - Integration complexity - Sample language: [Provide talking points] 4. CORE COMPETENCY ARGUMENT - Is this their differentiator? - Should engineering focus here or on core product? - Sample language: [Provide exact wording] 5. HYBRID OPTION - Can they use our platform and customize? - Reduce scope of internal build - Sample language: [Provide proposal structure] 6. PROOF POINTS - Companies that tried to build and switched to us - Time/cost comparisons - What to say: [Provide examples] Present as a conversation guide, not a pitch deck. Include questions to ask throughout, not just statements to make.

You are a senior sales professional skilled at handling pricing objections consultatively. I received this objection: '[Insert specific objection, e.g., This is too expensive, We don't have budget, Your competitor is cheaper]' DEAL CONTEXT: - Our price: [Price] - Competitor price (if known): [Price] - Value discussed so far: [What they've acknowledged] - Their business impact: [Pain/opportunity size] Create a consultative response that: 1. ACKNOWLEDGE & ISOLATE - Validate their concern (don't dismiss it) - Confirm this is the only remaining concern - Sample language: [Provide exact wording] 2. REFRAME TO VALUE - Shift conversation from cost to investment - Reference their stated pains/goals - Sample language: [Provide exact wording] 3. QUANTIFY THE COST OF INACTION - What's the cost of NOT solving this? - Opportunity cost calculation - Sample language: [Provide exact wording] 4. BREAK DOWN THE INVESTMENT - Per user/per day/per transaction cost - Compared to the problem cost - Sample language: [Provide exact wording] 5. OFFER OPTIONS (Not Discounts) - Phased approach - Reduced scope with expansion path - Payment terms - Sample language: [Provide exact wording] 6. TRIAL CLOSE - Test if price was the real objection - Sample language: [Provide exact wording] Provide the full response as a conversational script I can adapt, not a formal document. Include tonality notes (when to pause, when to ask vs. tell).

Respond to the sales objection below with a confident, value-focused response. Objection: {{objection}} Product value: {{value_prop}}