The monthly actuals pack lands on the CFO’s desk. Revenue missed budget by ₹7.7L. The commentary says: “Revenue was below budget due to lower enterprise closures, partially offset by SMB outperformance.” The CFO reads it, sets it down, and asks the question the commentary did not answer: “Is the enterprise shortfall a pipeline problem or a capacity problem? And is the SMB beat repeatable or did we discount our way to it?”

The first sentence of that commentary described the variance. It did not explain it. The revenue bridge is the tool that closes that gap, and most finance teams build it wrong.

What the Revenue Bridge Actually Does

A revenue bridge, built properly, decomposes the total revenue variance into its underlying drivers so that each component points to a decision. It does not just answer “how much did we miss?” It answers “which specific behaviour caused each rupee of the miss, and who owns the decision to address it?”

The core framework is price-volume-mix (PVM) analysis. It separates a revenue variance into three components: how much was driven by a change in what you charged, how much by a change in how many you sold, and how much by a shift in the composition of what you sold. I cover Mix variance in detail in The Margin Illusion: Decoding Mix Variance in Your Revenue Bridge, where it gets the full treatment it deserves. This article focuses on Price and Volume, the two components that together explain the majority of most revenue variances and the two a Finance BP needs to be able to build and narrate from scratch.

The bridge I find most useful as a Finance BP is not the two-line “budget vs actual” table most teams produce. It is a segment-level decomposition: Price variance and Volume variance calculated separately for each customer segment, then summed to a total. That structure reveals the story rather than hiding it.

The Formulas

For each segment, the bridge has two components.

Price variance measures the revenue impact of charging a different price than budgeted, holding actual volume constant:

\[\text{Price Variance} = (\text{Actual ACV} - \text{Budget ACV}) \times \text{Actual Logos}\]

Using actual volume as the weight rather than budget volume is deliberate. It avoids double-counting the volume effect, which is the most common construction error in PVM bridges I have reviewed.

Volume variance measures the revenue impact of closing more or fewer deals than budgeted, valued at the budget price:

\[\text{Volume Variance} = (\text{Actual Logos} - \text{Budget Logos}) \times \text{Budget ACV}\]

Valuing at budget price isolates the volume movement from the price movement. If you valued at actual price, any price change would contaminate the volume figure.

The proof that the bridge is constructed correctly:

\[\text{Budget Revenue} + \text{Price Variance} + \text{Volume Variance} = \text{Actual Revenue}\]

If that equation does not hold to zero, something is wrong in the construction, either the wrong baseline or the wrong ordering of the two variances.

Worked Example: ₹50 Cr ARR SaaS, April FY27

The numbers below are from the same ₹50 Cr ARR SaaS business I use across this series. The scenario is a single month: April FY27 budget versus actual for new logo bookings, split across Enterprise and SMB segments.

The inputs

Segment Budget Logos Budget ACV (₹ L) Actual Logos Actual ACV (₹ L)
Enterprise 8 10.0 6 10.8
SMB 40 1.5 50 1.35

Enterprise closed 2 fewer logos than budgeted but at a higher ACV than plan on the deals that did close. SMB closed 10 more logos but at a lower ACV, signalling discount pressure in the mid-market.

The bridge

Enterprise:

\[\text{Price} = (10.8 - 10.0) \times 6 = +₹4.8\text{L}\] \[\text{Volume} = (6 - 8) \times 10.0 = -₹20.0\text{L}\]

SMB:

\[\text{Price} = (1.35 - 1.50) \times 50 = -₹7.5\text{L}\] \[\text{Volume} = (50 - 40) \times 1.50 = +₹15.0\text{L}\]

The aggregate

Segment Price Variance (₹ L) Volume Variance (₹ L) Total (₹ L)
Enterprise +4.8 -20.0 -15.2
SMB -7.5 +15.0 +7.5
Total -2.7 -5.0 -7.7

Proof: Budget revenue (₹140.0L) + bridge total (-₹7.7L) = Actual revenue (₹132.3L). ✓

What the Bridge Reveals That the Commentary Missed

The two-line summary (“enterprise down, SMB up”) was technically accurate but analytically empty. The bridge makes the story specific:

The enterprise shortfall is almost entirely a volume problem, not a pricing problem. At -₹20.0L, the volume variance dwarfs the +₹4.8L pricing gain. Two closures slipped. The ACV on completed deals was actually above plan, which means the pipeline quality is intact. The question for the sales leader is whether those two deals are in May’s pipeline or have been lost.

The SMB picture is the reverse. The volume beat of +₹15.0L is real, but ₹7.5L of it was given back in price. That is a 50% erosion rate: for every ₹2 of volume gain, ₹1 was funded by discounting. Whether that is acceptable depends on whether those SMB customers convert at the same LTV as full-price customers, which is a question the bridge surfaces but cannot answer alone.

Neither of those observations is visible in “enterprise down, SMB up.” Both are visible the moment you decompose by Price and Volume per segment.

Writing the CFO Narrative

The bridge does the analytical work. The narrative does the communication work. A good CFO narrative from this bridge is one paragraph, three sentences, one decision prompt.

Here is what that looks like from the April numbers:

April revenue was ₹7.7L below budget, driven by a two-deal slip in Enterprise (₹20.0L adverse on volume) and SMB discount pressure (₹7.5L adverse on price), partially offset by enterprise ACV above plan (+₹4.8L) and a strong SMB volume beat (+₹15.0L). The enterprise shortfall is a pipeline timing issue, not a pricing or capacity problem: ACV on closed deals was 8% above budget. The SMB volume gain came at a 50% price concession rate, which warrants a review of mid-market discounting policy before Q1 close.

Three sentences. The first states what happened and quantifies each component. The second interprets the enterprise number and says what it means for the forecast. The third identifies the SMB number as a structural question requiring a decision, by whom, and by when.

That is the difference between a variance report and a variance analysis.

Download the Template

The PVM bridge built from this example is available as a downloadable Excel file. Enter your own Budget and Actual figures in the yellow input cells and all variances calculate automatically. The CHECKS tab verifies that Price plus Volume ties to total revenue variance before you present.

Where This Fits in the Planning Infrastructure

The revenue bridge answers a backward-looking question: why did revenue land where it did? The driver-based model answers the forward-looking version: given our operational assumptions, where will revenue land next quarter? The variance analysis framework covers how the bridge fits into a complete monthly actuals review, moving from what happened through why, to what it means for decisions.

And if your April bridge shows that the SMB segment is consistently missing ACV budget across multiple months, the mix variance framework in The Margin Illusion is where that conversation leads next: not just that SMB is cheaper than Enterprise, but how the shift in the proportion between them is affecting gross profit in ways that a pure price-volume bridge will not surface.

The revenue bridge is the entry point. Building it at segment level, decomposed into Price and Volume, is what makes it useful rather than decorative.

I would love to hear how your team structures the revenue bridge in practice: whether you work at segment level, product level, or something else, and where the CFO commentary tends to land well or fall flat. Let’s connect.