# A discount policy small sales teams will actually follow

https://salesbond.app/blog/discount-policy-sales-teams/
Published: 2026-09-29 · Updated: 2026-10-25

Give reps a threshold they can use alone, require a manager’s yes above it before a quote goes out, make every discount trade for something, and record the percentage in a Pipedrive deal field so you can see it. A rule that fits on one page gets followed; a pricing framework does not.

Most small teams have no discount policy at all. They have a habit. Somebody gave a big discount to close a deal at the end of a quarter, it worked, and now it’s the unofficial price for anyone who pushes back. Nobody wrote that down, which is exactly why nobody can change it.

So here’s the small-team version: one written rule, one custom field, one saved filter, and a quarterly look at whether discounts are buying you anything. No approval matrix. No deal desk.

That covers price; for non-price terms such as payment schedule or custom clauses, [a named reviewer and a same-day answer](https://salesbond.app/blog/deal-desk-for-small-sales-teams/) is the one-page version.

## Why reps discount (it’s rarely greed)

Watch a rep offer a discount on a call and you’ll usually see relief, not strategy. The buyer said “that’s more than we budgeted,” the silence got uncomfortable, and a lower number made the silence stop. The discount wasn’t a pricing decision. It was a way out of a conversation the rep didn’t know how to continue.

That’s why we treat discounting as a symptom first. When a rep can’t say what the product changes for this buyer, in the buyer’s own terms, price is the only lever left. Cut it and the objection goes away for now. The deal still closes at a lower value, and sometimes later than it would have anyway. It also helps to know [how to answer the price question before a discount enters the talk](https://salesbond.app/blog/first-call-price-question-pipedrive/). The real fix sits in how reps handle the price objection itself; we wrote up a way to [log objections in Pipedrive and coach from them](https://salesbond.app/blog/objection-handling-pipedrive-log-coach/) so you’re not guessing which conversations go wrong.

Two other drivers are on the manager, not the rep. The first is ambiguity: with no stated limit, every rep invents one, and the most generous rep sets the market. The second is invisibility. If the discount lives in a PDF quote and nowhere else, you won’t see a pattern until the margin report at the end of the quarter, and by then it’s history.

A policy can’t fix a weak value conversation. It can remove the ambiguity and the invisibility, and it can make the discount cost the buyer something. That alone slows the reflex down.

## The one-page discount approval rule

A sales discount policy is a written rule for how much a rep can discount alone, who approves more, and what the buyer gives in return. That’s all it needs to be. If yours runs to a second page, something on it is there for the manager’s comfort rather than the rep’s clarity.

![A visual representation of discount tracking in Pipedrive.](https://salesbond.app/wp-content/uploads/2026/09/discount-policy-for-sales-team-2.png)

Start with the threshold. Pick one number, X%, that a rep can give without asking anyone, and write it as a percentage off list price so there’s no argument about what it means. We’re deliberately not giving you a number. The right one depends on your margins, and a benchmark copied from someone else’s blog is how the most generous rep ends up setting policy again. Choose it, write it down, revisit it at the quarterly check below.

Then name the approver and the moment. Above X%, one named person says yes; on a small team that’s the sales manager or the founder. The approval happens *before the quote goes out*, and it’s written as a note on the deal, not given in a hallway. One sentence is enough: “Approved above the limit because they’re prepaying the year.” A [discounted quote should carry an expiration date](https://salesbond.app/blog/quote-expiry-validity-date-pipedrive/), so the exception does not outlive the deal it was approved for.

Last, the give-get. Every discount, including the small ones a rep gives alone, trades for something the business values:

- a longer contract term;
- payment up front instead of monthly;
- a signature by a specific date;
- a case study or reference call, if that actually matters to you.

Reps push back on this part hardest, and its the part that does the most work. A discount that costs the buyer nothing gets requested every time. One that asks them to commit to a term or prepay forces a real decision on their side, and some buyers, given that choice, will pay list price rather than sign for longer. You only find out which ones by asking. [Longer payment terms](https://salesbond.app/blog/net-60-payment-terms-request-pipedrive/) work the same way: they cost money, so they need a give-get too. The sentence a rep says out loud when the buyer asks is in [how to trade concessions in a sales negotiation](https://salesbond.app/blog/sales-negotiation-trade-concessions-pipedrive/).

Print the rule, pin it in the team channel, and read it out once at a team meeting so nobody can say they didn’t know.

## Making discounts visible in Pipedrive

The policy is words. What makes it stick is that every discount shows up somewhere a manager looks every week, and in Pipedrive that’s a few minutes of setup.

1. Create the field. Open the account menu in the upper right corner, go to Personal preferences > Data fields, pick the Lead/deal tab and click “+ Custom field”. Name it “Discount %” and choose the Numerical type. Pipedrive has no percentage type, so the name carries the unit: reps type 12 for 12% off list, matching the wording in your policy. Only users with the right global permissions can add custom fields, so on most accounts this is an admin job.
2. Get reps to fill it in when they build the quote, not afterward. If your pipeline has a “Proposal sent” stage, that’s the natural point to make it expected.
3. Agree on the default. A deal with no discount gets 0, not a blank. Blanks make it impossible to tell “full price” from “forgot to fill it in.”
4. Save a filter for deals over the limit. In the deals list view, open the filter drop-down in the top right corner, click “+ Add new filter”, then “Add condition” twice: Status is Open, and Discount % is greater than X. Give it a name the whole team understands, like “Over discount limit”, set who can see it, and save.
5. Check that filter against deal notes. Every deal in it should have an approval note. The ones that don’t are your conversation for this week’s pipeline review.
6. Add the column to the list view you already use. Click the gear icon in the top right of the list view and tick Discount %. Seeing it next to deal value and stage beats a separate report nobody opens. To see what a discount does to [deal margin on the card](https://salesbond.app/blog/pipedrive-formula-fields-deal-margin/), add a cost field and one formula.

The filter is the enforcement. You don’t police quotes; you open one list once a week and ask about the deals that have no note. The same column also shows which customers already pay below list, worth knowing before a [price increase letter](https://salesbond.app/blog/price-increase-customers-pipedrive/) goes out.

If you already track [why deals are lost in Pipedrive](https://salesbond.app/blog/pipedrive-lost-reasons/), compare how often “price” shows up there with how often you’re discounting. A team that discounts a lot and still loses on price has a value problem, not a pricing problem.

## Do discounts buy speed? A quarterly check

The usual defence of a discount is that it gets the deal closed faster. Sometimes it does. Often nobody has checked. Once the Discount % field has a quarter of data behind it, you can.

Export closed deals for the the quarter with three columns: Discount %, won or lost, and days from creation to close. Split them into two groups, deals with no discount and deals with one, and compare the win rate and the median days to close.

If you only need the average discount by rep, Insights can show it without an export; see [averaging a custom field in Pipedrive Insights](https://salesbond.app/blog/pipedrive-insights-custom-field-averages/).

A hypothetical example, to show the shape of the answer and not a benchmark: say a team closed 40 deals last quarter. The 25 with no discount took a median of 34 days to close. The 15 with a discount took a median of 37. In that team’s case the discount bought nothing on speed, and the next team meeting writes itself. We gave margin away and the deals weren’t any faster, so either the give-get needs enforcing or X% is set too high.

Your numbers might say the opposite. That’s fine; the point is to have numbers at all. Read them with two cautions. Small samples lie: on a team closing a few dozen deals a quarter, one or two big accounts can swing the median. And discounted deals are often the harder ones to begin with, so a slower close doesn’t prove the discount caused it. Treat the result as a question for the team, not a verdict.

If you score deals already, a [deal health score](https://salesbond.app/blog/deal-health-score/) makes a useful third column here. It tells you whether the discounted deals were shaky before anybody touched the price.

## When the policy should bend

Some deals should break the rule. Better to say which ones up front than to argue about each exception as it comes.

A strategic logo you’d put on your homepage is one. A multi-year prepaid deal where the give-get is already enormous is another. A renewal where the account is genuinely at risk of leaving might be a third. Write these down as named exceptions, still approved by the same person, still noted on the deal. An exception with a note is part of the policy. An exception without a note is how the policy dies.

Be suspicious of the deal where the discount is the only thing moving. One contact, no timeline, a request for a lower price: the discount won’t rescue that. It’s usually a [single-threaded deal](https://salesbond.app/blog/single-threaded-deals/) with a price objection standing in for a missing champion, and more discount just makes it a cheaper loss.

Then there’s X% itself. Look at it every quarter, alongside the check above. If nearly every deal lands in “Over discount limit”, the threshold is fiction and reps have learned that approval is automatic. If nobody ever gets near it, you’ve probably set it higher than you need to. Either way the fix is one number on one page, which is the whole reason to keep the page short.