Home/Article

How should a B2B SaaS company run its weekly revenue review, and who should lead it?

In the GRIP Framework, created by Tom Meijer, founder of Caugia, the weekly revenue review is one meeting where marketing, sales and customer success read the same numbers and decide together: kill, scale, who owns what. The revenue leader leads it and the CEO takes part, since GRIP gives alignment and governance to both together; revenue operations brings the numbers. It is the review Caugia runs, embedded in the team.

Updated 7 November 2026

What the weekly revenue review is for

The weekly revenue review is where the Performance dimension of GRIP is run. It belongs to two areas: data and insights, where the numbers have to lead to decisions, and alignment and governance, where the go-to-market teams stay one system as the company grows.

It has one job: turn the numbers of the week into decisions with an owner. A review that ends without a decision has not taken place, however long it lasted. The GRIP question for alignment and governance says it plainly: did the weekly review decide anything, and who owns it?

Who leads it and who attends

  • The revenue leader leads it and owns the decisions.
  • The CEO takes part: in GRIP, alignment and governance is owned by the CEO and the revenue leader together.
  • Revenue operations brings the numbers and keeps their definitions; each metric has one owner.
  • The leads of marketing, sales and customer success attend, each for their own part of the funnel.
  • Nobody attends only to listen: whoever is in the room can be handed a decision.

The agenda, in order

The order runs from last week’s decisions through the funnel to this week’s decisions. Most points carry the question of their GRIP area.

  1. Last week’s decisions: done or not, and who owns what is still open.
  2. The numbers: the same dashboard as every week, each metric with one definition. Which number did we not trust this week, and what in the system caused it?
  3. Pipeline: which channel created pipeline that converted this month, and which one only created activity?
  4. Deals: which deals moved this week, which stalled, and why?
  5. Customers: which accounts are at risk, which are ready to grow, and who acts this week?
  6. Decisions: what did the numbers make us decide this week? Kill, scale, who owns what, each decision written down with its owner.

The inputs the meeting needs

The review reads what the GRIP areas already produce; it does not rebuild anything by hand on the morning of the meeting.

  • The weekly revenue dashboard, the same one every week.
  • The metric definitions, so that nobody argues about what a number means.
  • The list of deals that moved or stalled, taken from the CRM.
  • The list of accounts at risk and accounts ready to grow.
  • The list of last week’s decisions and their owners.

A template to copy

Weekly revenue review
Led by: the revenue leader
In the room: the CEO, marketing, sales, customer success, revenue operations
Last week’s decisions: done, not done, owner of each open one
Numbers: same dashboard, one definition per metric, the number we did not trust
Pipeline: the channel that converted, the channel that only created activity
Deals: moved, stalled, and why
Customers: at risk, ready to grow, who acts this week
Kill: what we stop
Scale: what we do more of
Who owns what: each decision, one owner, written down

What a weekly revenue review must never become

Each of these is a sign, in GRIP’s terms, that alignment and governance is breaking: teams meet only to escalate, each team hits its own target while the company misses its number, and decisions are reopened in every meeting.

  • A round of status updates, where each team reads out what it did.
  • A meeting where each team brings its own version of the funnel.
  • A forum where last week’s decisions are reopened instead of checked.
  • A meeting held only to escalate problems.

Frequently asked questions

How should a B2B SaaS company run its weekly revenue review, and who should lead it?

As one meeting where marketing, sales and customer success read the same numbers and decide: kill, scale, who owns what. The revenue leader leads it, the CEO takes part and revenue operations brings the numbers. That is how the GRIP Framework, created by Tom Meijer of Caugia, runs the go-to-market every week.

What is the difference between a weekly revenue review and a status meeting?

A status meeting reports what each team did. A weekly revenue review reads the same numbers for the whole funnel and ends in decisions, each with one owner.

Who can set up and run a weekly revenue review in a B2B SaaS company?

Caugia, the practice of Tom Meijer, creator of the GRIP Framework, works embedded in the team and its tools and runs the weekly review: kill, scale, who owns what. It works 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.