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

It comes up in almost every engagement. Usually from the sales director. Sometimes from the CEO. The concern is understandable. They’ve seen approval processes before. Deals stuck in someone’s inbox for three days. Reps chasing managers while the customer moves on. A well-intentioned process that becomes a bottleneck.

So they push back. Keep the approvals light. Or skip them entirely. Let the reps move fast.

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

The real cost of no approvals

Here’s what actually happens in organizations without structured approval processes.

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

The deal closes. The discount was 35% on a product line that should never go below 20%. Nobody catches it because there’s no system tracking it. The margin on that deal is thin. The renewal will be based on that discounted price. The customer now expects that discount on every future purchase.

Multiply this across a sales team and across a year. The numbers add up quietly. By the time finance flags the margin erosion in a quarterly review, it’s baked into dozens of accounts. Unwinding it means renegotiating with customers who believe the discounted price is their price.

I’ve seen this in every organization that runs quoting without discount governance. 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 most people have: approvals exist to prevent reps from giving away too much. It’s a control mechanism. A check on the people closest to the customer.

This framing creates resistance. Nobody wants to tell their best rep they don’t trust them. And the rep hears “approval required” as “we think you’ll make a bad decision.”

That’s the wrong framing. Approvals aren’t about limiting sales. They’re about defining the boundaries within which sales can move freely and fast.

Think about it this way. A rep without clear pricing authority has to check everything. Every discount, every special deal, every non-standard term. They either ask their manager (which takes time) or they guess (which costs money). 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. The quote goes out immediately. Want to go to 25%? Route it for approval — which in a well-configured system takes hours, not days.

The paradox: clear approval thresholds make sales faster, not slower. Reps spend less time asking permission for things that are within policy, because they know the policy. Only deals that genuinely need oversight go through extra steps.

What approvals actually protect

When I design approval processes with clients, I frame the value around four things. None of them are “preventing bad behavior.”

Margin visibility. Without approvals, discount decisions are invisible until they hit the P&L. With a structured approval chain, every discount above a threshold is captured, reviewed, and recorded. Management can see discount patterns across reps, regions, product lines, and time periods. That’s not surveillance. That’s operational intelligence.

Consistent customer experience. When two reps from the same company offer the same customer different discounts on different deals, it creates confusion and erodes trust. Approval structures enforce consistency. This matters even more when you sell through channels. If dealers can see that direct sales gets deeper discounts, your channel relationship is damaged.

Renewal and expansion economics. A discount given at acquisition doesn’t just affect that deal. It sets the baseline for every renewal and expansion that follows. If the original deal was discounted at 40% with no oversight, the customer’s contracted price is now 40% below list. Every renewal inherits that. Every expansion is negotiated from it. The cumulative margin impact over five years is enormous.

Organizational learning. Approval data tells you something important over time. Which products need price adjustments because reps consistently have to discount them to close? Which customer segments are most price-sensitive? Which competitors trigger the deepest discounts? This learning only exists if discounts are tracked through a structured process.

How a good approval process actually works

The resistance to approvals usually comes from experience with bad ones. A manager buried in requests. Deals sitting in queues. No visibility into where a request stands. The rep stuck waiting while the customer loses patience.

A well-designed approval process solves all of these.

Routing should be automatic, not manual escalation. The system evaluates the quote against defined criteria — discount percentage, deal size, product line, customer type — and routes it to the right approver automatically.

When multiple conditions trigger, approvals should run in parallel. If a deal needs both a margin approval and a legal review, don’t run them sequentially. Run them at the same time. Total approval time is the longest single approval, not the sum of all of them.

The approver needs full context at the point of approval. The customer, the deal size, the product mix, the requested discount, how it compares to standard pricing, and the margin impact — all in one view, actionable from a phone in under a minute. 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. Deals don’t sit in inboxes.

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 sales manager approval.” No ambiguity.

A practical framework for setting thresholds

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

For most B2B companies, this means three tiers. First: the rep’s own authority — standard discounts, no approval required. This should cover the majority of deals. If more than 30 to 40 percent of quotes require approval, the thresholds are too tight.

Second: the sales manager, covering discounts beyond the rep’s authority but still within an acceptable margin range. Third: leadership — VP or commercial director — reserved for deep discounts or strategic deals. These should be rare.

One thing I always recommend: 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 be below floor. Discount percentage alone doesn’t tell you enough.

Special cases that need their own rules

Non-standard payment terms. Net-90 instead of net-30 has a real cost. Extended payment terms should trigger a separate approval, independent of the discount level.

Multi-year discount commitments. A discount locked in for three years has a very different impact than a one-time deal. Multi-year pricing commitments should flag for additional review.

Bundle or package overrides. If a rep is breaking apart a bundled product or overriding bundle pricing, that should require approval. Bundle pricing usually reflects a strategic decision about how products are sold together.

Channel pricing exceptions. If a partner is requesting pricing outside their tier agreement, that’s worth reviewing. It might be justified, but it should be visible.

The adoption challenge is cultural, not technical

Configuring approval workflows in Salesforce CPQ or any other platform is straightforward. The technical implementation takes days.

The cultural adoption is harder. Sales teams that have operated without guardrails will feel constrained. Managers used to approving deals over Slack will resist moving to a formal process.

The key is to show, not tell. Run the approval process alongside the existing process for a month. Let people see how fast it actually is. 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 that are within policy. Show leadership the discount visibility they’ve never had before.

Once the team sees that approvals make them faster on standard deals and smarter on non-standard ones, the resistance fades. Not immediately. But within a quarter.

In closing

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. A company selling through twenty channel partners across three regions definitely 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. And the companies that understand this tend to be the ones with the healthiest margins.