The Competitive Intelligence Playbook

Competitive intelligence usually dies as a slide deck nobody opens or a flood of competitor news nobody can use in a live call. This is a plug-and-play workflow that turns competitor moves into living battlecards and rep-ready talk tracks — built from signals you can watch for free, with Claude doing the synthesis. Apollo, Google Sheets, and Claude. The prompts and the steps are below.

Competitive intelligence fails two ways. The first is the static battlecard: built once in a big effort, accurate for a quarter, quietly wrong forever after. The second is the firehose: a Slack channel of competitor news that nobody turns into something a rep can actually say when a prospect brings up the other logo. Both leave your team improvising in the exact moment a deal is won or lost.

Good CI is not a document, it is a standing process that converts signals into decision-ready assets: what changed, why it matters, and what to say. And the moment that matters most — honesty — is also where most battlecards go wrong.

What to buy, what to build

Stage 1 — Pick the competitive set

Watch the competitors who actually show up in your deals, not every logo in the category. Three to seven is right; more than that and nothing gets watched well.

1. List the competitors that appear in real deals — pull them from won/lost notes in your CRM, not from an analyst's quadrant.
2. For each, set the sources you will watch: their pricing page, changelog or product blog, job board, G2 page, news, and LinkedIn.
3. Stand up two tabs: competitors (name, category, sources, card_built_date) and signals (competitor, signal_date, signal_type, source, detail).

Stage 2 — Monitor the signals

Most of a competitor's strategy is public if you know where to look. Watch for the moves that change a deal:

1. Pricing & packaging. A new tier, a price change, a repackage — it shifts every deal you are both in.
2. Product & changelog. What they shipped tells you where they are investing; what they have not shipped is your opening.
3. Hiring. Their open roles are their roadmap leaking — a wave of AI or enterprise hires says where they are headed.
4. Positioning & messaging. Homepage and category-page language shifts signal who they are now chasing.
5. Reviews & funding. G2 themes reveal real strengths and sore spots; a raise becomes a bigger sales team within two quarters.

Stage 3 — Synthesize the change

Raw signals are not intelligence until someone says what they mean. Let Claude turn a competitor's recent signals into a brief a GTM leader can act on — what changed, why it matters, what to do.

You are a competitive intelligence analyst. I will paste recent raw signals about one competitor. Turn them into a decision-ready brief.

Return three short sections, plain text:

WHAT CHANGED
- 2-4 bullets, only material changes (pricing, packaging, positioning, product, funding, leadership, a notable win or loss). Ignore noise. Note the date of each.

WHY IT MATTERS TO US
- 2-3 bullets on the implication for our deals and positioning. Be specific about which segments or deal types this affects.

RECOMMENDED RESPONSE
- 2-3 concrete actions: a messaging adjustment, a battlecard update, a play to run. No vague advice.

Ground every point in the signals provided. Treat anything older than 90 days as context, not news. Invent nothing.

Competitor: [COMPETITOR NAME]
Signals, tab-separated: signal_date  signal_type  source  detail

Rows:
[PASTE SIGNALS]

Stage 4 — Build the battlecard

The battlecard is the asset reps actually use. This prompt is built around honesty on purpose: it forces an acknowledgement of where the competitor is strong, because a card that pretends otherwise gets a rep caught and loses trust in the room.

You are building an honest competitive battlecard for our sales team. Honesty wins: acknowledge the competitor's real strengths and beat them on true differentiation, not FUD. A rep who overstates gets caught and loses the deal.

Return a one-page battlecard in these sections:

POSITIONING - how they describe themselves, in one or two sentences.
WHERE THEY ARE GENUINELY STRONG - 2-3 honest points. Do not minimize these.
WHERE WE WIN - 2-3 points of real, defensible differentiation, each tied to a buyer outcome.
LANDMINES - account types or situations where we should not compete, or should compete carefully.
OBJECTION HANDLING - the 2-3 objections a rep hears when this competitor is in the deal, each with a true, non-defensive response.
DISCOVERY QUESTIONS - 3 questions that surface where we are stronger, without naming or disparaging the competitor.

Use only the inputs provided plus our positioning. Do not fabricate features or claims.

Competitor: [COMPETITOR NAME]
Their positioning and known facts: [PASTE FROM THE SYNTHESIS BRIEF]
Our positioning and differentiation: [PASTE YOUR OWN POSITIONING]

Stage 5 — Arm the team

A battlecard is reference; a talk track is what a rep says. Turn the card into responses organized by who is in the room, using the same segments from the rest of the series — the CFO's concern about this competitor is not the CRO's.

You are turning a battlecard into rep-ready talk tracks for live calls, organized by who is in the room.

For each relevant buyer segment, return:
SEGMENT
- the one concern this buyer has when the competitor is in the deal
- a two-sentence talk track that addresses it honestly, then pivots to our strength
- one trap-setting discovery question

Segments to consider (include only those relevant to the deal):
GTM Ops Leaders | Sales Leadership | Marketing Leadership | Client Success | Finance & Founder

Keep every talk track honest and specific. No disparagement, no absolute claims. Ground it in the battlecard.

Battlecard: [PASTE THE BATTLECARD]
Buyers in this deal: [LIST TITLES OR SEGMENTS]

Keep the cards fresh

A stale battlecard is worse than none — it is confidently wrong. The whole point of building CI as a process is that it updates itself when the competitor moves.

1. Manual, free. Each week, scan the sources, log new signals, and re-run synthesis. Regenerate a battlecard only when a material change fires — not on a calendar.
2. Scheduled, with the API. An Apps Script trigger checks the sources, writes new signals, and flags any battlecard a newer signal has outdated, so you regenerate exactly the cards that need it.

// Flag battlecards a newer signal has outdated.
// battlecards tab: competitor in A, card_built_date in B.
// signals tab: competitor in A, signal_date in B.
=IF( MAXIFS(signals!$B:$B, signals!$A:$A, A2) > B2, "REFRESH - new signal", "current" )

// Days since the card was last built
=TODAY() - B2

What good looks like

• A live battlecard for every competitor that actually shows up in deals — and none for those that do not.
• Each card is honest about where the competitor is strong; you win on true differentiation, not FUD.
• Every claim on a card traces to a dated signal, not a hunch.
• Cards refresh on change, not on a quarterly calendar — a new signal flags the card for an update.
• Reps have talk tracks by buyer segment, not just a feature grid.
• Win/loss notes feed back into the signals tab, so the cards learn from real deals.

Competitive intelligence is not a binder, it is a living system that turns a competitor's public moves into the words your team uses in the next call. Watch a tight set, synthesize honestly, arm the team by buyer, and refresh on change — and your reps stop improvising in the moment that decides the deal.