Deal Desk Basics: How Smaller Sales Teams Can Approve and Close Faster

"Deal desk" sounds like something only companies with 500 reps need. A whole department to manage pricing approvals? A formal review committee for every custom quote? That's enterprise territory.

But here's the reality: every sales team, even one with 10 people, runs into non-standard deals. A prospect wants 40% off the standard rate. Another needs a custom payment schedule. A third is asking for contract terms that legal has never reviewed. Without a process, each of those situations becomes a fire drill: the rep pings the VP on Slack, the VP pings the CEO, someone digs up a past exception to use as precedent, and three days pass while the prospect waits.

A deal desk doesn't need to be a department. It needs to be a documented process, a designated owner, and a set of clear thresholds. Here's how to build one that's light enough for a small team but structured enough to actually reduce approval time. It also connects directly to how you define forecast categories: a commit without a deal desk process behind it is just a rep's optimism.

---

What a Deal Desk Actually Is

A deal desk is the process and people responsible for reviewing and approving non-standard deals before they're committed to a prospect.

Gartner defines deal desks as a cross-functional capability that coordinates pricing, legal, finance, and sales to accelerate deal velocity while managing risk. Even at small team sizes, the core function is the same.

Non-standard means anything that deviates from your published pricing, standard terms, or normal contract structure. That includes:

• Discounts above your approved rep threshold
• Multi-year commitments that require financial review
• Custom payment schedules (net 90, milestone-based, etc.)
• Legal terms that aren't in your standard MSA
• Bundled pricing that doesn't exist in your rate card

Standard deals (those that fit your published pricing and contract templates) auto-approve. The rep quotes, the prospect accepts, and nobody needs to loop in a manager. The deal desk only activates for exceptions.

What a deal desk replaces: the informal approval chain that currently runs through Slack DMs, email threads with four people cc'd, and the occasional walk to the CEO's desk. Every team already has a deal desk. Most teams just don't have one that's documented or consistent.

---

Step 1: Define What Needs Desk Review

The single most useful thing you can do before building any other part of the process is write down exactly which deals require review and which don't.

Start with discount thresholds. Your deal desk will spend most of its time on pricing exceptions. Define:

Then define the other triggers. Non-discount situations that require review:

• Payment schedules longer than net 30
• Multi-year deals above $X in total contract value
• Custom legal terms (any changes to your standard MSA)
• Deals involving security reviews, data processing agreements, or compliance attestations
• Any deal where the rep has verbally committed to something not in the standard template

Write these down in a single reference document and share it with every rep. The goal is that any rep can self-determine whether their deal needs desk review without asking a manager. If they have to ask, your thresholds aren't clear enough. This is the same principle behind building a sales process one deal type at a time: explicit criteria beat informal judgment every time.

---

Step 2: Assign a Deal Desk Owner

Not a committee. One person.

In a 10-30 person sales team, the deal desk owner is usually the Head of Sales Operations, a senior sales manager, or the VP of Sales themselves if those roles don't exist. The owner is the person who receives submissions, runs the approval process, and communicates decisions back to reps.

What the owner does:

• Reviews submissions for completeness before routing to approvers
• Owns the 24-hour turnaround SLA
• Escalates to the appropriate approval tier based on deal size and risk
• Documents the outcome and any conditions of approval
• Identifies recurring exceptions that should become standard policy

The escalation path is separate from the owner. The owner manages the process. The approvers make the decisions. Define who approves at each tier before the first submission arrives.

24 hours is the target SLA. Not "we'll get back to you by end of week." A deal desk that takes three days to approve a discount loses the benefit of having a deal desk. Research by Forrester on B2B sales cycle friction shows that internal approval delays are among the most cited reasons buyers disengage or shift their timeline. This mirrors the SDR-to-AE handoff SLA: deal momentum is fragile, and every hour of delay is a cost. The rep still has to manage an anxious prospect and a stalled deal. If you can't commit to 24 hours, figure out why before rolling this out.

---

Step 3: Build the Deal Submission Form

The deal submission form is what the rep fills out when they need desk review. It exists to give approvers everything they need to make a decision without a back-and-forth email chain.

Eight fields. No more, no less to start:

Field 1: Deal name and CRM link The specific opportunity, linked directly so approvers can see deal history.

Field 2: What's being requested Specific ask in plain language: "32% discount off standard annual rate" or "custom payment terms: 50% at signing, 50% at 90 days."

Field 3: Deal size (ARR/TCV) The dollar value of the deal at the requested terms.

Field 4: Close date The rep's committed or expected close date.

Field 5: Why the non-standard request The business justification the prospect has given or that the rep is offering: competitive pressure, budget cycle, strategic account importance. Not "they asked for it." The actual reason.

Field 6: What happens if we don't approve Honest assessment: will the deal die, move to a competitor, reduce in scope, or delay? This forces the rep to think through the real stakes, and it helps approvers weigh the risk.

Field 7: Relevant context Prior conversations with executives, previous exceptions granted to this account, any compliance or legal flags.

Field 8: Requested response by The date the rep needs an answer to keep the deal on track.

The form can live in a shared Google Form, a Notion page, or a dedicated field in your CRM. The format doesn't matter. What matters is that every submission is complete before it gets routed to an approver.

---

