Competitive Intelligence

Key Competitive Scenarios

#### Salesforce vs. Microsoft (Dynamics 365 + Power Platform)

Salesforce strengths in this matchup:

• Salesforce is purpose-built for CRM; Microsoft bundles it alongside ERP and productivity
• Agentforce and Einstein are native AI — not bolted on or requiring Azure credits
• AppExchange ecosystem is significantly deeper for CRM-adjacent solutions
• Salesforce professional services and partner network specializes in CRM outcomes

Microsoft's common pitches:

• "You already have Microsoft licenses — Dynamics is cheaper/included"
• "Power Platform gives you low-code customization without code"
• "Copilot is integrated across all our products"

Objection handlers:

• "We already have Microsoft licenses" → "Bundled doesn't mean best. Most companies with Microsoft licenses still choose Salesforce for their revenue-critical processes because the business outcomes are measurably better. Let's calculate what each option actually costs when you factor in outcomes."
• "Copilot is already in our stack" → "Copilot is a productivity assistant. Agentforce is an autonomous sales agent that takes actions in Salesforce, updates records, drafts outreach, and coaches reps. They solve different problems."

Trap-setting questions:

• "When you think about where Copilot or Power Platform have delivered the most business impact, what were those use cases?" (tests whether they've actually gotten value from Microsoft AI)
• "How do you currently measure your CRM adoption rate?" (Dynamics often has lower adoption)
• "Have you talked to any companies that switched from Dynamics back to Salesforce?" (they exist)

#### Salesforce vs. HubSpot

Salesforce strengths:

• Enterprise-grade governance, security, and compliance
• Custom objects and metadata flexibility at scale
• Platform depth: Service Cloud, Marketing Cloud, Agentforce — true multi-cloud
• Better fit for complex B2B sales processes, territories, forecasting

HubSpot's common pitches:

• "HubSpot is easier to use and faster to implement"
• "HubSpot is cheaper for our company size"
• "HubSpot's marketing and CRM are truly unified"

Objection handlers:

• "HubSpot is easier" → "Ease of adoption is a real consideration. Salesforce is more flexible, which means it needs to be configured for your process — and that pays dividends at scale. For a company of your size and complexity, the question isn't which is easier to start; it's which one won't limit you in 3 years."
• "HubSpot is cheaper" → "Let's compare total cost including the seats you'd need as you grow, the integrations you'd have to build, and the revenue impact of a less capable forecasting and pipeline tool."

Trap-setting questions:

• "What's your growth trajectory over the next 3 years?" (HubSpot gets expensive and limited at scale)
• "How are you planning to handle [complex process — territories, CPQ, service escalations]?" (HubSpot gaps)

#### Salesforce vs. Status Quo / "Build In-House"

The hardest objection — they're not choosing a competitor, they're choosing to do nothing.

Salesforce strengths:

• Time to value vs. building: 6 months vs. 2+ years
• Ongoing innovation (3 releases/year) included; custom builds require ongoing maintenance
• Risk: custom builds fail, have no support, and create technical debt

Objection handlers:

• "We can build this ourselves" → "The question isn't whether you can build it — you clearly can. The question is what's the opportunity cost of your best engineers spending 18 months building CRM infrastructure vs. working on your core product?"
• "We already have something that mostly works" → "Mostly is where we should focus. What does 'mostly' cost you in leads, deals, and rep productivity? Let's put a number on it."

The "Why Salesforce" Narrative Framework

Structure every competitive narrative in this order:

1. ACKNOWLEDGE — "That's a fair point about [competitor strength]."
   Never dismiss or belittle the competitor.

2. REFRAME — "The question that matters most for your situation is..."
   Shift to a dimension where Salesforce wins.

3. DIFFERENTIATE — "Here's what's unique about Salesforce in this area..."
   Specific, evidence-based, not generic.

4. PROOF — "Here's a customer similar to you who faced the same choice..."
   Customer reference, case study, or benchmark data.

5. CONNECT — "Given what you told me about [their specific situation]..."
   Tie the differentiation back to their stated pain.

# Battle Card: Salesforce vs. [Competitor]
**Deal:** [Opportunity] | **Created:** [Date] | **SE:** [Name]

## At a Glance
- **Competitor's primary pitch:** [In 1 sentence]
- **Our primary counter:** [In 1 sentence]
- **Our biggest advantage:** [The single strongest differentiator]
- **Their biggest threat:** [Where they genuinely challenge us]

## Comparison Matrix
| Dimension | Salesforce | [Competitor] |
|-----------|-----------|-------------|
| [Key criterion 1] | [Strength] | [Weakness] |
| [Key criterion 2] | [Strength] | [Weakness] |
| [Key criterion 3] | [Tie or edge] | [Tie or edge] |

## Objection Handlers
| Objection | Response |
|-----------|---------|
| "[Their pitch]" | [Our counter in 2-3 sentences] |

## Trap-Setting Questions (Use in Discovery)
1. [Question that surfaces competitor's weakness]
2. [Question that surfaces competitor's weakness]
3. [Question that surfaces competitor's weakness]

## Landmines to Watch For
- [Thing the competitor will say or do that could hurt us]
- [Thing the competitor will say or do]

## References
- [Customer who chose Salesforce over this competitor]
- [Case study or benchmark link]