A competitor ships a feature that directly overlaps with your roadmap, and they ship it before you do. The first instinct in most marketing organizations is to respond immediately — a blog post, a tweet, a battle-card update, an emergency all-hands. The instinct is usually wrong. The speed of the response is less important than the shape of it, and most bad responses come from the 48-hour window when the team is reacting rather than deciding.
The response plan below is 10 days, not 10 hours. The first 48 hours are decision-making, not public output. Days 3 through 10 are the real response, scoped by the decisions from the first 48. A team that inverts the order — rapid public response, followed by figuring out what to actually do — usually ships two or three things they later regret and misses the one thing that would have mattered.
Day 0 · The moment you learn
The first decision: is this a Respond signal or a Preempt signal? Most competitor launches are Respond — scoped, tactical, answered with a battle-card update and maybe a blog post. Some are Preempt — structural, category-shifting, requiring a real strategic answer. Treating a Respond as a Preempt burns resources; treating a Preempt as a Respond loses market position.
The test: would the launch, if it landed well, change how buyers think about the category? If yes, Preempt. If it just gives the competitor feature parity on a capability you had, Respond. Most surprise-launches are Respond. The ones that aren't almost always involve the competitor making a category-level claim that the analyst community is likely to validate.
Both axes have to be high for a Preempt response. Either axis low, it's a Respond.
The first 48 hours · Decisions, not output
The discipline in the first 48 hours is that nothing ships publicly. No blog post, no tweet, no battle-card update in sales enablement, no CEO LinkedIn response. Instead, four decisions get made.
Decision 1 · What did they actually ship?
Read the competitor's announcement twice — once on the surface, once with skepticism. What is the actual capability? What is the marketing framing? How do they differ? Most competitor launches over-claim on the marketing side by 20–30% against what the feature actually does. A response that attacks the over-claim is weak; a response that acknowledges the real capability and focuses on what's still missing is durable.
The first 48 hours includes signing into the competitor's product if possible — trial account, free tier, or a customer's instance with their permission — to verify the capability. Marketing claims about what a feature does are often different from what the feature actually does, and a team responding to the marketing claim rather than the product reality will respond to the wrong thing.
Decision 2 · Which of our buyers notice this?
Not every competitor launch affects every buyer segment. The surprise launch that matters to your Series A customers may be irrelevant to your enterprise customers. The first 48 hours has to identify which segments are actually exposed. Narrow scoping tightens the response; broad scoping dilutes it.
Check the sales team's active deals for the past 30 days — which deals does this launch put at risk? Check customer success for renewal conversations in the next 60 days — which accounts will surface this launch? The number will almost always be smaller than the first-panic guess. A realistic scope is usually 10–25% of pipeline, not 100%.
Decision 3 · What is our honest response to "why didn't you ship this first?"
Customers, analysts, and your own team will ask this question. The answer has to be true, concise, and specifically not defensive. "We prioritized X in this quarter's roadmap" is honest if it's true; "we have it on the roadmap for Q3" is credible only if Q3 is actually plausible. The response that doesn't work: "we don't believe this is the right approach for our customers." That answer is an evasion — it may be true, but it sounds like defensiveness, and buyers will discount it.
Pre-scripting this answer in the first 48 hours prevents the scenario where the CEO, the CRO, and the VP of Product each give a slightly different answer at their next respective external meeting — and the collective incoherence becomes the story.
Decision 4 · Respond on their ground or pull them onto yours?
The most important decision. A response that rebuts the competitor's feature on its own terms (a comparison grid, a head-to-head blog post) concedes that the competitor's framing is the right frame. A response that reframes — that pulls the conversation to a different axis where you win — refuses the frame and wins the bigger fight.
The reframe takes preparation the competitor-comparison doesn't. Most teams default to the comparison because it's faster; the reframe is almost always better. Ask: what's the axis where we win durably, and how do we redirect the conversation there? Service quality, installed-base advantage, narrative ownership, ecosystem — these are reframing axes that don't require the competitor to have done anything different for you to still win.
Days 3 through 7 · The scoped response
With the four decisions made, the scoped response begins. A typical Respond-tier response includes three artifacts, each scoped tightly.
What to skip
Three things that feel urgent and almost never help.
A same-day tweet or LinkedIn post. The 24-hour public response rarely moves the needle for buyers, and it signals panic to the market. The blog post on day 7, written carefully, does more for your positioning than the same-day tweet does.
An emergency all-hands meeting. All-hands meetings for competitor news tell the company the competitor controls your calendar. Brief the exec team privately, brief sales and CS specifically, and let the rest of the company learn about it through the normal channels. The emergency-meeting framing creates an internal narrative of threat that outlasts the actual threat.
An email to the customer base. Existing customers usually do not need to hear from you about a competitor's launch unless it directly affects them. An email blast frames the competitor as more important than they are and plants a comparison in customers' minds that wasn't there. Proactive outreach from CS to the specific at-risk accounts, yes. A newsletter blast, no.
The post-response retrospective (day 30)
When the signal escalates
Sometimes a launch initially classified as Respond turns out to be Preempt within 30 days — analyst coverage lands, customer advocacy emerges, or buyer vocabulary shifts. The 30-day retrospective is the checkpoint for that escalation. If two or more of the retrospective signals show a bigger impact than expected, the response needs to escalate: a category-level position piece, a roadmap re-prioritization, an executive-level customer meeting tour.
Most surprise launches do not escalate. The 10-day scoped response handles them well. The 10% that do escalate need the CMO and the CEO to be in the room together within 72 hours of the signal, because the response at that scale is not a tactical response — it's a strategic one, and the PMM should not be the decision-maker. The discipline is knowing which 10% you're in, and the retrospective is what makes that visible.
Battle Cards
Auto-updating per-competitor rebuttal kits. Each card updates when Competitor Signals detects a material move.
See how it worksOne sharp positioning read, most Thursdays.
Field-tested frameworks, teardowns, and pattern notes from our working library. No "Top 10" lists. No launch roundups. Unsubscribe whenever.
Keep reading
7 Competitor Moves That Demand a Response (And 3 That Don't)
Seven competitor moves where silence costs you — and three that look urgent but aren't. A response-tier framework PMMs can run in twenty minutes.
How to Write Battle Cards for Pricing Objections
Most pricing battle cards re-argue the price. The ones sales reps actually use reframe the comparison — here's the five-section template, the three objections it has to answer, and the test for whether the card is working.
Competitor Signal Response Tiers: Ignore, Monitor, Respond, Preempt
Not every competitor move deserves a response. A four-tier framework for deciding which signals demand action, which get logged, and which get ignored on purpose.