When a Larger Competitor Dumps Price

A bigger competitor starts dumping surplus stock at reduced prices. For a smaller business it looks like an attack. Often it is. It is also, sometimes, an opening; the larger competitor’s attention is on clearing stock rather than serving the market, and the smaller business that moves deliberately during that window can build a position that is harder to dislodge once the pressure eases. The most durable response is almost never to compete on price. A smaller business fighting a price war against a larger one with more inventory and more margin to absorb losses is unlikely to win that particular contest. The more productive move is to use the competitor’s distraction as cover for differentiation, and to do so quickly enough that the position is established before the pressure lifts.

The differentiation that holds through price pressure

I have seen this play out in connected product markets where the hardware line is commoditising but the software layer is not. When a larger competitor drops device prices, the immediate effect is on the procurement conversation: the customer sees a number and asks why the smaller business charges more for what looks like a comparable device. The answer almost always lives in the software layer, but making that answer visible under pricing pressure is harder than it should be, because the software differentiation is less tangible and requires more explanation than a spec sheet.

The businesses that hold their position through that kind of pressure tend to be the ones that use the disruption as an occasion to make the software value explicit; in customer conversations, in product demonstrations, in the framing of total cost of ownership rather than device cost. In fleet-managed connected products, the relevant comparison is not the unit price; it is the cost of managing a hundred devices across a site with full visibility, reliable remote diagnostics, and integration into the operator’s existing workflow. A hardware-led competitor dumping device prices has not solved those problems. The smaller business that has solved them, and can show it clearly, is competing in a different evaluation than the one the larger competitor is trying to force.

The businesses I have seen lose ground in these situations were not outcompeted on product quality. They were outcompeted on framing: they accepted the competitor’s terms, treated the event as a price war, and tried to defend hardware margin rather than demonstrate software value. That is the move the larger competitor needs the smaller business to make. Not making it is the harder and more important discipline.

What agility actually requires

The word is used so frequently it has nearly lost its meaning. In operational terms, agility is not a mindset. It is a set of specific organisational capabilities: short decision cycles, people who are authorised to act without escalating every adjustment, processes that can be redirected without a three-month change management programme, and a leadership team that can update its own strategy in response to new information without treating the update as an admission of failure.

Most businesses that claim to be agile have none of these in place. They have the language and the retrospectives, but the actual decisions still require approval from the same three people, the same bottlenecks appear every time anything needs to change, and the strategy review happens once a year regardless of what the market is doing.

Building genuine agility before a disruption is easier than discovering its absence during one. The businesses that navigated market turbulence most effectively during the supply chain pressures of 2020 and 2021 were overwhelmingly the ones that had already built short decision loops and trusted their teams to act. The ones that were still routing every decision upwards discovered that their speed of response was inversely proportional to the height of the approval chain.

The most concrete version of this I have experienced was a hardware revision during a supply chain disruption. A component specified in the original design became unavailable; the supplier had discontinued their product line. In a genuinely agile team, the sequence is: identify the alternative, confirm compatibility, update the bill of materials, continue. In the teams I have seen stuck waiting for approvals, the same sequence takes three weeks; the production window closes; the disruption compounds. The external event is identical either way; what the organisational structure determines is not whether the problem happens, but how long the business sits with it before it can move.

The internal dimension

Price pressure from a competitor creates an external challenge and an internal one simultaneously. The external challenge is commercial. The internal one is that the team needs to know what the strategy is.

In practice, when a competitor makes an aggressive pricing move, the instinct of senior leadership is to focus outward: on the customer conversations, the competitive response, the margin analysis. The team, watching, is trying to understand whether the strategy has changed. Are we going to lower prices? Are we investing more in differentiation? Should we be worried?

The businesses that handle turbulence most steadily are the ones where the leader communicates clearly and quickly about what the response is and what it is not. They do not necessarily have all the answers; those may not exist yet. What they provide is a clear statement of the direction and the reasoning. Uncertainty that is acknowledged and framed is far less disruptive than uncertainty left to fill the space between meetings.