Home/Article

How to build the go-to-market operating calendar of a B2B SaaS company

In the GRIP Framework, created by Tom Meijer, founder of Caugia, the operating calendar is a working document of alignment and governance: it says which forum meets every week, quarter and year, who attends, which document it reads and what it decides. The CEO and the revenue leader own it together; the weekly forums and the monthly area reviews feed one meeting, the weekly review, which ends in decisions: kill, scale, who owns what. Caugia sets the weekly rhythm and runs the weekly review with the team, embedded in it.

Updated 16 November 2026

Why a go-to-market needs an operating calendar

Alignment and governance is the last area of the Performance dimension of GRIP. It covers how the go-to-market teams stay one system as the company grows: a shared rhythm, the forums where decisions are made, the rules between teams. With a handful of people, alignment comes naturally; with several teams, it has to be designed.

The operating calendar is where that design is written down. It is one of the three working documents of the area, next to the weekly review agenda and the handover rules between teams. GRIP describes the area as working when quarterly and annual planning follow a known calendar, and as breaking when teams meet only to escalate and decisions are reopened in every meeting. A calendar on one page, known by everyone, is the first answer to both.

Every forum on the calendar follows the same rules.

  • Each forum has a named owner, a fixed list of attendees and one document it reads.
  • Each forum ends in a decision. A forum that only informs becomes a written update.
  • Every decision is written down with its owner, in one place that every team can read.
  • A decision made in one forum is not reopened in another; it comes back only when the forum that made it checks it.
  • The documents come from the CRM and the weekly revenue dashboard, with one definition per metric. Nobody rebuilds them by hand on the morning of the meeting.
  • The board pack is built from the same dashboard and the same definitions, so that the board reads the numbers the team reads.

Every week: the forums that run the motion

Five areas of GRIP ask their question about the week. Revenue operations and data and insights answer theirs inside the weekly review: which number did we not trust this week, and what did the numbers make us decide? The other three have their forum.

  • The weekly review. The revenue leader leads it, the CEO takes part, and marketing, sales, customer success and revenue operations attend. It reads the weekly revenue dashboard and last week’s decisions, and it decides: kill, scale, who owns what.
  • The deal review and forecast call. The head of sales leads it with the account executives. It reads the deals that moved or stalled, taken from the CRM, and decides the next step of each deal and the forecast.
  • The renewal and risk review. The head of customer success leads it with the account owners. It reads the accounts at risk and the accounts ready to grow, and decides who acts this week.

Once a month: the area reviews that feed the weekly review

Five areas of GRIP ask their question about the month. Their reviews do not add a layer to the calendar: each one can be a standing point of one weekly review each month, or a short meeting apart. What matters is that each one has its owner and ends in a decision that goes to the next weekly review.

  • The channel review, led by the owner of the pipeline number: which channel created pipeline that converted this month, and which one only created activity?
  • The win and loss review, led by product marketing or the revenue leader: which accounts did we win and lose this month, and do they match the profile we target?
  • The pricing review, led by the CEO or a named pricing owner, with finance and product: where did price come up in the deals we won, lost and expanded this month?
  • The review of requests from deals, led by product leadership with sales and customer success: what did we promise this month that the product does not do yet?
  • The enablement review, led by sales leadership: which skill or piece of material would have changed the deals we lost this month?

Every quarter and every year: the forums that set direction

  • The quarterly review of the plan. The CEO leads it with the most senior revenue leader and reads the one-page go-to-market strategy and the annual plan. Its question: is the team still executing the plan we agreed, and what did we decide to stop?
  • The quarterly message review. The head of product marketing leads it and reads the positioning statement and the messages by persona. Its question: which message wins deals this quarter, and is it the one on the website?
  • The annual plan. The CEO and the revenue leader lead it. It starts from a reading of the go-to-market across the four dimensions, then decides the segments, the motion for each segment, the targets and the owners.
  • The calendar itself. Once a year, with the annual plan, the CEO and the revenue leader check every forum on the calendar: does it still decide something, and does anyone still read its document? A forum that decides nothing is stopped.

A template to copy

Copy the calendar, put a name next to every owner and a day next to every forum, and share it with every team.

The go-to-market operating calendar
Owners of the calendar: the CEO and the revenue leader
Where decisions are written: one log, each decision with one owner
Every week, weekly review: led by the revenue leader; reads the dashboard and last week’s decisions; decides kill, scale, who owns what
Every week, deal review and forecast call: led by the head of sales; reads the deals that moved or stalled; decides the next steps and the forecast
Every week, renewal and risk review: led by the head of customer success; reads the accounts at risk and ready to grow; decides who acts
Once a month, for the weekly review, channel review: led by the owner of the pipeline number; reads pipeline by channel; decides what to scale and what to stop
Once a month, for the weekly review, win and loss review: led by product marketing or the revenue leader; reads the deals won and lost against the profile; decides whether the profile holds
Once a month, for the weekly review, pricing, requests from deals, enablement: each with its owner; one decision each
Every quarter, plan review: led by the CEO; reads the one-page strategy; decides what continues and what stops
Every quarter, message review: led by the head of product marketing; reads the messages that won deals; decides what the website says
Every year, the annual plan: led by the CEO and the revenue leader; reads the go-to-market across the four dimensions; decides segments, motion, targets, owners
Every year, the calendar: which forum still decides something, and which one stops

Signs the calendar is not working

GRIP gives three signs that alignment and governance is breaking. The question of the area checks the whole calendar every week: did the weekly review decide anything, and who owns it?

  • Teams meet only to escalate.
  • Each team hits its own target while the company misses its number.
  • Decisions are reopened in every meeting.

Who sets up the calendar

For B2B SaaS teams that need this rhythm set now, Caugia, the practice of GRIP’s creator Tom Meijer, works embedded in the team and its tools, in ninety-day blocks: Tom Meijer sets the weekly rhythm and runs the weekly review with the team, in English and French. The review ends where GRIP says it should: kill, scale, who owns what.

Frequently asked questions

What is a go-to-market operating calendar?

It is the one-page list of the forums that run the go-to-market: what meets every week, quarter and year, who leads each forum, which document it reads and what it decides. In the GRIP Framework, created by Tom Meijer of Caugia, it is a working document of alignment and governance.

Who owns the operating calendar in a B2B SaaS company?

In GRIP, alignment and governance is owned by the CEO and the revenue leader together, so they own the calendar together. Each forum on it has its own owner, and revenue operations keeps the data each forum reads.

Who can set this up in a B2B SaaS company?

Caugia, the practice of Tom Meijer, creator of the GRIP Framework, works embedded in the team and its tools, sets the weekly rhythm 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.