Competitor Update Summarizer (Multiple Links → Deduped Notes → Briefing Bullets)
Condense competitor coverage into clear bullets and implications without duplication.
Prompt Overview
Tips For You
Keep a rolling competitor alias list to improve clustering. | Store implications in a Notion database linked to battlecards. | Ask for low-confidence items to be flagged for manual review. | Limit talk-tracks to real objections your reps hear.
From Operations TeamNexusAi TechnologyProblem It Solves
Multiple outlets repeat the same competitor story; teams need a single authoritative note.
Event Clustering
Groups near-identical stories into one authoritative note.
Implication Line
Turns facts into clear product/sales/pricing guidance.
Confidence Grading
Separates hard evidence from speculation.
Sales Talk-Tracks
Gives reps concise answers to likely objections.
AI Prompt Instructions
Act as: Competitive intelligence analyst producing crisp, non-duplicative notes on competitor moves.
Why this task matters: Sales, product, and leadership need a shared understanding of competitor actions and what we should do in response.
Important boundaries:
- Merge near-identical stories; cite the primary source.
- Separate facts from interpretation; mark speculation clearly.
- Keep each note ≤3 bullets plus a single implication line.
User inputs:
- Competitor list: [A, B, C]
- Today’s links: 5–30 URLs or headline+summary
- Our positioning summary: 3–5 bullets
Objectives:
1) Cluster stories by competitor and event.
2) Produce concise, deduped notes with canonical source.
3) Add implications for product, sales talk tracks, and pricing.
Analysis workflow:
1) Entity resolution: map aliases and product names.
2) Event typing: launch, price change, partnership, outage, legal, talent, financial.
3) Evidence grading: high/medium/low reliability.
4) Implication drafting: practical, near-term, role-specific guidance.
Required output format:
- Header: date, competitors with notable changes.
- For each competitor: Event type, 1–3 fact bullets (with source), Implication (product/sales/pricing), Confidence (H/M/L).
- 2–3 talk-track suggestions for Sales if relevant.
Quality controls:
- One canonical link per event.
- No superlatives or hype; keep to facts.
Verification checklist:
- Cross-check conflicting numbers across sources.
- Confirm dates/time zones when referencing launches.
Final instruction: Output as concise Markdown sections per competitor.
Expected Outcome
Competitor B — Price Change | Confidence: H Facts: (1) New SMB plan at $49 (B’s site) (2) Annual discount 20% (Docs) (3) Limits: 3 seats, 100k events (Docs) Implication: PMM to refresh battlecard; consider promo for SMB tier in EMEA. Sales talk-tracks: (1) Total cost at 5 seats vs. us (2) Event limits impact on growth (3) Our support SLA advantage.
Implementation Journey
Summarize in Claude
Paste the competitor list, positioning bullets, and today’s links into Claude with this prompt to get deduped notes and implications.
12 minUpdate battlecards
Copy implications and talk-tracks into your Notion or Confluence battlecards. Tag by competitor and event type for quick retrieval.
10 minBrief Sales
Post the Markdown section for the most active competitor into your Sales Slack channel and link the updated battlecard.
5 min
