Variance analysis: monthly review meetings that surface real signal

Almost every growth-stage Indian company we work with has a monthly variance review meeting. The format is consistent: finance presents the P&L versus budget, walks through the lines that have moved materially, the department heads respond, and the founder closes with a few directives. The meeting runs 90 to 120 minutes and concludes with everyone feeling like progress was made.

What we observe, two months later, is that the conversation in the next variance review covers the same ground. The reason is structural. A line-item variance review surfaces noise — random month-to-month fluctuations that look like signal in isolation but mean nothing in trend. A bucket-driven variance review, where each bucket has a defined decomposition, surfaces signal because the decomposition itself is diagnostic.

Below is the framework we use, the five buckets that matter for almost every business, and the meeting structure that makes the 90 minutes useful instead of decorative.

The five variance buckets

1. Revenue variance: volume vs price

Revenue variance breaks into two effects. Volume variance: actual units sold minus budget units, multiplied by budget price. Price variance: actual price minus budget price, multiplied by actual units. The two sum to the total revenue variance.

This decomposition is the first diagnostic question on revenue. A miss driven by volume is a demand problem or a pipeline problem; a miss driven by price is a discounting problem or a mix problem. The corrective action is different in each case, and a P&L review that just shows 'revenue Rs. 1.2 crore below budget' tells you nothing about which conversation to have.

For a SaaS company, replace volume with new customer additions and price with ARPU. For a services firm, with utilisation and rate. The structure is the same.

2. Gross margin variance: mix, rate, volume

Gross margin variance decomposes into three effects. Mix variance: the change in product or customer mix at constant per-unit margins. Rate variance: the change in per-unit gross margin at constant mix. Volume variance: the change in absolute margin driven by overall volume.

This is the most powerful decomposition in the bucket. A gross margin compression that the line-item P&L shows as 'cost of goods up by Rs. 30 lakh' could be: a shift in mix toward lower-margin products, an input cost spike on a high-volume product, a discounting pattern that has changed the realised price, or a volume drop that has eroded fixed-cost absorption. Each requires a different response.

We run the mix-rate-volume decomposition every month for product companies and every quarter for services companies (where the decomposition is utilisation-rate-volume).

3. Opex variance: controllable vs uncontrollable

Opex variance is the line item that most variance reviews handle line-by-line and where the noise problem is most acute. A 60-line opex schedule with month-over-month variations of Rs. 30,000 to Rs. 2 lakh on individual lines produces 90 minutes of explanations that, individually, do not change any decision.

The fix: classify every opex line as controllable or uncontrollable, and report variances by category, not by line.

Controllable opex: marketing spend, sales commissions, consulting fees, travel and entertainment, hiring costs, software licences. These are line items where a department head has decisional authority and the variance is a management choice.

Uncontrollable opex: rent, utilities, statutory fees, audit fees, banking charges, insurance renewals. These are line items where the variance is either timing or external rate movement, and the department head has limited authority over them.

Reporting variance by category collapses 60 line items into 6 meaningful aggregates: controllable opex by department (marketing, sales, ops, G&A) and uncontrollable opex. The conversation moves from 'why is the travel line up' to 'why is sales department controllable opex up versus plan'.

4. Capex variance: planned vs unplanned

Capex variance, like opex, benefits from a category cut. Planned capex (against the board-approved capex plan) versus unplanned capex (urgent equipment replacement, new business line initiation that was not in the plan).

For an asset-light services or SaaS company, this bucket is small. For an asset-heavier D2C, manufacturing, or fulfilment-led business, it is often the second largest discretionary spend after payroll. A monthly variance review that does not have a clear capex slide misses a category that, on an annual basis, can move EBITDA by 200 to 400 basis points.

5. Working capital variance: DSO, DPO, DIO trends

Working capital variance is rarely treated as a variance bucket in monthly reviews because the P&L does not surface it. The balance sheet does, and the cash flow statement does, but most monthly variance reviews are P&L-focused.

The three working capital metrics — days sales outstanding (DSO), days payable outstanding (DPO), days inventory outstanding (DIO) — are best tracked as trends and as variance against the company's stated working capital policy. A DSO that has crept from 38 days to 46 days over three months is the equivalent of a Rs. 2 to Rs. 3 crore cash outflow at a Rs. 100 crore revenue company, and the line-item P&L will not show it.

Working capital variance review needs its own slide and its own 10 minutes in the monthly review meeting.

Why bucket-driven analysis surfaces signal

The difference between line-item and bucket-driven variance review is the difference between description and diagnosis.

Line-item review: 'Marketing spend is Rs. 8 lakh above budget this month, driven primarily by an unplanned Google Ads campaign and a higher-than-expected agency invoice.' Description. No clear action.

Bucket-driven review: 'Volume of new customer acquisitions is 22% below plan; CAC has risen 35% over the prior month, primarily through a paid-channel mix that has shifted toward higher-cost performance marketing. Recommended action: revisit channel mix targets for the next quarter and reset spend authority limits for the marketing director.' Diagnosis. Clear action.

The line-item review answers 'what happened'. The bucket-driven review answers 'why it happened and what to do about it'. The first is a finance team artefact; the second is a management decision tool.

The 90-minute meeting structure

The structure we use, against the clock:

Minutes 0 to 30: variance walk by FP&A. The FP&A or finance manager walks through the five buckets, in order. For each bucket, the variance against budget and against the prior month, the decomposition that explains the variance, and the one-line conclusion. No department-head response yet — questions held until the end of the walk.

Minutes 30 to 60: department-head response. Each department head responds to the variances in their domain. The format is structured: the reason for the variance as the head sees it, the action being taken, the expected timing for resolution. Other heads can ask questions but the founder holds the synthesis to the final segment.

Minutes 60 to 90: decisions on corrective actions. The founder synthesises. Decisions get made: budgets reset, authority limits adjusted, projects accelerated or deferred, hiring frozen or unfrozen. The decisions get documented in a one-page action log that is the artefact of the meeting.

The discipline is in the 30-minute walk. A walk that runs to 50 minutes leaves no time for response and decision. A walk that runs to 20 minutes has not been thorough enough on the decomposition. The FP&A team's job is to deliver the walk in 30 minutes, with the supporting analysis available if any head wants to see it.

What this requires from the finance team

The bucket-driven variance review requires more preparation than the line-item review. The decompositions (mix-rate-volume on gross margin, volume-vs-price on revenue, controllable-vs-uncontrollable on opex) need to be set up in the FP&A workbook and re-run every month.

Setup time: a one-week project to build the decompositions for the first time. Run time: 3 to 4 hours per month for the FP&A team to refresh the analysis.

Three to four hours of finance team time, for a meeting that converts 90 minutes of management attention from description to decision. That is a meaningful productivity ratio.

Variance analysis is a discipline, not a report. The companies that get this right are the ones that have decided what the monthly review is for. The teams that get it wrong have decided what the variance report looks like — thorough, line-by-line, exhaustive — without first deciding what it is meant to achieve.