A quarterly competitive review should answer three questions: What changed? Does it matter to us? What do we do about it? Most don't. They become status reports—a parade of screenshots, a few "interesting" job postings, a vague sense that competitors are "doing something." Then everyone forgets by week two.
The format below takes 90 minutes, requires a moderator who's been tracking competitors all quarter, and produces a one-page action list. It works because it separates signal from noise and forces a vote on what actually requires response.
The 90-minute structure
Segment 1: Threat scan (20 minutes)
The moderator presents three categories of change observed over the quarter:
- Pricing or packaging moves (new tiers, bundling, discounting patterns, free/trial availability)
- Product capability claims (new features, integrations, platform shifts visible on websites or in reviews)
- Hiring signals (sales team expansion, new role creation, geographic scaling)
No narrative. Just the facts: "Competitor A raised prices on their mid-tier plan 15% in August." "Competitor B posted 12 sales engineer roles in the past 90 days, all in EMEA." "Competitor C launched a native integration with [platform] in September." Stick to what's observable—pricing pages, G2/Capterra/Trustpilot review dates and tone shifts, job postings across major ATS platforms, news, website changes.
Segment 2: Relevance voting (25 minutes)
For each change, the room votes: Does this affect our strategy in the next 90 days? Yes, no, or maybe.
"Maybe" items go to a holding list. "Yes" items move forward. This forces disagreement into the open. If your VP of Sales thinks a competitor's pricing move is urgent and your product lead doesn't, that's a conversation worth having now, not in a Slack thread in November.
Typical result: 15–20 changes observed, 5–7 voted "yes."
Segment 3: Implication mapping (30 minutes)
For each "yes" item, answer two things:
- Who inside our company needs to know this and act on it? (Sales, product, marketing, leadership)
- What's the one thing we could do in the next 30 days to respond or stay ahead?
Examples: If a competitor hired 8 sales engineers and you're losing deals in technical evaluations, maybe you need a sales engineer hiring sprint or a pre-sales training program. If they bundled two products you sell separately, maybe your packaging conversation with product moves up. If they launched in a new region, maybe you audit your own go-to-market there.
The point: each threat gets one owner and one 30-day action. Not "monitor this." Not "we'll discuss later." An actual thing someone will do.
Segment 4: Priorities and close (15 minutes)
Rank the actions by impact and effort. The top 3 become quarterly OKRs or at least named initiatives. The rest go into a backlog. Write them down. Share them. Check them in 30 days.
What makes this work
The discipline comes from three constraints: You've been collecting data all quarter (not scrambling the day before). You vote on relevance (not debating endlessly). You map to one owner and one action (not vague commitments).
The moderator role matters. They need to have been watching competitor pricing pages, review sites, job postings, and news throughout the quarter—not assembling it from memory. If you're doing this manually, set calendar reminders to check each competitor's careers page, pricing, and latest reviews every two weeks. If you're using a tool that monitors websites, pricing, reviews, job postings, and news automatically and surfaces changes in a daily briefing, the moderator's job becomes curating signal from that stream and preparing the three-category summary.
The vote step is underrated. It prevents the loudest person from determining what matters. It also surfaces blind spots: if the room thinks a competitor move is irrelevant but sales thinks it's urgent, that's a data gap worth investigating before next quarter.
The output
One page. Date. Three to five actions. Owner. 30-day check-in date. Distribute it to leadership and the owners. That's it. No 40-slide deck. No "key takeaways." Just decisions.
Done well, this meeting becomes the place where competitive reality collides with strategy, and strategy changes. Done poorly, it's a ritual. The difference is whether you walk out with a list of things to do or just a list of things that happened.