The commercial team comes into the monthly business review with a strong quarter. New logos beat budget by 19%. The head of sales puts the number on the slide with an upward arrow. Then the CFO asks why revenue missed budget by ₹33L, and the room goes quiet.

The answer is mix variance. The logos beat happened almost entirely in SMB. Enterprise closures came in six short of plan. A logo in SMB carries an ACV of ₹1.5L. A logo in Enterprise carries ₹10.0L. Selling more of the cheaper segment while missing the expensive one produces exactly the scenario above: a volume beat that masks a revenue miss.

Mix variance is the component of a PVM bridge that measures this. It is also the component most SaaS finance teams either omit from their bridges or calculate incorrectly. This article covers what it measures, how to calculate it properly, and why the LTV implications make it more consequential than the revenue number alone suggests.

The general PVM framework, the plug trap mechanics, and the order-of-operations argument are covered in depth in Price-Volume-Mix Analysis: The FP&A Tool Most Teams Get Wrong. This article applies that framework specifically to a two-segment SaaS business using the canonical ₹50 Cr ARR model I use across this series.

What Mix Variance Measures

Mix variance isolates the revenue impact of selling a different proportion of products or customer segments than budgeted, holding both volume and price constant. It answers a specific question: if total logos and ACV had both matched budget exactly, but the split between Enterprise and SMB had shifted the way it actually did, how much revenue would we have lost?

That question is not answered by the price variance (ACV was held at budget). It is not answered by the volume variance (total logos changed, but that effect is separated out first). Mix variance is what remains once those two components have been cleanly isolated.

The formula:

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

Applied per segment, then summed. The segment-level decomposition is what makes it actionable, because it tells you which segment drove the mix shift and by how much.

The Plug Trap

Before the worked example, one technical point that matters for credibility. The most common way mix variance gets calculated incorrectly is by treating it as a residual: calculate price, calculate volume, take whatever is left. The residual reconciles to the total variance, which is why the error survives review. But it is not a clean mix figure. It absorbs a distortion from the price component.

The correct sequence is deliberate. Volume variance first, at budget ACV. Then price variance, at actual volume. Then mix as the remaining component. The ordering matters because price variance calculated at budget volume includes a volume effect, which bleeds into the residual and makes the mix figure analytically meaningless even though it ties mathematically.

A concrete demonstration using April Enterprise numbers from the Revenue Bridge article (ACV ₹10.0L budget, ₹10.8L actual, 8 logos budget, 6 logos actual):

Approach Price Variance Volume Variance Residual
Correct (price at actual volume 6) +₹4.8L -₹20.0L ties exactly
Wrong (price at budget volume 8) +₹6.4L -₹20.0L -₹1.6L unexplained

The ₹1.6L residual in the wrong approach has no business meaning. It is a calculation artefact. Use actual volume as the weight for price variance and the residual disappears.

Worked Example: Q1 FY27, ₹50 Cr ARR SaaS

The inputs. Q1 new logo bookings, budget versus actual, at budget ACV to isolate the mix effect from any pricing movement.

Segment Budget Logos Budget ACV (₹ L) Actual Logos Budget Mix % Actual Mix %
Enterprise 24 10.0 18 37.5% 23.7%
SMB 40 1.5 58 62.5% 76.3%
Total 64   76 100% 100%

Total logos beat budget by 19%. Enterprise missed by 6 logos. SMB beat by 18 logos. The mix shifted 13.8 percentage points away from Enterprise toward SMB.

The bridge. Volume variance first (total logo change at budget average ACV of ₹4.69L):

\[\text{Volume Variance} = (76 - 64) \times ₹4.69\text{L} = +₹56.2\text{L}\]

Mix variance per segment, at budget ACV:

\[\text{Enterprise Mix} = (23.7\% - 37.5\%) \times 76 \times ₹10.0\text{L} = -₹105.0\text{L}\] \[\text{SMB Mix} = (76.3\% - 62.5\%) \times 76 \times ₹1.5\text{L} = +₹15.8\text{L}\] \[\text{Total Mix Variance} = -₹105.0\text{L} + ₹15.8\text{L} = -₹89.3\text{L}\]

The aggregate:

Component ₹ L
Budget revenue 300.0
Volume variance +56.2
Mix variance -89.3
Actual revenue (at budget ACV) 267.0
Total variance -33.0

Proof: ₹300.0L + ₹56.2L - ₹89.3L = ₹267.0L. ✓

The business beat its logo target by 12 deals and missed revenue by ₹33L. The volume variance was +₹56.2L favourable. The mix variance was -₹89.3L adverse. The mix effect was 1.6x larger than the volume gain.

The LTV Dimension

Revenue variance is the immediate number. LTV implications are what make this conversation matter to the CFO beyond the current quarter.

Enterprise and SMB do not just carry different ACVs. They carry different retention profiles, different expansion trajectories, and different gross margins. Using the canonical model assumptions (72% gross margin, 1.5% monthly churn):

\[\text{LTV} = \frac{\text{ACV} \times \text{Gross Margin \%}}{\text{Monthly Churn} \times 12}\]
Segment ACV (₹ L) LTV (₹ L)
Enterprise 10.0 40.0
SMB 1.5 6.0

Enterprise LTV is 6.7x SMB LTV. The 6 missed Enterprise logos represent not just ₹60L of missed Q1 ACV but approximately ₹240L of foregone LTV. The 18 SMB overperformers represent ₹27L of ACV and ₹108L of LTV. The net LTV impact of the Q1 mix shift is -₹132L, four times larger than the revenue variance in the quarter.

I find this is the number that changes the CFO conversation. Revenue miss of ₹33L in a single quarter is manageable. Implied LTV deterioration of ₹132L from a single quarter’s mix shift is a structural question about whether the go-to-market motion is pointing in the right direction.

The CFO Narrative

The bridge and the LTV table do the analytical work. The narrative closes the loop with a decision prompt.

Q1 new logo revenue came in ₹33L below budget despite a 19% volume beat, driven entirely by mix degradation: Enterprise closures fell 6 short of plan, shifting the logo mix 13.8 percentage points toward SMB. The mix variance of -₹89.3L more than offset the volume gain of +₹56.2L. At current LTV assumptions, the implied foregone customer lifetime value from the Enterprise miss is approximately ₹240L, against ₹108L of incremental LTV from the SMB overperformance. The question for the commercial team before Q2 planning is whether the Enterprise pipeline deficit is a timing issue or a capacity issue, and whether SMB overperformance reflects genuine demand or a sales motion that is defaulting to easier closes.

Three sentences. What happened with numbers, what the LTV implication is, what decision it opens.

How This Connects to the Planning Infrastructure

Mix variance connects the revenue bridge directly to the driver-based model. When the mix shifts adversely for a second consecutive quarter, the budget ACV assumption in the driver-based model needs to be revisited. An ASSUMPTIONS tab that assumes 37.5% Enterprise mix when the business is consistently closing at 23% is forecasting a revenue number the go-to-market motion cannot deliver.

The variance analysis framework covers how the mix bridge fits into a complete monthly actuals review: Layer 1 (what happened) is the table above, Layer 2 (why it happened) requires a conversation with the sales leader about pipeline coverage by segment, and Layer 3 (what it means) is the LTV calculation and the forecast revision question.

You can download the PVM bridge template, which includes the mix variance calculation alongside price and volume, from the Revenue Bridge article.

I would love to hear how your team handles the enterprise versus SMB mix conversation in practice: whether it shows up in the monthly bridge, how the sales leader typically responds, and whether the LTV frame ever lands differently than the revenue frame. Let’s connect.