Guide

How to track competitor moves

Track competitor moves by watching the small number of things a competitor states that change a decision - price, packaging, product, leadership, positioning - and recording each change with the date the source gave and a link to it. The discipline that matters is not collection but dating: a change nobody can date is an opinion, and a battlecard that cannot show when a line was last confirmed will be quoted wrongly in a deal.

What counts as a move

Five categories cover almost everything that changes how you sell against a competitor:

  • Price or packaging. A tier added or removed, a limit tightened, a feature moved up a plan, a number changed.
  • Product. A capability announced, documented or deprecated.
  • Positioning. The words on their homepage and category page. A quiet repositioning often precedes a product change.
  • People. A new function head, especially in product or sales.
  • Structure. Funding, acquisitions, market entries and exits.

Dating a move properly

Every move needs two dates: when it happened according to the source, and when you observed it. They are frequently weeks apart, and conflating them is how a team convinces itself a competitor moved recently when the change is six months old.

For page changes the honest form is a range: the page said A on this date and B on that date. Unless a company announces a change, that is the most anyone can truthfully say, and it is enough.

Where the record should live

One record per competitor, with each line carrying its date and its link, and the artefacts people actually use - battlecards, the sales wiki page - generated from it rather than maintained separately.

The moment those two diverge, the battlecard becomes fiction, because the person updating the record is not the person who wrote the battlecard, and nobody is measured on keeping the second one current.

A review rhythm that survives a quarter

Weekly: read what arrived, and delete what was not a move. Monthly: reread the top three competitors records end to end and mark anything older than a quarter as needing reconfirmation. Quarterly: ask whether the competitor list is still the right list, which it often is not.

Where QuikSignal fits

QuikSignal keeps the record automatically: every finding carries the date the source gave, the date it was collected, and a link to the document, and it is organised by company.

Because the collection repeats on a schedule, a line that has not been reconfirmed recently is visible as an old date rather than as an unmarked assumption.

See it on your own market →

What it does not do
  • It records what is on the record. An unannounced roadmap item is not visible and is not guessed at.
  • It does not write positioning or battlecard argument. It keeps the facts underneath current.
  • Page change claims are stated as a range between two captures, never as a precise moment, unless the company announced it.
Questions

What people ask

How far back can a competitor record go on day one?
For pricing pages, as far back as public archive captures exist, which is often years. For job postings, as far back as the boards keep them, usually months. For filings, as far as the register goes.
What is the most common error in competitor tracking?
Treating the observation date as the event date. It makes old news look fresh and leads teams to react to something that settled months ago.
Should sellers see the raw record?
They should be able to. What they read day to day should be the short version, but a seller who can open the source when a customer pushes back is a seller who wins the exchange.

Read your own market the same way.

Eleven agents, the companies you choose, every night, with the document behind every line.