Annual GTM Planning for B2B SaaS: A Diagnostic-First Approach
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 to attack what is actually capping growth 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 diagnostic-first planning beats target-first planning, 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, which single part of the go-to-market is capping growth right now. The plan allocates resource by precedent and by who argued hardest, not by where the constraint actually sits. So the budget gets spread across every function in roughly the proportion it had last year, which guarantees that the one function that most needs investment is funded at the same relative level as five 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
One constraint sets throughput for the whole system. This is not a slogan, it is how a chained process behaves: the slowest stage caps the output of every stage downstream of it, and adding capacity anywhere else just deepens the queue in front of the real bottleneck. A go-to-market is exactly such a chain, demand to pipeline to win rate to expansion, and at any given moment one link is the bottleneck.
When the annual plan funds every link in last year's proportions, it under-funds the one link that is actually holding the system back and over-funds several that are already running below the ceiling. The predictable result: the team executes the plan well and still misses, because effort was concentrated where it could not move throughput. Three patterns recur:
- Hiring into a coverage problem. The plan adds sellers when what is capping growth is pipeline coverage. More closers chase the same insufficient pipeline, ramp slowly, and quota attainment falls rather than rises.
- Funding demand when the leak is retention. The plan pours budget into top-of-funnel when the leak is net revenue retention. New logos pour into a leaking bucket, blended acquisition cost climbs, and net new revenue barely moves.
- Chasing volume when the constraint is win rate. The plan targets more opportunities when what is capping growth is conversion. The funnel widens, sales capacity gets consumed on deals that will not close, and the gain evaporates.
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 versus diagnostic-first planning
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.
| Stage | Target-first planning | Diagnostic-first planning |
|---|---|---|
| Starting point | A revenue number, usually last year's result times a growth rate. | A read of what is capping growth today, with a euro figure on it. |
| Budget logic | Back-solved from the target and split across functions by precedent. | Weighted toward what is capping growth; other functions held steady. |
| Hiring logic | Headcount sized to hit the number, function by function. | Capacity added where it lifts the constraint, not everywhere at once. |
| What it optimises | Activity and coverage across the whole go-to-market. | Throughput of the system, by clearing its slowest link first. |
| 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. |
Diagnostic-first does not mean ignoring the target. It means earning it. You still commit to a number, but you commit to it knowing which one thing has to move 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 diagnostic-first GTM planning process, step by step
Inserting the diagnostic 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.
- 1. Diagnose before you plan. Before the first planning meeting, read every function of the go-to-market, with the people who run it, and establish what is capping growth. This is the input the rest of the process is missing, and it is the step this guide exists to argue for.
- 2. Quantify the leak. Put a revenue figure on what the constraint is costing. A constraint with a number attached can be ranked against everything else competing for budget; a constraint described in adjectives cannot.
- 3. Set the target against the constraint. Sanity-check the revenue goal against what clearing the constraint can realistically unlock. A target that ignores what is capping growth is a hope, not a plan.
- 4. Allocate to the constraint first. Give the largest share of new budget and headcount to what is capping growth, then hold other functions roughly steady. This is the step target-first planning structurally cannot do, because it never identified the constraint.
- 5. Sequence, then govern. Order the initiatives so the constraint is attacked first, and put a cadence in place to keep the organisation on it until it clears, rather than letting the plan drift back to business as usual by February.
The output is a plan that can survive contact with the year, because it is anchored to the one thing that decides whether the number is reachable, not to a budget split inherited from a year whose constraint 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 one to three days a week, reviewed weekly against the number agreed up front.
Read the motion before the planning cycle opens, take what it finds into the room, and build the year around clearing it. 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