What to do when a competitor cuts their price

A competitor cuts their price and the reaction inside most small teams looks the same: a Slack channel lights up, a rep asks what they can say on a call in twenty minutes, and someone reopens a pricing spreadsheet for the first time in months.

Knowing the price changed is the easy part. What almost nobody has ready is an answer for what to do about it, so the gap gets filled by whoever reacts fastest, not whoever is right.

Why a price cut is not one kind of event

The reason this is hard is that a price cut is not one kind of event. It can be a competitor discounting a tier that is not selling, a land grab aimed at a different segment than yours, a time-boxed promotion that reverts in a month, or a structural repricing that signals a real shift in their strategy. Each of those calls for a different response, and from the outside they can look identical: a number went down.

Guessing wrong in either direction is expensive. Match a cut reflexively and you reset the price your own market expects from you, on every deal going forward, not just this one. Hold and say nothing when the cut is real and the overlap is real, and you lose exactly the price-sensitive slice of your pipeline to a competitor who is now cheaper for no reason your reps can explain. Dismiss it as "not our segment" without checking, and you find out you were wrong when a renewal walks.

So the goal is not to react fast. It is to classify the cut correctly, then respond in a way that fits what it actually is. That takes a short procedure you can run every time, instead of a fresh argument in a Slack thread.

A step-by-step procedure for responding to a competitor's price cut

Run these five steps in order. Most of the cost of a bad response comes from skipping straight to step four.

1. Detect the change precisely. You want the specific before and after, not a vague sense that they got cheaper. Which plan moved, from what to what, and did anything shift alongside it (a feature added to the tier, a seat minimum dropped, an annual discount introduced). A generic page monitor tells you a page is different; it does not tell you which number moved or by how much. Set up how to track competitor pricing changes so the exact delta lands in front of you instead of a red highlight over a whole pricing page.

2. Classify segment overlap. Ask whether the cut reaches the deals you actually compete for. A cut on a self-serve starter plan is irrelevant if you sell to teams of fifty. A cut on the exact tier your best prospects evaluate is a direct hit. Overlap is the single filter that decides whether this is your problem at all, so answer it before you spend another minute on the cut.

3. Classify structural versus promotional. A structural cut is a new list price with no end date, often paired with repackaging or a public rationale. A promotion is time-boxed, coupon-driven, or framed as a seasonal or launch offer. The tell is usually in the wording and the surrounding page, not the number itself. Structural cuts change the market you sell into; promotions mostly test whether you will panic.

4. Choose the response that fits the two answers above. Only a real, structural overlap justifies matching. A real overlap with a defensible difference in what you offer is a case for holding and repositioning on value. No overlap, or a short-lived promo, is a case for ignoring the cut, but ignoring it out loud so reps have a line ready.

5. Get ahead with your at-risk customers. Whatever you decide in step four, name the accounts and open deals most likely to hear about the cut, and reach out first. A price cut you raise becomes a retention conversation you started. A price cut they raise becomes one you were forced into.

Choosing your response: match, hold, or ignore out loud

The response falls out of steps two and three, not out of who shouted loudest in the channel.

Match only when the overlap is real and the cut is structural. This is the one case where quietly doing nothing cedes price-sensitive pipeline to a competitor who is now genuinely cheaper on the same ground you fight for. Even here, matching is a deliberate repricing decision, not a reflex, because it resets what your market expects from you going forward.

Hold and reposition when the overlap is real but you carry a defensible difference, such as better onboarding, a capability they lack, or a support model that closes deals. The move is to make that difference plain on the call, which means your reps need current talking points. This is where how to build a competitor battlecard that stays up to date earns its place: the cut should update the card the same week, so the answer to "but they are cheaper now" is already written down and still true.

Ignore out loud when there is no overlap or the cut is a short-lived promotion. You are not matching and not repositioning, but you still tell the team it happened and why it changes nothing, so nobody improvises a discount on a call they did not see coming.

A worked example: reading a cut on their Pro tier

Say a competitor drops their Pro tier from $49 to $39 per seat, and your monitor also flags that the tier now includes a feature that used to sit one level up.

Step one gives you the precise change: a $10 cut plus a feature moved down a tier. Step two: your best prospects evaluate exactly this tier, so overlap is real. Step three: the change carries no end date and is paired with repackaging, so it reads as structural, not a promo. Steps four and five follow directly. This is a match-or-reposition situation, and you decide which based on whether that newly bundled feature is one you also offer, then you contact the three open deals sitting on that tier before your competitor's cheaper number reaches them through a cold email.

Same starting number, different reading: if that $39 arrived under a "spring offer, ends April 30" banner and your prospects buy annual contracts, it is a promotion with weak overlap. You note it, tell the team, and move on. The procedure, not the number, tells you which world you are in.

The practical fix: an interpreted alert, not a raw diff

Every step above depends on the same thing, and it is the thing raw change detection cannot give you. Knowing a pricing page is different from yesterday is change detection. Knowing which plan moved, whether it reaches your deals, and whether it is structural or a stunt is interpretation, and interpretation is what turns a price cut from a fire drill into a decision.

That is the layer Presagon is built to be. Instead of a pixel diff over a whole page, or an enterprise intelligence suite you have to staff, an alert arrives already interpreted: what shipped, why it matters to you, and what to do next. The classification work above happens before the alert reaches you, so the twenty-minute-warning version of this problem stops existing. You are choosing a response from a clear read of the cut, not reconstructing what happened while a rep waits on the line.