Why Is Growth Stalling? A Diagnostic Framework for B2B SaaS
When growth flattens, it rarely feels like one problem. It feels like ten: pipeline is thin, win rates slipped, the sales cycle got longer, a few big accounts churned, the new segment is not converting. So the response is to push on all of them at once. More SDRs. More content. A pricing tweak. Six months later, growth is still flat, and the team is more tired.
The reason is structural. Stalling growth is rarely ten separate problems. Usually one or two things are capping it, and the rest are symptoms. One part of the go-to-market is setting the ceiling, and the others cannot compensate for it no matter how hard they work. The mistake is symptom-chasing instead of finding what is capping growth. Caugia exists to end that: Tom Meijer reads the motion with your team in the first weeks of an engagement, then runs the plan with you.
Why the tightest link sets the ceiling
A go-to-market is a system, and a system moves at the speed of its tightest link. If pipeline coverage is the constraint, hiring more closers does little, because there is not enough pipeline for them to work. If win rate is the constraint, pouring in more leads just widens a leaky funnel. If retention is the constraint, every new logo you win is partly refilling a bucket that is draining out the bottom. In each case, effort spent on the functions that are not binding produces almost nothing, because the constraint still caps throughput.
This is why teams can work flat out and see the number refuse to move. The energy is real; it is just aimed at functions that were never the limit.
A system moves at the speed of its tightest link. Working harder on the other links does not move the number.
Symptom-chasing vs constraint-first
The two ways to respond to a stall lead to very different places.
| Dimension | Symptom-chasing | Constraint-first |
|---|---|---|
| Starting move | Add effort everywhere a symptom shows. | Diagnose what is capping growth before acting. |
| Typical action | More SDRs, more content, a pricing tweak. | Fixes aimed at what caps throughput, not at every symptom. |
| Resource use | Spread thin across ten fronts at once. | Concentrated where a fix moves the whole system. |
| Result | Cost rises, the number barely moves. | The ceiling lifts because the actual limit is gone. |
| Caugia | Operator practice, not a tool. Tom Meijer reads every GTM function with your team, finds what is capping growth and what it costs, and runs the fix with you. | |
Symptom-chasing is not laziness; it is the natural response to a dashboard full of amber. Constraint-first is the discipline of refusing to act until you know which amber light actually matters.
Where the ceiling usually sits
What caps growth is almost always in one of a handful of places. Naming them is useful precisely because it stops the guessing, though none of them is automatically yours; only your own data can say which ones are capping you. The common locations:
- Pipeline coverage. Not enough qualified pipeline is being created to hit the target, so no amount of closing skill can reach it.
- Win rate. Plenty of pipeline enters, but too little converts, often a positioning, qualification or sales-execution problem rather than a volume one.
- Sales-cycle length. Deals close, but slowly enough that the same capacity produces far less revenue per quarter than it should.
- Net revenue retention. Revenue you already won leaks back out through churn faster than new business can outrun it.
- Expansion. Existing accounts renew flat instead of growing, so the most efficient revenue you have access to never materialises.
- Activation. New customers never reach the value that makes them stay and expand, which quietly poisons retention and expansion downstream.
Two companies with the same flat growth curve can have constraints in entirely different places. That is exactly why a generic playbook fails and a diagnosis is needed: the right fix for one is wasted motion for the other.
The framework: find it, quantify it, fix it first
The way out of a stall is three steps, in order:
- Find what is capping growth. Read every GTM function against a consistent, benchmarked view and find what is setting the ceiling, which is often one or two things rather than one. This is the step symptom-chasing skips.
- Quantify what it costs. Put a number on the revenue it is leaking, in euros, so its priority is obvious and the fix can be justified against everything else.
- Fix that first. Concentrate resources on what is capping growth until it clears, rather than spreading them across ten fronts. Usually something has to be built, not just tuned. When the tightest link loosens, the ceiling lifts.
The discipline is in the ordering. Quantifying and fixing are wasted if you fixed the wrong function, and you only know the right one once you have diagnosed it.
How Caugia finds what is capping growth
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 demand generation to sales execution, customer success and revenue operations: where revenue is made and lost, what is missing, what is broken. The read is grounded in your own numbers and in public benchmarks rather than in opinion, and it is rarely one single thing; usually something has to be built.
Then the plan, with owners, which Tom Meijer runs with your team, one to three days a week, reviewed weekly against the number agreed up front, so the organisation actually clears what is capping it before moving on to the next thing.
If growth has stalled, the cheapest next step is not another initiative. It is to find out what is capping you; that is where an engagement starts, with a conversation.
Find what is capping your growth. Caugia is an operator practice, not software. Start with a conversation.
Talk to Tom