“You learned about your competitor's launch from the deal your team just lost.”

The struggle

The deal review is where it lands. Someone says the prospect went with Acme because of a feature you didn’t know existed, and everyone turns to you. You open Acme’s site for the first time in six weeks and there it is — shipped, on the pricing page, with a launch post from eleven days ago. Now you spend the rest of the afternoon reconstructing what changed, fielding “so what do I say to my pipeline?” in Slack, and quietly wondering what else you’ve missed. That afternoon costs about four hours, and you’ll pay it again next quarter, because nothing you learned got written down anywhere durable.

The obvious fix — “I’ll check their changelogs every Monday” — dies in week three. Not because you’re lazy, but because a manual sweep across five competitors is 45 minutes of tab-opening for an output that usually reads “nothing much changed,” and nobody sustains a 45-minute ritual with a mostly-empty result. So the habit lapses, and the intelligence arrives the expensive way: from a lost deal. This playbook makes the sweep cheap enough to survive a bad week — a saved prompt, a diff instead of a rewrite, and a battlecard that lives where sales already looks.

The chain

Step 1 — Save one sweep prompt you never rewrite · Perplexity

Create a Space (or just a pinned thread) for competitive sweeps and paste this prompt in once. Every Monday you change the date and the competitor names stay put. Perplexity is the right first link because it searches live and returns sources inline; the prompt guide is blunt that specificity in the query is what improves retrieval, which is why this prompt names categories instead of asking “what’s new with Acme”.

Weekly competitive sweep. Today is <YYYY-MM-DD>. Window: the last 7 days ONLY.
Competitors: <Acme>, <Bolt>, <Cirrus>.

For EACH competitor, report these four categories in this order:
1. Changelog / release-notes entries
2. Pricing or packaging page changes (tiers, prices, limits, add-ons, trials)
3. Product launches or public announcements
4. Funding, acquisition, or leadership changes

Rules:
- Every claim needs a source URL on the same line as the claim. No link, no claim.
- If a category has nothing, write exactly: "No change found — checked <the
  specific pages/sources you checked>." Do NOT pad the section with older news,
  company background, or general commentary to make it look complete.
- Do not describe marketing copy as a shipped feature. If something is a
  waitlist, private beta, or "coming soon", label it that way in the line.
- Anything you cannot date inside the last 7 days goes at the very end, under
  "Older or undated" — not in the per-competitor sections.
- No summary, no analysis, no recommendations. Findings only.

The two load-bearing rules are the source link and the mandatory “no change found” line. Without the first, you get plausible launches that never happened. Without the second, a model with nothing to report will invent something to report — a quiet week reads as suspicious to a text generator, so you have to make “quiet” an acceptable answer.

When to skip Perplexity: if you only track one competitor, RSS on their changelog plus a Google Alert is free and better. And for traffic or market-share trends rather than announcements, Similarweb answers a different question than any search tool will.

Step 2 — Diff, don’t rewrite · ChatGPT

Any frontier model runs this step. Claude and Gemini do this job as well as ChatGPT does; the prompt is plain text in, text out. We name ChatGPT because it’s the one most PMs already have (see last field-tested above) — not because it’s required. Use whichever you already pay for.

Paste last week’s battlecard and this week’s raw sweep into one ChatGPT conversation. You are not asking for a summary — you’re asking what changed, which is the only part you have to read.

You maintain a competitive battlecard. Two documents follow:
A) LAST WEEK'S BATTLECARD
B) THIS WEEK'S RAW SWEEP (claims, each with a source URL)

Output ONLY the delta, in these five sections:

1. NEW — present in B, absent from A. One line each, with the source URL.
2. CHANGED — contradicts or updates a line in A. Quote A's old line verbatim,
   then the new line, then the source URL.
3. STALE — lines in A that B suggests are now out of date. Say which line and why.
4. NO CHANGE — name every competitor with nothing new this week, one line each.
   I want to see this stated, not infer it from silence.
5. SALES LINE — one sentence, max 25 words, the single most deal-relevant item
   this week, in language a salesperson can say out loud. If nothing this week
   is deal-relevant, write "Nothing sales-relevant this week."

