afrexai-competitive-intel

# Competitive Intelligence Engine A complete system for understanding, tracking, and outmaneuvering competitors. Covers market mapping, product analysis, pricing intelligence, sales battlecards, win/loss analysis, and ongoing monitoring. ## When to Use - Entering a new market or launching a product - Losing deals to competitors and need to understand why - Quarterly strategy reviews - Pricing decisions (new product or adjustment) - Sales team needs competitive talking points - M&A due diligence on a target or acquirer - Investor pitch prep (show you understand the landscape) - Content strategy informed by competitor gaps --- ## Phase 1: Market Mapping ### 1.1 Competitor Identification Classify every competitor into one of four tiers: | Tier | Definition | Example | Monitoring Frequency | |------|-----------|---------|---------------------| | **Direct** | Same product, same buyer | Your closest rivals | Weekly | | **Adjacent** | Different product, overlapping buyer | Platform expanding into your space | Bi-weekly | | **Indirect** | Different solution to same problem | Spreadsheets replacing your SaaS | Monthly | | **Emerging** | Early-stage, same vision | YC startups in your category | Monthly | ### Discovery Methods Search these sources systematically: 1. **Google**: "[your category] software/tool/service" — note top 10 organic + ads 2. **G2/Capterra/TrustRadius**: Your category page — note top 10 by reviews 3. **Product Hunt**: Search your keywords — sort by votes 4. **Crunchbase**: Search your category — filter funded companies 5. **LinkedIn**: "[competitor name]" company pages — note employee count trends 6. **Reddit/HN**: "alternative to [leader]" or "[category] recommendations" 7. **Customer interviews**: "Who else did you evaluate?" 8. **Lost deal notes**: Who did you lose to and why? ### Market Map YAML ```yaml market_map: category: "[Your Category]" date: "YYYY-MM-DD" total_addressable_market: "$XB" competitors: - name: "Competitor A" tier: "direct" website: "https://..." founded: 2019 funding: "$50M Series B" estimated_revenue: "$10-20M ARR" employee_count: 150 employee_trend: "growing" # growing | stable | shrinking hq: "San Francisco, CA" key_customers: ["Customer 1", "Customer 2"] primary_market: "mid-market" # smb | mid-market | enterprise positioning: "All-in-one platform for X" strengths: ["Feature A", "Strong brand"] weaknesses: ["Expensive", "Slow support"] threat_level: "high" # low | medium | high | critical notes: "" ``` --- ## Phase 2: Product Teardown ### 2.1 Feature Matrix For each direct competitor, build a feature comparison: ```yaml feature_matrix: last_updated: "YYYY-MM-DD" categories: - name: "Core Features" features: - name: "Feature X" us: "full" # none | partial | full | superior competitor_a: "full" competitor_b: "partial" weight: 5 # 1-5 importance to buyer notes: "We have deeper customization" - name: "Feature Y" us: "none" competitor_a: "full" competitor_b: "full" weight: 3 notes: "On our roadmap for Q3" - name: "Integrations" features: - name: "Salesforce" us: "full" competitor_a: "partial" weight: 4 ``` ### 2.2 Product Teardown Template For each major competitor, conduct a structured teardown: ```markdown ## [Competitor Name] Product Teardown **Date:** YYYY-MM-DD **Analyst:** [name] ### First Impressions (0-5 min) - Homepage messaging: What problem do they lead with? - Sign-up friction: How many steps? What info required? - Time to value: How fast can you DO something? - Design quality: Modern, dated, cluttered, clean? ### Onboarding (5-30 min) - Guided tour? Checklist? Video? Nothing? - Sample data provided? Sandbox mode? - How quickly did you feel competent? - What confused you? ### Core Workflow - Complete their primary use case end-to-end - Note: steps required, clicks per task, speed, error handling - Screenshot key screens ### Differentiators - What can they do that we can't? (be honest) - What's their "magic moment"? - What do their happiest customers praise? (check G2 reviews) ### Weaknesses - Where did you get stuck? - What felt missing or half-baked? - What do their angriest customers complain about? (check G2 1-2 star reviews) ### Pricing vs Value - What plan would a typical customer need? - Price per user/month at that tier? - Any hidden costs (implementation, support, integrations)? - Free trial? Freemium? Money-back guarantee? ### Technical Assessment - Stack: (check Wappalyzer, BuiltWith, job postings) - API: Public? REST/GraphQL? Rate limits? Docs quality? - Mobile: Native app? Responsive web? PWA? - Performance: Page load speed, UI responsiveness - Uptime: Status page? Historical incidents? ``` ### 2.3 UX Scoring Rubric Score each competitor's product (0-10 per dimension): | Dimension | What to Evaluate | Weight | |-----------|-----------------|--------| | **Ease of Setup** | Time to first value, onboarding friction | 15% | | **Core UX** | Primary workflow efficiency, intuitiveness | 25% | | **Feature Depth** | Covers edge cases, power user needs | 20% | | **Reliability** | Uptime, bugs encountered, error handling | 15% | | **Integrations** | Ecosystem breadth, API quality | 10% | | **Support** | Response time, quality, self-serve resources | 10% | | **Mobile** | Native quality, feature parity | 5% | **Total = weighted sum. Compare across competitors.** --- ## Phase 3: Pricing Intelligence ### 3.1 Pricing Comparison Table ```yaml pricing_intel: date: "YYYY-MM-DD" competitors: - name: "Us" model: "per-seat" # per-seat | usage | flat | hybrid | freemium entry_price: "$29/user/mo" mid_price: "$79/user/mo" enterprise_price: "Custom" free_tier: true free_limits: "5 users, 1000 records" annual_discount: "20%" contract_required: false implementation_fee: "$0" hidden_costs: [] - name: "Competitor A" model: "per-seat" entry_price: "$49/user/mo" mid_price: "$99/user/mo" enterprise_price: "Custom ($150+/user)" free_tier: false annual_discount: "15%" contract_required: true # annual minimum implementation_fee: "$5,000" hidden_costs: ["API access on enterprise only", "SSO $50/user extra"] ``` ### 3.2 Price Positioning Analysis Answer these questions: 1. **Where do we sit?** Map all competitors on a 2x2: Price (low→high) vs Feature depth (basic→advanced) 2. **Who's cheapest?** At 10 users? 50 users? 200 users? (pricing often crosses over at scale) 3. **Total Cost of Ownership**: Include implementation, training, migration, hidden fees 4. **Value ratio**: Features-per-dollar compared to each competitor 5. **Pricing trend**: Are competitors raising prices? (check Wayback Machine on /pricing) 6. **Discount behavior**: Do they discount aggressively in deals? (ask sales team, check G2 reviews mentioning price) ### 3.3 Pricing Strategy Recommendations Based on analysis, recommend one of: | Strategy | When to Use | Risk | |----------|------------|------| | **Premium** | Clearly superior product + brand | Losing price-sensitive deals | | **Parity** | Similar product, compete on other axes | Race to bottom | | **Penetration** | New entrant, need market share fast | Perception of low quality | | **Value** | Better product at lower price | Margin pressure if costs rise | | **Niche** | Specialized for segment competitors ignore | Small TAM | --- ## Phase 4: Sales Battlecards ### 4.1 Battlecard Template Create one per direct competitor: ```markdown # 🏆 Battlecard: Us vs [Competitor] **Last Updated:** YYYY-MM-DD | **Confidence:** High/Medium/Low ## Quick Stats | Metric | Us | Them | |--------|-----|------| | Founded | | | | Funding | | | | Est. Revenue | | | | Employees | | | | G2 Rating | | | | Gartner Position | | | ## Their Pitch (in their words) "[Their homepage headline or elevator pitch]" ## Why Customers Choose Us Over Them 1. **[Reason 1]**: [Specific proof point — customer quote, metric, demo moment] 2. **[Reason 2]**: [Specific proof point] 3. **[Reason 3]**: [Specific proof point] ## Why Customers Choose Them Over Us (be honest) 1. **[Reason 1]**: [And how to counter it] 2. **[Reason 2]**: [And how to counter it] ## Landmines to Plant 🧨 Questions to ask the prospect that expose competitor weaknesses: 1. "Ask them how they handle [weakness area] — you'll find it requires [workaround]" 2. "Request a demo of [specific feature] — it's not as deep as it looks" 3. "Ask about [hidden cost] — it's not on the pricing page" ## Objection Handling **"[Competitor] is cheaper"** > Response: "At first glance, yes. But when you factor in [hidden cost 1], [hidden cost 2], and [limitation requiring workaround], the total cost is actually [higher/comparable]. Plus, [our unique value] saves you [X hours/dollars] per [period]." **"[Competitor] has [feature we lack]"** > Response: "[Acknowledge honestly]. Here's why our customers find that [our approach] actually works better for [their use case]: [specific reasoning]. [Customer name] evaluated both and chose us specifically because [reason]." **"We're already using [Competitor]"** > Response: "That makes sense — they're solid at [genuine strength]. The customers who switch to us typically hit a wall with [specific limitation]. Are you experiencing [common pain point with that competitor]?" ## Trap Plays (When to Walk Away) - If prospect needs [specific capability we truly lack], acknowledge it honestly - If they're deeply embedded in [competitor ecosystem], switching cost may be too high - If deal size is below $[X], cost of competing isn't worth it ## Win Stories - **[Customer A]**: Switched from [Competitor] because [reason]. Result: [metric improvement] - **[Customer B]**: Evaluated both, chose us because [reason]. Quote: "[testimonial]" ## Recent Intel - [Date]: [Competitor] announced [product change/funding/hire] - [Date]: [Customer feedback about competitor] ``` ### 4.2 Quick Objection Matrix For the sales team's daily use: | Objection | Short Response | Proof Point | |-----------|---------------|-------------| | "Too expensive" | [Value reframe] | [ROI stat or customer quote] | | "Never heard of you" | [Social proof] | [Customer logos, G2 rank] | | "Missing [feature]" | [Alternative or roadmap] | [Workaround or timeline] | | "Happy with current tool" | [Trigger question] | [Common pain with incumbent] | | "Need enterprise features" | [What we have] | [Enterprise customer reference] | --- ## Phase 5: Win/Loss Analysis ### 5.1 Win/Loss Interview Framework After every significant deal (won or lost), capture: ```yaml win_loss: deal: "[Company Name]" date: "YYYY-MM-DD" outcome: "won" # won | lost | no-decision deal_size: "$X ARR" sales_cycle_days: 45 competitors_evaluated: ["Competitor A", "Competitor B"] decision_factors: - factor: "Ease of use" importance: 5 # 1-5 our_score: 4 # 1-5 winner_score: 3 notes: "Demo experience was decisive" - factor: "Price" importance: 4 our_score: 3 winner_score: 4 notes: "We were 20% more expensive but justified by ROI" - factor: "Integration with Salesforce" importance: 5 our_score: 5 winner_score: 2 notes: "They required middleware; we're native" champion: "VP of Sales" decision_maker: "CRO" buying_trigger: "Previous tool couldn't scale past 50 users" key_quote: "Your Salesforce integration sealed the deal" lessons: - "Lead with integration story for Salesforce-heavy orgs" - "ROI calculator was critical for justifying premium price" ``` ### 5.2 Win/Loss Trend Dashboard Track quarterly: ```markdown ## Q[X] Win/Loss Summary ### Win Rate by Competitor | Competitor | Wins | Losses | Win Rate | Trend |