Competitor Tracking Dashboard, Updated Weekly

The PROMPTS

Every [Monday at 8am], run our competitor sweep and update the intelligence dashboard. Competitors: [competitor list with homepage URLs]. For each one, visit and read: the pricing page, changelog or release notes, homepage and main product pages, careers page, customer stories page, and newsroom or blog. Also check [review site URLs, e.g. G2 profile] for new reviews since last week. Compare everything with last week's snapshot, stored at [Google Sheet URL]. Log every change as one row: competitor, signal (pricing, product, messaging, hiring, customers, funding and news), what changed in one sentence, the before and after text where there is one, source URL, and the date checked. If nothing changed for a competitor, write "no change" — do not pad the log. Keep facts and analysis separate. In a second column, add at most one line on what the change might mean for us, clearly labelled as analysis. Then update the battlecards in [Google Doc / folder URL]. Rewrite only the sections a change affects — pricing comparison, feature comparison, where we win, landmines, objection handling — and mark each edited section with the date and the log row that triggered it. Never delete a claim without replacing it; if a claim is no longer true and I have no replacement, flag it for me. Refresh the web dashboard: one card per competitor with its latest changes, a 2×2 positioning chart on [axis 1] and [axis 2] with every placement linked to its evidence, and a "this week" summary at the top. Post the summary to [Slack channel] with a link. If a page cannot be loaded, record it as "not checked" with the reason — never assume nothing changed.

Most battlecards are accurate for about a month. After that a competitor changes its pricing, ships the integration your reps have been selling against, or rewrites its homepage to sound exactly like you, and nobody updates the doc. Reps notice quickly — usually on a live call — and once they stop trusting the battlecard, they stop opening it. Competitive intelligence is not a research project. It is a weekly sweep, and the battlecard is only as good as the last time someone checked.

‍

What this recurring task does

Every week, Sai visits the same set of pages for each competitor, compares them with last week's snapshot, and logs every change with the before and after text and a source link. It then rewrites only the battlecard sections those changes affect, marks each edit with the change that triggered it, refreshes a dashboard with one card per competitor and a positioning chart, and posts a short summary to your sales channel.

‍

Six signals checked every week, and what each one usually means

A competitor sweep is only useful if it looks in the same places every time. These are the six, and where each change lands in the battlecard.

★ SIX SIGNALS CHECKED EVERY WEEK, AND WHAT EACH ONE USUALLY MEANS

Signal	Where it is checked	What a change usually means	Battlecard section it updates
Pricing	Public pricing page, plan limits, free tier terms	A new segment is being targeted, or margin pressure	Pricing comparison, discount objections
Product	Changelog, release notes, docs, integration directory	A gap you sell against may have just closed	Feature comparison, "where we win"
Messaging	Homepage headline, product pages, ad copy	Repositioning — often months before the product catches up	Positioning statement, landmines to set
Hiring	Careers page, open roles by function and region	Where they will be in six to twelve months	Strategic notes for account executives
Customers	Case studies, logo walls, public review sites	Which segments they are winning, and why buyers leave	Proof points, trap questions
Funding & news	Press releases, funding announcements, leadership changes	Runway to discount aggressively, or a change of direction	Risk notes, talk track on stability

‍

A positioning matrix built from evidence

The 2×2 chart on the dashboard uses axes you choose — for example implementation time and depth of integrations — and every placement links to the pages that justify it. When a competitor moves, the chart shows where it was last week and where it is now, with the change that moved it. That is the difference between a positioning slide someone drew once and a matrix sales can defend when a buyer pushes back.

‍

What happens on the second run

The weekly log accumulates into a history of every competitor move with dates and sources, which is what product marketing needs at the next quarterly positioning review. Facts and analysis stay in separate columns, so a guess about strategy never gets repeated to a customer as fact. A page that fails to load is recorded as "not checked" rather than "no change," and a claim that stops being true is never silently deleted — if there is no replacement, it is flagged for a human to rewrite.

‍

Where this fits

For the wider view — every player in the market, placed and grouped once a month — see the monthly market landscape map; this page follows the handful of direct competitors your reps meet in deals. Changes in competitor pricing often explain shifts in the channel CAC payback model, and the latest battlecard is worth reading before you reply to inbound sales conversations on LinkedIn. For a practical framework on structuring battlecards, see Crayon's guide to sales battlecards.

Track competitor changes weekly and keep sales battlecards current

Platforms this prompt works across

What this recurring task does

Six signals checked every week, and what each one usually means

A positioning matrix built from evidence

What happens on the second run

Where this fits

Stop doing repetitive tasks. Let Sai handle them for you.