A deal desk exists to help close complex deals faster while protecting margin. In practice, many deal desks become the opposite: a bureaucratic checkpoint that slows deals down, creates friction between sales and finance, and costs more in lost velocity than it saves in discount protection.
Done right, a deal desk is one of the highest-leverage RevOps investments you can make. Here's what good deal desk design looks like.
What a Deal Desk Actually Does
A deal desk is a cross-functional team (typically sales, finance, legal, and sometimes RevOps) that supports non-standard deal structuring. The "desk" part is a bit of a misnomer — it's really a process and a set of decision rules, not necessarily a physical team.
The core functions: pricing and discount approval, non-standard contract terms review, bundling and configuration decisions on complex deals, and revenue recognition guidance for unusual deal structures. Deal desks exist because complex enterprise deals have pricing, legal, and financial implications that a rep shouldn't be navigating alone — and that a single sign-off from a manager often can't adequately address.
The Most Common Deal Desk Failure Mode
The failure mode is universally the same: a deal desk with no SLA, no clear ownership, and no standardized process. A rep submits a deal for review. Nobody knows exactly who needs to approve it or in what order. Legal has questions. Finance has questions. The rep answers them on different timelines. The prospect waits. The deal slips.
This failure mode is so common because deal desks are often created reactively — a few bad deals happen, leadership decides there needs to be a review process, and a process is stood up without being designed. The result is a gate without a path.
Designing a Deal Desk That Works
Define What Goes Through the Desk
Not every deal should require deal desk review. The first design decision is what triggers a deal desk submission. Common triggers: any discount over 20%, any non-standard payment terms, any multi-year deal, any deal over a certain ACV threshold, any deal that includes non-standard contract language.
Write these triggers down. Make them explicit. If reps don't know exactly what requires deal desk involvement, they'll either submit everything (overwhelming the desk) or submit nothing (defeating the purpose).
Set an SLA — and Hold It
Every deal desk process needs a published SLA. Standard deal desk review: 24 business hours. Complex deal desk review (unusual contract terms, significant discounts): 48-72 business hours. Emergency reviews for deals closing this week: 4 business hours with a designated emergency contact.
Publish the SLA. Track it. Report on it in your RevOps metrics. A deal desk that misses its SLA is creating deal velocity problems — and that needs to be visible to leadership, not hidden in a process nobody's watching.
Build a Submission Template
A deal desk submission should include: the deal overview (who, what, how much), the non-standard elements requiring review (what exactly needs approval), the competitive context if relevant, the rep's recommendation, and the business justification for the exception being requested.
A standardized submission template does two things: it ensures the reviewers have the information they need to make a decision quickly, and it forces the rep to think through the business case for the exception before asking for it. Many bad discount requests die in the template — which is exactly what should happen.
Define the Decision Authority Matrix
Every type of deal desk decision should have a named owner. Who approves a 25% discount? Who approves a net-90 payment term? Who approves a non-standard data processing addendum? The answer to these questions should be documented and accessible to reps before they submit — so they know who will be reviewing their deal and can loop in the right stakeholders proactively.
Metrics That Tell You If Your Deal Desk Is Working
- Average deal desk cycle time — how long from submission to approval?
- SLA compliance rate — what percentage of submissions are resolved within the published SLA?
- Deal desk submission volume by trigger — are some triggers overloaded?
- Approved vs. rejected submission rate — is the desk approving everything (no value) or rejecting too much (blocking revenue)?
- Average discount on deal-desk-reviewed deals vs. non-reviewed deals — is the desk actually protecting margin?
When to Build a Deal Desk
Most companies don't need a formal deal desk until they're doing meaningful enterprise deal volume — typically $20M+ ARR with ACV over $50K and complex enterprise contracts. Before that point, clear discount authority levels for sales leadership (rep can approve up to 10%, manager up to 20%, VP required above that) combined with basic contract review are usually sufficient.
Build the deal desk when deals are slipping because approvals are unclear, when discount levels are inconsistent across the team, or when legal review is consistently the bottleneck on enterprise deals.
Build a deal desk that closes faster, not slower.
I help mid-market and growth-stage teams design approval processes and deal desk workflows that protect margin without killing deal velocity.
Talk to Gage →