Case patterns · B2B SaaS

Five constraints. Where most B2B SaaS pipelines actually stall.

Caugia is pre-revenue. We do not pretend otherwise. What we do have is a deterministic engine that has already been run on a private cohort of B2B SaaS teams, and the constraint patterns repeat. Here are the five we see most.

How to read this page. No named logos, no fabricated metrics. These are pattern descriptions drawn from completed Intelligence Reports across B2B SaaS teams who asked us to keep names off-record. The point is not to brag. It is to show you what the diagnostic typically catches that the leadership team had already debated and gotten wrong.

1

“Sales is the problem.” When it is not.

Series A, B
Symptom

Pipeline coverage falls. Win rates drop. The CRO is on the chopping block by Monday. The board wants a head.

Mis-read

Leadership concludes the AE team is under-performing. They start interviewing replacement reps. They consider replacing the CRO.

What the engine surfaces

Inbound volume against the ICP collapsed two quarters ago. Marketing kept reporting on overall lead volume. The constraint is demand-shape, not sales execution.

Action cascade pointed at marketing-to-ICP alignment first. Sales reorg deferred.
2

Product-channel fit drift, the silent revenue tax.

Post-PMF, pre-scale
Symptom

The first channel worked: founder-led, outbound, or community. Every new channel underperforms. CAC climbs.

Mis-read

“We need better paid performance.” The team layers on agencies, ad spend, attribution tooling. Nothing closes the gap.

What the engine surfaces

The product’s value proposition is channel-specific. A motion that fits the founder’s network does not survive a colder channel. Constraint is packaging, not paid.

Action cascade pointed at offer-redesign for the next channel. Paid scaled second, not first.
3

The ICP gap nobody wants to admit.

Series B, C
Symptom

Logos look fine. NRR drifts down. CS is stretched. Renewal motions get heavier every cycle.

Mis-read

“Our CS team needs to be more proactive.” Leadership invests in success ops, journey mapping, more headcount.

What the engine surfaces

Sales closed two adjacent segments to hit a quota stretch. Those segments do not expand. CS is rescuing a sales-side ICP problem. Constraint is ICP discipline, upstream.

Action cascade pointed at sales-side ICP gating. CS headcount frozen until the cohort changed.
4

The expansion ceiling that was not about expansion.

Mid-market growth-stage
Symptom

NRR plateaus around 105-110%. The board wants 120%+. Expansion offers do not move the needle.

Mis-read

“We need a better expansion play.” The team launches a second product, runs cross-sell campaigns, builds tiering complexity.

What the engine surfaces

The packaging gates the natural expansion path behind a feature wall most customers cannot reach. The constraint is pricing-packaging, not expansion motion.

Action cascade pointed at packaging redesign first. Cross-sell came after the gating was removed.
5

Invisible in the answer market.

All stages
Symptom

Direct traffic is fine. Branded search is fine. But the new buyer journey runs through ChatGPT, Perplexity and Claude, and you do not show up.

Mis-read

“That is an SEO problem.” The team adds blog content, runs more PR, layers in schema. Visibility in answer-market does not move.

What the engine surfaces

Foundation-model knowledge cut-offs and citation graphs work differently from Google. The constraint is citation-presence in the corpus that LLMs read, not domain authority.

Action cascade pointed at named-entity placement and citation distribution. Traditional SEO investment paused.

The pattern matters more than the story.

Every constraint in these cases looks obvious in hindsight. That is the trap: the leadership team had already debated it, formed an opinion, and committed to the wrong fix. The diagnostic does not out-think them. It quantifies the financial impact of each candidate constraint against a structured set of business inputs, and the engine returns the binding one.

Most teams already know the symptoms. What they do not know is which symptom is downstream and which one is the cause, and which one, fixed first, makes everything else cheaper.

Find the pattern that is actually running your pipeline.

The Intelligence Report names your binding constraint and quantifies the cost of waiting. One published price.

Get the Intelligence Report → See pricing