Competing Beyond Price

The price war trap is consistent enough across the companies I have worked with to be worth describing clearly. A larger competitor, or a new market entrant with different unit economics, starts offering similar products at a lower price. The natural response is to consider matching or undercutting. Almost always, this is the wrong move.

The reason it is the wrong move is structural. A hardware-software company with a developed product has a cost structure that includes the R&D amortised into each unit, the manufacturing overhead, the support and warranty costs, and the sales cycle that brought the customer in. Competing on price against a larger business that has already amortised those costs across a bigger installed base, or against a newer entrant that has not yet built in the support infrastructure, requires accepting margins that cannot sustain any of those things long-term. The price competition looks viable for a quarter. It tends to become unsustainable before the year is out.

What the competition is actually about

The more durable position is to compete on the dimensions where scale does not automatically confer advantage. For most hardware-software businesses, those dimensions are integration depth, support quality, domain-specific features, and the speed with which the product evolves in response to customer feedback. A larger competitor with a broader product line and a larger sales team cannot always match the responsiveness of a focused business that genuinely understands a specific vertical or use case.

This is not a comfortable position because it requires resisting the pressure to compete directly when customers raise price objections. The answer to a price objection is not a discount; it is a clearer articulation of what the customer is actually getting. If that articulation is not compelling enough to justify the price difference, the problem is either in the product or in how it is being sold, and discounting papers over both without fixing either.

The margin point

Healthy margins are not just a financial metric. They are what funds the R&D that maintains differentiation. A business that has competed itself into thin margins has competed itself out of the ability to improve its product faster than its competitors. The erosion tends to compound: lower margins reduce investment in the product, reduced investment allows competitors to close the gap, a narrower gap weakens the value argument, and the pressure to compete on price increases.

The companies that win sustained price competitions are almost always the ones with a structural cost advantage: lower manufacturing costs, a dominant distribution position, or a scale that allows them to absorb lower margins on individual products. Without one of those advantages, sustained price competition is a war of attrition that a smaller business is not positioned to win. The better strategy is to maintain the margin and defend the value, even when that requires accepting that some customers will go elsewhere.

The signals of being drawn in

Price pressure rarely arrives as a single decisive event. It tends to begin with one or two customers raising the subject, “we’ve had a better quote from,” and escalate from there. The point at which it becomes a strategic problem, rather than a sales conversation, is when discounting has become routine rather than exceptional, when the sales team is leading with price rather than value, and when the cost of acquiring and retaining customers is rising even as the margin on each one is falling.

In connected-product businesses, there is an additional signal that is easy to miss: the price conversation moving from the operational buyer to the procurement function. When the person comparing quotes is no longer the person who operates the product, the evaluation shifts from total cost of ownership to unit price, and the dimensions that justify the premium, integration depth, diagnostic capability, field support, firmware lifecycle, become invisible in the comparison. That shift is not a pricing problem. It is a positioning problem, and it is best addressed before the procurement function has already framed the decision as a like-for-like price comparison.

At that point the problem is no longer the competitor’s pricing. It is that the value argument has stopped working at the point of sale, which usually means it has stopped working in the product or in how the product is being positioned. Both are fixable, but they require a different diagnosis than the one a price war invites.

Defending value operationally

The principle of not competing on price is straightforward. The operational reality is harder. Customers ask for discounts. Distributors press for margin. The sales team, under pressure to close, finds it easier to discount than to make the value argument at length.

The discipline that prevents this from becoming a pattern is not a pricing policy. It is a shared understanding across the commercial team of what the product actually delivers and why it is worth the price. That understanding needs to be specific: not “better support” but “we resolve integration issues within 48 hours because we have engineers who have worked with nothing but this protocol for two years, and the competitor does not.” Not “higher quality” but “our mean time between failures in the field is this, the market average is that, and the cost of downtime for the customer is the other.”

When the sales team can make that argument with confidence, the conversation shifts from negotiating the price to establishing whether the customer understands the value. Those are different conversations with different outcomes. One ends in a discount. The other ends in a decision.