A growth bottleneck is the single constraint limiting how fast your whole growth system can run — and it is rarely the thing making the most noise.

Founders do not usually describe it as a system problem. They say leads are soft, paid is expensive, SEO is too slow, outbound is not converting, or the team needs to ship more. Those symptoms are real. They just do not all point to the same fix, and treating them as separate problems is how a growth function ends up with five channels, none of which reinforce each other.

The useful question is not what is going wrong. It is which one thing, if we fixed it, would make the others start mattering.

Constraint versus symptom

The distinction is the whole discipline.

A symptom is what you can see: CAC drifting up, a flat month, a channel that used to work and stopped. A constraint is the thing producing it. One constraint typically produces several symptoms, which is why chasing symptoms individually feels like effort without compounding.

Two tests separate them:

  1. Would fixing this let something else start working? If yes, it is probably the constraint. If it just removes one annoyance, it is a symptom.
  2. Does more of your current input make it better or louder? Add budget to a positioning problem and you buy more people bouncing off the wrong message. Constraints get louder under pressure. Genuine capacity problems get better.

That second test is the reason “we need more leads” is almost never the answer at this stage. More traffic into a weak system produces more confident-sounding confusion.

The five layers where post-PMF growth breaks

For B2B SaaS and AI companies past product-market fit, the constraint almost always sits in one of five places. For each, the useful thing is not the label — it is the red signal, because that is observable this week.

LayerAskRed signal
PositioningDo buyers describe the problem the way the website does?Acquisition keeps getting harder upstream. Sales calls feel like education.
AcquisitionAre channels reinforcing each other, or running in isolation?Pipeline lands in waves. CAC is unstable.
ConversionIs the offer asking for too much, too early?Qualified visitors don’t become qualified conversations.
ReportingDoes weekly reporting produce decisions?Activity is reported. Scale / stop / fix calls aren’t made.
Team ownershipIs there an internal owner running the rhythm?Founder hours fill the gap. Growth stays personal.

The layer with the strongest red signal is your bottleneck. Not the one with the most complaints attached to it.

Work through each layer in depth on the five-layer diagnostic. The Growth Bottleneck Scorecard asks a narrower question in about four minutes — what still depends on you personally — which is usually the fastest way into the team-ownership layer.

Positioning is upstream of almost everything

If buyers do not describe their problem the way your site does, every downstream number degrades quietly. Ads cost more because the click-through audience is wrong. Sales calls run long because the rep is teaching before selling. Content gets read by the wrong people.

This is the constraint most often misdiagnosed as an acquisition problem, because the symptom shows up in the channel metrics.

Reporting is upstream of knowing anything

A team can run experiments for two quarters and learn nothing if reporting describes activity rather than forcing decisions. The test is not whether you have a dashboard. It is whether Friday produces a scale, stop or fix call that someone is accountable for.

If it does not, you cannot trust any conclusion about the other four layers — which is why reporting is worth fixing early even when it is not the headline problem.

Team ownership is the one founders discount

Growth that only moves when the founder is in the room is not a growth system, it is a founder doing growth. It looks fine on a revenue chart and fails the moment attention moves. The red signal is subtle: nothing is broken, the founder is just quietly in every loop.

What this looks like in practice

Three patterns worth recognising, because they recur:

  • “Our CAC is rising, we need a better paid agency.” Often positioning. The audience that converts cheaply has been exhausted and the message does not travel to the next segment. A better media buyer optimises a losing auction.
  • “We need more top-of-funnel.” Often conversion. Qualified visitors are arriving and not converting, so the funnel is being fed rather than fixed. Check the ratio before adding volume.
  • “We’re running lots of experiments but growth is flat.” Almost always reporting. Experiments without a decision rhythm produce activity and anecdotes, not learning.

Pre-PMF: none of this applies

If you do not yet have product-market fit, the constraint is the product or your understanding of the customer, and growth work will not rescue it. It will just spend money finding out faster.

A diagnosis worth paying for will tell you this on the first call rather than take the engagement. If you are not sure which side of the line you are on, that ambiguity is usually the answer.

What to do once you have named it

Naming the constraint is most of the value, because it makes the next decision obvious rather than contested:

If the constraint is…The honest next step
PositioningReframe the offer and message before adding any spend
AcquisitionConnect the channels into one system rather than adding a sixth
ConversionFix the offer and the path before feeding more volume into it
ReportingBuild the weekly decision rhythm first — you cannot judge the rest without it
Team ownershipPut an internal owner on it, or bring in senior leadership until you can hire one

Two ways to get there. The Growth Bottleneck Scorecard is free, takes about four minutes, and names the strongest thing still depending on you personally. A Growth Diagnosis takes about a week from £2,000, and audits 90 days of CRM pipeline, GA4 reports and ten recent sales calls to produce a constraint map, an evidence table and a 90-day priority memo.

If you already know your constraint and simply need execution capacity against it, you do not need either — hire for the gap directly.