Step 4: Approval Tiers

Three tiers covers most situations. Resist the urge to create more.

Tier 1: Sales Manager

• Discounts in the 11-20% range
• Standard extensions (net 45-60)
• Minor scope adjustments within a standard contract

Tier 2: VP Sales

• Discounts in the 21-30% range
• Multi-year deals under $100K TCV (adjust threshold to your business)
• Non-standard payment schedules
• Any deal with a strategic account flag

Tier 3: CEO or CFO

• Discounts above 30%
• Multi-year deals above $100K TCV
• Custom legal terms (reviewed alongside legal counsel)
• Any deal with a material financial or compliance risk

Define the thresholds in writing before you launch the process. Post them somewhere every rep can see them. The first time a rep finds out their deal requires CEO approval should not be in the moment they need an answer in 48 hours.

---

Step 5: Standard vs. Non-Standard Pricing

One of the most valuable outputs of building a deal desk is that it forces you to maintain an explicit rate card: a document that defines what reps can quote without any approval. MIT Sloan Management Review research on pricing strategy notes that organizations with documented pricing tiers and discount governance consistently outperform those relying on ad hoc rep-level judgment.

If your rate card doesn't exist in writing, reps invent their own interpretation of "standard pricing" and you end up with inconsistent quotes across accounts. That means your deal desk will be busier than it needs to be, handling requests that should have been self-service.

Your rate card should define:

• Base pricing by product tier and seat count
• Standard annual vs. monthly multiplier
• Standard discounts for multi-year (e.g., 10% for 2-year, 15% for 3-year)
• Volume discount tiers (if applicable)
• What's not negotiable

Update the rate card at least quarterly. Make sure every rep has the current version. A deal desk that processes exceptions to an outdated rate card is doing more work than necessary.

---

Step 6: Post-Approval Documentation

Once a deal gets approved, three things need to happen before it moves to contract:

1. CRM update: the approval is logged in the deal record with the terms approved, the approver, and the date. Not just "approved by VP." Specific terms: "32% discount approved for annual contract. No further concessions authorized."

2. Contract generation trigger: who initiates the contract, using which template, incorporating which approved terms. The deal desk owner typically triggers this, not the rep.

3. Customer communication: who tells the prospect the deal is approved? Usually the rep, but the timing and language should be agreed in advance. Reps sometimes communicate approval before the contract is ready, which creates expectation management problems.

If the approval comes with conditions (e.g., "approved at 28%, not 32%") those need to be communicated to the rep clearly before they go back to the prospect. Nothing damages deal momentum like a rep who tells a prospect "we can do that" and then has to walk it back.

---

Common Pitfalls

A McKinsey analysis of B2B commercial excellence found that companies with clear pricing governance frameworks close deals 10–15% faster than those without, largely because internal friction drops.

Approval by committee. If every deal requires three people to weigh in before a decision gets made, your 24-hour SLA will become a 72-hour SLA. Pick one approver per tier. Others can be informed, not consulted.

Undocumented exceptions that become precedent. The most dangerous phrase in deal negotiations is "we did that for [Company X]." Every exception you approve without documenting becomes a lever the next rep uses to justify the same exception. Log every approval with conditions in the CRM. Your deal desk owner should review recurring exceptions quarterly and either codify them into the rate card or explicitly retire them. Your CRM data model should include fields for discount level, approval tier, and conditions to make this review possible.

Reps quoting non-standard terms verbally before approval. When a rep says "I think we can do that" in a discovery call before they've run it through the deal desk, you've already lost control of the negotiation. The prospect anchors to that number. Train reps to say "let me check on that and get back to you by tomorrow" instead. It's slower in the moment and faster overall.

---

Deal Desk Templates

Deal Submission Form

DEAL DESK SUBMISSION
Submitted by: [Rep Name] | Date: [Date]
CRM Link: [URL]

1. Deal name:
2. What's being requested (specific terms):
3. Deal size (ARR):
4. Expected close date:
5. Business justification:
6. Risk if not approved:
7. Relevant context (prior discussions, account history):
8. Response needed by:

Approval Tier Matrix

---

What to Do Next

The fastest way to set your deal desk thresholds correctly is to work backwards from actual data, not forward from theory.

Pull last quarter's closed deals. Tag each one as:

• Standard (no exceptions, closed on rate card pricing)
• Minor exception (discount under 20%, handled by a single manager)
• Major exception (required VP or CEO involvement)
• Custom terms (legal or payment structure changes)

Look at the deals in the "major exception" category. How many went straight to the CEO? How long did they take to close after the rep first asked for approval? What's the pattern in why they escalated that high?

Set your Tier 2/Tier 3 threshold based on where most of the CEO-level approvals clustered. If 80% of CEO approvals were on deals over $75K ARR, your threshold should probably be $75K, not $100K.

Build the process around your actual deal flow, not an ideal you haven't tested yet. You can tighten or loosen thresholds after three months of data. The same backward-looking approach works for win/loss analysis: use actual deal history to calibrate your process, not assumptions.

---

Learn More

• Forecast cadence: weekly vs. monthly vs. continuous
• Commit, best case, pipeline: defining forecast categories
• Running a weekly pipeline review that doesn't waste an hour
• RevOps maturity model: where does your team stand?