How to react to a competitor: a counter-attack playbook

Saturday, 9pm. The competitor drops a 35% coupon valid through Sunday and the store’s WhatsApp group catches fire: match it? hold? answer with free shipping? The question of how to react to a competitor almost always shows up like this: at the worst hour, with no data at hand and in a hurry. And a margin decision made in a panic tends to be a bad decision.

The alternative is not to improvise faster; it is not to improvise at all. This article shows how to build a competitive response plan per competitor, a playbook with three parts: the battlecard (what we know about them and how we win), the reaction triggers (if they do X, we do Y, decided calmly before the war) and the counter-brief the AI builds when a trigger fires. If you already keep a dossier per rival, the playbook is the next step: turning a record into a pre-agreed response.

Reacting to a competitor on the fly costs margin

Improvising fails in three predictable ways. First, it responds to everything: every post from the rival becomes an urgent priority and the commercial calendar of the company that should be setting the pace ends up being set by them. Second, it responds late: the typical aggressive campaign lasts a few days, and the response that ships two weeks later answers an offer that is already over. Third, it responds in the dark: matching a discount without knowing whether it is a one-off inventory clearance or a price repositioning are two completely different decisions with the same appearance.

The classic case is price. The reflex to match without doing the math can destroy more margin than the extra sales bring in, and the discount break-even math (with the criteria of match, hold or differentiate) deserves its own article. The playbook attacks all three mistakes at once: it defines in advance what deserves a response, how fast and with which move.

The foundation: a battlecard with strengths, weaknesses and “how we win”

The battlecard is the page the team consults before reacting. What to record about each rival (positioning, relative price, channels, threat level) was already covered in the dossier article; what matters here is the combat version: short, current and decision-oriented. A battlecard from six months ago, with the wrong offer, is worse than none.

In Batedor, this page keeps itself up to date. On each competitor’s screen there is the AI Battlecard card: one click on Generate now and the AI reads the campaigns detected in the last 90 days (the scan runs 24/7 across Instagram, Facebook, YouTube and the website) and returns a page with apparent positioning, dominant communication tone, most frequent offers, dominant keywords, observed price range, strengths, weaknesses, recent changes and suggested actions. Each statement is tied to a data point from the period, in the style of “coupon in 14 of the 21 detected campaigns”.

The battlecard expires in 7 days on purpose: a read on a competitor ages fast. You can regenerate it whenever you want, compare it with previous generations (the history is kept) and export it as text to the document where the team’s playbook lives.

The field only you can fill in

The AI infers strengths and weaknesses from observable data: posting frequency, channel coverage, coupon aggressiveness. But the how we win (which proof, which differentiator, which counter-argument in front of the customer) is a business decision, not an algorithmic one. Write two or three sentences per rival with the team and paste them alongside the exported battlecard. It is the cheapest part of the playbook and the one most often missing when the pressure hits.

The competitive response plan: if they do X, we do Y

The heart of the playbook is a short list of triggers: observable condition, pre-agreed response, owner and deadline. The discussion about what to do happens in a one-hour meeting, with margin calculated and a cool head; when the alert arrives, nobody decides, they just execute. A template to adapt:

For a trigger to work, the detection has to arrive in time. Batedor classifies each detection by type (16 types, from coupon and free shipping to product launch), alerts by email and through the panel’s bell in real time and sends it to the channels where the team already lives: Slack, Telegram or WhatsApp. And when the change is not an isolated campaign but the rival’s pattern shifting, it shows up on the Signals page, classified as Pivot (a change in campaign mix), Anomaly (off-pattern volume, type or discount) or Creative fatigue (copy recycling), with severity from low to high.

The counter-brief: the first version of the response in minutes

A trigger fired and the agreed response is to answer with a campaign. Between “we decided to respond” and “we have an asset live” there is a valley where the reaction tends to die: someone has to turn the detection into a brief for the creative team, and that someone is busy.

It is this valley that the counter-brief shortens. On the detected campaign (or on the strategic signal), the Response brief button makes the AI read what was detected and return an actionable brief: the strategic reading of the move in one sentence, the proposed creative angle, suggested tone, recommended format (for example, an Instagram carousel plus a short reel), a headline and CTA suggestion, channels, differentiators to highlight and pitfalls to avoid, such as “don’t compare price directly, it can look like desperation”. It closes with an effort estimate: S for hours, M for days, L for a week or more. The system prompt forbids copying the competitor: the proposal is always a response that positions itself against them, not a clone of the campaign.

Each brief is saved in the panel’s briefing history, so on the same rival’s next move you can revisit what was done last time and what worked. Here too the honest caveat holds: the brief is a starting point, not a final asset. The AI does not know your margin, your inventory or your promotional calendar, and the differentiators it suggests highlighting need to pass the judgment of whoever knows the operation. The real gain is time: the team’s discussion starts from a structured draft, not from a blank screen.

Build the playbook in one afternoon

The whole process fits into one working afternoon for anyone who already monitors their rivals:

1. Pick up to 3 competitors with the highest threat (the dossier’s 1-to-5 score works as a filter). A playbook for 15 rivals does not survive the first week.
2. Generate each one’s battlecard and fill in the “how we win” with the team. Export it to the playbook document.
3. Write 3 to 5 triggers per rival in the format of the table above: observable condition, response, owner, deadline. Less is more: a trigger nobody remembers fires nothing.
4. Write the non-triggers on the same page, to protect the margin from a reflex reaction.
5. Schedule the review: regenerate the battlecard before a big date (Mother’s Day, Black Friday) and review the triggers every quarter or whenever the recent changes section signals a behavior shift.

If you are not monitoring anyone yet, the test fits within the 14-day trial, no card required: add the competitors, let the first detections arrive and generate the first battlecard before deciding anything.