Hard rules:
- Tag every claim [STATED] if the source says it plainly, or [INFERRED] if you
  concluded it. Every [INFERRED] claim must carry your reasoning in brackets.
- Use only what is in B. No outside knowledge, no filling gaps, no guessing at
  a competitor's motive or roadmap.
- Do not restate A. If a section is empty, write "None."
- Do not rewrite the battlecard. Delta only.

A) LAST WEEK'S BATTLECARD:
"""
<paste>
"""

B) THIS WEEK'S RAW SWEEP:
"""
<paste step 1 output>
"""

The [STATED] / [INFERRED] tag is what makes this reviewable in ten minutes. “Acme raised prices 20%” and “Acme is moving upmarket” are different kinds of sentence, and only one of them survives a sales rep repeating it to a prospect. Building the battlecard for the first time is a separate job — build a competitor battlecard is the one-off prompt for that, and positioning one-pager from competitor sites covers the quarterly version where you rethink the framing rather than track the changes.

Step 3 — Put the battlecard where sales already looks · Notion AI

One page per competitor, one shared parent page, in the workspace your go-to-market team already has open. Apply the delta by hand or have Notion AI fold it into the existing structure so the card keeps one voice instead of accreting five weeks of paste jobs. Keep a dated “changed this week” line at the top of each card — that line is what a rep reads before a call, and it’s the only part they’ll read.

Honest trade-off: Notion AI is the smallest link in this chain. What matters is location, not the AI — a battlecard in Confluence, Google Docs, or your CRM works identically if that’s where sales lives. A beautifully maintained card in a tool only PMs open is worse than a scruffy one in the sales channel.

Step 4 — The human check: verify, then tell one person

Two things only you can do. First, open the source link for every claim you’re about to put in front of sales. Anything tagged [INFERRED], anything about pricing, and anything that sounds like a big launch gets clicked — that’s about five minutes and it’s the difference between intelligence and rumor. Second, post the sales line in the channel where reps actually talk, tagged to the competitor, with the link. One line, every week, including the weeks when it says “nothing sales-relevant.”

That last habit is the whole point. A battlecard that updates silently is a file. A weekly line in a channel is a signal reps come to expect — and intel nobody reads is worth exactly zero, no matter how accurate it is.

Where it breaks

• Hallucinated launches. The most common and most expensive failure. Ask a search tool what’s new and it will find you something new, including a feature announcement assembled from a blog post’s aspirational paragraph. This is why the source-link rule is non-negotiable and why step 4 exists: a rep who repeats an invented competitor feature to a prospect loses credibility you can’t refund. If a claim has no link, delete it — don’t go looking for the link yourself.
• Public sweeps only see the public. Enterprise announcements delivered under NDA, private roadmap briefings, quiet pricing given to a single large account, sales-deck claims never published anywhere — none of it shows up in a changelog sweep. Ever. Your highest-signal competitive intelligence still comes from win/loss conversations and your own reps, and this workflow doesn’t replace either. Treat “no change found” as “nothing public changed.”
• A battlecard nobody opens is theatre. It is genuinely possible to run this workflow flawlessly for six months and have zero effect on a single deal. The tell is silence: no rep ever replies to your weekly line, no one asks a follow-up. If that’s your situation, stop maintaining the card and go ask two reps what they actually needed in their last competitive deal. Then maintain only that.
• Competitor obsession, dressed up as rigor. A weekly sweep is a very comfortable way to feel productive while learning nothing about your customers. April Dunford’s point is the guardrail: most of the alternatives you track aren’t on your prospects’ shortlists, and the status quo beats you more often than any named rival. Thirty minutes a week is the budget. If it’s creeping toward two hours, you’ve swapped a customer problem for a competitor hobby.
• Week one has no baseline. The first run has nothing to diff against, so it returns everything and looks like an emergency. Build the battlecard first, sit on it a week, then start sweeping — otherwise you’ll conclude the workflow is noisy when it’s just uncalibrated.