PRODUCTQUANT WORKBOOK

SaaS CI Framework

Competitive intelligence + internal retrospective system on a monthly cadence

Table of Contents

Section Description
01 CI Tracking TemplateA single source of truth for capturing, verifying, and contextualizing competitive signals.
02 Signal Categorization GuideClassify incoming intelligence by type, urgency, and required response.
03 Competitor Move Analysis MatrixDecode competitor actions by intent, capability, and likely impact on your market position.
04 Internal Retrospective WorksheetTurn competitive losses and wins into institutional learning and process improvement.
05 Prioritization & Response FrameworkSystematically decide which competitive gaps to address, in what order, and with what resources.
06 Monthly CI Cadence ChecklistThe operational rhythm that turns intelligence from a project into a process.
07 Decision Log TemplateDocument CI-driven decisions to create accountability and a historical record for future strategy.
08 CI Report TemplateCommunicate key findings, decisions, and actions to stakeholders in a single, scannable page.
01
CI Tracking Template
A single source of truth for capturing, verifying, and contextualizing competitive signals.

CI Tracking Template

A feature matrix looks precise but often misleads. The goal is not a checklist, but a record of capability depth, verification status, and strategic weight. This template prevents teams from reacting to marketing claims instead of verified product reality. It shifts the focus from binary presence to a nuanced understanding of competitive capability, which is critical for accurate gap analysis. Without this structured capture, teams rely on anecdotal evidence, which leads to reactive and inconsistent strategy.

Most competitor feature matrices confuse presence with depth. A row marked as present on a marketing page may deserve a partial score once documentation, tier limits, or workflow caveats are checked. This discrepancy is a primary source of strategic misjudgment. In one analysis, a competitor's "AI feature" scored a presence of 5, but a depth score of 2 after testing revealed it was a basic automation rule.

Core Tracking Dimensions

Each signal you track must be evaluated across four dimensions to be decision-useful. This moves you from a reactive "they have it, we don't" posture to a strategic assessment of impact. These dimensions create a common language for product, sales, and marketing teams to assess competitive threats and opportunities with consistent criteria. The scoring system forces quantification, reducing ambiguity in team discussions about competitor strength.

Dimension Definition Scoring Guide Example
Presence Does the capability exist in any form?
"Audit logging"
Depth Implementation quality & workflow completeness.
"Exportable, role-aware, enterprise-credible audit logging"
Verification Source quality and evidence.
Live Demo
Docs
Rumor
Verified via help doc vs. sales rumor.
Strategic Weight Importance to your target buyer's core job. High Medium Low Deal-breaker for 13% of pipeline.

Template Worksheet

Use this worksheet for each major competitor or product category you track. Update it monthly with new signals from sales calls, review sites, and product exploration. The discipline of regular updates prevents the template from becoming a stale artifact and ensures your competitive view remains current and actionable. Assigning a single owner for each competitor sheet ensures consistency in scoring and prevents duplication of effort across the organization.

