Running a Weekly Competitive Review with Your Team
Short answer: A 30-minute weekly meeting driven by your KompWatch digest turns raw competitor data into team-level decisions. This guide gives you the agenda, who to invite, and how to avoid the meeting becoming noise.
Why schedule a recurring review at all?
Individual alerts are for real-time reactions. The weekly review is for pattern recognition — spotting trends that no single change triggers on its own. A competitor that tweaks their pricing page five times in a month is running an A/B test. One that quietly expands their feature list three sprints in a row is shipping toward a new capability. Neither shows up as a Critical alert, but both are strategically significant.
The weekly cadence also creates a forcing function: intel that enters the digest gets acted on, not buried.
Who to include
You don't need everyone every week. A lean standing invite works better than a large rotating one.
| Role | Why they're in the room |
|---|---|
| Product (owner or PM) | Feature and positioning signals — what's competitors building? |
| Sales lead or rep | Objection prep — what will prospects say this week? |
| Marketing | Messaging and campaign signals — how is their copy shifting? |
| Optional: CEO/founder | For Critical-severity changes only — set a threshold for escalation |
Customer Success can join monthly rather than weekly. Engineering rarely needs to be in this meeting unless you're tracking a direct technical competitor.
The 30-minute agenda
1 — Digest triage (10 min)
Open Digests → Latest in KompWatch. Walk through Critical and High-severity changes as a group.
For each change:
- What changed? (read the AI summary aloud — 30 seconds)
- Does anyone need to act on this? (yes/no — assign an owner if yes)
- Is this part of a pattern? (flag if you've seen related changes recently)
Changes classified as LOW or MEDIUM: skip in the meeting. Those belong in async reading.
2 — Owner updates (10 min)
Anyone who was assigned an action item last week gives a one-sentence update: done, in progress, or dropped. No elaboration unless the room needs to weigh in.
3 — Battlecard sync (5 min)
Look at your top three competitors. Has anything in the past week invalidated a claim on your battlecard? If yes, assign an owner to update the card before Friday.
This is the highest-leverage use of competitive intel. A stale battlecard loses deals. See Creating Sales Battlecards for the update workflow.
4 — Flag for CEO/leadership (5 min)
Agree on whether any change from this week rises to the level of a leadership brief. Use the bar from Responding to a Major Competitor Move: does this affect pricing, a major feature, or a segment you both target? If yes, one person drafts a three-line brief by EOD.
KompWatch features that make the meeting faster
Pre-meeting: send the digest to all attendees before the call. In Settings → Digest Preferences, you can add teammate emails to the digest distribution. They arrive 15 minutes before your scheduled meeting time.
Filter by competitor during the meeting. The digest includes a competitor filter. Focus the first 5 minutes on your primary competitor, then scan the rest.
Use Change History for pattern questions. If someone asks "has [Competitor] been changing their pricing page a lot lately?", go to Competitors → [Name] → Change History and filter by change type. You'll see the full timeline immediately.
Export to JSON for the 2-week audit. Once a month, export change data for your top three competitors and drop it in your competitive Notion/Confluence page. This creates a running record useful for board decks and new hire onboarding.
Common failure modes
The meeting becomes a passive news recap. Every change gets described but nothing gets assigned. Fix: add a named owner to every High-severity change before the meeting ends, even if the action is just "monitor for another week."
The meeting gets cancelled when there's nothing Critical. Low-signal weeks are when patterns slip through unnoticed. Keep the cadence even for quiet weeks — use the time for battlecard hygiene if there are no alerts to triage.
Sales doesn't attend consistently. The meeting loses its primary output. Solve this by sending reps the battlecard update directly after the meeting, regardless of attendance. They'll start coming when the cards are visibly more accurate.
Too many people, too many opinions. Cap the standing invite at four people. Add others as needed for specific topics, then let them drop.
Scaling the cadence for different plan tiers
| Plan | Recommended meeting cadence | Why |
|---|---|---|
| Free | Bi-weekly or monthly | Daily snapshots don't generate enough volume to fill a weekly review |
| Pro | Weekly (standard) | 6-hour snapshots across 10 competitors generate meaningful weekly volume |
| Team | Weekly + async daily digest | Hourly snapshots mean real-time alerts should handle the urgent layer; the weekly review focuses on patterns |
On the Team plan, consider separating the digest review from the meeting entirely. Route the daily digest to a dedicated Slack channel. The weekly meeting becomes purely a discussion of trends and actions, not raw alert triage.
Template: meeting notes structure
A simple doc captures enough without overhead:
## Competitive Review — [Date]
Attendees:
### Critical/High changes this week
- [Competitor] — [What changed] → Owner: [Name] by [Date]
### Patterns noticed
-
### Battlecard updates needed
- [Competitor] — [Section] → Owner: [Name]
### Leadership brief needed?
[ ] Yes — [Name] drafting by EOD
[x] No
Related articles
- Competitive Intelligence Best Practices — day-to-day habits between reviews
- Managing Alert Fatigue — keeping signal-to-noise high before the meeting
- Creating Sales Battlecards — updating cards from weekly intel
- Responding to a Major Competitor Move — when a change can't wait for the weekly meeting
- Using KompWatch Insights for Sales — routing intel directly to your sales team
Questions? Email support@kompwatch.com — a team member will respond within 24 hours.