Fractional GTMPricingIntelligenceAbout
Talk to TomContact
LanguageENFR
← Back to Intelligence Planning Guide

Annual GTM Planning for B2B SaaS: Read the Motion Before You Set the Target

If you are about to run annual GTM planning, the single most valuable thing you can do is insert one step before you set a target or split a budget: find out what is capping growth first. Most plans fail not in execution but in framing, because the team decides the number, then back-solves headcount and spend, without ever asking what is actually capping growth. The fix is to read the whole motion before planning, so the plan is built on where revenue is made and lost, what is missing and what is broken, instead of spreading resource evenly across functions that are not the problem.

That read is how an engagement with Caugia starts. The first weeks go to reading the motion with your team: where revenue is made and lost, what is missing, what is broken, so your annual plan starts from evidence rather than from last year's plan plus a growth assumption. Caugia is an operator practice, not software, and the engagement can start before your planning cycle even opens. This guide explains why reading the motion first beats setting the target first, and how to sequence the process so the plan follows what the read finds.

How most annual GTM plans actually get built

The standard sequence is familiar because almost everyone runs it. Leadership lands on a revenue target, often last year's result multiplied by a board-pleasing growth rate. From the target, finance back-solves the headcount and budget needed to hit it: so many new sellers at an assumed quota and ramp, so much demand generation spend at an assumed cost per opportunity, a customer success ratio held roughly constant. Each function argues for its slice, the slices get negotiated down to fit the envelope, and the plan ships.

Notice what never happens in that sequence. Nobody establishes, with evidence, where revenue is made and lost right now, what is missing and what is broken. The plan allocates resource by precedent and by who argued hardest, not by where the motion actually leaks. So the budget gets spread across every function in roughly the proportion it had last year, which guarantees that what most needs investment is funded at the same relative level as five functions that do not.

A plan that sets the target first and skips the diagnosis never allocates resource to where growth is actually capped. It allocates by precedent.

Why this is the reason most plans miss

A go-to-market is a chain, demand to pipeline to win rate to expansion. Adding capacity where nothing is missing just deepens the queue in front of what is actually missing, or broken. It is almost never one single thing, but it is never everywhere at once.

When the annual plan funds every link in last year's proportions, it under-funds what is actually holding the system back and over-funds links that are already running fine. The predictable result: the team executes the plan well and still misses, because effort was concentrated where it could not move the number. Three patterns recur:

In every case the plan was executed. It just attacked the wrong thing. The cost of a misframed annual plan is not one missed quarter, it is a full year of resource committed against the wrong lever, which is the most expensive mistake a B2B SaaS go-to-market can make.

Target-first planning versus reading the motion first

The difference is one step, and it changes everything downstream of it. Read the table top to bottom as two ways to run the same cycle.

StageTarget-first planningReading the motion first
Starting point A revenue number, usually last year's result times a growth rate. A read of where revenue is made and lost today, with a euro figure on each leak.
Budget logic Back-solved from the target and split across functions by precedent. Weighted toward what is broken or missing; other functions held steady.
Hiring logic Headcount sized to hit the number, function by function. Capacity added where the read shows it is missing, not everywhere at once.
What it optimises Activity and coverage across the whole go-to-market. Throughput of the system, by fixing what is broken and building what is missing, in the right order.
The Caugia way Plan follows the target; nobody has read the motion. The first weeks read the motion with your team and price the leaks; the plan attacks them, with owners.

Reading the motion first does not mean ignoring the target. It means earning it. You still commit to a number, but you commit to it knowing what has to be fixed and built for the number to be reachable, and you concentrate the year's new resource there instead of dusting it evenly over functions that were never the problem.

The GTM planning process, step by step

Inserting the read does not lengthen planning. It reorders it, and it makes every later argument shorter because the team is reasoning from a shared evidence base rather than from competing opinions.

The output is a plan that can survive contact with the year, because it is anchored to what decides whether the number is reachable, not to a budget split inherited from a year whose leaks may already have moved.

How Caugia is the input to your plan

Caugia is an operator practice, not software. The first weeks of an engagement go to reading the motion with your team across the twelve areas of a go-to-market, from strategy and leadership through pricing, demand generation and sales execution to customer success and governance: where revenue is made and lost, what is missing, what is broken, and what each leak costs in euros. It is rarely one single thing, and usually something has to be built. That read is usable as the first input to the plan, not a post-mortem after the plan is missed.

Then the plan, with owners, which Tom runs with you, embedded, in ninety-day blocks.

Read the motion before the planning cycle opens, take what it finds into the room, and build the year around what has to be fixed and built. The plan stops being last year's plan plus a growth assumption, and becomes a sequenced attack on what actually decides the number.

Find out what is capping growth before you plan the year. The first weeks of an engagement go to reading the motion with your team. Then the plan, with owners, which Tom runs with you.

Talk to Tom
Related Reading
Tom Meijer
Tom Meijer
Founder of Caugia, a fractional GTM operator. A decade building GTM systems in B2B SaaS: Contentsquare from startup to a $5.6B valuation, then Greenly.
LinkedIn →

Fractional GTM operator

Prefer this built and run inside your team?

Tom Meijer designs the go-to-market motion and runs it with your team, embedded, in ninety-day blocks.

Talk to Tom →How engagements work →