CI Program Maturity Model

What it is

A staged model for diagnosing how mature a company's competitive intelligence (CI) function actually is, the direct structural sibling of the Sales Enablement Maturity Model (Category 9) applied to the CI discipline rather than enablement. Klue, a competitive-enablement software vendor, published a five-stage version, the Competitive Enablement Maturity Model, developed with the Strategic and Competitive Intelligence Professionals association (SCIP) from its 2021 Competitive Enablement Report survey data: Ad Hoc (competitor knowledge lives in individual heads, no shared repository, no owner), Adopting (a named function exists and first attempts at battlecards and a shared repository appear, but intel is scattered across Slack, email, and shared drives), Impacting (structured processes and a dedicated CI tool are in place, with the first real cross-functional distribution to sales), Influencing (CI findings demonstrably shape roadmap, positioning, and go-to-market decisions, not just sales collateral), and Transforming (CI is embedded across the company as a continuously measured system with executive visibility). A separate academic systematic review (see Sources) surveyed fourteen distinct published CI maturity models and found consistent convergence around the same underlying dimensions, evidence this is a genuinely converged practice rather than one vendor's invention. This entry adapts that research tradition into a distinct model for this knowledge base rather than reproducing Klue's stage names verbatim, in the same spirit as this knowledge base's existing Forrester Customer Advocacy Model.

When to use it

• You are inheriting a CI function, or building one from scratch, with no clear picture of what exists. A fast, honest diagnosis beats guessing from whatever battlecard was most recently updated.
• Sales reports that competitive intel is stale, hard to find, or contradicts what they hear live in deals. This is almost always a symptom of a function stuck at Ad Hoc or Adopting, not a research-quality problem alone.
• Leadership asks why the company isn't in a specific analyst report, or seems consistently surprised by a competitor's move. Both are classic Ad Hoc-to-Adopting symptoms: no systematic monitoring, no distribution loop.
• You have built strong point-in-time artefacts (a battlecard, a perceptual map) but they decay within a quarter. As with the Sales Enablement Maturity Model, that decay usually points to a stage gap in ownership or tooling, not an asset-quality gap.
• You need a business case for CI headcount or a dedicated competitive-intelligence platform. A scored stage and a named target give leadership a concrete "what this actually costs to fix" ask instead of an unscored list of requests.

Ownership

At a scaled company with a dedicated Competitive Intelligence Manager or a Head of Competitive Intelligence, that role owns the scoring exercise and the target-stage decision, with the Head of Product Marketing signing off since CI findings feed directly into positioning and battlecards. At a solo or founding-PMM stage, competitive intelligence usually has no dedicated owner at all, and the founding PMM runs the scoring, the interviews, and the target-setting alone, since there is no separate CI role to hand any of it to.

How to read it

Read the five stages as a ladder across four dimensions that must each clear a bar before a team can honestly claim the next stage. Repository and process: Ad Hoc has no shared location, Adopting has a first shared drive or Slack channel with no structure, Impacting has a dedicated CI tool with a defined intake process, Influencing has that process feeding a documented cadence of deliverables, Transforming has the process embedded in company-wide planning rituals. Distribution to sales: Ad Hoc is nothing beyond word of mouth, Adopting is a first static battlecard or deck, Impacting is regular, versioned battlecards distributed through a tool reps actually use, Influencing ties distribution to measured usage, Transforming ties usage to deal outcomes. Cross-functional reach: Ad Hoc is CI talking to itself, Adopting reaches sales only, Impacting reaches sales and marketing, Influencing reaches product and executive planning, Transforming is a standing input to strategic decisions across the company. Measurement: Ad Hoc tracks nothing, Adopting tracks anecdote, Impacting tracks content usage, Influencing ties usage to win rate, Transforming reports CI's revenue impact as a standing metric. A function is rarely at the same stage across all four dimensions at once; the gap between them is usually the real finding.

How to apply it

1. Score each of the four dimensions honestly and separately, resisting a single blended score; a function can be Impacting on repository and process while still Ad Hoc on cross-functional reach, and averaging hides exactly the gap worth fixing.
2. Interview a sample of the sales reps and product managers who should be consuming CI output, not just whoever runs the function. Ask what they actually use in a live deal or planning cycle, and what they have built themselves because nothing existed; consumer behaviour is the real signal, not the CI team's own inventory count.
3. Identify the lowest-scoring dimension as the priority, not the lowest-scoring stage overall. A function stuck at Ad Hoc on measurement while Impacting everywhere else should instrument next, not produce more battlecards that will only compound the same measurement gap.
4. Set a realistic target, one stage forward on the priority dimension, for the next two quarters, rather than "Transforming" as an immediate goal.
5. Name an owner and a review cadence for the dimension being advanced, since ownership and cadence are themselves stage-defining criteria; a plan with no named owner cannot progress past Ad Hoc on repository and process, however much research exists.
6. Re-score quarterly against the same four dimensions, tracking movement rather than activity; a quarter of heavy research output that does not move the distribution or measurement score has not actually advanced the function's stage.
7. Use the resulting stage and specific dimension gaps as the business case for the next CI investment, the same pattern the Sales Enablement Maturity Model uses: a scored gap and its cost to close is a stronger ask than an unscored tooling wishlist.