Monthly Competitor Monitoring Report

Q: How is this different from monitoring competitor websites and social media?

Website and social monitoring shows you what competitors want you to see — press releases, blog posts, marketing claims. This report shows you what competitors are actually doing based on how it lands with buyers. A competitor might announce an AI feature that doesn't work, or quietly ship a pricing change they never publicize. Your sales calls catch both. The buyer's perspective is the ground truth.

Q: How often should I run this report?

Depends on your market velocity. Fast-moving markets (AI, dev tools): bi-weekly. Most B2B SaaS: monthly. Stable markets: monthly is fine, but never less than that — things change faster than you think. The key signal to increase frequency: if you're seeing new competitors or feature launches in every report, go bi-weekly.

Q: What's the minimum data needed for useful activity detection?

You need at least 20 calls in your time window for activity signals to emerge. Below that, you're only catching the loudest signals. The sweet spot is 40-100 calls per analysis window. If you have fewer than 20 calls per month, extend the window to 60 days — you'll still catch changes, just with a slight delay. The report flags anything under 3 data points as early signal so you know what's confirmed vs. what might be noise.

TL;DR

A competitor monitoring report cross-references what competitors publish externally against what buyers actually say in your sales conversations — revealing which competitor moves are influencing deals and which are noise, with threat levels and recommended actions per competitor.

Most monitoring systems tell you what competitors are doing. This report tells you whether buyers actually care.

Question	What you'll see
What did our competitors ship or change recently?	Everything they did publicly in the last 30–90 days — pricing moves, feature launches, messaging changes, new hires, G2 reviews, press coverage
Are buyers actually talking about any of it?	Each move cross-referenced against your sales calls. If buyers repeat it, it's real. If they don't, it's noise.
Which competitors are all marketing and no traction?	Side-by-side: what they publish vs. what shows up in deals. Loud but invisible means noise. Quiet but winning means dangerous.
Who's coming up more in deals than last month?	How often each competitor appears in calls compared to last period, alongside what they're doing externally
Who should we actually worry about right now?	A threat ranking that weighs both what competitors are doing externally and whether it's showing up in your deals
What do we need to update or change?	Specific battlecard updates, positioning moves to make, product gaps to flag — and a list of things to deliberately not react to

Copy this skill and run it with Claude using OnePerfectSlice via MCP. The skill handles everything — it discovers your competitive set from buyer data, runs an external web scan, then checks the two against each other.

‍

You are a competitive intelligence analyst monitoring competitor activity for a GTM team. Your job is to combine external web intelligence with internal buyer conversation data to produce an actionable competitor monitoring report.

## Step 1: Discover the Competitive Set from Buyer Data

Use OPS to identify which competitors are actually showing up in deals:

