deal desk

Deal desk software: what the desk decides, which tools run it, and where legal fits

Tomas ArkwrightLegal technology writer10 min read

Written by Tomas Arkwright A deal desk is the small group that says yes, no, or "yes if" to sales deals that fall outside standard pricing and terms. Deal desk software is the workflow that gets those deals in front of the right people, records what was decided and why, and stops a quote going out before it is approved. Most companies searching for a deal desk tool are really asking three questions at once: what should the desk decide, which product should route the decisions, and how does legal's review of non-standard terms fit without becoming the slowest step. ## What a deal desk decides, and what it should not The desk exists to make exception decisions fast and consistently. Its scope varies, but a sensible split looks like this. | Decision | Usually owned by | Escalates when | |---|---|---| | Discount beyond the rep's authority | Sales leadership via the deal desk | Discount crosses the next band in the approval matrix | | Payment terms (net days, annual vs monthly billing, milestones) | Finance | Terms push cash collection beyond policy | | Bundles, free months, custom SKUs | Deal desk with product or pricing owner | The offer creates a new pricing precedent | | Multi-year commitments and price protection | Finance and sales leadership | Price locks run past the planning horizon | | Revenue recognition impact | Finance or revenue accounting | Terms create acceptance, refund or contingent clauses | | Non-standard legal terms | Legal | The customer's redline moves outside the playbook | | Data, security and privacy commitments | Legal with security | The customer asks for terms the product cannot support | What the desk should not do is negotiate legal language itself. When a deal desk analyst starts editing an indemnity clause to save time, the company has quietly moved a legal judgement to someone not trained to make it. ## The approval matrix is the real product Before choosing any deal desk platform, write the approval matrix on one page. It answers, for each lever, who can approve what. A simplified example for a software company: | Lever | Rep can approve | Sales manager | Deal desk and VP Sales | CFO | Legal | |---|---|---|---|---|---| | Discount | Up to the first band | Up to the second band | Up to the third band | Above the third band | Not involved | | Payment terms | Standard terms | One step longer | Two steps longer | Anything else | Not involved | | Contract length | One year | Up to three years | Longer with price protection | Over five years | Reviews term and termination clauses | | Liability cap | Standard cap | Not authorised | Not authorised | Commercial sign-off on higher caps | Approves any change | | Customer paper instead of ours | Not authorised | Not authorised | Agrees in principle | Not involved | Reviews and negotiates | The bands are yours to set. The point is that every cell has an owner, and the software only enforces what the matrix already says. Our contract approval matrix guide covers designing one for contracts more broadly. ## The tool types that run a deal desk There is no single "deal desk" product category. Teams assemble the desk from one of these. CPQ suites. Configure, price, quote software, which Salesforce defines on its CPQ explainer as software that lets sales staff assemble offerings, enforce pricing and discount policies and route sign-offs, builds the quote from a product catalogue, applies pricing rules, and routes out-of-policy quotes for approval. Conga CPQ describes showing sellers which discounts are acceptable and routing out-of-policy discounts into automated approval workflows. Salesforce sold CPQ for years on its CRM; its own migration page now says Salesforce CPQ is end of sale, not end of life, and points customers to Revenue Cloud. If you are buying fresh on Salesforce, that changes which product you evaluate. Quote-to-revenue platforms. These link quoting, contracts, subscriptions and billing under one set of rules. DealHub describes a platform covering CPQ, contract lifecycle, subscriptions and billing, with an approval agent that routes exceptions to the right approver so the desk reviews exceptions instead of every order form. CRM-native approval workflows. Many companies start with the approval engine already in their CRM: an approval process on the opportunity or quote object, a required field for discount justification, and a report of pending approvals. Cheap and fast, but it strains once products, currencies and pricing models multiply. General workflow and ticketing tools. Some desks run from a request form and a ticket queue. This works for low volume and gives a clean audit trail, but the quote and the approval live in different systems, so someone has to check they match. | Tool type | Best for | Watch out for | |---|---|---| | CPQ suite | Complex catalogues, many pricing rules, high quote volume | Implementation effort; catalogue upkeep | | Quote-to-revenue platform | Subscription businesses wanting quote, contract and billing linked | Overlap with existing billing or contract tools | | CRM approval workflow | Early-stage desks, simple pricing | Becomes brittle with many products and exceptions | | Ticketing or forms | Low volume, mixed deal types | Quote and approval held in separate places | ## Where legal sits in the flow Legal touches perhaps a minority of deals, but those deals are usually the largest and slowest. Three points decide whether legal speeds the desk up or holds it back. 1. A written playbook with fallbacks. For each clause that customers commonly push on (liability cap, indemnity scope, termination for convenience, data processing, audit rights, governing law), legal writes the standard position, one or two acceptable fallbacks, and the line it will not cross. With that in hand, the desk can tell a rep "fallback one is pre-approved" without a legal ticket. Our explainer on playbooks and fallback positions shows how to structure them. 2. A clear trigger for legal review. Legal should be pulled in by rule, not by instinct: customer paper, any change outside the playbook, specific products (for example those processing sensitive data), or deal size above a threshold. Everything else flows past legal entirely. 3. A turnaround target legal can meet. Set a target time for first redline, measured from complete request to response, and report it. A desk that cannot predict legal's turnaround cannot forecast close dates. If legal is consistently the bottleneck, see our piece on unblocking legal in the deal cycle. The decision record matters too. When legal agrees a non-standard cap for one customer, the deal desk should be able to see it on the deal, and the next rep asking for the same thing should find the precedent. ## One enterprise deal, start to finish A worked example shows how the pieces connect. A rep is closing a three-year subscription with a large retailer. The customer wants a discount one band above the rep's authority, quarterly instead of annual billing, and has sent back the order form with its own master services agreement attached. The rep submits the quote. The approval engine sees two triggers: the discount band and the billing change. It routes the discount to the deal desk and VP Sales, and the billing change to finance. Both approve within a day, the VP with a note that the discount is conditional on the three-year term. The customer paper trips a third trigger: legal review. Legal reads the retailer's MSA against the playbook. Most terms are acceptable or have a pre-approved fallback. Two are not: an uncapped indemnity for any data breach, and a termination for convenience right on 30 days' notice that would undo the multi-year discount. Legal proposes a cap tied to fees for the indemnity and deletes the convenience right, offering instead a termination right if service levels are missed. The redline goes back with a short cover note. The customer accepts the indemnity cap but insists on some exit right. Legal and the deal desk agree together: a convenience right after year one, with the discount repaid pro rata if exercised. That is both a legal and a commercial decision, so both owners sign off on the deal record. Total time from quote to agreed terms is a week, and every decision is recorded where the next rep can find it. Without the matrix, the same deal tends to take a month of email and leaves no precedent behind. ## What a deal desk should report each month - Approval cycle time by lever, from request to decision.

  • Exception rate: share of deals needing any approval, tracked as a trend rather than a target.
  • Legal turnaround on the deals that reached legal, from complete request to first redline.
  • Repeat exceptions: requests that recur often enough to become a new standard or a pre-approved fallback.
  • Leakage: signed deals whose terms differ from what was approved. These numbers turn the desk from a gate into a feedback loop that keeps the pricing policy and the legal playbook current. ## Signs your deal desk tool is failing - Approvals are given in chat and later typed into the CRM, if at all.
  • Reps cannot see what they are allowed to offer without asking.
  • Finance finds signed contracts with discounts or terms nobody approved.
  • The same non-standard request is escalated again and again with no change to the playbook.
  • Legal and the desk keep separate trackers for the same deals.
  • Quarter end produces a pile of approvals that sat for days. Each of these points at a process or matrix gap first. Changing software without fixing the matrix moves the same mess into a new screen. ## Rolling out a desk in a quarter 1. Weeks 1 to 2: Pull the last two quarters of closed deals. List every exception granted, who approved it and how long it took.
  1. Weeks 3 to 4: Write the approval matrix and the legal playbook for the five most negotiated clauses.
  2. Weeks 5 to 8: Configure approvals in your existing CRM or CPQ before buying anything new. Measure approval time.
  3. Weeks 9 to 12: Decide whether the existing tools hold. Buy a dedicated platform only if volume or pricing complexity has clearly outgrown them. Keep the legal playbook on the same review cycle as the pricing policy, so a fallback that sales keeps asking for gets a decision instead of another escalation. ## Adira covers legal's lane, not the desk Adira is not CPQ and not a deal desk platform; it does not build quotes, apply pricing rules or route discount approvals, and we claim no connection to any CRM or CPQ product. If your desk needs quoting and pricing approvals, choose one of the tool types above. Where Adira helps is legal's part of the flow. When a customer sends its own paper or a heavy redline, Adira's Document Intelligence Dashboard marks each position as favourable, neutral or unfavourable to your company and lists red flags and missing clauses, which gives legal a fast first read before checking the draft against its playbook. Clause-Level Editing lets a lawyer type an instruction such as "cap liability at 12 months of fees" in plain English and get the precise edit back as a diff. The Company Persona carries your preferred terms and risk posture into drafts. The result is exported to Word or PDF to send back to the customer. Pricing is published at adiralaw.com: from USD 89 per seat per month billed annually, minimum three seats, with a 7-day free trial.

