The takeaway
Competitive intelligence in the deal, not only in the wiki - a buyer guide for enterprise GTM teams. Competitive intelligence teams are often busy in the ways that look productive. Long battlecards. Quarterly readouts. Win-loss notes in a folder with a careful name. Then a rep hits a trap question on a Wednesday call and improvises.
Product marketing, enablement, and sales leaders who need approved competitive stances to show up in live opportunities, not only in a portal.
Beautiful wikis nobody opens; AI-generated takedowns; battlecards that disagree with what proposals say.
Opportunity-triggered delivery; approval and retirement on claims; use in real deals; the same stance in questionnaires and decks.
Deliver approved knowledge into rep workflows and formal responses so competitive claims stay consistent across the deal.
Competitive intelligence teams are often busy in the ways that look productive. Long battlecards. Quarterly readouts. Win-loss notes in a folder with a careful name. Then a rep hits a trap question on a Wednesday call and improvises.
The CI function looks healthy. The deal still runs on memory. A wiki that never reaches the opportunity is research. It is not enablement. Buyers do not care how complete your portal is if the person on the call invents a sharper line than product will stand behind next month.
Where CI usually dies
The card is too long to use under pressure. The portal is three clicks from the CRM. Claims go stale after a competitor launch and still rank first because nobody retired them. Sales and proposals keep slightly different “truths.” Feedback from the field lands in a side channel and never upgrades the card the same week.
You can see the failure mode without a dashboard. The SE whispers a safer answer after the call. The proposal team softens a claim that a rep already used live. Legal finds a comparison they never approved. Everyone works hard. The company still has three competitive stories.
The wiki can still look excellent while this happens. Search works. Tags are clean. The last quarterly refresh has a date stamp. None of that helps the rep who has eight seconds before the buyer expects a confident answer. Under pressure, people use what is nearest. If nearest is memory, memory wins.
None of that is fixed by another all-hands deck. It is fixed by treating competitive claims like any other high-risk answer: owned, approved, delivered, and retired on purpose. If retirement is slower than competitor packaging, your “current” card is a liability with good formatting.
What “in the deal” actually means
It means the competitor name on the opportunity surfaces the current approved stance without a scavenger hunt. Claims stay inside what product and legal allow, not warrior mythology from a loud deal three quarters ago. Proof points and landmines are short enough to use live. After the call, what was said can be checked against the approved line. Repeating traps become promoted answers, not one-off chat threads that die in a private channel.
In practice that looks simple. Open the opportunity. See the competitor. Open a two-minute card with the three claims you may make, the two you must not make, and one proof link an SE can open if the buyer pushes. If the card takes longer to find than the trap question takes to land, the design failed.
Picture a real Wednesday. The buyer names a competitor mid-demo. The rep does not open a thirty-page PDF. They open a short card that already knows this opportunity is competitive, shows the approved contrast in plain language, and flags the landmine legal will not allow. The SE can deepen if needed. The proposal team will not rewrite a different story two weeks later because the same object feeds both paths.
That is the bar. Not “we have CI.” Not “we published a battlecard.” Reachable, owned, short enough for the call, deep enough for the SE, and identical when the same question shows up in a portal.
If a stance cannot be retrieved in the flow of the opportunity, it does not exist for revenue. That sentence is uncomfortable. It is also how you stop paying for CI theater. Budget for research without delivery is how you get elegant PDFs and the same improvisation on Friday. When leadership asks whether CI is working, answer with deal moments, not publish counts.
A practical stack
Build the stack around the deal path, not around a content calendar.
Inputs. Win-loss, call moments, public competitor changes, product truth, marketing claims, and security differentiators that are actually true, not the ones that only sound good in a brainstorm. Prefer primary sources you can defend. A polished slide with no owner is not an input. It is decoration. Capture the trap question in the buyer’s words when you can. That wording is what the next rep will hear.
Control. Approval state on what sales may say. Retirement when product reality or competitor packaging moves. Legal review on high-risk comparisons. Shadow decks are not a strategy. They are future RFP landmines. When two teams keep “their” version, the buyer will eventually hold both versions in the same week. One object with an owner beats five clever variants.
Delivery. CRM, chat, and meeting prep, not only a portal. Short form for live use; deeper proof one click away for SE support. Two minutes to scan should be the design target for the live card. If delivery only works for people who already know where the wiki lives, you have not delivered. You have archived. Opportunity context should reduce search, not add another place to remember.
Loop. Field feedback upgrades the card the same week when it can. If the field is a dead-letter inbox, the wiki will rot no matter how pretty the template is. A single trap that shows up three times in a month should force a promotion decision: approve a stance, retire a bad line, or escalate to product. Silence is a decision too. It is just the worst one.
When the stack is healthy, a competitor change triggers retirement and a new approved line before the next wave of demos. When the stack is sick, the old claim keeps winning search because it has more links pointing at it. Design for the first outcome on purpose.
How CI connects to proposals
Buyers ask the same competitive questions in RFPs that they ask on calls. If the proposal library and the battlecard disagree, you taught the buyer to distrust both. Promote one governed stance and reuse it. The person answering a portal row at 11pm should not invent a fourth version because chat was faster than the card.
AI that drafts competitive language should only draft from approved sources. Generative trash talk is a brand and legal risk with a smile. Fluency is not a license. If the model can write a sharper attack than your approval state allows, the failure is governance, not “the model being creative.”
Treat competitive language like security language: same object, same owner, same retirement path, whether it appears in a call, a deck, or a questionnaire. When those channels diverge, buyers notice even when nobody on your side meant to invent anything.
Metrics that matter
Count opportunities where the relevant card was opened or delivered in-workflow. Count trap questions that still escalate after a card exists. Measure time from a competitor change to retirement of the old stance. Spot-check consistency between call notes and proposal language on a small sample every month.
Do not confuse homepage page views on a wiki with revenue impact. Views without use are a vanity metric with a content team attached. A card that is opened before every competitive stage advance is worth more than a beautiful page that only enablement visits during cleanup week.
When a metric improves, name the behavior that moved. “More card opens in CRM before competitive demos” is a real signal. “We published twelve new pages” is not, unless those pages changed what reps say under pressure.
Why Tribble
Tribble helps put approved knowledge into rep workflows and formal responses so competitive claims stay consistent across the deal. Treat CI content as governed answers, not orphan PDFs.
When you evaluate CI or enablement tools, ask a simple question: is the stance reachable in the moment, with an owner behind it, and can the same stance draft a proposal row without a second invention? If the answer is no, you still have a wiki problem wearing new software.
Clari’s public path shows what happens when answers finally have a home across the tools people already live in. UiPath’s public scale story is the other side of the same coin: many people getting trustworthy answers in the flow of work, not only in a library. Competitive claims deserve that same standard. A stance that only lives in a portal will lose to whatever is easiest in the moment.
FAQ
How long should a live battlecard be?
Short enough to scan in under two minutes, with links to deeper proof for SE support. Length is not rigor.
Who owns competitor claims?
Product and marketing jointly own truth. Sales leadership enforces use. Legal reviews high-risk comparisons. If ownership is “everyone,” it is no one.
Should AI generate competitive takedowns?
Only from approved sources, and only inside the claims you are willing to stand behind later. Ungoverned generation creates sentences you will spend legal time unwinding.
How often should cards refresh?
On material competitor or product change, not only on a quarterly calendar. Retirement speed matters more than publish ceremony.
What if sales wants sharper language than legal allows?
Coach with the approved edge. Do not run a shadow deck. Shadow decks become RFP landmines and broken trust inside the company.
How do we know CI is working in live deals?
Look for card delivery in the opportunity path, fewer trap escalations on known competitors, and matching language between calls and proposals. If those stay flat, the wiki is still the product.
What to do with your top competitors this month
Pick your top three competitors by open pipeline. For each, ship a two-minute live card into CRM or chat with an owner and an approval date. Track whether trap escalations drop over the next twenty opportunities. Expand only after delivery works. If the card is not opened when the competitor is on the opportunity, fix delivery before you write more pages.