Deal Desk and Discount Approval: How to Set the Rules
Leah Clapper
A deal desk is a small team that reviews non-standard deals, and a discount approval policy is the set of rules for who may approve which price reduction.
This guide shows how to design both. It covers discount tiers, approval paths, guardrails and metrics.
What is a deal desk?
A deal desk is a cross-functional group, often in RevOps or finance, that reviews pricing, terms and structure on deals outside standard policy.
Its purpose is to keep deals fast and consistent while protecting margin and revenue quality.
A deal desk is not a gatekeeper for every deal. Standard deals follow the price list and close without review.
The desk handles exceptions. For contract workflow tooling, see the sales contract automation guide.
What is a discount approval policy?
A discount approval policy is a written rule set that states how much discount each role may give and who must approve more. It replaces case-by-case negotiation with known limits.
Policy element | Purpose |
|---|---|
Discount tiers | Define how much each role can approve |
Conditions | State what the buyer must give in return |
Approvers | Name who approves each tier |
Time limits | Set how fast approvers must respond |
Records | Log the reason for each exception |
How do you design discount tiers?
Build tiers by size of the discount and size of the deal, with higher tiers needing more senior approval. Start from your own discount history, not a figure from another company.
Tier (illustrative) | Discount range | Approver |
|---|---|---|
Standard | Within list price and published bands | Rep |
Tier 1 | Small discount | Front-line manager |
Tier 2 | Moderate discount | Sales leader |
Tier 3 | Large discount or non-standard terms | Deal desk with finance |
Choose the ranges from the distribution of discounts you gave over the last four to eight quarters. If most deals already receive a given discount, a policy that forbids it will be ignored.
What should buyers give in return for a discount?
A discount should buy something specific: a longer term, upfront payment, a larger volume, a reference or a faster close.
Giving a discount for nothing teaches buyers to ask for it.
Concession from buyer | Example give |
|---|---|
Longer contract term | Multi-year commitment |
Upfront payment | Annual billing in advance |
Larger scope | More seats or modules |
Reference or case study | Public customer reference |
Faster close | Signature by quarter end |
Write the trade list into the policy. Reps then have a script: this discount in exchange for that commitment. Do not offer a reference as a trade unless the customer has agreed to be named.
How should the approval path work?
The approval path is a fixed sequence with time limits and a single point of contact. Slow approvals cost deals, and unclear approvals cause side deals.
The rep submits the request with the deal facts.
The system or deal desk checks it against tiers.
The named approver decides within the time limit.
The decision and reason are logged.
If the time limit passes, the request escalates.
Keep the request form short. Required fields: deal size, discount requested, term, competitor, reason and what the buyer gives in return. Link the form to your CRM so the data does not need retyping.
What guardrails protect margin and quality?
Guardrails are checks that catch risky deals before they close. Set them in the policy and check them in the review.
Floor price. A price below which only the highest approver may go.
Non-standard terms list. Payment terms, termination rights or custom clauses that trigger review.
Stacking rule. Limits on combining discounts.
Renewal protection. Discounts that reset at renewal rather than lock in.
Competitive evidence. A named competitor and price when the discount is competitive.
Review the guardrails each quarter against actual deals. Rules that nobody triggers can be loosened, and rules everybody breaks need a fix or an owner.
How do you handle exceptions without slowing sales?
Decide fast on the common cases and escalate only the unusual ones. Publish the policy so reps know in advance what they can offer.
Use two speeds. Standard requests within a tier get approved within a short, stated window.
Complex deals get a deal desk review with a longer window, and reps are told which path they are on at submission. The sales management guide covers management cadence.
Which metrics show the policy works?
Track discount behavior and cycle impact, and report by rep, segment and quarter.
Metric | What it shows |
|---|---|
Average discount by segment | Whether discounting is consistent |
Share of deals discounted | How often reps discount |
Discount by approval tier | Whether tiers match reality |
Approval turnaround time | Whether approvals slow deals |
Win rate by discount band | Whether discount drives wins |
Exceptions per quarter | Policy fit |
Compare win rate by discount band carefully. Discounts may go to harder deals, so a lower win rate at high discount does not by itself prove discounts do not work. See revenue operations KPIs and sales dashboard examples for reporting layouts.
How does pricing structure reduce discounting?
Clear packaging and published price bands reduce the need for discounts. If buyers cannot tell what they pay for, they negotiate on price.
Review packaging when many deals ask for the same exception. A repeated request for one module at a lower price is a signal about packaging, not about negotiation.
See enterprise revenue agent pricing for an example of how pricing is explained on a Rox page.
Where can agents help?
Agents can pre-fill requests from CRM data, check a request against policy tiers and summarize similar past deals for the approver. Approvers decide, and a person reviews the output. Rox agents operate within user-defined parameters and require oversight. See the human in the loop guide.
What mistakes weaken a discount policy?
Tiers that ignore real history. Reps work around them.
Discounts with no trade. Buyers learn to ask.
Slow approvals. Reps agree to terms before approval.
No log of reasons. The pattern cannot be reviewed.
Lock-in of discounts at renewal. Margin erodes.
No quarterly review. The policy drifts from practice.
Conclusion
A deal desk and a written discount policy keep pricing consistent without slowing every deal. Standard deals close at list or within published bands, and exceptions follow a known path with named approvers and time limits.
Tiers should come from your own discount history, and every discount should buy a specific concession. Guardrails on floor price, terms, stacking and renewal protect margin, and a log of reasons gives the quarterly review something to examine.
Start by reading the last four quarters of deals. Find the real discount distribution, set tiers around it, list the trades and name the approvers. Review the results each quarter and adjust.
Results vary with data quality, deal mix and market conditions. Rox does not guarantee specific revenue outcomes.
Frequently asked questions
Do I need a deal desk?
Smaller teams can start with a policy and a named approver. Add a desk when exceptions grow or involve finance and legal.
How big should discount tiers be?
Base them on your own discount history.
Who should sit on the deal desk?
RevOps, finance and sales leadership, with legal as needed.
How fast should approvals be?
Publish a time limit by tier and escalate when it passes.
Should discounts be public?
Share the policy tiers with the sales team. Do not share individual customer pricing outside those who need it.
Similar Articles
We build with the best to make sure we exceed the highest standards and deliver real value.