Frequently asked questions

Is a deal desk a team or a piece of software?
It is a team and a process first. Deal desk software is whatever routes non-standard deals to that team and records the decisions: often the approval engine in a CPQ product or CRM, sometimes a dedicated quote-to-revenue platform. A company can run a deal desk with no special software at all while volumes are low.
Does a deal desk replace legal review of sales contracts?
No. The deal desk decides commercial questions such as discount, payment terms and bundling. Legal still decides non-standard legal terms such as liability caps, indemnities and data clauses. A good desk routes each question to the right owner and keeps both decisions on the same deal record.
When does a company need a deal desk platform?
Usually when approvals start happening in chat and email, when reps cannot tell what they are allowed to offer, or when finance finds signed deals that nobody approved. Those signs tend to appear once there are several sales teams or many products and pricing models.
Can CPQ handle legal clause approvals?
CPQ tools focus on product configuration, pricing and quote approval. Some quote-to-revenue platforms add contract generation, but negotiation of counterparty redlines and clause fallbacks is usually handled by legal in a contract tool, with the outcome reported back to the deal record.
Was this useful?

See how Adira drafts in your voice and reads contracts from your side.

Explore the showroom

Working through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.

Try Weave — free

Book a demo

See Adira on your own contracts

A 30-minute walkthrough with our team. Tell us a little about you, then pick a time that suits you.

Prefer email? [email protected]