When growth is flat and every explanation sounds plausible

“Revenue is flat” is an outcome, not a diagnosis. Break the path to revenue into demand, qualified opportunity, conversion, price and mix, delivery capacity, retention, and expansion. One of those transitions will usually explain more of the change than the others.

Use comparable periods and cohorts. A larger top-of-funnel number can hide weaker qualification. New bookings can hide churn. Average revenue can hide a move toward lower-margin work. The objective is not to build a larger dashboard; it is to locate the first place where otherwise viable growth stops becoming cash.

• Compare volume and conversion at every major stage.
• Separate new revenue from retained and expanded revenue.
• Measure committed demand that delivery could not accept or complete.
• Test whether price and mix changed even when unit volume did not.

A useful hypothesis predicts what else must be observable. If demand is the constraint, qualified opportunities should have fallen before revenue. If conversion is the constraint, loss reasons and stage movement should change. If capacity is the constraint, backlogs, cycle time, or turned-away work should rise while demand remains present.

Write the strongest case for each plausible explanation and the evidence that would rule it out. This prevents a favored theory from surviving every contradictory fact. It also exposes questions that are actually two decisions—for example, whether to change the offer and whether the current sales motion can sell it.

A stall rarely yields to a portfolio of vague initiatives. Choose the diagnosis with the strongest evidence and design the smallest test that can produce a meaningful result. Name an owner, a decision date, a leading indicator, and a tripwire that says the explanation was wrong.

The test must be large enough to matter. Changing messaging for a handful of prospects cannot settle whether positioning is broken. Asking delivery to absorb one more rushed project cannot settle whether capacity is the constraint. Underpowered tests preserve ambiguity and create false confidence.

• State what must move before revenue can move.
• Set a result that would cause leadership to abandon the hypothesis.
• Pause competing initiatives that would contaminate the evidence.
• Decide in advance what action follows either result.

When demand is not the constraint, pushing more volume into the same system can deepen the stall. Work queues grow, delivery quality falls, and the company discounts to compensate. The sales number improves briefly while cash and reputation deteriorate.

A founder-led software company in BridgeStride’s published results had demand but could not move work through delivery efficiently. The decision changed how projects entered and flowed through the company and placed capability at the actual narrow point. The lesson is not that every stall is operational. It is that the first obligation is to locate where growth stops, rather than default to the function easiest to blame.