What to Do When a Competitor Launches Something

Announcements and products diverge more often than anyone admits. Read the launch page, then try to find the thing itself: is it generally available or on a waitlist, is it in all plans or only the highest tier, does it work in your market, and does it require anything the customer probably does not have.

Check the pricing page in the same pass. A launch that arrives with a new tier or a changed limit is a commercial move as much as a product one, and the commercial part is usually what affects your deals.

Write a one-paragraph factual summary of what exists today. This is the single most useful artefact of the whole week, because everything else that happens internally will otherwise be based on the marketing copy.

Anyone in sales or support will be asked about this within days, and the worst outcome is hearing about it first from a prospect. Send the factual summary, plus a holding line they can use before the full response exists.

A good holding line acknowledges the launch, states your own position without disparaging, and offers to go deeper. Something like confirming you have seen it, noting what your product does differently, and asking what specifically the prospect is trying to solve.

Ask for the objections back. The exact sentences prospects use in week one are the raw material for whatever you publish in week two, and they are far better than anything guessed internally.

Three questions decide the response size. Does this overlap your core value or an edge of it. Does it affect a segment you actively sell to. And is it a capability you already have but communicate badly.

The third question catches more launches than teams expect. Frequently a competitor announcement is about something you already do, and the honest response is not a product change but clearer communication, which you needed anyway.

Be equally honest when the answer is that they built something genuinely better. That is a product conversation with a timeline, not a marketing problem to be solved this week, and pretending otherwise produces claims your customers will test.

Rank the options by cost and reversibility. Updating internal enablement is cheap and always worth doing. Publishing your own clearest statement of value is moderate and usually right. Building a comparison page is expensive, needs maintenance, and invites scrutiny. Changing your roadmap is the most expensive and should never be decided in week one.

Say out loud what you are not doing, and why. Most launches deserve no public response, and an explicit decision to stay quiet prevents the slow drift into reactive marketing that follows every competitor announcement.

If you do publish, lead with what you are best at rather than with a rebuttal. Content written to answer a competitor ages badly, while content that states your own strength keeps working after the launch is forgotten.

Watch what happens to the launch rather than to the announcement. Does the ad spend behind it grow or stop, do the reviews mention it, does it stay in the navigation, does it get a pricing tier of its own. Launches that quietly disappear are common and informative.

Update your battlecard once, properly, with the verified facts and the objections you actually heard. A card updated in the panic of day one usually contains marketing copy rather than facts.

Then check whether the early signals were there. Hiring, unlinked pages, ad tests: most launches announce themselves weeks in advance. Oppira tracks those signals daily for the competitors you follow, which is what turns the next launch from a surprise into a scheduled conversation.