Competitor Monitoring Digest
A weekly digest on your competitors — adopting-account footprint, review sentiment shifts, and the category intent moving around them — in one read.
Competitor footprint, review sentiment, and category intent — one weekly read
Adopting-account footprint + review
sentiment + the wedge each weakness opens.
| Competitor | Footprint | Wedge |
|---|---|---|
| Datadog | Broadest base | Pricing complaints rising |
| New Relic | Mid-market heavy | Migration intent up |
| Dynatrace | Enterprise-skewed | Complexity reviews |
Overview
Produce a competitor-monitoring digest for a named set of competitors: their adopting-account footprint (how many companies run each product), recent review-sentiment shifts (TrustRadius), and the category intent moving around them — so PMM tracks the competitive set from data instead of Google Alerts.
Use cases
Competitive monitoring that's actually intelligence
Press alerts tell you what competitors announce. Adopting-account footprint and review sentiment tell you how they're actually doing — and where they're vulnerable.
A wedge per competitor, refreshed weekly
Each digest names the specific weakness (price, complexity, churn) that opens a messaging wedge — kept current so the sales narrative stays sharp.
View workflow prompt
# Competitor Monitoring Digest
## Parameters
- `{{competitors}}` *(required)* — Competitor products to monitor. Example: `Datadog, New Relic, Dynatrace`
- `{{category}}` *(required)* — The category they compete in. Example: `observability`
## Purpose
Produce a competitor-monitoring digest for {{competitors}} in the {{category}} — adopting-account footprint, review-sentiment shifts, and category intent — so PMM has one weekly read grounded in data, not a folder of alerts.
## Process
1. **Adopting-account footprint** — `search_companies` filtered by each competitor's product (technology filter) to count how many companies run it; use `company_technographic` on a sample of those accounts to characterize the typical buyer environment. NOTE: this measures the competitor's CUSTOMER base, not the vendor's own stack — never query the competitor's own domain for "installed base".
2. **Review sentiment** — `get_product_reviews` for each competitor; surface recent themes and any sentiment shift (rising complaints = a wedge).
3. **Category intent** — `intent_category` for the {{category}} to see overall market temperature around the set.
4. **Synthesize** — a one-paragraph digest per competitor: footprint + sentiment headline + the wedge it opens for us.
5. **Watch items** — flag the single most important change this period to act on.
## Output Format
Markdown with:
- `# Competitor Monitoring Digest — {{category}}`
- `## Per-Competitor Snapshot` (table: competitor | adopting-account footprint | review sentiment | wedge)
- `## Sentiment Shifts` (notable review-theme changes)
- `## Watch Item` (the one change to act on)
- `## Citations`
## Quality Checklist
- Footprint counts cite `search_companies`; buyer-environment reads cite `company_technographic`
- Footprint is the competitor's customer base, NOT the vendor's own internal stack
- Sentiment claims cite `get_product_reviews`
- Each wedge ties to a specific competitor weakness, not generic positioning
- The watch item is a single, specific action