The Competitive Intelligence Meeting Problem
Founders and small teams that run regular competitive intelligence reviews have a documentation problem that most other team types don't: the information they're discussing goes stale faster than almost any other research. A competitor's pricing page from six months ago may be wrong today. A product feature captured in a G2 review from Q3 may have been sunset in the Q4 release. A competitor's funding round from last year changes the picture of their trajectory significantly.
This means a competitive intelligence meeting recap needs something that most meeting recaps don't: date-stamped citations for every competitive claim. Not just "Competitor X charges $49/user/month" but "Competitor X pricing page as of [Date] shows $49/user/month." The date-stamp is what makes the information useful six months from now, when someone reads the recap and needs to know whether the claim is likely still accurate.
The second problem: competitive intelligence discussions generate a lot of inference and reaction. "If they're doing X, they must be targeting enterprise" is the team's interpretation, not the research's conclusion. A useful competitive intelligence recap clearly separates what the research shows from what the team inferred and decided in response.
What Makes a Competitive Intelligence Recap Different
A competitive intelligence meeting recap serves different purposes than other meeting recaps:
| Standard meeting recap | Competitive intelligence recap |
|---|
| Documents decisions and actions | Documents what was observed + decisions + actions |
| Citations are nice to have | Date-stamped citations are required (information decays) |
| Decisions are about what the team will do | Decisions include "what we believe about the market" |
| Open questions are operational | Open questions include market monitoring needs |
| Mostly for internal team | Often referenced in fundraising, board, or investor materials |
The competitive intelligence recap is partly a reference document: future-you (or a new hire) will read it and need to know not just what was decided but what the research showed when those decisions were made.
Three Types of Competitive Intelligence Meetings (and Their Recap Needs)
The type of competitive intelligence session determines what the recap should emphasize:
Type 1: Competitor Monitoring Review
A regular cadence (monthly, quarterly) review of what competitors are doing. The recap should document what changed since the last review, what stayed the same, and what the team decided to do in response to changes.
Type 2: Win/Loss Analysis Session
A structured review of recent won and lost deals, focused on how competitors influenced the outcome. The recap should document patterns across multiple deals, specific competitive weaknesses or advantages surfaced, and what the team will do differently.
Type 3: Strategic Positioning Session
A less frequent session where the team reassesses their positioning in relation to the competitive landscape. The recap should document the team's current competitive view, the evidence that supports or challenges their positioning, and strategic decisions made.
The Date-Stamp Requirement
For any competitive claim in the recap, the format is:
[Competitive claim] — Source: [Where this came from] — As of: [Date]
Examples:
- "Competitor X's pricing page lists $49/user/month for the Standard plan" — Source: competitor-x.com/pricing — As of: [Date of research]
- "G2 reviews (2024 Q3, 47 reviews) show Competitor Y's most common complaint is onboarding time" — Source: G2.com/products/competitor-y/reviews — As of: [Date reviewed]
- "LinkedIn shows Competitor Z has grown from 45 to 78 employees in the past 12 months" — Source: LinkedIn company page — As of: [Date checked]
The date-stamp rule applies even when information feels stable. Feature lists change. Pricing changes. Employee counts change. What seems permanent today may not be in six months.
Separating Research Claims from Team Inferences
The most important discipline in competitive intelligence recaps: clearly separating what the research shows from what the team inferred or concluded.
RESEARCH vs. INFERENCE DISTINCTION
Research claim (what the data shows):
"Competitor X's G2 reviews (Q3 2024) cite 'slow support response time' as the top
complaint in 23 of 47 reviews." — Source: G2, As of: [Date]
Team inference (what the team believes this means):
"This suggests Competitor X is likely undersupported relative to their customer base —
possibly a growth-without-scale problem. [Team member name] noted this pattern often
precedes churn spikes."
Team decision in response:
"We'll add 'dedicated onboarding specialist for first 90 days' as a differentiator
in our sales materials targeting customers who've had the Competitor X support experience."
Research claims are what the evidence shows. Inferences are the team's interpretation of what that evidence implies. Decisions are what the team will do in response. All three belong in the recap — clearly labeled.
Step 1: Organize Research by Competitor and Topic
Before writing the recap, organize the competitive research that was discussed:
COMPETITIVE RESEARCH INVENTORY (post-meeting)
Competitor: [Name]
Research items discussed:
1. Topic: [Pricing / Product features / Customer reviews / Team growth / Messaging]
Specific finding: "[What the research shows]"
Source: [Where from] — As of: [Date]
Was this discussed in the meeting? [Y/N]
Team's response: [What the team said about this finding]
2. [Same structure]
Team's overall read on this competitor:
Strengths (from research): [...]
Weaknesses (from research): [...]
Movement (from research): [What changed since last review]
Team's inference (labeled as inference):
"We believe..." / "This suggests..." / "Our read is that..."
Step 2: Document the Team's Competitive Intelligence Decisions
A competitive intelligence session typically produces two types of decisions:
Market assessment decisions: "We believe Competitor X is targeting mid-market. We believe their recent enterprise push is not threatening to us because [reason from research]."
Response decisions: "We will add [feature] to address the gap their customers complain about. We will reposition [aspect] in our messaging. We will monitor [specific indicator] next quarter."
Both need to be documented with their rationale and the research that informed them.
CI DECISION RECORD
Decision type: □ Market assessment □ Response action □ Monitoring commitment
Decision: "[What was decided]"
Evidence from research: "[The specific competitive data that drove this decision]" — [Citation, Date]
Team inference stated: "[What the team concluded from the evidence]"
Confidence level: [High — multiple sources / Medium — one source / Low — inference only]
Decision status: [Decided / Still open — needs more research]
Step 3: Draft the Competitive Intelligence Meeting Recap
COMPETITIVE INTELLIGENCE MEETING RECAP
Meeting: [Type: Monitoring Review / Win-Loss / Positioning Session]
Date: | Attendees:
Research reviewed: [Competitor names and sources reviewed]
COMPETITIVE LANDSCAPE SNAPSHOT (as of [Date])
[2-3 sentences on the current competitive picture — who the key players are, what's changed since last review]
COMPETITOR UPDATES
Competitor: [Name]
What's changed: [New findings since last review, date-stamped]
What stayed the same: [Stable findings]
Key research findings discussed:
1. "[Finding]" — Source: [Source] — As of: [Date]
2. [Same structure]
Team's read on this competitor: [Team's collective inference — labeled as such]
[Repeat for each competitor reviewed]
WIN/LOSS ANALYSIS (if applicable)
Pattern identified: [What the win/loss data shows across recent deals]
Evidence: [N wins vs. N losses involving Competitor X in Q[N]; themes in loss reasons]
Team's interpretation: [...]
DECISIONS MADE
Market assessment decisions:
1. "[What the team now believes about the competitive landscape]"
Evidence: [Citation(s)] — As of: [Date]
Confidence: [High / Medium / Low]
Response decisions:
1. "[What we will do in response to competitive research]"
Rationale: "[What the research showed that prompted this]" — [Citation, Date]
ACTION ITEMS
□ [Owner] — [Deliverable] — [Due date]
MONITORING COMMITMENTS (what to track before next review)
□ [Competitor]: [What to watch] — [Who tracks it]
OPEN QUESTIONS
□ [What the research didn't answer that the team needs to know]
NEXT REVIEW
Date: | Focus:
SOURCES
[All competitive sources cited, with dates accessed]
Before/After Worked Example
Context: A co-founder of a project management tool for creative agencies ran a quarterly competitive intelligence review with her two co-founders. They reviewed research on their top three competitors: Asana (large/established), Monday.com (mid-market), and a newer entrant, Motion (AI-scheduling focused).
Research gathered before the meeting:
- Asana pricing page (as of [Date]): Business plan $24.99/user/month
- G2 reviews for Motion (Q3 2024, 89 reviews): 82% positive; top complaint (14 reviews): "AI scheduling gets confused when I have client meetings I can't move"
- Motion job postings (LinkedIn, as of [Date]): 3 open engineering roles, 0 sales roles
- Motion blog post (Date): "How Motion's AI learns your work patterns" — describes their ML approach
- Monday.com App Marketplace announcement (Date): 47 new integrations launched in Q2
Before (vague log without date-stamps or attribution split):
CI Review Meeting — [Date]
We reviewed Asana, Monday.com, and Motion. Asana is expensive. Motion has AI scheduling but customers complain about it with client meetings. Monday.com is adding more integrations. We think Motion is still in product-market fit mode, not sales mode. We decided to position against Motion by emphasizing that we don't auto-reschedule client meetings. Emma will update the competitive slide.
Which Asana plan is expensive? What was "customers complaining about"? No dates on any claim. "We think Motion is in PMF mode" — is this inference or research? The competitive slide update will be stale before it's finished.
After (date-stamped, source-attributed, inference-separated):
Quarterly Competitive Intelligence Review — Q3 2024
[Date] | Founders: [List]
COMPETITIVE SNAPSHOT (as of [Date])
Our primary competitive set remains large (Asana), mid-market (Monday.com), and AI-scheduling focused (Motion). Motion's rapid growth (based on G2 review volume increase) is the largest development since Q2. Monday.com's integration expansion is broadening their ecosystem defensibility.
COMPETITOR: MOTION
What's new:
- G2 reviews: 89 total (up from 34 in Q1) — 82% positive overall — Source: G2.com, reviewed [Date]
- Top complaint pattern: "AI scheduling gets confused when I have client meetings I can't move" — surfaced in 14 of 89 reviews — Source: G2, [Date]
- Hiring: 3 open engineering roles, 0 open sales roles — Source: LinkedIn company page, [Date]
- Product: Published blog post explaining ML approach to schedule learning — Source: Motion blog, [Date]
Team's read (labeled as inference):
"Motion's hiring pattern — engineering-heavy, no sales roles — suggests they're in a product depth phase rather than growth phase. The client-meeting scheduling complaint is structural: their AI is optimized for autonomous rescheduling, which conflicts with the client-service reality of agency work. We believe this is a fundamental positioning limitation, not just a bug."
Confidence: Medium — based on hiring data and review patterns, not confirmed
COMPETITOR: MONDAY.COM
What's new:
- 47 new integrations launched in Q2 — Source: Monday.com App Marketplace announcement, [Date]
Team's read: Ecosystem expansion increases switching cost for customers using their integration ecosystem. Not a direct competitive threat to us this quarter.
COMPETITOR: ASANA
Stable:
- Business plan $24.99/user/month — Source: asana.com/pricing, [Date]
No significant product updates to report. Not the focus of this review.
DECISIONS
Market assessment:
- "Motion's AI scheduling limitation with external client meetings is a structural positioning gap for the creative agency use case, not a temporary product bug."
Evidence: G2 reviews (14 reviews, Q3 2024); Motion's ML approach (blog, [Date])
Confidence: Medium — reviews suggest pattern; not confirmed with customer interviews
Response:
- "We will explicitly emphasize that our scheduling approach doesn't auto-reschedule client meetings in our agency-segment positioning."
Rationale: Motion's top complaint is our implicit differentiator; we should make it explicit.
ACTION ITEMS
□ Emma — Update competitive positioning slide: add "We don't reschedule your client meetings" as a differentiator against Motion — due [Date]
□ Jake — Pull 5 recent sales calls where Motion came up; check if client-meeting conflict was mentioned — due [Date]
MONITORING COMMITMENTS
□ Motion: Sales role job postings — check LinkedIn in 60 days — Owner: Emma
□ G2 Motion reviews: check again in Q4 — Owner: Emma
OPEN QUESTIONS
□ Is Motion targeting creative agencies specifically, or is the client-meeting conflict a segment-agnostic problem? Need to check their marketing messaging more carefully — Jake to investigate.
NEXT REVIEW
Q4 2024 CI Review — [Date] | Focus: Motion customer segment targeting; Monday.com integration impact on existing customers
SOURCES
- G2.com. Motion reviews. Accessed [Date]. G2.com/products/motion/reviews
- Motion. "How Motion's AI learns your work patterns." Motion Blog, [Date].
- LinkedIn. Motion company page / job postings. Accessed [Date].
- Monday.com. "Q2 Integration Marketplace Update." [Date].
- Asana. Pricing page. Accessed [Date]. asana.com/pricing
Every claim date-stamped; research findings clearly separated from team inferences; team inferences labeled with confidence level; action items properly formatted.
Prompts to Reuse
Meeting Recap From Competitor Research
I'm writing a competitive intelligence recap for [Meeting type, Date, Attendees].
Competitors reviewed: [List]
Research reviewed in the meeting:
Competitor 1: [Name]
Finding: "[What the research shows]" — Source: [Source] — As of: [Date]
Finding: "[...]" — Source: [...] — As of: [...]
Team's read (inference): "[What we believe this means — labeled as inference]"
Confidence: [High / Medium / Low]
Competitor 2: [Same structure]
Decisions made:
Market assessment: "[What the team now believes about the competitive landscape]"
Evidence: [Citation(s)]
Response: "[What we will do]"
Rationale: "[What research drove this decision]" — [Citation, Date]
Action items: [Owner, deliverable, due date]
Monitoring commitments: [What to track, who tracks it, when to check]
Open questions: [What the research didn't answer]
Draft a competitive intelligence recap that:
- Organizes by competitor, showing what changed vs. stayed stable
- Clearly separates research findings (what the data shows, date-stamped) from team inferences (what we believe this means)
- Labels confidence levels for inferences
- Documents market assessment decisions and response decisions separately
- Includes monitoring commitments for next review
- Closes with complete source list with access dates
Date-stamp rules: every competitive claim needs "As of [Date]"
Attribution rules:
"[Source] shows / reports..." = research finding
"We believe / Our read is..." = team inference
"We will / decided to..." = response decision
Never: presenting team inference as research finding
Key Takeaways
- Every competitive claim needs a date-stamp: competitive information decays fast; "Competitor X charges $49/month (as of [Date])" is useful six months from now; "Competitor X charges $49/month" may not be.
- Separate research findings from team inferences: what the data shows and what the team believes it means are two different things; mixing them produces a recap that can't be evaluated.
- Label confidence levels for inferences: "Medium confidence — based on hiring data" is more honest than presenting an inference as a fact.
- Document monitoring commitments: a CI recap that ends without "here's what we'll track and check by when" means you'll start the next meeting catching up on things you should have monitored.
- Record open questions explicitly: competitive questions the meeting didn't resolve should be in the recap so they're on the agenda for the next review, not lost.
Conclusion
A competitive intelligence meeting recap is a reference document as much as a meeting record. Future you, new hires, investors, and board members may read it to understand both what the competitive landscape looked like at a specific point in time and what the team decided in response. The disciplines that make it useful are simple: date-stamp every competitive claim, separate what the research shows from what the team inferred, and document the monitoring commitments that will keep the intelligence current. Without these, a competitive recap is a snapshot that nobody can trust — with them, it's a living document in a system that helps a lean team stay sharp on their competitive environment.
Try WebSnips free — clip competitor pricing pages, G2 reviews, product announcements, and job postings as organized text extracts tagged by competitor and date, so your next competitive intelligence recap can pull every relevant finding directly into the document rather than hunting for which tab had which competitor's pricing.