Pricing Exceptions Delete the Evidence Your Pricing Model Runs On

TL;DR: A pricing exception in B2B software is a deal priced off the published pricing surface by discretion rather than by rule. The usual case against discounting counts the margin; the larger cost is knowledge. A company closing tens or a few hundred deals a year has no other evidence base, and a discretionary exception moves price, term, packaging and commitment at once. Nobody can say afterwards which move closed it, so the row survives in the CRM and the observation does not. Four questions at the end test whether your exceptions can still be read.

Search for pricing exceptions and most of what returns is lending compliance: fair-lending exception logs, loan-officer overrides, cost-or-pricing-data exemptions in federal procurement. Regulated lenders manage exceptions for fairness reasons. Software has no regulator watching its discounts, but it shares the consistency problem, and in software the larger cost lands on the evidence the pricing model was supposed to learn from.

What Pricing Exceptions Are in B2B Software

A pricing exception in B2B software is a deal priced outside the published pricing surface by discretion rather than by rule. The pricing surface is the net-price function reps quote against: for any configuration, volume and term a customer might commit to, it produces a scheduled net price. A deal that lands on that surface is standard, whatever discount it carries. A deal that lands off it because someone decided it should is an exception.

That line separates the two kinds of discounting the lexicon keeps apart. Structured discounting is incentive programmed into the pricing model: a published volume schedule, a multi-year commitment discount, an edition step-up incentive, a partner margin. The rep applies it without asking anyone, because the rule already did the deciding. Unstructured discounting is the discretionary, per-deal concession, usually gated by a discount approval process that ends somewhere in sales leadership. A pricing exception is the unstructured kind.

Governance explains the distinction by who approves. Measurement explains it by what the record keeps. A discount produced by a rule carries its own rationale into the deal record, because the parameter that moved is known by construction. A discount produced by discretion carries nothing, because several parameters moved together and no rule says which one did the work. A pricing exception costs the pricing model an observation before it costs the P&L a dollar.

Why Low-Volume Selling Makes Every Deal an Observation

Consumer pricing learns from millions of transactions. A price test on a retail site resolves in a week because the volume averages out everything the test did not control. A B2B software company selling through an enterprise pricing motion closes tens of deals a year, or a few hundred. Those deals are the whole dataset the pricing model can calibrate on, and each one took a quarter of selling effort to produce.

What a signed deal tells the pricing model

Every signed deal is an observation with a configuration attached. The edition, the units of the value metric, the term, the payment terms and the net price against list all travel with it. Read together, the observations describe where buyers accept the surface and where they push against it. A cluster of deals that all landed at the same commitment level and the same net price says that point on the surface holds. A cluster that all needed something extra says the surface is wrong there.

Peer-reviewed work in applied pricing finds that models built from observable business behavior outperform purely theoretical constructions. For a software vendor, the deal record is where that observable behavior lives. There is no other place to look.

Why a small dataset cannot afford deleted rows

In a large dataset an unexplained transaction is noise, and the rest of the data absorbs it. In a small one there is nothing to absorb it with. Each row is expensive, and the value of a row is that its parameters are known. A deal whose parameters cannot be read is a hole in the only evidence there is, and the model does not know the hole is there. It sees a closed deal at a net price and treats it as support for whatever configuration the CRM recorded.

Procurement research on negotiation versus competitive bidding finds that complexity and contractual incompleteness push buyers toward negotiation. In software that means exceptions concentrate in the most complex deals, the multi-product, multi-year, multi-region ones, which are exactly the deals whose evidence is scarcest and most valuable.

The pattern our library holds is consistent on this point: the companies whose pricing models improve between redesigns are the ones whose deal records can say what moved on each deal. The companies that redesign from opinion every few years are usually the ones whose records cannot.

Pricing exceptions and the difference between a record and evidence

A record is what the CRM stores: the account, the products, the term, the amount. Evidence is a record whose parameters were held constant enough to be read. Every deal produces a record. Only deals where one parameter moved, and the record says which, produce evidence. Pricing discipline, on this view, is a measurement property before it is a behavioral one: it is whatever keeps the record readable.

The Deleted Row: What Pricing Exceptions Do to the Record

When a discretionary exception is granted, several parameters move at once. The price moves, the term stretches to justify it, and the edition contents shift because the buyer wanted one capability from the level above. The volume commitment is rounded up so the discount reads as earned, payment terms follow, and sometimes the value metric itself is swapped for a unit the buyer found easier to forecast. Nothing is held constant.

