On this page
A deal desk does more than approve discounts. It changes which opportunities reach the forecast, which customers enter the base and which future retention numbers look healthy.
That selection is easy to miss because the desk appears late in the process. A rep qualifies the opportunity, the desk reviews the commercial terms, and the CRM records an approval. For this review, treat the approved deal as an opportunity that has passed two filters: the seller’s judgment and the desk’s judgment. That is an operating model, not a universal description of every desk.
Why does a deal desk approval queue represent a non-random sample?
Every filter creates a population. A desk that sees only non-standard, high-value or high-risk deals does not provide evidence about the average deal. A desk that is required for every opportunity still changes behaviour before the review: sellers learn which terms will pass and which customers are not worth presenting.
The right question is therefore not only whether the desk approved the deal. It is what the desk was allowed to select, what it was trying to protect and what happened to the accounts it rejected or never escalated.
| Job | Visible record | Hidden effect | Evidence to retain |
|---|---|---|---|
| Commercial control | Approval, discount, term and exception | Sellers learn which deals and concessions are admissible | Original request, not only final terms |
| Selection | Opportunity enters, changes path or exits | The approved population differs from the funnel population | Rejected, withdrawn and desk-bypassed opportunities |
| Relationship protection | Fit, handoff and ownership discussion | A deal can be financially attractive and operationally fragile | Sponsor, service burden and relationship map |
| Learning | Reason code and outcome review | The desk can improve future qualification or merely add delay | Post-sale outcome linked to original decision |
Table 1A deal desk has two jobs
Approval is the visible action. Selection and learning are the effects that need their own fields.
Source: Author's operational synthesis. The rows are a framework, not a finding of one source.
This is the same reason the one number a commercial team should share needs a defined denominator. A number without its population is not neutral. It is an invitation to compare unlike decisions.
Discount approval is not customer fit
A desk can prevent an unpriced concession and still approve a poor customer. Price is one condition of the deal. It is not a proxy for the customer’s implementation burden, the number of stakeholders who will need support, or the relationship’s portability after the initial seller leaves.
The discount that outlives the deal shows the commercial memory created by a concession. The desk should therefore record what the concession buys: volume, term, reference rights, speed of payment, scope discipline or nothing. A discount without a defined exchange is not a strategy that failed later. It is an approval that never named its exchange.
The desk also needs an explicit fit decision. If the customer requires a service pattern the organisation cannot maintain, a higher price may not solve the problem. If the customer selected the seller because of one person’s personal relationship, a standard handoff may alter the risk after the deal closes.
The selection can corrupt the metrics
Suppose desk-approved deals retain at 95%. That sounds strong until the denominator is rebuilt. Perhaps the desk rejects low-fit customers before they enter the base. Perhaps the approved segment has longer terms. Perhaps the desk sees only enterprise accounts with a dedicated implementation team. The 95% may be real and still not be the right input for the whole funnel.
The same issue appears in win rate. If a desk removes opportunities with weak fit, the win rate can rise because the organisation improved qualification, because it improved pricing or because it stopped counting difficult cases. Those are different achievements.
The remedy is not to remove the desk. It is to keep the pre-filter population. The desk becomes useful when leadership can see the decision boundary it created.
| Field | Example answer | Why it matters |
|---|---|---|
| Customer problem | Named operational problem and required outcome | Keeps the desk from approving a price without a use case |
| Requested exception | 18% discount, annual prepay, custom implementation | Makes the trade visible |
| Exchange | Two-year term and reference permission | Distinguishes an exchange from erosion |
| Selection reason | Strategic segment, fit risk, or seller escalation | Shows which population is being filtered |
| Relationship ownership | Firm, named rep, partner or mixed | Flags portability risk |
| First-year cost | Onboarding, service, support and integration | Protects contribution margin |
| Review date | 90 days after go-live and at renewal | Creates the learning loop |
Table 2The deal desk decision record
The record makes the approval explainable after the quarter that created it has ended.
Source: Author's worksheet, informed by the relationship and pricing studies cited below.
How can a deal desk learn from rejected discount requests?
Most approval workflows review wins. That is the fastest way to make the desk look effective. The learning set also needs rejected opportunities, deals that bypassed the process, customers that churned early and customers that expanded despite a difficult start.
The outcome review should ask four questions:
- Did the exchange survive the contract?
- Did the customer use the product or service in the way the qualification assumed?
- Was the first-year cost inside the contribution model?
- Did the relationship remain attached to the firm or to one seller?
The answers turn approval into a commercial instrument. Without them, the desk is a queue with authority. With them, it can improve qualification, pricing and handoff.
This is also why what the customer relationship costs while it stays belongs beside a deal-desk review. A deal that looks attractive because it retains revenue can still carry a personal relationship, a selection mechanism or a service burden that the desk never priced.
The deal desk is not the place where commercial judgment disappears into a policy. It is the place where judgment becomes visible. Record the population it filters, the exchange it approves, the relationship it relies on and the outcome that would prove the decision wrong.
Evidence base. The analytical frame also draws on these additional sources: Kim et al. 2019; Palmatier et al. 2007; Schmitz et al. 2020; Shi et al. 2017. The links identify the exact works; they support the mechanisms and boundary conditions discussed here, not every claim in isolation.
References
- Kim, M., Sudhir, K., Uetake, K., & Canales, R. (2019). When salespeople manage customer relationships: Multidimensional incentives and private information. Journal of Marketing Research, 56(5), 749–766. https://doi.org/10.1177/0022243719847661
- Palmatier, R. W., Scheer, L. K., & Steenkamp, J.-B. E. M. (2007). Customer loyalty to whom? Managing the benefits and risks of salesperson-owned loyalty. Journal of Marketing Research, 44(2), 185–199. https://doi.org/10.1509/jmkr.44.2.185
- Schmitz, C., Friess, M., Alavi, S., & Habel, J. (2020). Understanding the impact of relationship disruptions. Journal of Marketing, 84(1), 66–87. https://doi.org/10.1177/0022242919882630
- Shi, H., Sridhar, S., Grewal, R., & Lilien, G. (2017). Sales representative departures and customer reassignment strategies in business-to-business markets. Journal of Marketing, 81(2), 25–44. https://doi.org/10.1509/jm.15.0358
