Measuring CI When You Can't Attribute the Win
Attribution is the fight competitive intelligence always loses. Measure what you can control instead: how early you knew, how rarely you were surprised, and whether your hit rate moved where you aimed.
Why attribution fails in CI
An industrial deal is decided by more factors than any single function can see. Price, specification fit, relationship history, delivery risk, financing, timing. When the deal closes, every function assembles a story in which it mattered, and intelligence is one voice among many. The louder voice usually wins the story, not the true one.
Cycle length makes it worse. A competitor move you flagged in spring shapes a negotiation the following year. By the time the deal closes, the organization has rewritten its memory of what it knew and when. The warning that feels obvious in hindsight was not obvious when it was sent, and nobody kept the receipts.
Then there is the missing control group. You never get to watch the parallel quarter in which your team saw nothing. Without that counterfactual, attributing a win to intelligence, or a loss to its absence, is a guess dressed up as analysis. Finance knows this, which is why the attribution argument dies the moment a CFO looks at it.
The practical consequence is simple: tie your program to attributed wins and you hand the program to luck. One quarter of unrelated losses makes the function look useless. One lucky win makes it look brilliant. Neither reading tells you whether the intelligence capability is actually improving, which is the only question a metric should answer.
Three leading indicators you can control
All three share one property: they measure the machinery of the program, not the outcome of individual deals. Each needs a definition, a collection habit, a unit, and a cadence. Each also has a failure mode in which the team quietly fools itself.
- Decision lead time. Definition: the number of days from the first appearance of a signal to the moment the company makes a decision that references it. Collect it by timestamping two events: when the signal entered any channel, and when a decision document first cites it. Report the median, monthly, per competitor or per topic. Median, not average, because one stale signal can drag an average forever. The self-deception risk is backdating: if the first sighting gets recorded after the decision, you are measuring your filing discipline, not your speed.
- Surprises per quarter. Definition: the count of significant competitor moves that surfaced this quarter with no prior written warning in any of your channels. Freeze the definition of significant before the quarter starts, or you will negotiate it afterward. A warning counts only if it was written down and circulated; a hallway mention is not a warning. The self-deception risk is reclassification: teams quietly move last quarter's surprises into the expected column, or claim a vague six-month-old note as coverage.
- Quote hit rate, segmented. Definition: win rate on quotes where a named competitor was present, tracked per competitor rather than overall. The overall rate moves with deal mix and market conditions, which makes it useless for judging CI. The segmented rate tells you whether intelligence changes outcomes exactly where it is aimed. Sales tags each closed quote with the competitors involved; you report quarterly. The self-deception risk is small samples: print the quote count next to the rate, so a two-quote swing does not get read as a trend.
Notice what these measure: how early, how rarely blind, and whether aim converts. None of them requires anyone to believe a story about a single deal.
The one-page scorecard
One page, monthly, four blocks. Channel output: valid signals per channel this month, where valid means the signal passed your noise filter, not that it was interesting. Lead time: the median from indicator one. Surprises: the running count for the current quarter. Hit rate: the segmented table from sales operations.
Divide the filling by ownership. The CI lead owns channel output and lead time, because those come from the signal log. Sales operations owns the segmented hit rate, because it comes from the CRM. Leadership owns the surprise count, because a surprise is only real when the people who were surprised say so at the quarterly review.
Resist expansion. The page works because it fits into a monthly meeting without preparation. The moment it grows into a deck, it becomes a quarterly ritual, and the cadence that makes it useful is gone.
| Metric | Definition | How to collect | What it does not prove |
|---|---|---|---|
| Channel output | Valid signals per channel per month | Signal log tagged by channel | That anyone used the signals |
| Decision lead time | Median days from first sighting to decision | Timestamps in the log plus decision documents | That the decision was right |
| Surprises per quarter | Significant moves with no prior written warning | Frozen significance list plus quarterly review | That you saw everything |
| Segmented hit rate | Win rate by named competitor | CRM tagging at quote close | That CI caused the change |
That last column is the spine of the whole instrument. Every metric on the page earns its place by being honest about what it cannot show. A scorecard that admits its limits survives audit; one that implies causation does not.
Presenting it without overclaiming
The scorecard lets you say we were earlier, and mean it. That is a stronger claim than it sounds, because it is checkable against the log. What you cannot say is that the program produced revenue. Nobody can run that experiment, and pretending otherwise is how programs lose credibility the first time a deal goes wrong.
Three phrasings that hold up under questioning:
- Our median time from first signal to decision fell from months to weeks across the last two quarters.
- One significant competitor move reached us without warning this quarter, down from three the quarter before.
- Against the two competitors we actively track, quote hit rate moved; the overall rate did not, which is what aim looks like.
Three phrasings to retire:
- CI contributed this much revenue. Unprovable, and finance knows it.
- We won this deal because of intelligence. The rep, the price, and the spec all claim the same deal with better stories.
- The program pays for itself. Maybe it does. You cannot demonstrate it, and claiming it invites the one audit you will lose.
The paradox works in your favor. The programs that survive budget reviews are the ones that underclaim. A scorecard built on leading indicators survives scrutiny precisely because it only claims what it measured, and that restraint is what buys the program another year.
Measure lead time, not luck.
For the budget conversation that follows this argument, read our guide to justifying a CI budget. For getting signals to decision-makers, see our piece on CI digest design.
Get in touch