The deal closes. The row stays; the signal is gone. The record shows a number, and the number cannot be attributed to any single move, because nobody can say afterwards whether the buyer needed the price, the term or the packaging. In the structured case the opposite holds: a rule on the surface produced the discount, so the parameter that moved is known and the deal remains an observation.

When is a discount an observation, and when is it a deletion?

The size of the discount does not decide it. A deep discount produced by a published rule is an observation: the rule names the parameter and repeats on the next matching deal. A shallow discount produced by discretion is a deletion: nothing names the parameter and nothing guarantees repetition. The question to ask of any concession is whether what moved is known and repeatable.

Peer-reviewed work on quantity discounts in industrial pricing makes the same point. A discount serves a specific economic function, a volume incentive or a segmentation device, and its structure should follow that function. A rule-governed discount carries its function into the record; a discretionary one carries nothing.

Genuinely novel deals exist, and the surface may have no rule for them yet. The line still holds: a novel deal handled by writing the missing rule is an observation the next one can build on, and the same deal handled by improvisation is a deletion.

Why the won deal is the more dangerous case

Sales leadership worries about lost deals. A lost deal is at least legible: the record shows a configuration, a price and a refusal. A won exception records a yes that cannot be attributed to anything. It enters the record as support for a net price that no rule produced. The next rep who quotes a similar account will find that deal in the CRM and treat it as precedent; the model has learned something false from a row with no signal.

What the record holds a year later

A year on, the people who negotiated the exceptions have moved on. The rationale that lived in their heads left with them. What remains is a set of net prices the surface cannot explain and a list-to-net spread nobody can account for. When the next redesign starts, it starts from recall instead of record, and recall is mostly the loudest rep’s memory of the deal that went badly.

If last quarter’s exceptions cannot be read, describe them to a pricing expert and one replies.

The Compounding Cost: A Pricing Model That Cannot Improve

The margin lost on an exception is bounded and visible. Finance can total it at quarter end. The knowledge lost compounds and never appears on a report. A pricing model whose inputs are corrupted cannot be recalibrated from its own history. Each redesign is then built on opinion, the list-to-net spread widens without anyone being able to say why, and the company substitutes intuition for the evidence it paid to generate.

When a company’s own record is empty, the only calibration left is borrowed. Decades of pricing work across many companies produce patterns that can stand in for a record: where surfaces hold, where they fail, which concessions recur. Reading a company against that pattern library is what SPP does, and it is also why a company with a readable record needs less borrowing: its own deals carry more of the calibration. A pricing architecture assessment is the shortest way to find out how far the model has drifted from its evidence.

The Tests: Can Your Pricing Exceptions Be Read?

Four questions, run against your own deal record. The answers are the diagnosis. What to do about them is judgment work, and it differs by company.

1. Take a non-standard deal that closed last quarter. Which parameter moved, and would the record say so without asking the rep?
2. If that same exception had been withheld, could anyone say what would have changed: the price, the term, the packaging, or the outcome?
3. Of last quarter’s exceptions, which could have been produced by a rule on the pricing surface, and which were genuinely novel?
4. Does the record keep the configuration that was offered before the concession, or only the one that was signed?

A record that answers all four is evidence, whatever its exception rate. A record that answers none of them is a list of amounts. If you want a second reading of what yours says, describe the exception pattern you are seeing and a pricing expert replies.

Where This Sits Against the Discounting Problem

The margin argument is made elsewhere. The discounting approaches that slow growth piece covers what refusal, inflated list prices and discretionary chaos cost the P&L. Margin-Calibrated Discounting is the architecture-side answer to a surface that keeps producing exceptions. The deal desk piece argues that a documented, approved exception can be run as a test across matching customers. Pricebook deviation measures the size of the gap between pricebook and signed price.

All of them assume one precondition. An exception can only become a test, or a measured deviation, if something was held constant. The unstructured exception is the one where nothing was. Managed is not the same as measured: an exception that wins a key account and leaves no readable record has bought one deal with the evidence that would have priced the next ten. Faster approval does not change that; a fast, undocumented exception is deleted faster.

If the exceptions in your record cannot say what moved, the place to start is a conversation rather than a policy. Describe the exception pattern you are seeing and a pricing expert replies with a read on whether the record can still be recovered and where the surface is producing the exceptions. When an engagement moves on to rebuilding the architecture, LevelSetter is the infrastructure that keeps the deal record readable afterwards, so the next observation is one the model can use.

FAQs