Is a deal desk part of RevOps or Sales Ops?

It can sit under either, or under Finance. In mature orgs it most often lives under the RevOps umbrella, alongside Sales Ops as a sub-function. What matters more than the reporting line is a written approval matrix and a fast review SLA.

Does RevOps replace Sales Ops?

No. When companies adopt RevOps, Sales Ops usually becomes a sub-function within it — still owning CRM, sales tooling, and rep-level reporting, while RevOps owns the cross-functional data model and forecasting across marketing, sales, and customer success.

Can one person do all three jobs?

Below about $20M ARR, one person usually does. The risk isn't the workload — it's that deal-desk judgment gets no explicit mandate, so discount discipline erodes quietly. A one-page charter and a discount ladder fix most of that.

What's the difference between deal desk and deal review?

The deal desk is the function; a deal review is the thing it does — evaluating a specific deal's pricing, discount, and terms before signature, ideally against comparable past deals.

Who sets discount approval thresholds?

Typically RevOps and Finance set the thresholds together, since they own the system and the margin model. The deal desk enforces them on each deal and reports back when the ladder no longer matches how deals actually close.

When should the deal desk become a dedicated role?

When non-standard deals are frequent enough that reviews are a weekly occurrence — for most B2B SaaS companies, somewhere in the $20M–$50M ARR range. Before that, it's a hat worn by an ops leader or a fractional operator.

Deal Desk vs RevOps vs Sales Ops: Who Owns What

These three titles get used interchangeably, and it costs companies real money. I've watched a 30% discount sail through because Sales Ops thought RevOps was watching it and RevOps thought the deal desk existed — when nobody had ever stood one up. The fastest way to sort out the confusion is to ask what question each function answers, because they answer different ones.

What does each function actually own?

Here's the split, compressed into one table:

	Sales Ops	RevOps	Deal Desk
Core question	Is the sales team running efficiently?	Is the whole revenue engine aligned?	Is this deal priced and structured well?
Scope	One team: sales	Marketing + Sales + CS, end to end	One deal at a time
Owns	CRM hygiene, territories, comp, quota, rep reporting	Full GTM tech stack, data model, forecasting, process across funnels	Pricing exceptions, discount approvals, non-standard terms, deal structure
Time horizon	This quarter's productivity	This year's revenue architecture	This week's contract
Typical artifact	Territory plan, pipeline report	Funnel dashboard, tech-stack map	Approval matrix, deal review brief

Sales Ops came first historically. RevOps is the newer umbrella that grew out of it. The deal desk is the specialist function that can live under either. If you want the full picture of what that specialist function does, I wrote a plain-English guide to what a deal desk is — this post is about the boundaries.

What is the difference between a deal desk and RevOps?

RevOps builds and runs the system: the tech stack, the data model from first marketing touch through renewal, the forecast, the process that connects marketing, sales, and customer success. It's an architecture job. Success looks like clean data, aligned teams, and a forecast the CFO trusts.

The deal desk works inside that system, on individual deals. When a rep wants 25% off, or a buyer demands net-90 payment terms, or a deal needs a multi-year ramp — that's a deal desk call. It's a judgment job. Success looks like defensible discounts, terms that don't blow up at renewal, and reps getting an answer in hours, not days.

The practical test: if the work would still matter with zero deals in flight, it's RevOps. If the work only exists because a specific deal is on the table, it's deal desk.

The overlap point is approval thresholds. RevOps typically partners with Finance to set them — who can approve what discount depth. The deal desk enforces them deal by deal, and flags when the ladder no longer matches reality.

What is the difference between a deal desk and Sales Ops?

Sales Ops keeps the sales team productive: CRM, tooling, territories, comp plans, pipeline reviews. In a lot of companies, deal desk work is a hat Sales Ops wears — the analyst who runs pipeline reports also gets pinged when a weird deal shows up.

That works until it doesn't. The failure mode is that Sales Ops is measured on sales-team throughput, so when a rep pushes hard on a discount, the person reviewing it reports into the same org that wants the deal closed. Discount discipline erodes one exception at a time. A deal desk with real teeth needs a mandate that isn't just "help sales go faster" — it's "protect the economics of the deal," which sometimes means saying no to sales.

Who should the deal desk report to?

There's no single right answer, but there are honest trade-offs:

Under RevOps — the most common home in companies that have a RevOps leader. The desk inherits the cross-functional data and the neutral position between Sales and Finance.
Under Finance — strongest margin discipline, and approvals carry weight. Risk: reviews slow down and reps start routing around the desk.
Under Sales — fastest turnaround, best rep adoption. Risk: the fox audits the henhouse, and average discount creeps up a point or two a year.

In mature orgs, Sales Ops doesn't disappear when RevOps arrives — it becomes a sub-function under the RevOps umbrella, and the deal desk usually sits beside it there. My own bias after running deal reviews for teams in the $5M–$50M ARR range: reporting line matters less than two things — a written approval matrix, and a review SLA under 8 business hours. Get those right and any of the three homes can work. Get them wrong and none will.

How do the three work together on a live deal?

Walk one non-standard deal through the machine and the division of labor gets concrete:

Sales Ops built the pipeline that surfaced the deal and keeps the CRM record clean enough to trust.
RevOps set the threshold that flags it — say, any discount past 15% or any non-standard payment term — and wired the routing.
The deal desk reviews the deal itself: how does this discount compare to the last three deals at this ACV, what did net-90 cost us the one time we accepted it, what's the fallback position.
The deal desk routes the exception to the right approver with that context attached, and records the decision.
RevOps watches the aggregate: average discount trend, exception rate, review turnaround — and adjusts the thresholds quarterly.

The system finds and moves the deal. The desk judges it. The record of that judgment is what makes deal #201 smarter than deal #37 — and it's the step most teams skip.

What if you can't staff all three?

Below roughly $50M ARR, almost nobody staffs all three, and that's fine. What I see work:

Under $5M ARR: the founder or CRO is all three functions. Write down a discount ladder anyway — it takes an afternoon.
$5M–$20M ARR: first ops hire (usually titled RevOps or Sales Ops — the title matters less than the mandate) owns the system. Deal desk is a hat, worn with a written charter.
$20M–$50M ARR: deal volume and deal size now justify dedicated deal-desk capacity. This is where teams either promote an operator into it, or rent the function — a fractional deal desk gives you the judgment layer without the headcount.

The mistake isn't running lean. The mistake is running lean implicitly — nobody named as owner, no written thresholds, every exception negotiated from scratch. That's how the same bad term gets signed three times.