saurabhships Competitive Intelligence Briefing
Why this exists
Raw competitor tracking fails in three predictable ways:
- The link dump — "Competitor X changed their pricing page" with no analysis, leaving the reader to do the actual thinking every single week.
- False urgency — every finding treated as equally important, which trains readers to skim past all of it, including the one that actually matters.
- The stale watchlist — tracking the same one or two obvious competitors indefinitely while an adjacent player quietly becomes the real threat.
This skill exists to produce analysis, not a feed, and to only raise alarm when an alarm is warranted.
Process
1. Maintain a deliberately scoped watchlist
Three tiers, reviewed periodically rather than set once and forgotten:
- Direct competitors — same product, same buyer
- Adjacent/emerging competitors — different angle, same budget or same job-to-be-done
- Budget competitors — the alternative a customer actually picks when they don't buy any dedicated tool: doing nothing, a spreadsheet, an internal build
A watchlist that's never revisited is how blind spots form — schedule a periodic check (e.g., quarterly) on whether it's still the right list.
2. Pull from a fixed set of source types each cycle
Changelogs/release notes, pricing and packaging pages, review sites (G2, Capterra), competitor blog and marketing content, sales win/loss notes, job postings (hiring signals reveal strategic bets before launches do), funding and M&A news.
3. Classify each finding
- Feature launch
- Pricing/packaging change
- Messaging/positioning shift
- Win/loss signal (from sales)
- Talent/org signal (key hires, layoffs, reorgs)
- Funding/M&A
4. Answer "why does this matter" before writing anything down
For each finding, state explicitly whether it affects your competitive position, your pricing power, or a specific deal currently in flight. If the honest answer is "probably not much," write that — a brief that pads itself with low-relevance items teaches readers to stop trusting all of it, including the parts that matter.
5. Recommend a response only when one is warranted
Use a simple scale: no action / monitor / raise for planning discussion / immediate response needed. Resist the pull to recommend an action just to make an item feel more actionable — see the anti-patterns below for why that specifically backfires.
6. Carry forward a "still true" list
Track a short list of standing competitive facts across cycles (e.g., "Competitor X remains the only player with real-time collaboration") so each brief connects to an ongoing picture instead of reading like disconnected weekly news.
7. Output format
## Competitive Brief — Week of [date]
**This week's headline:** [the single most significant item, if any]
| Finding | Type | Source | Why it matters | Recommended action |
|---|---|---|---|---|
**Still true (standing facts):** [...]
Anti-patterns to avoid
- Don't manufacture urgency — an inflated "immediate response needed" that turns out not to matter costs you credibility on every future brief, including the one where something genuinely urgent shows up.
- Don't let the watchlist go stale — put a recurring review of it on the calendar, not just the brief itself.
- Don't report a bare fact without "why it matters" — that's a news feed, not intelligence.
- Don't quote a competitor's marketing copy or a reviewer's exact words at length — summarize in your own words and cite the source; this matters both for keeping the brief tight and for not casually reproducing someone else's copyrighted material.
Example (illustrative, placeholder competitors)
## Competitive Brief — Week of 2026-08-24
**This week's headline:** Competitor B dropped its entry-tier price by 30% — first pricing move from them in 18 months.
| Finding | Type | Source | Why it matters | Recommended action |
|---|---|---|---|---|
| Entry-tier price cut, 30% | Pricing | Competitor B pricing page | Their entry tier now undercuts ours by ~$15/mo at the segment where we see the most price-sensitive churn | Raise for planning discussion |
| New "AI summary" feature shipped | Feature launch | Competitor B changelog | Overlaps with a Q3 roadmap item; no immediate competitive gap since ours ships in 6 weeks | Monitor |
| Posted 4 open reqs for "enterprise sales" | Talent/org signal | Job board | Possible signal they're pushing upmarket; worth watching but not yet actionable on its own | Monitor |
**Still true (standing facts):** Competitor A remains the only player with native SSO on their free tier. Competitor B has not shipped a mobile app in over a year.
Note the job-posting signal is logged but explicitly not escalated — a single data point that's worth watching rather than worth acting on, which is exactly the distinction this skill is meant to preserve.