Has the initial segment saturated?

The telltale metric is new-logo win rate holding steady while qualified pipeline volume falls. That combination is specific: it means you still win the deals you find, and there are fewer of them to find. A sales-execution problem looks different, with volume flat and win rate falling. Saturation is common at this band because the segment that produced the first $5M was usually reachable through the founder's own network and the obvious channel, and both have finite depth.

This is not a product problem in the sense that the product is wrong, but the fix usually runs through product anyway, because entering an adjacent segment almost always exposes capability gaps the current segment tolerated.

Has the product stopped earning expansion?

The telltale metric is net revenue retention flattening while gross retention holds. Customers are staying and not growing, which means the product does what they bought it for and has not become more valuable as they have used it more. This is a product problem and it is the most commonly missed of the four, because gross retention looks healthy on a board slide and the absence of expansion registers as a sales failure to upsell.

Look for it in cohort data rather than aggregates: take accounts by signup quarter and plot revenue per account over time. A flat line eighteen months in, in a product that is supposed to grow with usage, is the signature.

Has the go-to-market motion outgrown founder selling?

The telltale metric is win rate on founder-involved deals sitting well above win rate on deals the team runs alone. That gap is the most concrete measure of how much of the sale depends on a person who cannot scale. It appears at this band because the motion that worked to $5M was often the founder personally translating an unfinished value proposition, which works well and does not transfer.

This one is not a product problem, though it is often reported as one, because the team without the founder in the room encounters objections that get relayed inward as missing capabilities.

Has pricing left the value behind?

The telltale metric is realized price per account drifting downward while usage rises, or discounting spreading without a policy behind it. Both mean the price is anchored to a version of the product that no longer describes what customers get. This is a product problem in the sense that packaging is a product decision, and it is the fastest of the four to fix and the one most likely to be deferred, because changing pricing touches sales compensation, existing contracts and the website at the same time.

From our own category research: in our analysis of this category's search results, Google restructured them across the March–April 2026 core updates: vendor pages fell out of the top 20 while informational pages held. Buyers now research this category through answers rather than vendor sites, which is worth knowing here, because each of the four causes above has a category of vendor whose diagnosis is decided in advance.

Why does the board's default answer usually lose a year?

Because "hire more sales" is the correct response to exactly one of the four causes and an expensive mistake against the other three. It is also the fastest to authorize, the easiest to measure, and the only one that produces visible activity within a quarter. Against a saturated segment it adds sellers to a market that has run out. Against flat expansion it adds acquisition to a leaky base. Against a pricing gap it sells more of the underpriced thing.

The cost is not just the payroll. It is the months before the new team's numbers can be read, plus the quarter after that spent debating whether they were ramped, during which the actual cause continues. A month of diagnosis in front of that decision is cheap by comparison, and it does not preclude hiring; it decides what the hires should be doing.

"Hire more sales" is the correct answer to one of the four causes and an expensive mistake against the other three.

What does the one-month diagnosis look like?

Four weeks. Week one: pull the four telltale metrics, all segmented rather than aggregate, and build the cohort readout of revenue per account by signup quarter. Weeks two and three: 30 interviews split across recent wins, closed-lost, churned accounts and your largest expansions, because the expansion accounts tell you what the product is actually worth when it works. Week four: write the finding as one primary cause with its evidence, plus one secondary, and state what would have to be true for you to be wrong.

The output is a decision about where the next two quarters go, not a report. If the diagnosis does not cause something on the roadmap or in the go-to-market plan to stop, it has not been completed. The larger evidence program that prioritization runs on afterwards is 60–80 interviews; thirty is the scope this diagnostic uses. Qualitative work of this kind commonly lands in the 20–30 range, and where saturation actually falls depends on how varied your segments are, so treat it as a chosen scope rather than a statistical threshold.

Who should run it?

Someone who does not already own one of the four answers. That rules out the sales leader, the product lead and in most cases the founder, all of whom hold a defensible prior view and will find evidence for it. A research agency can run the interviews and will hand back a report with no decision attached. An outside product leader can run the diagnosis and then own the prioritization that follows from it, which is the fractional model. Choose on whether what you need is the finding or the follow-through.

Sivan Kadosh, a fractional Chief Product Officer for B2B SaaS companies between $2M and $15M ARR, works that third option at $8,000 a month against 20–25 hours and a 3 month minimum. The leadership version of this question is covered in product leadership when growth stalls, the sales-versus-product split is in telling a product problem from a sales problem, and the cost comparison if you conclude you need a leader is in fractional CPO cost in 2026.

Four causes stall growth at this band, each with a metric that gives it away, and two of them are product problems. The default answer costs a year when it is wrong, which is three times out of four. Spend a month on the diagnosis first, and make the deliverable a decision about what stops rather than a document.