aiwg/agentic/code/frameworks/media-marketing-kit/templates/sales-enablement/objection-handling-template.md

Cognitive architecture for AI-augmented software development with structured memory, ensemble validation, and closed-loop correction. FAIR-aligned artifacts, 84% cost reduction via human-in-the-loop, standards adopted by 100+ organizations.

# Objection Handling Guide

**Card ID**: `SLS-{PROJECT}-{NNNN}`
**Version**: 1.0
**Status**: Draft | Current
**Product**: {PRODUCT_NAME}
**Last Updated**: {DATE}
**Owner**: {OWNER_NAME}

---

## Objection Handling Framework

### The A.C.E. Method

**A**cknowledge → **C**larify → **E**ngage

1. **Acknowledge**: Validate the concern
2. **Clarify**: Understand the real issue
3. **Engage**: Provide value-based response

---

## Price Objections

### "It's too expensive"

**Acknowledge**: "I understand budget is a key consideration."

**Clarify**: "Help me understand—when you say expensive, are you comparing to another solution, or is it about fitting within your current budget?"

**Engage** (vs. competitor):
> "While our list price may be higher, let me walk you through the total cost of ownership. When you factor in {implementation costs, hidden fees, productivity gains}, customers typically see {X}% better ROI with us."

**Engage** (budget concern):
> "I appreciate that. What I can tell you is that our customers typically see {ROI figure} within {timeframe}. Would it help to see how {similar company} justified this investment?"

**Proof point**: "{Customer} initially had the same concern, but after implementing, they saw {specific result} within {timeframe}."

---

### "We don't have budget right now"

**Acknowledge**: "That's completely understandable, especially given {market conditions}."

**Clarify**: "Is this about timing, or have you already allocated funds elsewhere for this initiative?"

**Engage** (timing):
> "When do you typically plan budgets for the next fiscal year? Let's map out a timeline so you're ready when budget opens up."

**Engage** (reallocation):
> "Many of our customers have funded this by {reallocating from X, showing cost savings from Y}. Would it help to see how others have approached this?"

**Next step**: "Can we schedule time in {month} to revisit when you're planning next year's budget?"

---

### "Can you match {competitor}'s price?"

**Acknowledge**: "I appreciate you sharing that with me."

**Clarify**: "To make sure we're comparing apples to apples—what's included in that price? Does it cover {implementation, support, features we include}?"

**Engage**:
> "Our pricing reflects the full value you get: {key differentiators}. We've found that customers who choose based on initial price often end up spending more long-term due to {hidden costs, limitations}. Let me show you a true TCO comparison."

---

## Competitor Objections

### "We're already talking to {Competitor}"

**Acknowledge**: "It makes sense to evaluate your options thoroughly."

**Clarify**: "What is it about {Competitor} that caught your attention? What's most important to you in this decision?"

**Engage**:
> "I'm glad you're doing your due diligence. What I'd suggest is evaluating us on {key differentiator 1} and {key differentiator 2}—these are areas where customers tell us we really stand out. Can I show you specifically how we compare?"

**Landmine**: "When you speak with them, I'd suggest asking about {their weakness}. We've heard that's an area where customers sometimes run into challenges."

---

### "We already use {Competitor}"

**Acknowledge**: "I appreciate you've made an investment there."

**Clarify**: "How long have you been using them? What's working well, and where do you see room for improvement?"

**Engage** (if pain exists):
> "What you're describing about {pain point} is actually a common reason companies consider alternatives. We specifically designed our solution to address {that pain}. Would it be worth 20 minutes to see how we approach it differently?"

**Engage** (satisfied):
> "That's great they're meeting your needs. I'd just encourage you to keep us in mind—the market's evolving quickly, and {industry trend} is changing what's possible. Can I send you some resources to have on hand for when you next evaluate?"

---

### "{Competitor} has {Feature} and you don't"

**Acknowledge**: "You've done your research."

**Clarify**: "Help me understand how you'd use that feature. What problem are you trying to solve?"

**Engage** (we have alternative):
> "We approach that differently through {our approach}, which actually gives you {additional benefit}. Let me show you how it works."

**Engage** (on roadmap):
> "That's something we're actively developing. In the meantime, here's how our customers are achieving that outcome today: {workaround/alternative}."

**Engage** (not planned):
> "That's not something we've prioritized because most of our customers achieve {similar outcome} through {alternative}. Is that something that's a must-have, or more of a nice-to-have?"

---

## Timing Objections

### "We're not ready right now"

**Acknowledge**: "I appreciate your honesty about timing."

**Clarify**: "Can you share what needs to happen before you'd be ready? Is it a resource, budget, or strategic priority issue?"

**Engage** (specific timeline):
> "That makes sense. Let's stay in touch—I'll reach out in {timeframe} to see where things stand. In the meantime, would it be helpful if I sent {relevant content} to keep you informed?"

**Engage** (vague timeline):
> "I hear this often, and what I've found is that companies who wait usually wish they'd started sooner because of {cost of inaction}. What would need to change to make this a priority?"

---

### "We need more time to evaluate"

**Acknowledge**: "Absolutely—this is an important decision."

**Clarify**: "What additional information would be most helpful? Is there someone else who needs to be involved?"

**Engage**:
> "Let's make sure you have everything you need. Can we schedule a {technical deep-dive, executive meeting, reference call} to address outstanding questions? What's your timeline for making a decision?"

