A competitor has just shipped the feature at the top of your roadmap. How do you respond?

Nothing about your customers changed this morning

The announcement is information about a competitor's beliefs, not about your users' needs. Those needs are the same as they were yesterday, and the first discipline is to resist letting a press release reorder work you chose for reasons that still hold. Panic reprioritisation is the standard failure here, and it is expensive twice: once in the switching cost, and again because a roadmap that reacts to every competitor launch has effectively outsourced its strategy to whoever ships fastest.

So begin by asking what actually changed. Three things might have. Your win rate in new deals may fall, if the feature is now a checklist item buyers ask both vendors about. Your retention may be at risk, if the feature was the reason a segment was tolerating a gap in your product. Or nothing measurable changes and the only effect is internal anxiety, which is the most common case and the one people handle worst.

Three questions that decide the response

Is it a differentiator or a table stake? A differentiator is a reason to choose one product; a table stake is something whose absence disqualifies you and whose presence wins nothing. Most features become table stakes eventually, and for those, being second is cheap — you need adequacy, not excellence, and you can build the boring version. Ask your sales team whether this now appears in requirements documents. If it does, it is a table stake and you have a deadline rather than a strategy problem.

Which segment does it serve, and is it yours? A competitor moving down-market to serve small teams with a self-serve version of something is not competing for your enterprise accounts even though the feature name matches. This is where candidates get sloppy: they compare feature lists rather than asking who the feature is for. If it serves a segment you have deliberately chosen not to serve, the correct response is genuinely nothing.

Did they validate the demand or manufacture it? A competitor shipping something is weak evidence that customers want it — it may be their fourth failed attempt at a segment, and you get to watch. If you have research saying this problem is real and they have now confirmed the same read, that raises your confidence. If your research said the demand was thin, their launch does not overturn your data, and in six months you may get to see it quietly deprecated.

The response menu

Response	When it fits	The cost of choosing it
Accelerate as planned	It was already top of your roadmap and it is a table stake	The rest of the roadmap slips; you are now on their timeline
Ship a deliberately narrower version	You need to remove the objection, not win on it	Reads as catch-up; sets an expectation you must maintain
Differentiate around it	Your strength makes the same job easier a different way	Requires a story buyers can repeat; slower to land
Do nothing, monitor	It serves a segment you have chosen not to serve	Internal nerve; you must give sales an answer they can use
Reframe the comparison	You can move the buying criteria to ground you own	Only credible if you are already strong on that ground

Whichever you choose, do two things immediately that cost nothing. Give the sales and success teams a written position within a day — what we do instead, who this matters for, what to say — because in the absence of one they will invent commitments on your behalf. And instrument the thing you claim to be watching: if your argument is that this will not affect retention, define which cohort's retention you are watching and by when, so that in a quarter you are reading a number rather than relitigating the argument.

The case for abandoning the item

Sometimes the right response is to remove it from the roadmap entirely, and a candidate who never reaches for this option looks like a follower. If the competitor has shipped it well and it is a table stake for a segment you do not lead in, the honest calculation is that you will spend a quarter reaching parity on ground where parity wins you nothing. That quarter spent on something they cannot copy is the higher-return trade.

The version of this that scores best is specific about what you will deliberately not match. Naming a capability you are choosing to be worse at, with the reason, is the clearest evidence available that you have a strategy rather than a backlog. It is also the hardest sentence to say inside a company, which is why interviewers value hearing it.

Why matching feature-for-feature is the losing move

The response that feels safest is to build exactly what they built, quickly. It fails for a structural reason worth being able to articulate. You will arrive second with something less mature, which invites the direct comparison you cannot win, and you will have made your roadmap a function of theirs. Every quarter spent at parity is a quarter not spent on the thing that made customers choose you, and the compounding runs against you: they set the agenda, you pay the switching costs, and buyers learn to evaluate the category on their terms.

There is a second, quieter failure that catches strong candidates. They reason well about the market and forget the internal problem. Within a day the CEO has seen the launch, sales has three accounts asking, and someone has already promised a customer something. Handling that is part of the answer, not an afterthought — a written position, a named metric, a date to revisit — because a correct strategic call that nobody in the company can repeat under pressure will be overturned by the third escalation.

A competitor's launch is evidence about the market, not an instruction about your roadmap; the strongest answer names what you will deliberately not match and why.