What to Do When a Competitor Cuts Prices in Half

01What should you do first when a competitor cuts prices by half?

Do not decide a price. Decide what the cut says about who your competitor is now trying to serve, because that is the question your response has to answer, and it is answerable from evidence you can collect in an afternoon.

The reason to lead with that rather than a pricing framework is a founder who did the opposite of the obvious thing. Their biggest competitor announced a cut of 50% across all plans. They raised their own prices 20% instead (the r/SaaS thread), pushed features from higher tiers down into lower ones, and repositioned explicitly as the premium alternative.

Win rate against that competitor up from 31% to 44%, average deal size up 15%, six months on, according to the post itself. Treat that as one report from one founder, not a finding. It is self reported, it covers a single company, and the thread was openly sceptical of the post.

What survives that scepticism is the reasoning, and the reasoning is testable in your own market. A price is a statement about which customer you want. A competitor who halves theirs has told you they now want a different customer, or that they need volume badly enough to accept one. The number is a consequence of a decision, and the decision is what you are responding to.

02Is the cut desperation or a deliberate share grab?

This is the question nobody answers, and it determines everything else. The founder assumed desperation and was later proved right in their case, noting that the competitor announced layoffs four months on. The highest signal reply in the thread pushed back on treating that as the rule.

Both readings are common and they call for opposite responses. If the cut is cash pressure, waiting is free and the price usually comes back up. If it is a funded push for share, waiting costs you the segment they are buying, and you have to decide which parts of that segment you were content to lose anyway.

You cannot read motive off a number. You can read it off the shape of the announcement, which is public.

None of that requires a tool. It requires someone to read the pricing page, the changelog, the careers page and the last ten deals you competed in, and write down what changed. It rarely happens because the announcement arrives as a panic, and panic produces a pricing meeting rather than a research task. The ranking advice compounds that: pages like Qlutch on responding to a price reduction do say to check whether the change is temporary, then send you into a customer survey and an elasticity exercise before the one fact that settles most of it is established.

03Why does matching a price cut usually lose?

Because it is the one response that changes your revenue immediately and your position permanently. Matching reprices your entire installed base to solve a problem that may exist in three deals, signals that your list price was always soft, and competes on the single dimension where a better funded rival outlasts you.

Harsh, and mostly right about the mechanism. Discounting under pressure is what a team does when it cannot say what the product is worth, and it works once. The published guidance agrees more than it disagrees. A widely shared summary of competing against low prices makes the useful operational point: if a buyer cannot afford the full scope, reduce the scope rather than quietly selling the same thing for less, because the second option trains the market to wait for a discount.

There is one honest exception. If the competitor genuinely delivers comparable outcomes at half the price, you have a product and cost problem, not a pricing one, and no messaging fixes it. The founder said the same about their own playbook.

04When does raising prices actually work?

When the sentence explaining why you cost more already exists, already works in live calls, and does not depend on the price rise to be believable. That is a narrow condition, and the founder who ran the play stated it themselves.

Read the play carefully and the price rise is the smallest part of it. Features moved down into lower tiers, so buyers at the same price point got more. The positioning became explicit rather than implied. The messaging named the tradeoff out loud. The number moved last, as a consequence of the other three changes, which is why copying the headline without the sequence is a bad idea.

The response from other founders is the most reliable signal in the thread: people describing their own decisions rather than their own results.

Undercutting an established product is the default move for a new entrant and it is a trap for the same reason matching is: it recruits the customers who leave first, and it caps what you can spend on the support and onboarding that would have made you hard to replace. Firmbee makes the adjacent argument that the answer to a cheaper rival is often a third package aimed at a different segment, which is a cheaper experiment than repricing what you already sell.

05What should change in the first two weeks, if not price?

Four things, in this order, all cheaper to reverse than a price change.

• The one line a rep says. When a prospect names the cheaper option, the rep needs a single sentence framing the tradeoff in terms the buyer uses. Write it the day the cut is announced and date it.
• The cost of the problem staying unsolved. A price only looks large next to nothing. Next to the cost of the thing it fixes, it is an input. Sales needs that number for your two most common use cases, sourced from customers rather than invented.
• A scope option below your entry point. Not a discount. A smaller thing with less in it, so the answer to a budget objection is a different package rather than the same package for less money.
• A walk away number. The discount level below which you decline, agreed before a rep has to improvise one. Most damage happens in the gap between the announcement and the day this number exists.

Three of the four are enablement, not pricing. That is why a cut hurts unprepared teams more: the cost is not the number they published, it is the six weeks your reps spend improvising an answer. a guide to SaaS competition from Justin Grant makes the related point from the product side: do not fight where a better capitalised competitor is strong, and do not start a price war with someone whose backers can fund one longer than you can. His corollary is the one that applies here. Customers pay more when the whole experience of buying and being supported is better, and support, documentation and onboarding cannot be built in the fortnight after an announcement.

06What does a competitor price cut do to your existing customers?

More than it does to your pipeline, and this is the part the ranking pages skip. Every guide on this question is written for the new deal. The cut reaches your installed base first, because your customers already evaluated that competitor once and some of them are on a mailing list that just announced half price.

The exposure is not spread evenly. It concentrates in accounts with low usage, a champion who has left, a renewal due, or a discount that already put them near the the old competitor price. That is a list you can build from data you already have.

The last row matters most. Customers who will not move are the clearest statement available of what you are worth more for, and their reasons are the raw material for the rep line, the packaging change and the renewal conversations. Asking five of them why the cheaper option does not tempt them produces better positioning than any internal workshop.

07What stops this from happening again?

A price cut is only frightening when price is the only difference the buyer can see. That is the condition to work on, and a separate thread on whether this category is heading to zero states the diagnosis in one line.

The follow on is where it gets practical: if the software is easy to reproduce, the competition moves to everything around the software.

What that thread never answered, and what a two person team needs, is how you build the knowing the customer better advantage without an enterprise sales organisation. The small scale version is unglamorous and mostly record keeping. Keep a written reason for every loss, named by competitor. Keep the exact words customers use for the problem, not your words for it. Keep a standing list of the three things your best accounts do that new accounts do not, because that is your onboarding roadmap and your renewal defence.

Then watch the competitor continuously rather than in bursts, so the next pricing change is something you saw on their page rather than something a prospect told you in a call. That shift, from reactive to observed, turns a price cut from an emergency into a data point. Our guide to competitor pricing intelligence covers the monitoring side, and keeping battlecards current covers getting the answer into the hands of a rep the day it changes.

The honest limit of all this: it rests on two discussions and the published guidance we could read, not on a study of price wars with outcomes attached. Those numbers are self reported and were disputed in that thread. What generalises is the sequence, read the cut before pricing against it, and the observation that a halved price is a statement about a customer segment. Whether raising works for you is an empirical question your renewal base will answer faster than any framework.

Frequently asked questions