How to Run a Competitor Signal Review Meeting (30 Minutes)

A weekly competitor meeting that produces zero decisions, week after week, is the default at most B2B SaaS companies that have one. A sales leader shares an anecdote from a lost deal. The PMM mentions a competitor's recent blog post. Someone brings up pricing chatter. Thirty minutes pass, two people nod, and the meeting ends. The next week's meeting looks identical. The meeting is not competitor monitoring; it's a status update pretending to be one.

The 30-minute version below produces decisions because it's structured around producing decisions. Same cadence, same duration, different shape. The shape is the difference between a meeting that moves pipeline and a meeting that consumes it.

The attendees

Four people, maximum. A PMM (owner), a sales leader or senior AE, a CS representative, and optionally the CMO for high-stakes weeks. More than four people dilutes the meeting into a broadcast; fewer than three loses the cross-functional signal that makes the meeting worth holding.

Not invited: the entire sales team, the entire marketing team, product (unless a specific signal warrants it), engineering, executives below the CMO level. If those teams need the outputs, the output document routes to them — but the meeting itself stays tight.

The three required artifacts

The meeting doesn't open with fresh discussion. It opens with three artifacts pre-circulated 24 hours before the meeting. Attendees show up having read the three, and the meeting time is spent on decisions, not information transfer.

The artifacts take the PMM roughly 45 minutes to prepare. The preparation is the actual monitoring work; the meeting is where that work converts to decisions.

The 30-minute agenda

The rule that keeps this from being a status update

The rule: every signal discussed in the meeting has to exit with a decision. No signal is allowed to float. Ignore, Monitor (with review date), Respond (with owner and timeline), or Preempt (with escalation). The rule sounds bureaucratic. It is the single most important rule in the meeting because it's what converts information flow into decision flow.

Most competitor meetings fail because signals get discussed without closure. The team walks out of the meeting having "discussed the competitor's pricing change" without deciding what to do about it. The next week, the signal reappears on the agenda, gets discussed again, and again exits without closure. The signal becomes a recurring topic rather than a resolved decision.

The fix is the one-sentence PMM prompt at the end of each signal discussion: "So the decision is [Ignore / Monitor with review in 30 days / Respond with [owner] by [date]]. Agreed?" If no one objects, it's recorded. If someone objects, the debate gets 60 seconds. If no resolution in 60 seconds, the decision is "Monitor, revisit next week with additional context." Something is always recorded.

The meeting note

Within two hours of the meeting, the PMM ships a one-page meeting note to a named distribution list. The note has four sections: decisions made (bulleted, with owner and date), signals logged as Ignore (with brief rationale), Monitor items extended (with new review date), and the next-meeting agenda items.

The distribution list is narrow: the meeting attendees, the sales team lead, the CMO. Not the whole company. A wider distribution produces pressure to be less candid, and the meeting's value depends on candor.

When the meeting is broken

Three signals that the meeting isn't working.

The signal log is empty or nearly empty. If the PMM has fewer than three signals to discuss, the monitoring work isn't producing enough volume — either the tier list is too narrow or the PMM isn't making the time. Fix this before doubling down on the meeting itself.

The same signal appears in three consecutive weeks. A signal that extends Monitor three times has almost always become Ignore; the team just hasn't had the conversation. Force the decision.

Decisions aren't followed through. If a Respond-tier decision is made in the meeting and the battle-card update doesn't ship within two weeks, the meeting's decisions don't have teeth. This is usually a CMO-level conversation — the meeting's decisions need executive air cover to actually get resourced, and if they don't have it, the meeting becomes theater.

Most competitor monitoring fails in meetings, not in the monitoring itself. The PMM doing the work is usually finding signal; the signal dies in the discussion. The 30-minute version above is the simplest intervention we've seen produce decisions consistently. It is boring, it is structured, and it works.