The most common objection when scoping a CPQ project: “We don’t want approvals to slow down our sales team.”

It comes up in almost every engagement. They’ve seen approval processes before: deals stuck in someone’s inbox for three days, reps chasing managers while the customer moves on. So they push back — keep the approvals light, or skip them entirely.

That sounds reasonable. It’s also the most expensive mistake a B2B company can make with its pricing.

The real cost of no approvals

A rep is in a negotiation. The customer pushes on price. The rep, who wants to close the deal, offers a discount. They don’t have a clear framework for how much they can offer, so they estimate. Maybe they check with their manager over Slack. Maybe they don’t.

The deal closes at 35% off a product line that should never go below 20%. Nobody catches it. The renewal is priced from that discounted baseline. The customer now expects that discount on every future purchase. By the time finance flags the margin erosion in a quarterly review, it’s baked into dozens of accounts.

The reps aren’t doing anything wrong. They’re doing exactly what the system incentivizes: close deals. The system just doesn’t have guardrails on how.

Approvals are not about limiting sales

The mental model is that approvals exist to prevent reps from giving away too much. This creates resistance — nobody wants to tell their best rep they don’t trust them.

That’s the wrong framing. Approvals define the boundaries within which sales can move freely and fast.

A rep without clear pricing authority has to check everything, or guess. Both are slow and unreliable. A rep with defined authority knows exactly what they can do on their own. Discount up to 15%? Done, no approval needed. Want to go to 25%? Route it for approval, which in a well-configured system takes hours, not days.

Clear approval thresholds make sales faster, not slower.

What approvals actually protect

Without approvals, discount decisions are invisible until they hit the P&L. With a structured approval chain, every discount above a threshold is captured and recorded — management can see discount patterns across reps, regions, and product lines. This also enforces consistency: two reps offering the same customer different discounts on different deals erodes trust, especially in channel selling.

The renewal economics matter too. A discount given at acquisition sets the baseline for every renewal that follows. And approval data tells you something over time: which products consistently get discounted to close, which segments are most price-sensitive, which competitors trigger the deepest cuts. This learning only exists if discounts flow through a structured process.

How a good approval process actually works

Routing should be automatic, not manual escalation. The system evaluates the quote against defined criteria and routes it to the right approver. When multiple conditions trigger, approvals should run in parallel — total time is the longest single approval, not the sum.

The approver needs full context in one view: customer, deal size, requested discount, margin impact, actionable from a phone. If approving requires navigating multiple tabs, the process is too heavy. Build in escalation rules with time limits — if an approver doesn’t respond within a defined window, the request escalates automatically.

The criteria need to be simple enough for a rep to evaluate mentally before submitting: “I’m at 18% discount, my limit is 15%, this needs manager approval.”

A practical framework for setting thresholds

Start with your target margin for each product line and work backwards to the maximum discount that still delivers acceptable margin. Everything above that floor is self-serve. Everything between the floor and some deeper threshold needs first-line approval. Anything below needs executive sign-off.

For most B2B companies, this means three tiers. The rep’s own authority should cover the majority of deals — if more than 30 to 40 percent require approval, the thresholds are too tight. Sales manager covers discounts beyond rep authority. Leadership is reserved for deep discounts or strategic deals. These should be rare.

flowchart TD
    Q[Quote submitted] --> D{Discount level?}
    D -->|"Within rep limit<br/>≤ 15%"| A["<b>Auto-approved</b><br/>Sent immediately"]
    D -->|"16 – 25%"| B["<b>Sales manager</b><br/>Approved in hours"]
    D -->|"> 25%"| C["<b>VP or executive</b><br/>Reserved for strategic deals"]

Build approval criteria on margin impact, not just discount percentage. A 25% discount on a high-margin product might still be profitable. A 15% discount on a low-margin product might not. And some things need their own rules regardless of discount level: non-standard payment terms, multi-year discount commitments, bundle overrides, and channel pricing exceptions.

The adoption challenge is cultural, not technical

Configuring approval workflows is straightforward. The cultural adoption is harder. Sales teams that operated without guardrails will feel constrained.

Show, don’t tell. Run the approval process alongside the existing process for a month. Show reps that 70 to 80 percent of their deals go through without any approval needed. Show managers the time they save by not reviewing deals within policy. Show leadership the discount visibility they’ve never had before.

Approvals replace tribal judgment with structured decision-making. Not because the judgment was bad, but because it doesn’t scale.

A company with five reps can manage pricing through conversations. A company with fifty can’t. The approval process is what makes pricing governance possible at scale, without turning every deal into an administrative exercise.

Approvals aren’t friction. They’re the infrastructure that lets your sales team move fast within clear boundaries.