competitive-and-objections

---
name: competitive-and-objections
description: Competitive positioning and objection handling for enterprise sales and marketing. Builds honest, sourced battle cards and competitor profiles, landmine (discovery) questions, responses to competitor moves (price cuts, launches, negative comparisons), comparison and alternative pages, and win/loss analysis; diagnoses and answers objections such as price, budget, timing, "we'll build it", "happy with current vendor", security and AI-risk concerns, procurement pressure and "send me some info". Use it whenever a competitor is named, the user asks how to beat or position against someone, a prospect pushes back, or a deal is at risk of "no decision".
---

# Competitive & Objections

Enterprise buyers check what you say. Reps who stay credible about competitors, including admitting where a competitor is stronger, win more trust than reps who trash them. Objections are usually information about what the buyer needs, not attacks to defeat.

## Part A — Competitive intelligence

### Collection rules
- **Only report what you actually opened.** Every fact carries a URL, the date observed, a confirmed/inferred label and confidence. For pricing and messaging, quote verbatim.
- **Public sources only.** Use competitor sites, docs, pricing pages, release notes, review sites (patterns, not single posts), job posts, filings and analyst summaries. Never use material behind a login, leaked documents, or anything obtained by misrepresentation.
- **"Unknown" beats a guess.** Never estimate a competitor's revenue, customers, pricing or roadmap without a cited source.
- **Single-source claims are flagged.** Rumors stay out of anything customer-facing.
- **Always include the non-vendor alternatives:** do nothing, build in-house, agencies or services, and reallocating budget to a different priority. In enterprise deals, "no decision" is often the biggest competitor.

### Battle card (internal; 1–2 pages; dated; refresh quarterly or on a major competitor release)
```
# <Competitor> — Battle Card · as of <date> · CONFIDENTIAL — internal only
## In one line: how they position themselves (verbatim) vs. how buyers actually see them (evidence)
## When we win / when we lose (from real win/loss data; mark if hypothesis)
## Their genuine strengths (3–5) — and how we respond to each without denying it
## Their weaknesses (verified, specific, sourced — not rumors)
## Our differentiators that matter to buyers (each with approved proof ID)
## Landmine questions (genuinely useful discovery questions that surface where we're stronger)
## Likely objections when they're in the deal + responses
## Traps they set for us + how to handle
## Proof: relevant approved customer stories, switch stories
## Don't say: claims we can't substantiate; anything disparaging
## Sources
```

**Landmine questions** must be questions a good advisor would ask anyway. They should surface criteria where we really are stronger. Example: "How will you keep product content consistent across retailers when attributes change?" They must not be thinly disguised attacks. If a question only makes sense as a trap, drop it.

**Positioning line:** "Where [competitor] is strong at [real strength], we focus on [differentiator], which matters if [buyer situation]."

### Responding to competitor moves

| Move | Response | Don't |
|---|---|---|
| Price cut | Re-anchor on value and total cost (implementation, services, internal effort, risk). Equip reps with TCO talk tracks. Hold price in segments where we win on value | Match by reflex; start a price war |
| Feature launch | Assess what it actually does (docs, not the press release). Decide: parity, differentiate, or ignore. Brief sales with an honest answer | Claim "we already do that" unless it's verifiably true |
| Negative comparison content about us | Respond with factual, balanced comparison content; correct factual errors directly and calmly | Attack back; make unverifiable counterclaims |
| Funding or acquisition | Reassure our customers on our stability and focus; watch for roadmap and price changes at the competitor | Spread fear about their future |
| Competitor crisis (outage, breach) | Stay quiet publicly; support any affected prospects who ask | Exploit it in marketing |

### Comparison and alternative pages (public)
- **Structure:**
  1. A summary for who each option is best for.
  2. A dated comparison table.
  3. Where we're stronger.
  4. **Where they're stronger, stated honestly.**
  5. Switching considerations and migration help.
  6. FAQ.
  7. A call to action.
- Every competitor claim is public, sourced, dated and fair. Tables include rows where we lose.
- Legal review before publishing. Comparative-advertising rules apply; see the claims reference in `customer-facing-quality-gate`.

### Win/loss analysis
- Interview soon after the decision, through a neutral interviewer where possible. Talk to winners and losers, and to "no decision" outcomes.
- **Ask:**
  - Why change at all?
  - Who was involved?
  - What criteria mattered, and how were they weighted?
  - When and why did each vendor get eliminated?
  - What almost changed the outcome?
- **Code the reasons:** value or ROI, capability gap, price or commercial terms, trust or risk, relationship and sales process, timing or priority, integration, incumbent advantage.
- Prioritize fixes by frequency × deal value × how addressable the reason is.
- Patterns need multiple deals. One loss is an anecdote. Say how many deals support each conclusion.

## Part B — Objection handling

