The Revenue Narrative for Flow Businesses

Revenue narrative is a term that gets used in two quite different contexts. In a fundraising setting it refers to the story of how a business generates and grows revenue, the mechanics, the model, the investor pitch.

In the context of ongoing board reporting it means something different. It is the commentary that accompanies the numbers every quarter, explaining how the business performed against budget, why it varied, and what the forward view is based on. That is the definition this piece works from.

Why flow businesses are harder to explain

In many business models, the link between what management does and what shows up in the revenue line is relatively direct. A SaaS business bills on contracted seats. A professional services firm bills on delivered work. When either misses budget, the explanation is grounded in things that were largely within the business's control, sales performance, churn, utilisation, pricing decisions. The external environment plays a role but it isn't structural to how revenue is generated.

Every business is affected by market conditions to some degree. In a flow business the relationship is more fundamental. Revenue is a function of throughput and margin inside a market that has its own momentum, and that market moves independently of what management does. A payments processor's volume is shaped by consumer and business spending patterns across the economy. An FX provider's revenue moves with currency volatility and cross-border trade flows. A lending platform's book is sensitive to credit conditions and rate environments. The market isn't a backdrop, it is embedded in the revenue model itself.

That creates a specific analytical challenge. In any given period, the revenue result contains two things at once: what the market delivered, and what the business actually built through its own commercial effort, pricing decisions and customer relationships.

Consider a quarter where volumes were strong but half of that volume was driven by a spike in currency volatility that nobody predicted and that is unlikely to repeat. The numbers looked good. The business didn't necessarily do anything differently. The result and the structural performance of the business are not the same thing, and in a flow business that distinction runs through everything.

The reporting frameworks most finance teams work with, budget versus actual packs, KPI dashboards, quarterly variance commentary, weren't designed to unpick that.

The gap and how to close it

The result is a board narrative that can describe what happened but struggles to explain it with any confidence. When variance against budget is partly structural and partly market-driven, and the framework to separate the two doesn't exist, the explanation is always going to feel incomplete. Guidance becomes difficult to anchor. The forward view rests on assumptions that haven't been made explicit. And over time, a board that can't distinguish between market-driven performance and what the business is actually building loses confidence in the numbers, not because the business is performing badly, but because the narrative isn't giving them enough to work with.

What makes the narrative credible is separating what the market is doing from what the business is actually building. Most management teams develop a feel for this over time but it rarely gets made systematic. 

What we are proposing is a structured framework, both quantitative and judgemental, that produces a revenue narrative grounded in what the business genuinely controls and honest about what it doesn't. The goal is to decompose total revenue into its two constituent parts: the portion the business generates through its own commercial activity, and the portion that market conditions are delivering on top of that.

From problem to framework

The framework works in two steps, though in practice they are iterative rather than strictly sequential. The process is as much judgemental as it is quantitative, and the outputs are not precise in an accounting sense but they are directionally honest, which is what the narrative requires.

The first is to define a normalised baseline, which is an estimate of what the business would earn in a stable market environment.This means normalising, that is, estimating what spread, volume and transaction frequency would look like in a steady market environment, across the different segments of the customer base, and treating client base growth that has come from commercial and GTM effort as a structural input.

The baseline represents what management is actually building, the revenue that would show up regardless of what markets happen to be doing in any given period.

The second step is to model the market-sensitive overlay, which is the difference between the baseline and actual revenue. This involves applying a sensitivity coefficient to each segment of the customer base, reflecting how client behaviour in that segment responds to external market conditions, and combining that with a volatility or an external market variable relevant to that segment. The overlay captures the market-driven component of the result, the revenue that came not from what the business built but from the conditions it was operating in.

In practice the process can start with a management discussion, using judgemental assumptions to sketch the initial decomposition before any modelling is done. Those assumptions are then tested by running them against recent revenue figures and external market data. That iterative loop between judgement and quantification is where the framework gets refined, and it means the process can begin with a conversation rather than a dataset.

The end point is a cleaner picture of what the business is actually generating on its own terms, separate from what the market is contributing in any given period. That is the foundation the revenue narrative is built from.

The forward narrative

A clean decomposition of the historical result is the starting point, but it isn't sufficient on its own. The forward narrative also requires a view on how exposed the existing customer base and the pipeline are to external market conditions going forward.

That starts with a segmentation of the book by market sensitivity. Some customer relationships are more exposed to external conditions than others, some are relatively insulated, and understanding that mix, and how it is shifting over time, is what gives the forward view its structure. Once that segmentation exists it can be made quantitative. A coefficient, in simple terms a number that reflects how sensitive each segment is to market movements, is applied to each part of the book to produce a forward estimate that carries the same structural and market-sensitive decomposition as the historical analysis.

The result is a forward narrative that is grounded in something more than an extrapolation of recent trends.

The pipeline adds a further layer of complexity. Not all of what is moving in the pipeline reflects genuine commercial momentum. Some of it is being shaped by the same external market conditions that influence the existing book, pulling opportunities forward in favourable periods and slowing them in difficult ones. Reading the pipeline at a portfolio level, rather than deal by deal, and forming a view on how much of the movement is signal and how much is market noise, is where cross-functional input becomes particularly important. It is a judgement that finance cannot make alone.

Building it cross-functionally

Finance brings the numbers and the analytical structure, but the assumptions that sit underneath the framework, the ones that determine how sensitive each segment is to market conditions, how to read the pipeline, what is driving customer behaviour, require input from across the business. Sales and growth have the commercial context and customer intelligence that the numbers don't capture. Comms has a view on how the external environment is being read and what that means for the forward narrative. 

When those inputs are part of the process, the narrative that reaches the board reflects a shared understanding of the business rather than a finance view with a commentary layer added afterwards.

The narrative itself

Once the analytical work is done, the narrative is crafted. The framework moves in a deliberate arc: initial judgemental assumptions to sketch the decomposition, then quantitative rigour to test and refine it, then judgement again in deciding how to present what the analysis has produced. 

That final stage involves decisions about what to emphasise, where to acknowledge uncertainty honestly, and how to frame the forward view in a way that gives the board something useful to work with. 

The quantitative work provides the foundation for those decisions but it doesn't make them. The narrative will always require human judgement, and that judgement is stronger for having a rigorous framework underneath it.