Measure it correctly or not at all
Three rules make the number honest.
Start the clock at submission. Not when a reviewer opens the ticket. The wait a rep experiences includes the queue. Stop it at decision, not at acknowledgment. A reply saying the request is under review is not a decision. Report the 90th percentile alongside the median. A median of four hours with a tail of five days means most reps have a fine experience and the ones with complex deals have a terrible one. The tail is what gets discussed in sales meetings.Break the report down by request type. A blended average across standard discounts and custom contract structures describes neither.
Set the SLA per request type
| Request type | What drives the time |
|---|---|
| Discount inside a standing band | Should be automatic, no human in the path |
| Discount past the band | One approver, one decision |
| Non-standard payment terms | Finance review, sometimes revenue recognition |
| Legal redlines | Counsel availability, precedent lookup |
| Custom deal structure | Multiple owners, genuine judgment |
Slow turnaround pushes deals
Approvals granted after a rep's stated close date move revenue into the next period. ORM identifies a rep changing the close date as the strongest single signal of deal slippage, and a pending approval is one of the common reasons that date gets changed.
The pattern is easy to miss because the deal usually still closes. It closes late, in a quarter that was already forecast, which turns an operational delay into a forecast miss. Cross-reference approval timestamps against close date changes for one quarter and you will see how much of your slippage is self-inflicted.
Fixes that hold
Auto-approve inside the standing bands so the desk only sees exceptions. Route independent approvers in parallel rather than as a chain. Name a backup for every approver so one calendar cannot hold a quote. Keep a precedent library, so a structure the desk approved twice last quarter gets the same answer in minutes rather than a fresh debate.
Then watch the trend rather than the point value. Rising turnaround usually means volume grew or thresholds went stale, and both are fixable before reps start negotiating outside the process. See sales velocity for how approval delay compounds through the rest of the cycle.
Frequently Asked Questions
How do you measure deal desk turnaround time?
Clock starts when a complete request is submitted and stops when the rep has a decision, not when the reviewer opens the ticket. Report it by request type and at the 90th percentile as well as the median, because the slow tail is what reps experience and complain about.
What is a reasonable deal desk SLA?
Set it per request type rather than as a single number. A standard discount inside a documented band should clear same day or automatically. A custom contract structure needing legal and finance review reasonably takes longer. One blended SLA either overpromises on complex work or underdelivers on simple work.
Why does deal desk turnaround time matter to the forecast?
Because approvals that land after a rep's stated close date push the deal into the next period. Slow turnaround is one of the upstream causes of slipped deals, and it shows up in the forecast as a quarter that misses on timing rather than on demand.
How do you speed up a deal desk without losing control?
Auto-approve everything inside the standing bands, route independent approvers in parallel instead of in a chain, name a backup for every approver, and keep a precedent library so similar requests get the same answer without a fresh review.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like deal desk turnaround time into prescriptive action for your team.
Schedule a Demo