---

### "Call me back in 6 months"

**Acknowledge**: "I understand. Just to make sure I follow up at the right time..."

**Clarify**: "What will be different in 6 months? Is there something specific happening then?"

**Engage**:
> "I'm happy to reconnect then. In the meantime, would you be open to receiving our quarterly update? Many leaders find it helpful for staying informed on {industry trends}."

---

## Need/Fit Objections

### "We don't have this problem"

**Acknowledge**: "That's great if it's not a pain point for you."

**Clarify**: "Just to understand your situation better—how are you currently handling {process/challenge}? What does success look like?"

**Engage**:
> "Interesting. Many of our customers thought the same initially, but when they looked closer at {specific area}, they found {hidden cost, inefficiency}. Would it be worth exploring whether there's an opportunity you might be missing?"

---

### "We've tried something like this before and it didn't work"

**Acknowledge**: "That's a really valid concern. Past experiences matter."

**Clarify**: "Can you share what happened? What do you think went wrong?"

**Engage**:
> "Thank you for sharing that. What you experienced with {previous solution} is actually why we built our approach differently. We specifically address {their past pain} by {our differentiated approach}. Would you be open to seeing how we're different?"

---

### "I need to think about it"

**Acknowledge**: "Of course—this is an important decision."

**Clarify**: "I want to make sure I've given you everything you need. What's the main thing you want to think through? Is there anything that's still unclear?"

**Engage**:
> "I appreciate that. Based on our conversation, it sounds like {key concern} is the main consideration. Let me send you {specific resource} that addresses that directly. Can we schedule a follow-up for {specific date} to discuss?"

---

## Authority Objections

### "I need to talk to my {boss/team}"

**Acknowledge**: "Absolutely—you want to make sure the right people are aligned."

**Clarify**: "That makes sense. Who else is involved in this decision? What would be most helpful for them to see?"

**Engage**:
> "Would it be valuable if I joined that conversation? I can tailor the discussion to address their specific concerns. Alternatively, I can prepare materials that speak to {their role's priorities}."

---

### "I'm not the decision maker"

**Acknowledge**: "I appreciate you being upfront about that."

**Clarify**: "Can you help me understand the decision process? Who else should I be speaking with, and what matters most to them?"

**Engage**:
> "Would you be willing to make an introduction? I'm happy to have a separate conversation that focuses on {decision maker's priorities}. In the meantime, what would help you champion this internally?"

---

### "I need to get legal/procurement/IT involved"

**Acknowledge**: "Of course—those reviews are important."

**Clarify**: "What does that process typically look like for you? How long does it usually take?"

**Engage**:
> "We work with {legal/procurement/IT} teams regularly. I can provide {security documentation, contract templates, technical specs} to streamline their review. Would it help to connect them with our {corresponding team}?"

---

## Trust Objections

### "I've never heard of you"

**Acknowledge**: "That's fair—we may not have the brand recognition of larger players yet."

**Clarify**: "What would help you feel more confident in us as a partner?"

**Engage**:
> "Let me share a bit about who we are. We {company credentials}. More importantly, we work with companies like {reference customers in their industry}. Would a reference call with a similar company be helpful?"

---

### "You're too small/new"

**Acknowledge**: "I understand the concern about working with a smaller company."

**Clarify**: "What specifically worries you about that—is it stability, support, or something else?"

**Engage** (stability):
> "We're backed by {investors/growth metrics}, and we've been growing at {rate}. More importantly, because we're focused, we're able to provide {specific advantage over larger competitors}."

**Engage** (support):
> "Our customer success team is {detail}. In fact, our NPS is {score}, which is {comparison}. Here's what one customer said about their experience: {quote}."

---

### "What if you get acquired?"

**Acknowledge**: "That's a forward-thinking question."

**Clarify**: "Is there a specific concern about what that would mean for you?"

**Engage**:
> "We're committed to our customers regardless of what happens. Our contracts include {protection terms}. And realistically, if we were acquired, it would likely be by a larger company that would continue investing in our product."

---

## Response Templates

### Email Follow-Up After Objection

**Subject**: Following up on {specific concern}

```
Hi {Name},

Thank you for our conversation today. I appreciated your candor about {objection}.

As promised, I wanted to share {resource/information} that addresses this directly:

{Key point 1}
{Key point 2}
{Key point 3}

I also wanted to connect you with {reference customer/resource} who had a similar concern and can share their experience.

Would {date/time} work for a brief follow-up to discuss?

Best,
{Your name}
```

---

## Training Notes

### Common Mistakes to Avoid

1. **Don't be defensive**: Objections aren't attacks
2. **Don't rush to respond**: Listen fully, then reply
3. **Don't argue**: Seek to understand first
4. **Don't make promises you can't keep**: Verify before committing
5. **Don't ignore objections**: Address them directly

### Best Practices

1. **Prepare**: Know common objections before calls
2. **Document**: Record objections to identify patterns
3. **Practice**: Role-play challenging scenarios
4. **Follow up**: Send relevant content after addressing objections
5. **Learn**: Each objection is feedback—use it

---

## Version History

| Version | Date | Author | Changes |
|---------|------|--------|---------|
| 1.0 | {DATE} | {Name} | Initial guide |

---

*Template version: 1.0 | MMK Framework*