Competitor / Product:
Date of Last Deep Review:
Primary Source of Signals This Month (e.g., G2 reviews, sales call transcripts, pricing page):
Feature / Signal Presence (1-5) Depth Notes Verification Source Strategic Weight
Monthly Verification Checklist:
  • Update at least one "Verification Source" from "Rumor" to "Docs" or "Live Demo".
  • Re-score "Depth" for one previously tracked feature based on new testing.
  • Flag any feature with "High" strategic weight and a presence score ≤2 for roadmap discussion.
  • Review one competitor's pricing page for changes in packaging or unit economics.
  • Operationalizing the Template

    Assign one product manager or product marketer as the owner of the master tracking document. Their role is to collate inputs from sales and marketing, challenge unverified claims, and ensure scoring consistency across competitors. This ownership is the first step in building a CI operating system. The owner should spend no more than 2-3 hours per week maintaining the template; the value is in the discipline, not the volume of data.

    Target: Each tracked competitor sheet updated at least once per month.
    02
    Signal Categorization Guide
    Classify incoming intelligence by type, urgency, and required response.

    Signal Categorization Guide

    Not all competitive signals are equal. A pricing change requires a different response cadence than a new marketing campaign. This framework categorizes signals by their operational impact and the evidence quality, ensuring your team focuses on what matters. Effective categorization acts as a triage system, preventing analysis paralysis and directing resources to the most pressing threats. Without categorization, urgent signals get buried and low-priority rumors consume valuable analysis time.

    Signal Types & Urgency Tiers

    Categorize every captured signal upon entry. This triage system prevents noise from consuming analysis bandwidth and ensures high-urgency items are routed correctly. The type determines which internal team should lead the analysis, while the urgency tier dictates the timeline for response. This dual-axis classification is the core of an efficient CI workflow.

    Type: Product Capability

    New feature, major enhancement, or change to existing workflow depth. Requires technical assessment.

    Common

    Type: Pricing & Packaging

    Price change, new plan, feature re-tiering, or billing unit shift. Directly impacts win/loss conversations.

    High Impact

    Type: GTM & Positioning

    New marketing message, case study, sales play, or partnership announcement. Affects narrative.

    Strategic

    Type: Market Perception

    Review site sentiment, social media chatter, analyst report mention. Indicator of brand health.

    Monitoring
    Urgency Tier Definition Response Timeline Example Signal
    Critical Direct, verified threat to current quarter pipeline or core differentiation. 48 hours Major competitor launches your flagship unique feature.
    High Strategic shift that will impact future positioning or pricing power. 1 week Competitor introduces a lower-cost plan targeting your highest-conversion segment.
    Medium Important market data point requiring analysis and potential roadmap adjustment. 2 weeks New integration partnership announced that expands competitor's use cases.
    Low / Informational Background intelligence for long-term strategy; no immediate action. Monthly review Competitor hires a new VP of Engineering from a related industry.
    Evidence quality dictates urgency. A rumor from a single sales rep is "Low" urgency. The same signal verified via a live demo, pricing page, and official announcement becomes "High" or "Critical". The escalation path is a function of verification, not just the signal's apparent importance. Teams that conflate importance with evidence often overreact to unverified claims.

    Categorization Worksheet

    Use this worksheet to practice categorizing real or example signals. This builds team muscle memory for the monthly triage process. Consistent application of these labels across the organization ensures everyone interprets competitive threats with the same lens. Run this exercise with your sales and product teams to align on classification criteria.

    Signal Description:
    Signal Type:
    Evidence Quality (Rumor, Claimed, Verified):
    Assigned Urgency Tier:
    Primary Source:
    Brief Rationale for Urgency Tier:
    1
    Informational
    File for reference. No action required this cycle.
    2
    Monitor
    Watch for corroborating signals. Discuss in monthly review.
    3
    Analyze
    Requires deeper investigation and impact assessment.
    4
    Act
    Develop a response plan. Assign owner and timeline.
    5
    Escalate
    Immediate threat. Convene cross-functional team within days.
    03
    Competitor Move Analysis Matrix
    Decode competitor actions by intent, capability, and likely impact on your market position.

    Competitor Move Analysis Matrix

    Competitors act for reasons—resource allocation, market pressure, strategic ambition. This matrix helps you move beyond "what they did" to "why they did it" and "what it means for us." It combines external signals with internal assessment to predict competitive trajectories. Understanding the archetype of a move allows you to anticipate follow-on actions and calibrate your strategic response appropriately. Misreading a "Land Grab" as a "Strategic Pivot" can lead to overinvestment in a counter-move that misses the real threat.

    Move Archetypes

    Most competitor moves fit into one of five archetypes. Identifying the archetype helps you predict their next steps and calibrate your response. Each archetype carries different implications for your win rate, pricing power, and strategic focus. Use this table as a reference during your analysis to quickly hypothesize about competitor intent.

    Archetype Typical Signals Probable Intent Your Risk Level
    Land Grab Price cut, freemium launch, aggressive sales hiring. Acquire market share quickly, often at low margins. High in low-ARPU segments.
    Feature Parity Launch of a known missing feature you offer. Remove a key objection in competitive deals. Medium (neutralizes an advantage).
    Upsell Expansion New premium tier, enterprise add-ons, price increase. Increase revenue from existing customer base. Low (may create acquisition opportunity).
    Strategic Pivot New branding, messaging shift, targeting a new persona. Capture an adjacent market or redefine the category. High if it overlaps your core.
    Defensive Hold Minor updates, focus on retention, loyalty programs. Protect current customer base from churn. Medium (harder to win their customers).
    A competitor's move often reveals their internal constraints. A "Feature Parity" launch may indicate they are reacting to your wins in the market, a sign of weakness, not strength. Conversely, a "Strategic Pivot" might signal they are conceding your core segment, creating an opening for you to solidify dominance. The archetype analysis is about reading their strategy, not just cataloging their actions.

    Impact Assessment Worksheet

    For each major competitor move, complete this assessment to quantify its potential effect on your business. This structured approach replaces gut-feel reactions with a disciplined evaluation of impact across three key dimensions: commercial, strategic, and operational. The radar bars provide a visual summary of the move's composite threat level.

    Competitor & Move Description:
    Archetype (from table above):
    Target Customer Segment:
    Evidence Strength (1=Weak, 5=Strong):
    Impact on Win Rate
    0%
    Impact on Pricing Power
    0%
    Strategic Surprise (Did we see it coming?)
    0%
    Recommended Initial Response (Monitor, Analyze, Counter-Message, Develop Counter-Feature):

    Response Decision Framework

    Use this logic tree to decide on a response after completing the impact assessment. This framework ties the analytical work to a clear action, preventing the common pitfall of analysis without conclusion. The framework is designed to be used in the Week 2 deep-dive meeting.

    If Impact on Win Rate is High AND Strategic Surprise is High → Escalate for immediate cross-functional response planning.
    If Impact on Pricing Power is Medium AND Evidence Strength is Low → Schedule deeper verification for next cycle.
    If Archetype is "Defensive Hold" → Opportunity to double down on acquisition messaging against their vulnerabilities.
    04
    Internal Retrospective Worksheet
    Turn competitive losses and wins into institutional learning and process improvement.

    Internal Retrospective Worksheet

    Competitive intelligence is useless if it doesn't change internal behavior. This retrospective format focuses on specific deal outcomes (win/loss) to extract lessons about your product, positioning, and process. It connects external signals to internal performance gaps. The objective is not to assign blame for a single loss, but to identify patterns across multiple deals that indicate systemic weaknesses in your CI system or GTM execution. Regular retrospectives shift the culture from reactive defense to proactive learning.

    Analyzing real sales conversations is the highest-fidelity source of competitive insight. In one audit, reviewing 60 calls revealed 53-60% of sales effort was going to the lowest-ARPU segment, while higher-value segments were being neglected. This operational misalignment, driven by a lack of competitive clarity, was more damaging than any single feature gap.

    Deal Post-Mortem Structure

    Conduct this analysis for a sample of key lost deals and surprising wins each quarter. The goal is pattern recognition, not individual blame. Focus on the disconnect between the prospect's stated reason and your team's assessed root cause—this gap often reveals where your CI system failed. Capture at least three deals per quarter to build a meaningful dataset.

    Deal ID / Customer Name:
    Outcome: Win Loss
    Primary Competitor:
    Stated Reason for Decision (from prospect):
    Assessed Root Cause (team analysis - e.g., feature gap, pricing, champion departure):
    Was this cause known/anticipated by our CI system? Yes No
    If no, what signal did we miss?
    One process change to prevent similar surprises:

    Retrospective Scoring Dashboard

    Aggregate findings from multiple deal post-mortems to score your CI system's effectiveness and identify systemic weaknesses. This dashboard provides a quantitative basis for improving your CI operating system over time. Track these scores quarterly to measure progress in turning intelligence into better outcomes.

    Performance Dimension Scoring (1-5) Evidence / Note
    Signal Accuracy
    Were we aware of the competitor's relevant strengths?
    Internal Communication
    Did sales/GTM have the right counter-messaging?
    Product Readiness
    Did we have a viable answer to the competitor's offering?
    Process Follow-Through
    Were insights from past retrospectives acted upon?
    Quarterly Retrospective Actions:
  • Complete at least 3-5 deal post-mortems (mix of wins and losses).
  • Update the CI Tracking Template with any newly verified competitor capabilities.
  • Present one key finding and recommended action to the leadership team.
  • Update the Decision Log with any process changes decided.
  • 05
    Prioritization & Response Framework
    Systematically decide which competitive gaps to address, in what order, and with what resources.

    Prioritization & Response Framework

    You cannot respond to every competitor move. This framework uses a weighted score based on impact, urgency, and alignment with your strategy to separate must-do projects from distractions. It turns analysis into clear resource allocation decisions. The framework explicitly considers multiple response types, preventing a default bias toward the most expensive option: building. This systematic approach prevents feature factory mentality and aligns responses with business objectives.

    Response Option Matrix

    Not every competitive gap requires building a feature. Consider the full spectrum of response types before defaulting to a roadmap item. Each option has different resource requirements, speed of execution, and strategic implications. The matrix encourages creative, non-build solutions that can be deployed faster and with less cost.

    Counter-Message

    Adjust sales narrative, marketing content, or positioning to neutralize the competitor's claim. Low cost, fast.

    GTM

    Package & Price

    Re-tier features, adjust pricing, or offer a limited-time incentive. Impacts revenue operations.

    Sales

    Build

    Develop a new feature or enhance an existing one. High cost, slow, but creates lasting capability.

    Product

    Acquire / Partner

    Fill the gap through partnership, integration, or acquisition. Strategic, variable cost.

    Executive
    Feature parity is not the goal. In the healthcare SaaS case, a flagship integration was a deal-breaker for only 13% of the pipeline, yet consumed disproportionate engineering resources. Prioritize based on pipeline impact, not loudness. A disciplined scoring process surfaces these discrepancies and prevents overinvestment in low-impact responses.

    Prioritization Scorecard

    Score each identified competitive gap or opportunity. The highest-scoring items deserve resource allocation in the next planning cycle. This scorecard creates a transparent, debate-free method for ranking initiatives, moving discussions from "what should we do?" to "how did you score this dimension?" Use this during your Week 3 prioritization meeting.

    Competitive Gap Impact Score (1-5) Urgency Score (1-5) Strategic Fit (1-5) Total Recommended Response
    Missing enterprise audit logs 5 4 5 14 Build
    Competitor's lower entry price 3 5 2 10 Package & Price
    New marketing claim about speed 2 3 4 9 Counter-Message
    -
    Top Priority Gap for Next Quarter:
    Assigned Response Type:
    Owner (Role/Name):
    Success Metric (e.g., Win rate increase, Churn reduction):
    Target Completion Date:

    Scoring Guidance

    Impact (1-5): 1=Negligible effect on deals; 5=Deal-breaker for a core segment.
    Urgency (1-5): 1=Can address in 6+ months; 5=Losing deals this quarter.
    Strategic Fit (1-5): 1=Diverts from our roadmap; 5=Directly advances our declared strategy.

    Total score ≥12 indicates a "must-do" item. Scores ≤8 suggest "monitor" or "counter-message" responses.
    06
    Monthly CI Cadence Checklist
    The operational rhythm that turns intelligence from a project into a process.

    Monthly CI Cadence Checklist

    Consistency beats intensity. This checklist defines the minimal viable process for maintaining a competitive intelligence operating system. It assigns clear tasks to specific roles each week of the month, ensuring insights are gathered, analyzed, and socialized without fail. A predictable cadence prevents CI from becoming a reactive, crisis-driven activity and embeds it into the operational fabric of the company. The four-week cycle creates a continuous feedback loop between collection and action.

    The Four-Week Cadence

    Each week has a distinct focus, creating a continuous loop of collection, synthesis, decision, and communication. This rhythm ensures no single phase is neglected and that insights flow steadily from raw signals to executed decisions. Adherence to this cadence is the single biggest predictor of CI program success.

    1

    Week 1: Signal Collection & Triage

    Designated team members (e.g., sales, marketing, product) submit signals to the CI Tracking Template. The CI lead categorizes each using the Signal Categorization Guide. Output: a list of categorized signals for Week 2 analysis.

    2

    Week 2: Deep Dive & Analysis

    Analyze high-urgency signals using the Competitor Move Analysis Matrix. Update verification status and depth scores. Begin impact assessments. Output: completed analysis worksheets for top 2-3 moves.

    3

    Week 3: Prioritization & Planning

    Run the Prioritization & Response Framework for the top 3-5 gaps. Draft recommended actions and owners for the upcoming month/quarter. Output: a prioritized list with recommended responses and owners.

    4

    Week 4: Communication & Retrospective

    Share findings via the CI Report Template. Conduct a brief internal retrospective on the month's process. Prepare for the next cycle. Output: distributed one-page report and updated Decision Log.

    Assign the CI lead role on a rotating quarterly basis if needed, but ensure someone is explicitly responsible for driving the weekly cadence. Without an owner, the process decays within two months. The owner's primary accountability is to enforce the rhythm, not to do all the analysis single-handedly. Their leverage comes from coordinating inputs from sales, product, and marketing.

    Monthly Checklist

  • Collection: Capture at least 5 new competitive signals from varied sources (sales calls, review sites, product exploration).
  • Verification: Upgrade at least one signal from "rumor" or "claimed" to "verified" via documentation or live testing.
  • Analysis: Complete one Competitor Move Analysis Matrix for the most significant move observed.
  • Prioritization: Score and rank all active competitive gaps using the Prioritization Scorecard.
  • Communication: Distribute a one-page CI report to stakeholders (see Section 8).
  • Process: Review one past deal (win or loss) using the Internal Retrospective Worksheet.
  • Decision Log: Add at least one new CI-driven decision to the log with a clear hypothesis.
  • Role Weekly 1 Task Weekly 3 Task
    Sales Submit 2+ competitor mentions from calls. Review draft counter-messaging.
    Product Review one competitor's feature depth. Provide effort estimates for "Build" responses.
    Marketing Flag new positioning/messaging from competitors. Develop draft counter-narrative.
    CI Lead Triage all signals, update master template. Facilitate prioritization meeting, draft report.
    07
    Decision Log Template
    Document CI-driven decisions to create accountability and a historical record for future strategy.

    Decision Log Template

    Without a decision log, competitive intelligence becomes a discussion forum, not a driver of action. This template records what was decided, why, and what the expected outcome is. It creates a clear line from signal to resource commitment, and allows for later review of decision quality. The log serves as an institutional memory, preventing the same debates from recurring and enabling you to learn from past strategic choices. It is the mechanism that closes the loop between analysis and execution.

    Log Entry Structure

    Each entry should be concise but complete. The "Hypothesis" field is critical—it states what you believe will happen as a result of this decision, making it testable later. This transforms decisions from opaque judgments into falsifiable strategic bets. The hypothesis is the bridge between the CI analysis and the eventual retrospective review of outcomes.

    Date of Decision:
    Decision Title:
    Primary Competitive Signal/Trigger (link to CI Tracking ID if possible):
    Decision Made (e.g., Build X, Adjust price to Y, Launch campaign Z):
    Rationale (reference Impact/Urgency scores from Prioritization Framework):
    Hypothesis (Expected outcome/metric change):
    Owner:
    Target Completion Date:
    Status: Pending In Progress Complete Abandoned
    The log is a strategic asset, not an administrative task. Reviewing past decisions—especially those that failed—reveals biases in your response patterns (e.g., always choosing to build, always dismissing pricing threats). This meta-analysis of your decision-making is where the highest-order CI learning occurs. It shifts improvement from tactical responses to strategic judgment.

    Quarterly Decision Review

    At the end of each quarter, review completed decisions to assess accuracy and effectiveness. This closes the CI feedback loop. The goal is not to punish missed hypotheses, but to understand why the prediction was wrong and improve the scoring and analysis that led to the decision. This review should be a dedicated agenda item in your quarterly planning.

    Decision Title Hypothesis Result Learning
    Launch Basic Audit Logs Reduce enterprise deal losses by 15%. Met Partial Missed2
    Adjust Starter Plan Price Increase conversion by 5% without hurting ARPU. Met Partial Missed
    Met Partial Missed

    Maintaining the Log

    The CI lead owns the decision log. New entries are added during the Week 3 prioritization meeting. Status is updated in Week 1 of each month. The quarterly review is a dedicated agenda item in the first month of each new quarter. This integration with the monthly cadence ensures the log remains a living document. The log should be stored in a shared, searchable location accessible to the leadership team.

    Target: At least one new CI-driven decision logged per month.
    08
    CI Report Template
    Communicate key findings, decisions, and actions to stakeholders in a single, scannable page.

    CI Report Template

    The final output of the monthly cadence is a concise report that informs stakeholders and drives alignment. This template is designed for a 5-minute read. It highlights what changed, what it means, and what we're doing about it. It turns intelligence into organizational awareness. The report's primary function is to create shared context and secure commitment for recommended actions, not to showcase the depth of your analysis. Its brevity forces distillation of complex analysis into actionable insights.

    Competitive Intelligence Report
    [Month, Year] | Prepared by [CI Lead Name]
    Executive Summary (2-3 sentences)
    Top Signal This Month
    Competitive Moves & Analysis (Bulleted list)
    Prioritized Gaps & Actions
    Gap Priority Action Owner
    High
    Medium
    Low
    Key Decision / Recommendation for Leadership
    Metrics to Watch Next Month
    Distribute this report on the last Friday of every month without fail. Consistency builds trust and ensures competitive insights remain a regular input for all functions, not a sporadic crisis briefing. The predictable rhythm of the report signals that CI is a core business process. Use the same format each month to reduce cognitive load for readers and make trends easier to spot over time.

    Report Dissemination Checklist

  • Report is a single page (PDF or shared doc).
  • Sent to: Executive Team, Product Leadership, Sales Leadership, Marketing Leadership.
  • Presented verbally in the first 10 minutes of the monthly leadership meeting.
  • Archived in a shared "CI Reports" folder for historical reference.
  • Any "High" priority action from the report is added to the next leadership meeting agenda for resource commitment.
  • Include a link to the underlying Decision Log entry for any new decisions.
  • Driving Action from the Report

    The report's purpose is to create decisions, not awareness. The "Key Decision / Recommendation" box must contain a specific, actionable ask for leadership (e.g., "Approve budget for Q3 to build feature X," "Change sales compensation to incentivize segment Y"). A vague recommendation is a failed output. Tie every insight to a concrete next step. This turns the report from an information document into a decision-support tool.

    Success metric: At least one recommendation from the monthly report leads to a documented decision in the log.

    About the Author

    Jake McMahon
    B2B SaaS Product Strategist

    Jake has spent 8+ years helping B2B SaaS companies turn product data into strategic decisions. With a background in Behavioural Psychology and Big Data, he specialises in competitive intelligence, product-led growth assessment, and pricing architecture. He has conducted over 200 product analyses across vertical SaaS, developer tools, and enterprise platforms — identifying the patterns that separate market leaders from the rest.

    productquant.dev