Your pricing is a list, not a logic

Ask for a price list and you get one in seconds. Ask what governs the price of the deal currently in legal review, and the answer takes a meeting.

That gap is the difference between a price list and a pricing logic, and it is where unexplained margin variance tends to originate.

A list is an output

A price list is a snapshot of what the logic produced for the standard case. It survives exactly until a deal needs an exception, a volume commitment, a competitive situation, a multi-year term, a customer who wants annual billing at monthly rates.

At that point somebody makes a judgement call. If there is no logic underneath, that judgement is made from precedent, pressure and whatever the seller thinks will close. It is recorded as an approval, not as a decision about the revenue architecture, and it is never revisited.

What the logic has to answer

• —What is the unit being charged for, and why that unit rather than an adjacent one.
• —How price scales with that unit, linearly, in bands, with a floor, with a cap.
• —What discretion a seller has without approval, and what the thresholds are above it.
• —What a discount is exchanged for. A concession given for nothing teaches the market the list price is fictional.
• —How price changes over a contract term, and what happens at renewal.

Each of those is a structural decision about what the company sells. None of them is a sales process question, even though all of them surface in the sales process.

The measurement that exposes it

Compute realised price per unit, actual revenue divided by units delivered, as a distribution, by segment and by quarter, and plot it against list.

In a company with pricing logic, that distribution is tight and its spread is explainable: this band is the volume tier, this one is multi-year. In a company with only a list, it is wide and drifting downward, and no single person can account for the shape. Nobody decided to sell at the average discount the company now sells at. It accumulated, one reasonable exception at a time.

Why this is upstream of everything

Realised price per unit is the numerator of unit economics, the base of expansion modelling, and the thing forecast accuracy is measured against. When it drifts without governance, payback periods lengthen quietly, segment profitability inverts without anyone noticing, and the capacity plan is built on an average that no longer describes anything.

A discount approval workflow does not fix this. A workflow routes an exception; it does not decide whether the exception should exist. That decision belongs to the layer that defined what is being sold in the first place.