A compete program is the connective tissue between knowing what competitors are doing and actually winning against them. Where ad-hoc competitive research produces the occasional deck, a compete program is a standing function (usually anchored in product marketing) with named owners, defined competitor tiers, recurring deliverables, and channels that put insight in front of sellers, product managers, and executives at the moment they need it.
The term took hold in the SaaS world, where crowded categories mean most deals are competitive and the cost of a stale battlecard is a lost deal. A compete program typically spans three kinds of work: gathering and analyzing competitor signals, packaging them into enablement content such as battlecards and talk tracks, and distributing intelligence through the channels the company already lives in: Slack, the CRM, sales onboarding, executive briefings.
Done well, the program creates a loop rather than a library. Field teams feed back what competitors are saying in deals, analysts confirm or refute it against observable evidence, and updated guidance flows back out. Companies that formalize this loop respond to competitor moves in days instead of quarters, and they stop relying on tribal knowledge that walks out the door when a tenured seller leaves.
The three pillars: intelligence, enablement, distribution
The intelligence pillar covers collection and analysis: monitoring competitor websites, pricing pages, release notes, job postings, and review sites, then turning raw changes into implications. The enablement pillar converts those implications into assets sellers can use under pressure (battlecards, objection-handling guides, demo counters, trap-setting questions) which is where a compete program overlaps with competitive enablement. The distribution pillar is the least glamorous and the most decisive: intelligence that sits in a wiki nobody opens might as well not exist, so mature programs push updates into Slack channels, CRM records, weekly digests, and onboarding curricula. Weak programs usually fail at the third pillar, not the first: they collect plenty and deliver little.
Compete program vs. CI program
The two terms describe largely the same organizational animal, and many companies use them interchangeably. The nuance is emphasis. A CI program borrows its framing from the traditional competitive intelligence discipline and foregrounds analysis: structured collection, prioritized intelligence topics, and briefings for strategic decision-makers. A compete program is the phrasing that grew up in SaaS and product marketing circles, and it foregrounds revenue outcomes: helping sales win head-to-head deals through battlecards, talk tracks, and rapid response to competitor moves. In practice a healthy program does both, and the label mostly signals who sponsors it: a compete program usually reports into marketing or revenue leadership, while a CI function may sit closer to strategy or corporate development.
Standing one up: from tribal knowledge to a working program
Most programs begin as tribal knowledge: a few sellers who know the top rival cold, a product manager with a spreadsheet of feature gaps. Formalizing that starts small. Name a single owner, even at half capacity, and have them tier the competitive landscape so effort concentrates on the two or three rivals that actually appear in deals. Define the questions stakeholders most need answered, ship one battlecard for the most-contested competitor, and revise it against feedback from live deals before writing the next. Automated website and pricing monitoring comes early, because it removes the manual checking that would otherwise consume the owner's week. The classic failure mode is boiling the ocean: launching twenty battlecards that are all stale within a quarter.
Measuring whether the program is working
The headline metric is competitive win rate (the percentage of closed deals won when a specific competitor was present) tracked per rival and over time. Around it sit leading indicators: how often enablement content is viewed or attached to opportunities, how quickly the program publishes guidance after a competitor move, and how many field submissions flow in, which measures whether sellers trust the program enough to feed it. Attribution deserves honesty: win rates move for many reasons, so treat the metric as directional evidence rather than proof. Qualitative signals matter too: when account executives cite the battlecard in deal reviews unprompted, the program is working; when they quietly build their own slides, it is not.