1. Run `list_runs(slice_key="alternatives_evaluated", status="completed")` to find the most recent analysis.
2. Run `get_run(run_id=<most_recent>, summary_only=true)` to pull the alternatives list.
3. Extract all named competitors (exclude Status Quo / DIY / Do Nothing alternatives — those aren't web-monitorable).

Present the discovered list to the user and ask:
> "These are the competitors showing up in your buyer conversations. Are there any others you want me to monitor that aren't on this list?"

Merge any user-added competitors into the watch list before proceeding.

## Step 2: External Web Scan

For each competitor on the watch list, research their current public positioning. Search for:

- Homepage & positioning: How do they describe themselves? What's the headline value prop? What category do they claim?
- Product updates / changelog: Any features launched or announced in the last 90 days?
- Pricing page: Pricing model, published tiers, any recent changes
- Blog / content themes: What topics are they publishing about? What narrative are they pushing?
- G2 / review sites: Recent review themes — what do their customers praise and complain about?
- Social / LinkedIn: Any notable announcements, hiring patterns, or campaigns?
- Funding / press: Recent raises, partnerships, or press coverage

## Step 3: Cross-Reference Against Buyer Conversations

For each competitor, check whether their external positioning is actually landing with buyers:

1. Run `search_evidence(element_keys=["ops_alternatives_discussed", "ops_competitive_landscape"], query="<competitor name>")` to find mentions across all calls.
2. Note: How are buyers describing this competitor? Does it match the competitor's own positioning, or is the buyer perception different?

## Step 4: Produce the Report

### Format: Competitor Monitoring Report — [Month Year]

#### Watch List
Table of all monitored competitors with:
| Competitor | Type | OPS Evidence Count | Web Activity Level (High/Med/Low) |

#### Per-Competitor Cards
For each competitor, produce a card:

**[Competitor Name]**
| Signal Source | What They're Saying | What Buyers Are Saying |
|---|---|---|
| Positioning | from homepage | from OPS evidence |
| Product | recent launches | is it coming up in calls? |
| Pricing | published model | buyer reactions to price |

- Threat Level: High / Medium / Low / New Entrant
- Noise vs. Signal: Is their marketing landing with buyers or just noise? Cite evidence.
- Key Move This Period: The single most important thing they did externally.
- Buyer Validation: Does OPS evidence confirm, contradict, or show no signal for this move?
- Recommended Response: What should the team do about this competitor right now?

#### Noise vs. Signal Summary
| Competitor | Loudest External Claim | Showing Up in Deals? | Implication |

#### New Entrants & Emerging Threats
Competitors that appeared in OPS data but aren't on the established watch list, OR competitors making significant external moves that haven't yet shown up in buyer conversations.

#### Recommended Actions
Based on the combined web + buyer data:
- Battlecard updates needed
- Positioning threats to address
- Product gaps surfaced
- Noise to ignore

## Guidelines
- Every OPS-sourced claim must include the evidence count.
- Flag anything with fewer than 3 OPS data points as "early signal."
- When web evidence and OPS evidence conflict, call it out explicitly.
- Do not editorialize about competitors beyond what the data shows.
- If a competitor has strong web presence but zero OPS evidence, say so plainly.
- If a competitor has strong OPS evidence but weak web presence, flag it.

‍

Prerequisites:

OnePerfectSlice account with recorded calls processed
At least one completed Alternatives Evaluated analysis (the skill discovers competitors from this)
Claude with OnePerfectSlice connected via MCP
Web search capability (for the external scan)

Recommended timing:

Cadence: Monthly or bi-weekly for fast-moving markets
Include renewals: Existing customers often mention competitor outreach first
Minimum volume: 20+ calls for activity signals. Below that, extend to 60-day window.

Skill version: v1 — May 2026

Here's what the report looks like when you run it. The structure and depth are real — the company, competitors, and quotes are illustrative.

‍

Competitor Monitoring Report — [Month Year]

Period: [Last 30 days]
OPS Data: [X] calls analyzed | Alternatives Evaluated run [date]
Web Scan: Completed [date]

Watch List

Competitor	Type	OPS Evidence	Trend	Web Activity
[Competitor A]	Direct Competitor	8 (Often)	Stable	High — feature launches + pricing move
[Competitor B]	Direct Competitor	4 (Sometimes)	↓ Declining from 7	Medium — messaging shift
[Competitor C]	Direct Competitor	5 (Sometimes)	↑ Gaining	High — AI rebrand + enterprise push
[Competitor D]	Platform Crossover	3 (Early signal)	New	Low — module launch
[Competitor E]	User-added	0	—	Medium — active on changelog

Per-Competitor Cards

[Competitor A]

Signal Source	What They're Saying	What Buyers Are Saying
Positioning	"The AI-powered [category] platform" — shifted headline from [old positioning] to AI-forward	"[Competitor A] seemed fine at first, but when we dug into [specific need], it wasn't there unless we upgraded twice." [4] evidence
Product	Launched [new capability] (changelog, 3 weeks ago). Added [integration] to marketplace.	"[Competitor A] just released [capability] — that was one of the reasons we were leaning your way, but now they have it too." [6] evidence
Pricing	New starter tier at $X/mo (down from $Y). Enterprise pricing unchanged.	"Their new starter plan is half the price of yours. I know it's less features, but my CFO is asking why." [4] evidence

Threat Level: High — active in deals AND making external moves
Noise vs. Signal: Their product launch is real — buyers are mentioning it unprompted. The AI repositioning is mostly noise — [0] buyers used the word "AI" when describing them.
Key Move This Period: Lower-priced starter tier. Undercuts our entry point.
Buyer Validation: Pricing move confirmed in [4] calls. Feature launch confirmed in [6] calls. AI narrative NOT confirmed — zero buyer mentions.
Recommended Response: Update battlecard with pricing counter (TCO at 12 months). Update demo to show depth gap on [new capability].

[Competitor C]

Signal Source	What They're Saying	What Buyers Are Saying
Positioning	Rebranded: "[AI-native platform for X]". New category page. Speaking at [conference].	"[Competitor C] is positioning themselves as the AI-native option. Are you guys AI-native or is that bolted on?" [5] evidence
Product	Launched enterprise tier (SOC2, SSO, SAML). AI feature in beta.	"They showed us an AI feature that [does specific thing]. Do you have something like that?" [3] evidence
Pricing	Enterprise pricing now public ($X/seat). No change to mid-market tier.	No buyer mentions of pricing changes.

Threat Level: High — AI narrative is actively shaping buyer expectations before first call
Noise vs. Signal: AI positioning IS landing — buyers are repeating "AI-native" as an evaluation criterion. Enterprise features are early signal — only [3] mentions.
Key Move This Period: AI rebrand. They're defining the category criteria.
Buyer Validation: Confirmed. [5] calls where buyers used their language when evaluating us.
Recommended Response: Create "AI-native" counter-positioning. Key message: "AI is how we work, not what we sell. What decisions does it help you make?"

[Competitor D] — New Entrant

Signal Source	What They're Saying	What Buyers Are Saying
Positioning	Module inside [larger platform]. "All your [workflow] needs in one place."	"Our [larger platform] team mentioned they're building something similar. We'd rather not add another vendor." [3] evidence
Product	Shipped [module] 4 months ago. Limited features vs. standalone tools.	No specific feature mentions from buyers.
Pricing	Included in [platform] enterprise license. No additional cost.	Bundling is the draw — [2] mentions of "already paying for it."

Threat Level: New Entrant — appearing in enterprise deals only where [platform] is deployed
Noise vs. Signal: Too early. Only [3] OPS mentions, all from same segment.
Key Move This Period: Existence. They shipped — now it's there in every enterprise pitch.
Buyer Validation: Confirmed in enterprise only. Zero mid-market mentions.
Recommended Response: Create brief battlecard. Key message: "Purpose-built vs. bolted-on. Ask: how many customers are using that module today?"

[Competitor E] — User-added, not in buyer conversations

Signal Source	What They're Saying	What Buyers Are Saying
Positioning	"[Their headline]" — targeting [adjacent market]	No OPS evidence. Zero mentions across [X] calls.
Product	Active on changelog. [3] releases in last 90 days.	—
Pricing	Published at $X/mo. Competitive with our mid-tier.	—

Threat Level: Low — active externally but not showing up in deals
Noise vs. Signal: All noise, no signal. Their marketing isn't reaching your buyers (yet).
Key Move This Period: [Specific release]. Could become relevant if they enter your market.
Buyer Validation: None. Zero OPS evidence.
Recommended Response: Do nothing. Monitor quarterly. If they appear in OPS data, escalate.

Noise vs. Signal Summary

Competitor	Loudest External Claim	Showing Up in Deals?	Implication
[Competitor A]	"AI-powered platform"	No — buyers mention features and pricing, not AI	Their AI marketing isn't landing. Don't overreact to it.
[Competitor A]	New starter pricing	Yes — [4] calls	Real threat. Needs a response.
[Competitor C]	"AI-native"	Yes — [5] calls repeat the language	They're shaping criteria. Respond now.
[Competitor C]	Enterprise features	Early — [3] calls	Watch. Not urgent yet.
[Competitor D]	Platform consolidation	Yes — [3] calls, enterprise only	Real in one segment. Contained for now.
[Competitor E]	[Their headline]	No — zero mentions	Ignore until they appear in OPS data.

New Entrants & Emerging Threats

[Competitor D] — Platform module (from OPS data)

Where spotted: OPS — [3] buyer mentions, all enterprise
Why it matters: Platform incumbency is the weapon. Buyers aren't evaluating features — they're evaluating vendor count.
Recommended action: Add to watch list. Create brief battlecard for enterprise reps.

[Tool F] — [Description] (from OPS data)

Where spotted: OPS — [1] mention. Too early to classify.
Why it matters: If it's a real trend, we'll see [3]+ next month.
Recommended action: Ignore. Re-check next period.

Recommended Actions

Battlecard Updates Needed

[Competitor A] (priority: high) — Add pricing counter (TCO comparison at 12 months including upgrades they'll need) + [new capability] depth argument showing workflow gaps at their basic tier
[Competitor C] (priority: urgent) — Add AI counter-positioning and rebrand context. The narrative has shifted from "[old positioning]" to "AI-native [category]" — a category creation play
[Competitor D] (priority: low) — Create lightweight one-pager for enterprise reps. Purpose-built vs. platform module framing.

Positioning Threats to Address

[Competitor C]'s "AI-native" narrative is the only competitor claim that's both loud externally AND validated in buyer conversations. This is the highest-risk signal. Counter-positioning needed now.
Platform consolidation narrative from [Competitor D] in enterprise — "purpose-built vs. bolted-on" one-pager needed for enterprise reps

Product Gaps Surfaced

[Competitor A]'s [capability]: They shipped a basic version. Ours is deeper, but if buyers can't tell the difference in a 30-min demo, we lose the perception battle.
"AI roadmap" question from [4] prospects — even a narrative helps. Silence reads as "no plan."
[Integration X] — surfaced in multiple calls as a workflow requirement (not competitor-driven, but a gap)

Noise to Ignore

[Competitor A]'s AI repositioning — not landing with buyers ([0] mentions). Don't reposition in response.
[Competitor E]'s entire presence — zero buyer mentions. Don't allocate energy here.
[Competitor B]'s messaging shift — declining in deals regardless. Watch, don't react.

Sources scanned:

[competitor-a].com — homepage, pricing, changelog, blog
[competitor-c].com — homepage, pricing, product pages, press releases
[competitor-d].com — homepage, product module page
[competitor-e].com — homepage, pricing, changelog
g2.com/products/[competitor-a]/reviews
g2.com/products/[competitor-c]/reviews

Data: OPS Alternatives Evaluated ([X] calls, [date]) + Web scan ([date]). Claims with <3 OPS data points flagged as "early signal." Prompt v1 — May 2026.

What this is: A report that checks public competitor activity against what buyers actually repeat in your sales conversations. Every claim is backed by evidence — either from a web scan or OPS call data. This isn't opinion; it's what competitors published and what prospects actually said.

Start with what matters to your role

Sales / Enablement: Jump to the Per-Competitor Cards. The "What Buyers Are Saying" column is your prep material — real quotes, real objections. The "Recommended Response" at the bottom of each card is your talk track update. The Noise vs. Signal Summary tells you which competitor moves to address on calls and which to ignore.
Product: Start with Recommended Actions — specifically "Product Gaps Surfaced." These are competitor features that buyers are actually asking about, ranked by evidence count. Then scan the Per-Competitor Cards for any "Buyer Validation: Confirmed" entries on product launches — those are the moves that landed.
Marketing / Positioning: Read the Noise vs. Signal Summary first — it's the executive summary of what's landing and what isn't. Then check each competitor's "Key Move This Period" and whether buyers confirmed it. The gap between what competitors claim and what actually shows up in deals is your best material for messaging.
Exec skimming in 2 minutes: Read the Watch List table (threat levels + trends), the Noise vs. Signal Summary (6 rows), and the Recommended Actions section. That gives you: who matters, what's real vs. noise, and what to do about it.

How to interpret evidence counts

10+ evidence: Strong pattern. This is real and recurring.
3–9 evidence: Established pattern. Confident enough to act on.
Fewer than 3: Flagged as "early signal" throughout the report. Worth watching, not worth reorganizing around yet.

How to interpret threat levels

Threat levels combine two independent signals — external activity and deal presence — to classify how much attention a competitor deserves right now.

High: Active in deals AND making external moves. Both signals confirm the threat.
Medium: Present in deals OR making external moves, not both. One signal is missing.
Low: Occasional mention, no significant external activity. Monitor, don't react.
New Entrant: Appearing externally but not yet in buyer conversations. Watch for crossover.

What "Noise vs. Signal" means

This is the core concept of the report. Every competitor move falls into one of four patterns:

Pattern	What it means	What to do
Loud externally + confirmed by buyers	Real threat. Their marketing is landing.	Respond. Update battlecards, create counter-positioning.
Loud externally + zero buyer mentions	Noise. Their marketing isn't reaching your deals.	Don't overreact. Monitor, but don't reallocate resources.
Quiet externally + showing up in deals	Winning on product or word-of-mouth. Often the most dangerous.	Investigate. This is the threat traditional monitoring misses entirely.
Strong OPS evidence + web evidence conflicts	What buyers experience ≠ what the competitor claims. Gold.	Use the gap. Their marketing promises something buyers aren't experiencing.

How this differs from the Competitive Landscape Brief

	Competitor Monitoring Report	Competitive Landscape Brief
Focus	What competitors are doing (external + internal)	Where you stand competitively (internal only)
Data sources	Web scan + OPS buyer data	OPS buyer data only
Unique value	Noise vs. Signal — separates what competitors claim from what shows up in deals	Win/loss patterns and capability battleground
Cadence	Monthly or bi-weekly	Monthly or quarterly
Best for	PMM, competitive intel, product	Leadership, strategy, planning
Primary question	"What are they doing and does it matter?"	"Where do we win and lose?"

Reading cadence

Monthly (most teams):

Read the Noise vs. Signal Summary first — it's the executive summary
Review per-competitor cards for anyone at Threat Level: High
Act on Recommended Actions
Share relevant competitor cards with sales, product, and PMM

Bi-weekly (fast-moving markets):

Scan Watch List for threat level changes
Check for new entrants
Act on any "immediate" recommendations

First time running it?

The web scan works immediately — you'll get a full picture of what competitors are publishing and doing externally. The buyer side depends on having call data. If you have fewer than 20 calls, that side will be thin — that's fine. The web intelligence alone is useful. Run it again in 30 days with more call data and the buyer comparisons get sharp.

What to do with the output

What to do	How
Update your battlecards	The report tells you exactly what changed — which competitor made a move, whether it landed with buyers, and what to update. Focus on the "Recommended Response" in each competitor card. Learn more about keeping battlecards current →
See the full competitive landscape	This report is the "what's changing" layer on top of the broader view. Pair it with the Competitive Landscape Brief for a complete picture — where you stand (landscape) plus what's shifting (monitoring). View the Competitive Landscape Brief →
Brief your sales team	Copy the Noise vs. Signal Summary and Recommended Actions sections into your competitive Slack channel or next team standup. The per-competitor cards with quotes make great coaching material.
Feed product planning	The "Product Gaps Surfaced" section maps directly to sprint priorities. Competitor features that are landing with buyers need a response — features that aren't can be deprioritized.
Ask follow-up questions	With OPS connected to Claude, drill into the underlying data — "show me all quotes about [Competitor A]'s new feature" or "which deals did we lose to [Competitor C] this month?"

Related Pages

Parent concept

Guide to Competitive Intelligence — the concept this output belongs to

Job that produces this output

Monitor Competitor Activity — the job that generates this report

Sibling outputs (same program, different deliverable)

Competitive Landscape Brief — where you stand; this report tracks what's shifting
Win-Loss Report — win/loss patterns across the same deals

What to do with this output

Keep Battlecards Current — use this report to update your battlecards

Frequently asked questions

How is this different from monitoring competitor websites and social media?

Website and social monitoring shows you what competitors want you to see — press releases, blog posts, marketing claims. This report shows you what competitors are actually doing based on how it lands with buyers. A competitor might announce an AI feature that doesn't work, or quietly ship a pricing change they never publicize. Your sales calls catch both. The buyer's perspective is the ground truth.

How often should I run this report?

Depends on your market velocity. Fast-moving markets (AI, dev tools): bi-weekly. Most B2B SaaS: monthly. Stable markets: monthly is fine, but never less than that — things change faster than you think. The key signal to increase frequency: if you're seeing new competitors or feature launches in every report, go bi-weekly.

What's the minimum data needed for useful activity detection?

You need at least 20 calls in your time window for activity signals to emerge. Below that, you're only catching the loudest signals. The sweet spot is 40-100 calls per analysis window. If you have fewer than 20 calls per month, extend the window to 60 days — you'll still catch changes, just with a slight delay. The report flags anything under 3 data points as "early signal" so you know what's confirmed vs. what might be noise.