# Deal Desk — Standard Operating Procedure > Source: https://b2bprocess.com/deal-desk > Last updated: 2026-07-08. Adapt owners, tools, and thresholds to your organization. ## 1. Purpose A deal desk is the cross-functional process (and usually the team) that reviews, structures, and approves deals that deviate from standard terms — non-standard discounts, custom payment schedules, atypical contract language, unusual product bundles, ramped pricing, or strategic exceptions. It sits at the junction of sales, finance, legal, and product, replacing ad-hoc email approval chains with defined thresholds, routing, and turnaround SLAs. ## 2. Scope & prerequisites Introduce a formal deal desk when non-standard requests become weekly — typically alongside a move upmarket, multi-product pricing, or the first finance complaints about revenue-recognition surprises. Prerequisites: a published price book, standard contract templates, and defined discount authority levels. ## 3. Roles & responsibilities | Role | Responsibility | | --- | --- | | Deal Desk analyst/manager | Runs intake, review, structuring, shepherding, documentation, and analytics. | | Sales rep / AE | Brings deals early with full context; sells the approved structure, not private promises. | | Finance | Approves margin/payment-term thresholds; owns revenue-recognition rulings. | | Legal | Owns clause deviations, fallback library, and contract risk. | | Sales leadership | Holds the line on desk authority; approves top-tier strategic exceptions. | | Product / Delivery (as needed) | Signs off on any promised functionality, capacity, or service exception. | ## 4. Procedure ### Step 1: Define standard — so 'non-standard' means something **Owner:** Deal Desk / RevOps + Finance Publish the standard box: price book, discount bands by segment and deal size, payment terms, contract templates, and the approved order-form clauses. Deals inside the box need no desk at all — the desk's first job is to maximize what never reaches it. - [ ] Publish price book and self-serve discount authority (e.g., rep 0–10%, manager to 20%) - [ ] Standardize order form and MSA templates with legal - [ ] Define what auto-approves vs. what must come to the desk ### Step 2: Set the approval matrix **Owner:** Deal Desk + Finance + Legal One matrix mapping each deviation type and size to its approver chain: discount depth, payment terms, non-standard legal clauses, custom SLAs, product exceptions, revenue-recognition-sensitive structures. Approvals run in parallel where possible; every threshold has exactly one accountable approver, not a committee. - [ ] Map deviation types → approvers → SLA per tier - [ ] Route rev-rec-affecting terms to finance always - [ ] Cap total approval chain length; escalate to one executive for the rest ### Step 3: Intake through one door **Owner:** Deal Desk All non-standard requests arrive through a single channel — a CPQ workflow or a structured request form — with required context: account, products, proposed structure, justification, competitive situation, and close date. Side-channel Slack approvals are politely redirected until they stop happening. ### Step 4: Review for economics, risk, and precedent **Owner:** Deal Desk The desk evaluates each request on margin impact, revenue-recognition consequences, legal risk, operational deliverability, and — most undervalued — precedent: this discount at renewal time, this clause in front of the customer's procurement next year, this exception cited by the next rep. The desk's institutional memory is its core asset. - [ ] Check the ask against comparable closed deals and the customer's history - [ ] Model multi-year and renewal implications, not just first-order bookings - [ ] Consult product/delivery on any promised functionality or service exceptions ### Step 5: Counter-structure, don't just approve/deny **Owner:** Deal Desk The desk's highest value move is the alternative structure: trade discount for a longer term or upfront payment, swap a price cut for a contraction-protected ramp, convert a custom clause into an approved fallback. Reps learn to bring the desk in early — during negotiation, not after handshake — when the desk reliably makes deals better rather than merely policing them. ### Step 6: Decide within the SLA **Owner:** Deal Desk + approvers Standard requests: same or next business day. Complex multi-approver deals: 2–3 business days with active shepherding by the desk. Quarter-end surge staffing is planned, not improvised. A desk that misses its SLAs teaches sales to route around it, which recreates the chaos it was built to end. ### Step 7: Document every exception **Owner:** Deal Desk Each approved deviation is recorded on the opportunity: what was granted, why, who approved, and any renewal implications (e.g., discount expires, price steps up). This record feeds renewal negotiations, audit trails, and the analytics in the next step. - [ ] Structured exception log tied to the CRM opportunity - [ ] Renewal-relevant terms flagged to the CS/AM team automatically - [ ] Approval audit trail retained for finance and auditors ### Step 8: Analyze and shrink the exception surface **Owner:** Deal Desk / RevOps Quarterly: discount trends by segment and rep, most-requested exceptions, approval cycle times, win rates with and without concessions, realized-vs-list pricing. Recurring exceptions become standard offerings or standard fallbacks; pricing feedback goes to the pricing owner. The desk should be shrinking its own queue. - [ ] Report discount depth and approval latency by segment/rep - [ ] Convert top recurring exceptions into pre-approved options - [ ] Feed win/loss pricing signal to pricing and product marketing ## 5. Metrics to monitor | Metric | Definition | Formula | Target | | --- | --- | --- | --- | | Approval turnaround time | Time from request submission to final decision. | Decision timestamp − intake timestamp (median, p90) | < 1 business day standard; < 3 complex | | Average discount depth | Realized discount vs. list, by segment — the economics the desk defends. | (List − sold price) ÷ list, weighted | trend-stable or improving; investigate creep | | Exception rate | Share of deals requiring desk review — the size of the non-standard surface. | Desk-reviewed deals ÷ closed deals | declining over time as standards absorb patterns | | First-pass approval rate | Requests approved without rework — a proxy for rep education and rule clarity. | Approved as submitted ÷ requests | > 70% | | Quarter-end cycle time delta | How much slower approvals get in the last two weeks of the quarter — the desk's stress test. | Quarter-end median TAT ÷ mid-quarter median TAT | < 1.5× | | Win rate on desk-structured deals | Whether desk involvement helps or hinders closing — the desk's value evidence. | Wins ÷ desk-reviewed opportunities vs. baseline | ≥ comparable non-desk deals | ## 6. Known failure modes | Failure | Symptom | Corrective action | | --- | --- | --- | | The desk as Department of No | Reps hide deals from the desk until signature, then present faits accomplis; exceptions surface in billing. | Measure and market the desk on deals improved and cycle time, not catches; counter-structure as the default response; engage-early SLA guarantees. | | Approval archaeology | Five serial approvers, each waiting on the last; a 15% discount takes nine days; deals die in the queue. | Parallel routing, single accountable approver per threshold, auto-escalation on SLA breach, and ruthless matrix pruning. | | Discount authority nobody respects | Every deal gets 'exceptional' pricing; the price book is fiction; renewal anchors are ruined for years. | Enforce bands in CPQ so out-of-band quotes physically require approval; report discount depth by rep to sales leadership monthly. | | Undocumented exceptions | Renewal team discovers a hidden 40% discount, expiring clause, or promised feature at the worst moment. | Structured exception log on the opportunity, with renewal-relevant terms auto-flagged to the post-sale team. | | Rev-rec surprises | Finance unwinds bookings after close because a payment schedule or acceptance clause broke recognition rules. | Finance holds mandatory approval on all rev-rec-sensitive structures; train the desk to spot them at intake. | | Quarter-end meltdown | 60% of requests land in week 13; SLAs collapse exactly when deals are most fragile. | Early-submission incentives, pre-approved fallback structures for common quarter-end asks, and surge coverage planned in advance. | | The desk never learns | The same exception is hand-approved 60 times a year and never becomes a standard option. | Quarterly exception analytics with a standing rule: any deviation seen more than N times gets productized or pre-approved. | --- This SOP is maintained as part of the B2B process encyclopedia at https://b2bprocess.com. Check the source page for the latest revision.