Key takeaway
Treat a competitor move as information to evaluate, not an alarm to answer. The post recommends responding only when the move actually threatens your customers reason to choose you, and matching the response to the real threat rather than reacting to the announcement.
A competitor ships something, the internal Slack lights up, and someone senior wants a response by Friday. That urgency is the tell that you are about to react to an announcement instead of a threat. Here is the worked version: the same seven-section structure YourBrief generates, applied to the competitive-response call so you can see the shape before the fire drill starts.
The decision
A competitor's move is mostly a two-way door — you can respond next quarter — but a reflexive response is not. A rushed price cut resets your floor; a me-too feature spends a roadmap slot and blurs your positioning. Both are hard to walk back. So the question is not "did they do something?" Competitors always do. It is "does this move actually change why our customers choose us, and if so, what is the smallest response that addresses the real threat?"
Key questions to answer before deciding
- Does the move target your actual customers and segment, or a different one you were never going to win anyway?
- Is it a durable capability, or a launch-day headline? A competitor's announcement and their shipped product sixty days later are often different things — respond to the second, not the first.
- What do your customers actually say about it, or are you reacting to a few loud posts?
- If you do nothing for thirty days, what concretely happens — measurable churn, or just discomfort?
- What is the cheapest response that neutralizes the real threat: positioning, a fast-follow, or nothing?
Recommended frameworks
Threat triage. Score the move on three axes: does it overlap your segment, is the capability durable, and do your customers cite it as important? A move that misses on any one rarely deserves a real response.
Do-nothing baseline. Before choosing a response, name the concrete cost of no response. If the thirty-day do-nothing cost is small and reversible, that is often the correct move — and the hardest one to get a fired-up room to accept.
Response-proportionality ladder. Pick the lowest rung that works: sharpen your message and positioning, ship a targeted fast-follow, commit to a full build, or move on price — in that order. Price is the last resort, not the reflex.
Decision criteria
Respond only if the move actually threatens your customers reason to choose you, and match the response to the real threat rather than the announcement. If a thirty-day do-nothing costs little, hold and watch. Never answer a price cut with a price cut by reflex.
Sources to consult
Your own customers in the overlap segment (ask them directly what they think of the move); the competitor's actually-shipped capability versus their announcement; your win/loss notes since the move landed.
Next steps
Triage the threat on overlap, durability, and customer-cited importance; price the do-nothing baseline; if a response is warranted, choose the lowest proportional rung and set a review date to revisit with data.
When to escalate
Escalate to the exec team or board if the response would change pricing or positioning company-wide, if it is a genuine platform-level threat, or if sales is demanding a reflexive discount that would permanently reset your price floor.
The honest answer is often "watch, do not react" — most competitor moves that trigger a fire drill do not survive the threat triage. Generate this exact brief against the specific move on your desk — $1 to start.