--- name: competitive-intelligence-support description: Extract competitive intelligence from customer support conversations including competitor mentions, feature comparisons, pricing sensitivity, and win/loss signals. Use when monitoring competitor mentions in tickets, analyzing competitive win/loss reasons, building competitive intelligence reports, alerting product and sales teams to competitive threats, identifying feature gaps from support conversations, or tracking competitive market share shifts. Triggers on phrases like "competitive intelligence", "competitor mention", "competitor comparison", "competitive win/loss", "feature gap analysis", "competitive threat", "support intelligence", "market share tracking". --- # Competitive Intelligence from Support Systematically extract competitive insights from support interactions to inform product strategy, sales positioning, and customer retention efforts. ## Workflow ### 1. Competitor Mention Detection and Classification 1. **Automated detection across all support channels**: - **Keyword matching**: Monitor for competitor names (maintain database of 20+ competitors) - Direct mentions: "We're comparing with [Competitor]", "[Competitor] does this better" - Indirect mentions: "Our other tool", "the alternative we looked at" - Code references: Competitor API names, SDK references, integration mentions - **NLP-based detection**: Identify competitive context beyond simple keyword matching - Comparison context: "Your feature vs theirs" - Switching intent: "We might move to [Competitor]" - Feature gap: "I wish you had [Competitor's feature]" - Pricing comparison: "[Competitor] charges less for this" - **Sentiment classification**: Positive, neutral, or negative sentiment about each competitor - "I loved [Competitor] but their support is terrible" → Positive product, negative support - "[Competitor] is too expensive and buggy" → Negative overall - "We're evaluating [Competitor] — they look promising" → Neutral/positive threat 2. **Contextual enrichment**: - Extract full conversation context surrounding the competitor mention - Identify customer segment: Enterprise/SMB/Startup, industry, plan tier, tenure - Detect competitive stage: Evaluating, currently using competitor, switching from competitor, at risk of switching - Extract specific features/products being compared - Identify pricing sensitivity indicators 3. **Signal strength scoring** (0-100): ``` COMPETITIVE SIGNAL STRENGTH MODEL ================================== Scoring Factors: 1. Mention type (0-25): Direct competitor name mention: +20 Indirect reference: +10 Generic "competitor" reference: +5 2. Customer segment (0-25): Enterprise customer (> $50K ARR): +25 Mid-market ($10K-$50K ARR): +15 SMB (< $10K ARR): +8 3. Competitive stage (0-25): Actively evaluating competitor: +25 Currently using competitor + considering switch to us: +20 Using us + considering switch to competitor: +25 Historical mention (no active evaluation): +5 4. Sentiment about competitor (0-25): Positive about competitor (threat): +25 Neutral: +15 Negative about competitor (opportunity): +20 Negative about us (threat): +25 Signal Response by Score: ≥80: Critical — Alert sales + product + support leadership within 2 hours 60-79: High — Alert sales rep + product team within 24 hours 40-59: Medium — Log in competitive intelligence dashboard, weekly review <40: Low — Log for trend analysis, monthly review ``` ### 2. Intelligence Extraction and Structuring 1. **Structured data extraction from conversations**: ``` COMPETITIVE INTELLIGENCE RECORD ================================= Basic Information: Customer: [Company Name, Segment, ARR] Date: [YYYY-MM-DD] Channel: [Email/Chat/Phone] Agent: [Name] Competitive Stage: [Evaluating/Switching/At Risk/Historical] Competitor Details: Competitor Name: [Name] Competitor Product/Feature: [Specific product or feature] Comparison Points: - Feature: [What feature is being compared] - Pricing: [Price difference noted, if any] - Performance: [Performance comparison, if noted] - Support: [Support experience comparison, if noted] Sentiment Analysis: Sentiment toward us: [Positive/Neutral/Negative + score] Sentiment toward competitor: [Positive/Neutral/Negative + score] Switching likelihood: [Low/Medium/High + reasoning] Key Quotes: "Customer's exact words about competitive comparison" Action Items: [ ] Alert account executive [ ] Create retention task (if at risk) [ ] Log feature gap (if applicable) [ ] Update battlecard (if new insight) [ ] Schedule CSM check-in (if at risk) ``` 2. **Feature gap identification**: - When customer mentions competitor feature we don't have: - Classify gap type: Missing feature, inferior feature, missing integration - Estimate customer impact: How many customers requesting this? - Check product roadmap: Is this planned? When? - Create product feedback ticket with customer quote and impact estimate - Monthly feature gap report to product team - Priority scoring: Customer count × ARR impact × urgency 3. **Pricing intelligence extraction**: - Track pricing comparisons mentioned: "They charge $X, you charge $Y" - Extract competitor pricing data points (if shared by customers) - Identify pricing sensitivity triggers: What causes price shopping? - Monthly pricing intelligence brief to sales and finance teams - Competitive positioning recommendations ### 3. Alerting and Distribution 1. **Real-time alerting workflow**: - Critical signals (score ≥80): Slack alert to #competitive-intelligence + email to named stakeholders - High signals (score 60-79): Logged in dashboard, daily digest to stakeholders - Medium signals (score 40-59): Weekly competitive intelligence report - All signals: Stored in competitive intelligence database for trend analysis 2. **Stakeholder-specific reporting**: - **Sales team**: Which deals have competitive threats; battlecard updates; win strategies - **Product team**: Feature gaps identified; customer quotes; prioritization data - **Support leadership**: Competitive threat trends; agent talking points; retention risks - **Executive team**: Quarterly competitive landscape summary; market share indicators 3. **Battlecard update cycle**: - Monthly review of new competitive intelligence from support - Update battlecards with: New competitor features, pricing changes, customer quotes - Validate against sales team feedback - Distribute updated battlecards to sales and support teams - Track battlecard usage and effectiveness ### 4. Retention and Response Strategies 1. **At-risk customer response**: - Customer mentioned competitor + negative sentiment about us: - Auto-create retention task in CSM workflow - Alert account executive within 4 hours - CSM schedules check-in call within 48 hours - Provide agent with retention talking points and competitive advantages - Customer mentioned competitor + positive sentiment about competitor: - Higher urgency — alert within 2 hours - Executive outreach recommended (match customer exec level) - Offer competitive comparison session - Consider special offer or value demonstration 2. **Competitive win opportunities**: - Customer using competitor + considering switch to us: - Alert sales team for competitive displacement opportunity - Provide migration plan and switching incentive - Share case studies of customers who switched from competitor - Offer trial or proof-of-concept 3. **Long-term competitive tracking**: - Monthly competitive mention volume trend by competitor - Win/loss rate against each competitor - Common reasons for competitive wins and losses - Seasonal patterns in competitive activity - Annual competitive landscape report ## Templates & Frameworks ### Competitive Intelligence Dashboard ``` COMPETITIVE INTELLIGENCE DASHBOARD — November 2025 ==================================================== OVERVIEW (Last 30 Days): Total competitor mentions detected: 87 Critical signals (score ≥80): 8 High signals (score 60-79): 23 Medium signals (score 40-59): 34 Low signals (score <40): 22 COMPETITOR MENTION VOLUME: Competitor | Mentions | Trend | Sentiment (Us vs Them) | Signal Avg Score ---------------|----------|--------|----------------------|---------------- DataFlow Pro | 28 | ↑ 40% | Mixed (38% us favored)| 68 CloudSync Inc | 21 | ↑ 25% | 52% competitor favored| 72 ⚠ RapidAPI Corp | 15 | → stable| 61% us favored | 45 TechBridge | 10 | ↓ 15% | 45% us favored | 51 APIFirst | 8 | ↑ New! | Neutral | 58 Other/Unknown | 5 | - | - | - CRITICAL SIGNALS REQUIRING ACTION: 1. [CRITICAL] MegaCorp evaluating CloudSync Inc for Q1 migration ARR at risk: $84,000 | Signal score: 92 Key concern: CloudSync offers native ERP integration we don't have Action: Executive outreach + integration roadmap share — Assigned to Sarah Chen (AE) Status: ⏳ Awaiting AE response (alerted 4 hours ago) 2. [CRITICAL] TechStart complaining about our pricing vs DataFlow Pro ARR at risk: $36,000 | Signal score: 88 Key concern: DataFlow Pro charges 30% less for comparable plan Action: Value demonstration + ROI analysis — Assigned to James Park (CSM) Status: ✅ Check-in scheduled for tomorrow FEATURE GAPS IDENTIFIED (Last 30 Days): Gap | Requests | Competitor Has It | Roadmap Status -----------------------------------|----------|-------------------|--------------- Native ERP integration | 12 | CloudSync, TechBridge | Planned Q1 2026 Bulk data export (CSV) | 9 | DataFlow Pro | In Development Custom SLA options | 7 | CloudSync Inc | Under Review Mobile app with offline mode | 5 | RapidAPI Corp | Backlog Advanced analytics dashboard | 4 | APIFirst | Not Planned ⚠ COMPETITIVE WIN/LOSS TRACKING: Competitor | Wins This Month | Losses This Month | Win Rate | Common Win Factor ---------------|-----------------|--------------------|----------|------------------- DataFlow Pro | 4 | 3 | 57% | Better pricing flexibility CloudSync Inc | 2 | 5 | 29% ⚠ | Native integrations RapidAPI Corp | 3 | 1 | 75% ✓ | Superior API documentation TechBridge | 2 | 2 | 50% | Comparable — features decisive APIFirst | 1 | 0 | 100% ✓ | New competitor — early wins PRICING INTELLIGENCE: Data points collected: 14 customer pricing comparisons Key findings: - CloudSync Inc pricing 20-30% higher than us (advantage) - DataFlow Pro pricing 15-25% lower than us (concern) - RapidAPI Corp similar pricing to us (neutral) - Price sensitivity threshold: >$50/mo difference triggers comparison Recommendation: Maintain current pricing; develop value messaging for DataFlow comparisons AGENT COMPETITIVE TALKING POINTS (Updated November 1): vs DataFlow Pro: "While DataFlow is lower cost, our average resolution time is 3x faster, and 92% of our customers report higher satisfaction. Here's our ROI case study..." vs CloudSync Inc: "CloudSync has native ERP integration (we're launching Q1). Meanwhile, our platform offers [differentiator]. Many CloudSync customers switch for [reason]..." vs RapidAPI Corp: "Our API documentation and sandbox environment are industry-leading. 95% of developers get integrated in under 2 hours. [Link to developer portal]..." ``` ### Competitive Intelligence Monthly Report ``` COMPETITIVE INTELLIGENCE MONTHLY REPORT — November 2025 ========================================================= EXECUTIVE SUMMARY: Competitor mentions in support: 87 (↑ 15% from October) Critical competitive threats identified: 8 (2 at risk of churn) Revenue at risk from competitive threats: $120,000 ARR Feature gaps from competitor comparisons: 5 new gaps identified Competitive win rate overall: 54% (↓ 3% from October — concerning) COMPETITIVE LANDSCAPE SHIFTS: 1. CloudSync Inc gaining ground: Mention volume up 25%, win rate against them down to 29% Root cause: Their new ERP integration is winning enterprise deals Recommended action: Accelerate Q1 integration launch; share roadmap with at-risk customers 2. DataFlow Pro price competition intensifying: 12 customers compared pricing unfavorably Root cause: DataFlow launched new "Starter" tier at $29/mo (vs our $49/mo) Recommended action: Develop "why we're worth more" value narrative; not a price match 3. APIFirst emerging as new competitor: 8 mentions in first month Status: Early stage, not yet a major threat but monitor Recommended action: Create battlecard; gather more intelligence RETENTION IMPACT: Customers retained through competitive response: 6 ($180,000 ARR protected) Customers lost to competitors: 3 ($95,000 ARR lost) Net competitive retention rate: 86% (target: >90%) Top retention strategies that worked: 1. Executive outreach for enterprise at-risk accounts (4/4 retained) 2. Value demonstration with ROI calculator (3/5 retained) 3. Migration assistance offer (2/3 retained) 4. Pricing exception approval (1/2 retained — used sparingly) PRODUCT FEEDBACK FROM COMPETITIVE COMPARISONS: Top 5 feature requests driven by competitive mentions: 1. Native ERP integration (12 requests, 4 at-risk deals blocked) 2. Bulk data export (9 requests, 2 lost deals cite this) 3. Custom SLA options (7 requests, enterprise demand) 4. Mobile offline mode (5 requests, field service customers) 5. Advanced analytics (4 requests, data-driven customers) Product team action rate on competitive feedback: 67% (4 of 6 items addressed) SALES ENABLEMENT IMPACT: Battlecards updated: 3 (DataFlow, CloudSync, APIFirst) Competitive case studies created: 2 (won deals vs CloudSync and DataFlow) Sales training sessions on competitive positioning: 1 (November 12) Battlecard usage by sales team: 78% of competitive deals reference updated battlecards TREND ANALYSIS: Month | Mentions | Critical | Win Rate | ARR at Risk -----------|----------|----------|----------|------------ September | 68 | 5 | 59% | $85,000 October | 76 | 6 | 57% | $105,000 November | 87 | 8 | 54% | $120,000 RECOMMENDATIONS: 1. URGENT: Accelerate ERP integration to Q1 — CloudSync is winning enterprise deals with this 2. Develop "Value vs Price" sales play for DataFlow Pro comparisons 3. Create APIFirst battlecard within 2 weeks (new competitor intelligence gathering) 4. Launch competitive win/loss survey to supplement support-sourced intelligence 5. Monthly competitive intelligence briefing for sales team (starting December) ``` ## Integration Points - **Help desk systems** (Zendesk, Freshdesk, Intercom): Source ticket data; keyword/NLP scanning; competitive tagging; alert triggers - **CRM systems** (Salesforce, HubSpot): Account competitive context; AE assignment; retention task creation; deal stage impact - **Competitive intelligence platforms** (Clari, Gong, Crystal): Battlecard management; competitive win/loss tracking; intelligence repository - **Sales enablement** (Seismic, Highspot): Distribute battlecards and competitive content to sales team - **Product management** (Jira, Productboard): Feature gap logging; competitive feedback prioritization; roadmap alignment - **Communication platforms** (Slack, Teams): Real-time competitive alerts; stakeholder notifications - **Analytics platforms**: Competitive trend analysis; win/loss rate tracking; revenue at risk modeling - **Customer success platforms** (Gainsight, ChurnZero): At-risk account flagging; retention playbook activation ## Edge Cases - **Customer mentioning competitor as positive reference without switching intent**: "We also use [Competitor] and love them" — not a threat but valuable intelligence: - Don't trigger retention workflow — log as multi-product user - Extract what they like about competitor for feature gap analysis - Opportunity: Ask if integration between our products would be valuable - Track: 34% of competitor mentions are coexistence, not competition - **Anonymous or vague competitor references**: "Our current tool has issues" without naming competitor: - Agent probe: "Can you share which tool you're currently using? It helps us assist better" - If customer declines: Log as "unknown competitor" with available context - Use contextual clues: Feature mentions, pricing, industry to infer competitor - Confidence score for inferred competitor: High/Medium/Low - **Competitive intelligence that contradicts sales data**: Support detects competitive threat but CRM shows no competitive flag on deal: - Auto-update CRM with competitive flag and source - Alert both sales rep and support manager to reconcile - Treat support-detected signals as potentially earlier than sales awareness - Monthly reconciliation: Compare support-detected vs sales-reported competitive activity - **Competitor name changes or acquisitions**: Competitor rebrands or gets acquired — old name still in monitoring: - Maintain alias list: Old name → new name, acquired company → parent company - Update keyword database within 48 hours of public announcement - Alert intelligence team: "[Competitor A] acquired by [Competitor B] — consolidate intelligence" - Post-acquisition: Monitor for combined product features and competitive threats - **Legal sensitivity around competitive intelligence**: Competitor sends cease-and-desist about competitive comparisons: - Review all competitive intelligence collection for compliance - Ensure intelligence is from customer-provided information (legal) - Never share competitor pricing/data externally (internal use only) - Legal review of battlecard language and competitive claims - Train agents on what competitive information is appropriate to collect and share ## Output ### Competitive Intelligence Weekly Alert ``` WEEKLY COMPETITIVE ALERT — Week of November 17, 2025 ====================================================== THIS WEEK'S SIGNALS: New competitor mentions: 23 (67% of monthly total in just 5 days — spike detected) Critical signals: 2 (both CloudSync Inc related) Feature gap mentions: 3 new references to missing ERP integration TOP STORIES: 1. CloudSync Inc launched new partner program — 3 customers mentioned this as advantage Impact: May increase CloudSync's enterprise competitiveness Action: Evaluate our partner program competitive position 2. DataFlow Pro price increase announced (15%) — could create opportunity for us Impact: Customers frustrated with price increase might consider alternatives Action: Proactive outreach to DataFlow customers expressing pricing concerns 3. Two enterprise customers (ARR $120K combined) mentioned evaluating CloudSync Impact: High — potential Q1 churn risk Action: Executive outreach already scheduled; integration roadmap share in progress AGENT COMPETITIVE UPDATES: - New talking point for CloudSync: "Their partner program doesn't include white-glove onboarding — we do" - DataFlow price increase: "Our pricing has been stable for 18 months — no surprise increases" - Reminder: Always focus on our value, never disparage competitors NEXT WEEK PRIORITIES: 1. Follow up on 2 critical CloudSync threats 2. Create DataFlow price-increase response talking points 3. Schedule competitive intelligence sync with product team (ERP integration priority) 4. Update CloudSync battlecard with partner program intelligence ```