Every negotiated deal reaches a moment where someone has to say yes. A deal review is what should happen in the minutes before that yes — a quick, disciplined look at whether the deal in front of you is actually good, or just closeable. Done well it takes a few minutes and saves a renewal. Done in a Slack thread at 6pm on quarter-end, it's a rubber stamp.

What is a deal review, in one sentence?

A deal review is the pre-signature check on a non-standard deal — the point where an approver examines the price, discount depth, payment terms, and contract structure against your policy and your history before the deal is committed.

It's the event; the deal desk is the function that runs it. A rep closes the deal, but the deal review decides whether the company can live with how it was closed.

What does a deal review actually check?

A good review isn't a vibe check on whether the logo is exciting. It works through a fixed set of questions, so nothing important gets skipped under deadline pressure:

  • Price and discount. How deep is the discount, and is it defensible at this deal size? How does it compare to what you've granted on similar deals?
  • Terms. Payment schedule, auto-renewal, SLAs, liability caps, termination rights — anything non-standard that shifts risk onto you.
  • Structure. Ramps, usage commitments, multi-year lock-ins, pilot-to-paid mechanics. Does the shape of the deal match the revenue you think you're booking?
  • Precedent. Have you agreed to something like this before? What happened at renewal?
  • The exception. If it's outside policy, is the reason strong enough to set the precedent — because the next rep will point to it.

The output isn't "approved / rejected." It's a recommendation with a rationale: here's what's defensible, here's where you're exposed, here's the fallback if the buyer pushes.

Deal review vs. deal approval — what's the difference?

People use these interchangeably, but they're two different acts. Approval is the authority to say yes; the review is the judgment that informs it. You can have approval without review — that's exactly how bad deals get signed, when a senior person clicks "approve" on a request they never really examined.

Deal review Deal approval
What it is The analysis of the deal The authority to commit it
Question it answers Is this deal good? Am I allowed to sign it?
Who does it Deal desk / reviewer The approver on the matrix
Failure mode Skipped under deadline Granted without a review

The fix is to make the review the thing that produces the approval — the approver sees the analysis, then decides. They shouldn't be able to say yes without it.

Who runs a deal review?

It depends on company size. Under roughly $50M ARR it's usually one experienced operator — a RevOps or Finance leader wearing the deal-desk hat, or a fractional deal desk brought in from outside — who runs the review and hands the approver a clear read. Larger companies staff a dedicated desk. Either way, the reviewer and the final approver are often different people: the reviewer does the analysis, the approver holds the authority. Keeping those roles distinct is what stops "review" from collapsing into a self-signed rubber stamp.

When should a deal get a review?

Not every deal. Reviewing standard, in-policy deals just slows the team down and trains reps to route around you. A deal should trigger a review when it crosses a line you've set in advance:

  • Discount past a set threshold — commonly anything beyond 15–20%.
  • Non-standard payment terms — net-60, net-90, or milestone billing.
  • Deal size above a dollar figure where a mistake actually hurts.
  • Custom legal language — unusual liability, termination, or most-favored-nation clauses.
  • Any multi-year or ramped structure where booked revenue and cash don't line up.

Everything below the line stays self-serve for reps. Everything above it earns a few minutes of scrutiny. Drawing that line explicitly is most of the work — it tells the team what's normal and what needs a second set of eyes.

The one-page brief behind a good deal review

Here's the part most teams miss. The quality of a deal review is capped by what the reviewer can see. "Can I do 25% off?" is impossible to answer well. The same request with context attached is a thirty-second decision.

So the artifact that makes a review work is a one-page brief — everything the approver needs on a single screen:

  1. The deal at a glance. ACV, term length, discount, and any non-standard terms, stated plainly.
  2. The flags. The two or three things that are actually risky, not a wall of green checkmarks.
  3. The precedent. Comparable past deals — the largest discount you've granted at this size, whether you've accepted these terms before, and what it cost you.
  4. The recommendation. What's defensible, where the exposure is, and the fallback position.

The hardest line to fill in is the precedent one, because it lives in old contracts, dead CRM fields, and the memory of people who've since left. So most reviews skip it, and deal #201 gets negotiated as if the first 200 never happened.

That's the gap Precedent was built to close — an AI-assisted fractional deal desk that turns your own deal history into a one-page review brief on every deal before sign-off, delivered in Slack within two hours. The review stops being a bottleneck and starts being the smartest read in the room.