Most businesses know their pricing is not as disciplined as it should be. What very few understand is why the problem keeps returning.
The pattern I encounter most often is this: an owner identifies that margins are being eroded by inconsistent discounting. They address it — new guidelines, a conversation with the sales team, sometimes a formal pricing policy. For a quarter, sometimes two, the discipline holds. Then it quietly unravels. The same conversations happen. The same exceptions get made. The margins erode again.
The owner concludes that it is a culture problem, or a sales management problem, or that some portion of the team simply does not understand the commercial stakes. Sometimes those things are true. More often, the real problem is structural. The pricing architecture was never built to hold under pressure. So it does not hold under pressure.
Pricing discipline is not a sales problem. It is not a training problem. It is an architecture problem.
When pricing decisions are made individually — by salespeople responding to buyer pressure in the moment, by account managers protecting relationships because the quarterly target is at risk, by owners closing deals because the pipeline feels thin — the cumulative effect is margin erosion that compounds across every transaction and never appears as a single identifiable failure.
Each individual exception looks reasonable. The customer relationship matters. The deal size justifies a concession. The competitive situation demanded flexibility. Taken individually, the logic is sound. Taken structurally, the logic is the problem.
What a pricing architecture does is remove the individual exception from the individual decision. It defines what flexibility exists, why it exists, under what conditions it can be applied, and who has the authority to apply it. The exception is not eliminated — pricing discipline does not mean inflexibility. The exception is governed. There is a structural difference between a discount made inside a defined framework and a discount made because the buyer pushed and the salesperson blinked.
The secondary problem with ungoverned pricing is what it does to positioning. Every time a product is sold below the price point that reflects its value, the market learns something about what that product is worth. Buyers share information. Procurement teams compare notes. The pattern of exceptions becomes the expectation of future exceptions. Recovering price position from that dynamic is significantly harder than maintaining it.
I have worked with manufacturers who were technically competitive but had gradually trained their market to expect margin concessions as part of the negotiation process. The product had not changed. The value had not changed. The commercial architecture had allowed a narrative to develop that the price was a starting point rather than a reflection of worth.
Rebuilding that position required not just a new pricing framework but a sustained period of holding it — of making the exceptions rare enough and governed enough that the market re-learned what the product cost and why.
The starting point is always the same: examine what is actually driving the pricing decisions being made. Not what the policy says. What is actually happening in the room when a buyer pushes on price. That gap between policy and practice is where the architecture problem lives — and where the structural fix has to be built.