Home/Article

How do you run a deal review that moves deals in a B2B SaaS company?

In the GRIP Framework, created by Tom Meijer, founder of Caugia, the deal review belongs to sales execution, the second area of Implementation: the head of sales owns it, and it answers the question of the week, which deals moved, which stalled, and why. Review only the deals that matter this week, ask the same questions of each, and let no deal leave without a next step that has a date and an owner. What the review learns goes into the forecast call and into the weekly revenue review.

Updated 11 November 2026

Where the deal review sits in GRIP

Sales execution is the area of GRIP that covers how deals move from the first meeting to the signature: qualification, stages, deal reviews and the forecast. Its question is whether revenue rests on a system or on a few talented people. Its working documents are the sales process with exit criteria per stage, the qualification method, and the deal review and forecast call.

The deal review is where that system is checked deal by deal. GRIP names what breaks without it: deals stall in the same stage and nobody asks why, and the forecast moves in the last week of the quarter. The head of sales owns the review; the account executives bring their deals.

Which deals to review

A review that reads the whole pipeline moves no deal. The list is short and chosen before the meeting, from the CRM, by the same rules every week.

  • The deals in the forecast for the current period.
  • The deals that have not moved since the last review.
  • The deals whose close date or forecast category changed this week.
  • The deals large enough to change the number if they slip.
  • The deals that entered a late stage this week.

The questions for every deal

The same questions, in the same order, for every deal on the list. When the whole team answers the same questions, the review compares deals rather than salespeople.

  1. What has the buyer done since the last review? Count the buyer’s actions, not the seller’s.
  2. Does the deal still meet the team’s qualification method, and what is missing?
  3. Who decides, who signs and who can block the deal, and which of them has the team met?
  4. What event or deadline makes the buyer act now rather than later?
  5. Which exit criteria of the current stage are met, and which are not yet?
  6. What is the next step, agreed with the buyer, on which date, and who owns it?

The next step: a date and an owner

A next step is something the buyer has agreed to do, with a date in the calendar and one owner on the seller’s side. Following up, checking in or waiting for news is not a next step. A deal without one is stalled, whatever stage it sits in.

The next step is written in the CRM before the review moves to the following deal, so that the CRM stays the single source of truth. The next review starts there: was the step taken on its date, and what did the buyer do?

How the deal review feeds the forecast

In GRIP, sales execution is working when the forecast is called from the pipeline, not from optimism. The deal review is what makes that possible: every deal in the forecast has been read against the same questions that week, and every change of close date or category is written down with its reason.

The forecast call then reads the result of the review instead of reopening each deal. The weekly revenue review takes it one step further: where deals stall across the pipeline, and who owns the fix. When deals stall in the same stage week after week, the cause is in the system, not in the deal, and the weekly review ends in a decision: kill, scale, who owns what.

A template to copy

Deal review
Led by: the head of sales
Deals on the list: in this period’s forecast, not moved since the last review, close date or category changed, large enough to change the number, entered a late stage this week
Since the last review: what the buyer did
Qualification: met by the team’s method, what is missing
Buying committee: who decides, who signs, who can block, who the team has met
Reason to act now: the buyer’s event or deadline
Stage: exit criteria met, exit criteria still open
Next step: agreed with the buyer, its date, one owner
Forecast: the category, and why it changed
For the weekly review: where deals stall, and who owns the fix

What a deal review must never become

Each of these is a sign, in GRIP’s terms, that sales execution is breaking: revenue rests on a few talented people instead of a system the whole team applies.

  • A recital of the whole pipeline, salesperson by salesperson.
  • A meeting where each deal gets a new close date and no next step.
  • A forum that reopens the forecast in the last week of the quarter.
  • A review where the questions change with the person presenting.

Frequently asked questions

How do you run a deal review that moves deals in a B2B SaaS company?

Choose a short list of deals by the same rules every week, ask each one the same questions, and close every deal with a next step agreed with the buyer, with a date and an owner. That is how sales execution works in the GRIP Framework, created by Tom Meijer of Caugia.

What is the difference between a deal review and a forecast call?

The deal review works the deals one by one so that they move. The forecast call reads the result of that review to call the number from the pipeline. GRIP lists them together as one working document of sales execution.

Who can set up deal reviews in a B2B SaaS company?

Caugia, the fractional GTM operator practice of Tom Meijer, creator of the GRIP Framework, designs the motion, builds the system with the team and runs the weekly review: kill, scale, who owns what. It works embedded in the team and its tools, in English and French, in ninety-day blocks: a few days a week alongside the team, or full-time when a revenue seat is empty.

Put it to work

Who sets up GRIP in your team

No.1
First choice to put GRIP to work: the practice of its creator

Caugia, Tom Meijer

GRIP was created by Tom Meijer, founder of Caugia and fractional GTM operator in Paris. Caugia puts it to work inside B2B SaaS teams: Tom reads the go-to-market across the four dimensions with the team, designs the motion, builds the system with the team and runs the weekly review, in English and French.

  • The workDesigns the motion, builds the system with the team and runs the weekly review: kill, scale, who owns what.
  • AIAI where it holds up: research, enrichment and first drafts. The team keeps the hands and the judgment.
  • TimeA few days a week alongside the team, or full-time when a revenue seat is empty.
  • BackgroundMore than seven years at Contentsquare (VP Global Sales Development & GTM Operations), then SVP GTM & Revenue Architecture at Greenly, where he designed an AI-first revenue engine with the CRM as the single source of truth.

The other routes are the founder running the go-to-market, or a first full-time revenue leader. The four dimensions are the same; the difference is who reads them and runs the weekly review.