### Method: diagnose before responding
1. **Listen fully.** Don't interrupt, and don't defend.
2. **Acknowledge** it in plain words, without "but" ("Makes sense. You're comparing it to the agency line, not zero."). Ask hard questions directly ("Was it the number?").
3. **Explore** with a diagnostic question. The stated objection is often not the real one.
4. **Respond** to the real concern with evidence (approved proof only) or an offer that reduces risk.
5. **Confirm:** "Does that address it, or is there more behind it?"

### Common enterprise objections

**"It's too expensive."**
- Diagnose: "Is it higher than you expected, or is budget for this category not secured yet?"
- Then decide which conversation you're in:
  - **Value:** rebuild the ROI in their numbers, compare against cost of inaction and total cost of alternatives.
  - **Budget:** phase it, reduce scope, or time it to their budget cycle.
  - **Negotiation tactic:** hold and trade (see the give/get rules in `business-case-and-proposal`, §5).

**"No budget this year."**
- Is it truly none, or not allocated? Ask: "If the business case were clear, where would funding come from?" Could existing spend be reallocated (agencies, manual effort, an incumbent tool)?
- Plan for their budget cycle.
- Walk away for now if the economic buyer confirms there is no priority.

**"Not the right time" / "not a priority."**
- "What *is* the priority?" Look for the connection between our value and their top priority.
- If there's no link, agree a revisit date and stay useful in the meantime.

**"We'll build it in-house."**
- Respect the option. Sometimes it's right, especially when the capability is their core differentiator.
- Explore the full cost honestly: build, maintenance, opportunity cost of the engineers, time to value, risk.
- Offer a fair comparison. **Don't quote invented build-vs-buy multipliers.**

**"We're happy with our current vendor" / "we're under contract."**
- Ask: "What would make it even better?" and "When does the contract renew, and when does evaluation start?"
- Plant criteria now. Re-engage well before the renewal window.
- Never imply they made a bad decision.

**"Your product is missing X."**
- Ask how often they'd use it and what it enables. Separate must-have from nice-to-have.
- If it's a hard requirement we can't meet, say so: "If X is a must-have, we're not the right fit today."
- Credibility matters more than this one deal.

**Security, privacy and compliance concerns.**
- Treat them as legitimate.
- Bring the approved security package: certifications stated exactly, documentation, the DPA.
- Offer to run the security review in parallel with evaluation.
- Never improvise answers. Use "I'll confirm in writing with our security team" and follow up.

**AI-specific risk** (accuracy, hallucination, data use, IP, brand safety, regulation).
- Ask what specifically worries them and who raised it: legal, security, brand, or the executive team.
- Answer with how the product actually controls the risk: grounding in their data, review workflows, guardrails, data-use terms, audit trails.
- Use approved documentation and proof only.
- Propose a pilot with explicit success and risk criteria that the concerned stakeholder helps define.

**"Our agreements don't let us share retailer data"** (POS, loyalty, clean-room outputs):
- Treat it as legitimate. Ask which data, under which agreement, and who owns derived insights.
- Offer what fits within their rights: brand-owned data, the retailer's own clean room, or approved-vendor programs.
- Never suggest a workaround.

**"You'll never get through our vendor risk / model risk / BAA review"** (banks, insurers, health systems):
- Agree that the review is real. Ask for their process, questionnaire and timeline.
- Offer to start it in parallel with evaluation, and supply the approved security package.
- Never claim regulators "approve" vendors. Say "we provide documentation to support your review".
- See the due-diligence sections in `account-targeting-and-research/references/industry-playbooks/`.

**"Send me some information."**
- Often a polite brush-off, sometimes a genuine request. Ask what they'd look for and who else will read it.
- Send one tailored item and propose a specific follow-up.

**"I need to talk to my boss / the team."**
- Offer help: a short internal summary, a business-case one-pager, or a joint meeting.
- Ask what the boss or team will care about most.
- If it has been weeks with no access to the decision-maker, the deal is stalled. Treat it in `enterprise-deal-strategy`.

**Procurement pressure** ("we need 30% off to sign this quarter").
- Clarify what is being asked and why: benchmark, budget gap, or standard procurement practice.
- Trade, don't give. See negotiation preparation in `business-case-and-proposal`.

### Guardrails
- **Never fabricate proof points to answer an objection.** Objection scripts often include "[Customer] saw X%" placeholders. Fill them only from the proof library, or remove them.
- **Never disparage a competitor or a prior vendor.**
- **When the honest answer is "we're not the right fit", say it.**

Run any customer-facing objection response, battle-card excerpt or comparison content through `customer-facing-quality-gate`.

From writer/skills at 20837c9, shown as plain text under its license: CC0-1.0 (permissive). The license text is in LICENSE.

• SKILL.md11 KB · 6bc473eb468c

1 file, 11 KB in total. Each file has a sha256 in the pin's manifest; the first 12 characters are shown.