Objection Handling Script Builder

Apply the FEEL Framework to this objection:

OBJECTION: "[Insert the objection you're hearing]"

CONTEXT:
- Your product/service: [What you sell]
- Buyer persona: [Who you're selling to]
- Relevant proof point: [A result you can reference]

GENERATE FOR EACH FEEL STEP:

1. FEEL ACKNOWLEDGED
   - Validating statement that shows empathy
   - Example: "That's a fair concern, and you're not alone in raising it."

2. EXPLORE THE CONCERN
   - 2-3 discovery questions to understand the real issue
   - Example: "Help me understand - when you say X, is it more about Y or Z?"

3. EDUCATE WITH EVIDENCE
   - Specific proof point or reframe that addresses the concern
   - Example: "What we've seen with similar companies is..."

4. LEAD TO NEXT STEP
   - Low-risk action that maintains momentum
   - Example: "What if we explored X together? No commitment, just clarity."

CONSTRAINTS:
- Each element should be 1-2 sentences max
- Sound like a helpful peer, not a pushy salesperson
- Never argue or get defensive

Create objection handling scripts for price-related concerns:

CONTEXT:
- Product: [Your product/service]
- Price: [Your pricing]
- Key value metrics: [Measurable outcomes you deliver]
- Competitor pricing: [If known]

GENERATE SCRIPTS FOR THESE PRICE OBJECTIONS:

1. "It's too expensive"
2. "We don't have the budget"
3. "Your competitor is cheaper"
4. "Can you give us a discount?"

FOR EACH, PROVIDE:

ACKNOWLEDGE: Validate without agreeing
Example: "I hear you - investment decisions deserve careful thought."

EXPLORE: Question to understand the real concern
Example: "When you say expensive, are you comparing to alternatives or to not doing anything?"

REFRAME: Shift from cost to value/ROI
Example: "Our customers typically see X result in Y timeframe, which means..."

BRIDGE: Next step that addresses the concern
Example: "What if we mapped out the ROI for your specific situation?"

CONSTRAINTS:
- Never apologize for your price
- Focus on value delivered, not features
- Use specific numbers when possible
- Avoid the word "but" after acknowledgment

Create objection handling scripts for timing-related concerns:

CONTEXT:
- Product: [Your product/service]
- Sales cycle: [Typical timeline]
- Implementation time: [How long to get started]
- Cost of delay: [What happens if they wait]

GENERATE SCRIPTS FOR THESE TIMING OBJECTIONS:

1. "We're not ready right now"
2. "Check back next quarter"
3. "We have other priorities"
4. "We're in the middle of [X project]"

FOR EACH, PROVIDE:

ACKNOWLEDGE: Respect their timeline
Example: "I completely understand - timing matters."

EXPLORE: Understand what's driving the delay
Example: "When you say next quarter, what needs to happen between now and then?"

CREATE URGENCY: (without pressure) Cost of waiting
Example: "The companies we work with typically find that waiting means..."

BRIDGE: Stay connected without being pushy
Example: "What if we put together a plan now so you're ready when the timing is right?"

CONSTRAINTS:
- Never dismiss their timeline as an excuse
- Create urgency through insight, not pressure
- Offer value in the interim
- Set a specific follow-up, not "let me know"

Create objection handling scripts for competitor-related concerns:

CONTEXT:
- Your product: [What you sell]
- Key competitors: [Names]
- Your differentiators: [What makes you different]
- Competitor weaknesses: [Where they fall short - be honest]
- Your ideal customer: [Who you serve best]

GENERATE SCRIPTS FOR THESE COMPETITOR OBJECTIONS:

1. "We're also looking at [Competitor]"
2. "How are you different from [Competitor]?"
3. "[Competitor] is cheaper/has more features"
4. "We already use [Competitor] - why switch?"

FOR EACH, PROVIDE:

ACKNOWLEDGE: Show respect for their process
Example: "It makes sense to compare options - that's smart buying."

EXPLORE: Understand their evaluation criteria
Example: "What's most important to you as you evaluate? That helps me focus on what matters."

DIFFERENTIATE: Focus on your unique value
Example: "Where we tend to win is when companies need X. If that's a priority for you..."

BRIDGE: Offer comparison help without desperation
Example: "Happy to put together a side-by-side focused on your specific criteria."

CONSTRAINTS:
- Never badmouth competitors directly
- Focus on fit, not "better"
- Acknowledge where competitors might be better for certain use cases
- Be confident, not defensive

Create scripts for handling authority and approval objections:

CONTEXT:
- Product: [What you sell]
- Typical decision makers: [Titles involved]
- Common stakeholders: [Who else has input]
- Average deal size: [Helps understand approval complexity]

GENERATE SCRIPTS FOR THESE AUTHORITY OBJECTIONS:

1. "I need to run this by my boss"
2. "We have a committee that makes these decisions"
3. "I'm not the decision maker"
4. "Legal/Finance/IT needs to approve"

FOR EACH, PROVIDE:

ACKNOWLEDGE: Respect the process
Example: "Absolutely - decisions like this should involve the right people."

EXPLORE: Map the process and players
Example: "Walk me through how decisions like this typically get made. Who's usually involved?"

ENABLE: Arm your champion
Example: "What would be most helpful - should I put together materials for the meeting, or would it help if I joined?"

BRIDGE: Stay involved without overstepping
Example: "What's the best way to support you through this process?"

CONSTRAINTS:
- Never go around your champion
- Offer to help, don't demand access
- Understand timelines and blockers
- Create materials they can use without you

Create scripts for status quo objections:

CONTEXT:
- Product: [What you sell]
- Common current solutions: [What they're using instead]
- Hidden costs of status quo: [Problems with current approach]
- Switching effort: [How hard is it to change]
- Quick wins: [Value they can see fast]

GENERATE SCRIPTS FOR THESE STATUS QUO OBJECTIONS:

1. "We're happy with what we have"
2. "We've always done it this way"
3. "Switching would be too disruptive"
4. "Our current solution works fine"

FOR EACH, PROVIDE:

ACKNOWLEDGE: Validate their comfort
Example: "If it's working, that matters. No one should change for change's sake."

EXPLORE: Surface hidden dissatisfaction
Example: "When you say it works, what would 'working even better' look like?"

CHALLENGE (gently): Cost of status quo
Example: "The companies we work with thought the same until they realized X was costing them Y..."

BRIDGE: Low-risk way to explore
Example: "What if we just compared notes? If your current approach is truly better, I'll be the first to say so."

CONSTRAINTS:
- Never insult their current approach
- Help them discover problems, don't tell them
- Focus on opportunity cost, not scare tactics
- Make switching feel safe and gradual

Help me customize my objection handling scripts:

MY PRODUCT/SERVICE:
- What we sell: [Description]
- Price point: [Cost]
- Primary value: [Main benefit]
- Proof points: [Key metrics/results]

MY CUSTOMERS:
- Ideal buyer: [Title, company size]
- Their main pain: [Problem we solve]
- Why they buy: [Top 3 reasons]
- Why they don't buy: [Top 3 objections]

MY COMPETITORS:
- Main alternatives: [Names]
- Our advantages: [Where we win]
- Their advantages: [Where they win]

CUSTOMER STORIES:
- [Company A] achieved [Result] in [Timeframe]
- [Company B] reduced [Metric] by [Percent]

GENERATE:
1. Top 5 objections I should prepare for
2. For each objection, a script using the FEEL framework
3. Specific proof points to reference for each objection
4. Follow-up questions to keep the conversation going

Create a roleplay scenario for objection handling practice:

MY CONTEXT:
- Product: [What I sell]
- Target buyer: [Who I'm selling to]
- Objection to practice: [The objection I want to work on]

SCENARIO SETUP:
Create a realistic buyer persona including:
- Name and title
- Company context
- Why they might have this objection
- Their communication style (direct, analytical, skeptical, etc.)

ROLEPLAY INSTRUCTIONS:
1. Start with the buyer raising the objection in a realistic way
2. After I respond, react as the buyer would
3. Include follow-up objections if my response is weak
4. Push back on generic or defensive answers
5. Acknowledge when I handle it well

DEBRIEF:
After the roleplay, provide:
- What I did well
- Where I could improve
- Alternative approaches to try
- Specific phrases that would have worked better