# Dynamic Pricing in B2B: Price Rules a Sales Team Can Run

https://salesbond.app/blog/dynamic-pricing-b2b-sales-team-owner-price-rules-discount-approval-in-crm/
Published: 2026-11-15 · Updated: 2026-11-15

Dynamic pricing is a flexible price that changes with demand, time, volume or the customer. In B2B sales it usually runs on rules a person wrote: a dated price list, a discount corridor for each role, and an approval step for exceptions, all recorded on the deal.

That second sentence is the part most guides skip, because most guides are written about retail.

## Dynamic pricing examples from retail (and why they don’t fit B2B)

Live Proxies’ glossary entry from August 2025 defines dynamic pricing as a technique where the price of an item or service is changed in real time based on market demand, competitor prices, time, or customer behavior ( [Live Proxies: What is Dynamic Pricing?](https://liveproxies.io/blog/what-is-dynamic-pricing)). Flights and rides are the examples nearly every guide reaches for.

Airlines change prices often depending on the day of the week, the time of day, and the number of days before the flight, according to [Wikipedia’s entry on dynamic pricing](https://en.wikipedia.org/wiki/Dynamic_pricing). Uber’s own explainer says that in cases of very high demand prices may increase, a system it calls surge pricing, and that the app lets riders know when rates are raised ( [Uber: How surge pricing works](https://www.uber.com/us/en/drive/driver-app/how-surge-works/), page checked November 2026).

Both run on thousands of near-identical purchases a day. The buyer sees one price and taps yes or no, and nobody on the seller’s side ever talks to them. Does your pipeline look like that?

## Why B2B dynamic pricing rarely looks like Uber

A five-rep team might close twenty deals in a month. Each one went through a quote, a couple of calls, a buyer who emailed back asking for “a bit of flexibility”, and maybe a purchasing department that asked again a week later. The price moved. A person moved it, and the CRM usually shows only where it ended up.

So B2B pricing is already dynamic. Order volume moves it through tiered price lists. Annual list price increases and expiring quotes move it with time. A customer with negotiated terms or a tender bid gets their own number, and the end of the quarter brings the discount every buyer has learned to wait for. It all happens in calls and email threads, which is why it’s so hard to see afterwards.

The usual advice at this point is to automate: let an algorithm or an AI model set the price for each deal. We disagree with that for a small B2B team. Twenty closed deals a month give a model very little to learn from. A quote is a promise with a validity date, and a price that shifts between Tuesday’s call and Thursday’s PDF costs the rep credibility. B2B buyers also compare notes. Two customers of the same size paying visibly different prices for no stated reason is a conversation you’ll have to have eventually.

## What can you automate in B2B dynamic pricing?

Automate the price list lookup, the discount-limit check, routing to the approver and the report; the decision below the limit stays with a named person. That’s most of the work. In CRM terms (product catalog, a workflow rule, a saved report), the lookup fills the list price when a product goes on the deal, a rule flags any deal whose discount is bigger than the rep’s limit, and the flag lands with whoever is allowed to say yes. The yes or no itself, and the name of the person who gave it, go into a deal field by hand. That’s the one part a machine shouldn’t own, because the reason behind it (“they paid three years up front”) is something only the person in the conversation knows.

## Three layers: price list, discount corridor, exception approval

Say a six-rep team sells annual maintenance contracts (a made-up example, numbers included), and the list price for a standard site is $24,000 a year.

**Layer one is the price list with a date on it.** The list holds the standard price and any rule that applies to everyone: 8% off for three or more sites, for instance. It has an effective date and a review date, and one person owns it. When the price changes, a new dated version replaces the old one, and open quotes keep the version they were issued on.

**Layer two is the discount corridor by role.** A corridor is the range each role can agree to without asking anyone, also called a price corridor, with a floor, a target and the limit for each role.

| Role | Can agree to, off list | Lowest price on a $24,000 contract |
| --- | --- | --- |
| Rep | up to 5% | $22,800 |
| Sales manager | up to 12% | $21,120 |
| Owner | anything below that | decided per deal |

Where should the numbers come from? From your margin and from what past discounts actually bought you. The margin side is worked through in [markup vs. margin for discount approval](https://salesbond.app/blog/markup-vs-margin-discount-approval-sales-manager/), and the win-rate side in [price elasticity for a small sales team](https://salesbond.app/blog/price-elasticity/).

**Layer three is the exception.** A buyer asks for 15% off in exchange for a three-year term paid up front. That’s $20,400, below the manager’s floor of $21,120, so it goes to the owner. The owner says yes or no, and the answer gets written on the deal along with the reason.

![Pyramid of three layers: dated price list, discount corridor by role, and exception with approver and reason, with a deal moving up from list to approved price.](https://salesbond.app/wp-content/uploads/2026/11/dynamic-pricing-b2b-sales-team-owner-price-rules-discount-ap-2.png)

A common version of layer three is “exceptions are fine as long as someone senior agreed”. We’d tighten that. An exception with no written reason should count as unapproved in your reporting, even if the owner nodded in the hallway. Six months later nobody remembers what the customer gave in return, and the renewal starts from the discounted number.

## What to record on the deal

Most CRMs store one amount per deal. That single number can’t tell you whether $20,400 was the list price, a volume tier, or a favor. Four custom deal fields fix it, and they work the same way in any CRM that supports custom fields:

- **List price.** The price from the dated list at the moment of quoting, $24,000 in the example. Filled once and left alone after the quote goes out.
- Approved price, the number the customer signed for ($20,400).
- **Approver.** A person field or a dropdown of the people allowed to approve. Empty means the rep stayed inside their own corridor, or that nobody approved.
- Discount reason: a short dropdown works better than free text, because you’ll want to count by it later. Volume tier, multi-year term, prepayment, competitive bid, other.

Discount percentage is then a calculation (list price minus approved price, divided by list price), so no one types it by hand. In the example that’s 3,600 / 24,000, or 15%.

Make the approver and reason fields required at the stage where the quote is sent, if your CRM lets you require fields per stage. If you run Pipedrive, the step-by-step version is in our [discount policy for small sales teams](https://salesbond.app/blog/discount-policy-sales-teams/).

## The manager report: closed below the corridor, by rep and by month

Once the four fields exist, one saved report tells you who’s discounting past their limit and whether anyone signed off. Filter closed-won deals for the month, keep the ones where the discount is larger than the rep’s own limit, and group by rep. Then split that group by whether the approver field is filled.

Take three reps from the example team and their October:

| Rep | Won deals | Below rep corridor | Approver recorded | No approver |
| --- | --- | --- | --- | --- |
| Dana | 6 | 1 | 1 | 0 |
| Marcus | 5 | 4 | 1 | 3 |
| Priya | 7 | 2 | 2 | 0 |
| Total | 18 | 7 | 4 | 3 |

Seven of eighteen deals closed below the rep corridor. Four of those went through approval and are doing what the corridor was designed for. The three in the last column are all Marcus’s, and that’s a one-to-one conversation this week, with the deals open on the screen.

Run the the same report by month too. Is “below corridor” climbing every month while win rate stays flat? Then the list price or the corridor is wrong, and your reps are telling you so with every quote they send. For how to read that against closed-won data, see [what closed-won discounts tell you about your pricing strategy](https://salesbond.app/blog/pricing-strategy-closed-won-discounts/).

A report like this is only as good as the deals behind it. Stale stages and missing amounts will skew it. Before you build the discount report on your pipeline, SalesBond’s free CRM audit shows whether stages and amounts are kept up to date: it looks at the last 30 days of your connected CRM and sends a PDF with money at risk, a CRM score, findings, a section on managers and deal health, then a second PDF seven days later with what changed. [Check your CRM with SalesBond](https://salesbond.app/).

## When to leave the price alone

Leave the price alone on an open quote before its validity date, on a renewal the contract already prices, and for a customer in the middle of a term. Quotes first. Until the validity date the buyer gets the price on the PDF, whatever happened to the list in the meantime (even if you raised it yesterday). A “Quote valid until” deal field means the rep sees at a glance which version of the price list applies.

Then renewals. The renewal price should follow whatever the contract says about increases, and if the contract says nothing, the question belongs to whoever drafted it. From the sales side the useful habit is to open the renewal deal with the original list price and the original discount reason copied across, so the rep knows whether last year’s 15% was a multi-year reward or a one-off.

A customer halfway through a contract who hears that new customers pay less will call. Decide in advance who takes that call and what they’re allowed to offer, and write it into the same corridor table.

## Start with last quarter

You don’t need new software to begin. Pull last quarter’s closed-won deals into a sheet, add teh list price next to each amount, and mark who approved anything beyond 5%. If you can’t fill the approver column from memory for more than a handful of deals, you’ve found your first rule to write down, and the four fields above are where it goes.
