Leak 01 · Pricing & Margin - Uncontrolled quote discounting

Salespeople discount quotes without the discount buying enough extra win probability to justify the margin given away. Thousands of individually reasonable decisions add up.

What is it?

Salespeople usually have discretion to modify prices when preparing quotes. Some of that discretion is valuable. A rep knows competitive conditions, the relationship, urgency, and volume expectations that a rigid pricing system does not.

The problem begins when discounts are given without producing enough incremental probability of winning the order to justify the margin sacrificed. A rep may discount because the customer asked, because they assume a competitor will be cheaper, because the customer historically got that price, because they do not trust the ERP’s suggested price, or simply because discounting has become habitual.

The result can be thousands of individually reasonable decisions that collectively erode gross margin.

Where does it occur?

At the point where a salesperson, CSR, branch employee, or quote desk turns a suggested price into a quoted price. It happens in ERP quoting modules, CRM quoting, spreadsheets, emailed quotations, and counter transactions. The more pricing discretion lives outside structured systems, the harder the leak is to observe.

Family
Pricing & Margin
Primary owner
VP Sales / Pricing Manager
Secondary owners
Branch Managers, Sales Managers, CFO
Primary impact
Gross margin
Typical data source
ERP quoting module, CRM, quote spreadsheets
Detection difficulty
30-day measurability

Ask yourself

Can you measure quote win rate by discount level, by salesperson?

Yes, partially, no, or don’t know. “Don’t know” is the most useful answer, because it points at the test below.

What does it look like?

Warning signs. None of these proves the leak exists. They tell you where to look.

  • Large differences in realized margin between salespeople on similar customers and products.
  • Similar customers receiving materially different prices for the same items.
  • Frequent manual price overrides, often applied just before the quote is sent.
  • Discounts clustered around certain reps or branches.
  • Little relationship between discount depth and win rate.
  • High-margin quotes winning at about the same rate as discounted ones.

What data do I need?

The minimum viable set. Most of it is already in your ERP.

FieldExample
Quote IDQ-18493
CustomerAcme Manufacturing
SalespersonJ. Smith
SKUSKF-6205
Quantity25
Cost$14.20
Suggested or list price$23.50
Quoted price$21.00
Quote date8/17/2026
Won / lostWon
Final selling price$20.75

The initial check

Start with a small sample. Gathering the exports, agreements, or observations is separate from running the check; agree that work with the person who owns the records.

  1. 1Export the last 30 to 90 days of quote lines with suggested price, quoted price, cost, salesperson, and outcome.
  2. 2Calculate discount percent on each line.
  3. 3Compare median discount and gross margin by salesperson, then by branch, customer, and product family.
  4. 4Look for outliers: the reps or branches whose median discount is well above the rest.
Discount % = (Suggested price − Quoted price) ÷ Suggested price

Then ask one question: Do the reps who discount substantially more actually win substantially more? If not, you have found somewhere worth investigating.

The 30-day test

Build a quote-level dataset that carries each line from recommended price to quoted price to final price, with cost and outcome. Then segment quotes into discount bands.

DiscountQuotesWin rateGross margin
0–2%1,42042%31.2%
2–5%93044%29.7%
5–10%51045%26.8%
>10%19046%21.9%

Hypothetical distributor. Fictional numbers.

This distributor would have an interesting question to investigate: why are we sacrificing roughly nine margin points for roughly four points of additional observed win rate?

Before concluding that discounting caused the difference, control for the obvious: customer type, order size, product category, incumbent relationship, and competitive intensity. Deep discounts may be concentrated in genuinely competitive situations. The point of the 30-day test is to find out, not to assume.

How much could it be costing us?

A conservative range, not a headline. The goal is a number management can trust enough to investigate.

Annual quoted revenue affected × unnecessary discount % × realistic recovery rate

Worked example

  • $18M annual quoted revenue
  • 40% of it receives discretionary discounts
  • Analysis suggests about 1.2 percentage points may be unnecessary
  • Assume only 35% can safely be recovered

$18M × 40% × 1.2% × 35% ≈ $30,000 per year

Deliberately conservative. The goal is not the biggest possible number. It is a number management can trust enough to investigate.

Common root causes

Fixes fall into three layers. Not every problem needs software, and almost none needs AI first.

Process
Salespeople lack clear discount authority, escalation rules, or any review of the overrides they make.
Data
Pricing recommendations do not adequately reflect customer, product, volume, cost, or market conditions, so reps override them on instinct.
Technology
Pricing guidance is not surfaced at the moment the quote is created, or overrides are not captured in a form anyone can analyze.

What should we do?

Start with the simplest intervention that could solve it. Move down the list only if the one above is not enough.

  1. Level 1

    Visibility

    A monthly discount report by salesperson and branch, with win rate beside it. Most of the behavior change comes from people knowing it is measured.

  2. Level 2

    Guardrails

    Discount thresholds that require a manager’s approval, with the reason recorded.

  3. Level 3

    Better pricing guidance

    Improve customer and product segmentation so the suggested price is one reps trust.

  4. Level 4

    Workflow intervention

    Surface a warning, comparable transactions, and the margin impact inside the quoting screen at the moment the price is changed.

  5. Level 5

    Intelligent pricing support

    Use historical transactions, customer characteristics, product relationships, and quote outcomes to recommend a price range and flag anomalous discounts for review.

Where AI helps

  • Detecting unusual pricing behavior across thousands of quote lines.
  • Surfacing comparable historical transactions while the quote is being built.
  • Explaining why a line was flagged in plain language.
  • Routing unusual quotes to the right reviewer.

Where AI probably doesn’t

If the problem is simply “salespeople can override prices and nobody reviews the overrides,” you do not need AI. You need a report and a management process.

Before you call it a leak

  • Deep discounts are sometimes correct. A competitive bid on a large project may be won only at a thin margin, and the analysis should not punish that.
  • Win rate by discount band is confounded by customer type, order size, and competition. Control for those before drawing conclusions.
  • Quotes without a recorded outcome are common. Decide how to treat them before calculating win rates.

ERP note. Most ERPs store the quoted price but not the price that was suggested before the override. If yours does not, the five-minute test can compare quoted price to list or matrix price instead, which is a weaker but still useful proxy.

Think this might be happening in your business?

Turn the finding into a next step.

If the numbers say there is something there, send us what you found and we will help you decide whether it is worth a full investigation. No transaction files needed for that conversation.

Let’s start with one thing.

What would better performance look like?

Bring a result you want to improve, a symptom, or a workflow you already understand. You do not need to know the bottleneck yet. We’ll help choose what to investigate first.

No transaction files needed for the first conversation.