Built for finance and RevOps running variance analysis

Sales volume variance isolates the volume component of a budget-to-actual gap so the finance conversation gets specific.

Sales volume variance measures the portion of a budget-to-actual revenue gap that is attributable to selling more or fewer units than planned, holding price and mix constant. The formula: (actual volume minus budget volume) times standard price. Pair it with price variance and mix variance to decompose the full gap. Strkr runs the three-variance decomposition natively on the CRM data so finance stops reconstructing from Excel exports.

Start free trial See pricing
What this audience is actually dealing with

The pains that bring buyers here.

Sales volume variance is a standard finance analysis that most companies run manually in Excel after month close. The three-variance decomposition (volume, price, mix) isolates each driver of the budget-to-actual gap. The analysis takes finance 2 to 4 days each month because the data comes from CRM exports, invoice systems, and the budget file. The reconstruction work gets in the way of the actual decision support finance should be providing. The six pain points below are the ones finance and RevOps teams feel when variance analysis runs manually.

Variance analysis runs 2-4 days late

Finance ships the variance report 5 days after close.

The common pattern is that finance runs variance analysis after month close by pulling CRM data, invoice data, and the budget file into Excel. The reconstruction and formula work takes 2 to 4 days. Variance analysis for January lands roughly February 10. The lag means intervention windows for the next period are gone. Strkr runs variance analysis live on CRM data so the number is available at close rather than a week later.

The three variances are not decomposed

Finance reports total variance without volume versus price split.

Many teams report total revenue variance (actual revenue minus budget revenue) without decomposing into volume, price, and mix components. The decomposition reveals whether a 2M miss was 1.4M volume (fewer units sold), 400K price (discounting), and 200K mix (lower-tier product). The composite number does not drive action; the decomposition does. Strkr runs the three-variance split natively.

Budget data lives in a separate file

The variance analysis depends on which budget version is current.

Budget data typically lives in a planning file maintained by finance separately from the CRM. Variance analysis depends on reconciling CRM actuals against budget. Budget version drift (which version is the current baseline) causes ambiguity. Strkr runs budget data in the same platform as actuals so variance analysis uses the current version.

Variance per segment requires rebuild

The finance team reruns the analysis per segment manually.

Variance analysis per segment (SMB vs mid-market vs enterprise) typically requires finance to rerun the three-variance calculation per segment manually. The rebuild for 3 segments effectively triples the analysis work. Strkr runs the decomposition per segment natively so slicing is instant.

Volume variance is confused with price variance

Discounting shows up as volume miss when it is actually price.

Common misdiagnosis: a 1M revenue miss gets attributed to volume (sold fewer units) when the actual driver was discounting (sold same units at lower price). The misdiagnosis leads to the wrong intervention (hire more SDRs when the fix was pricing discipline). The three-variance decomposition separates the two drivers so the right conversation happens.

Variance trends are unreviewed

Each month variance stands alone, no trend tracking.

Variance analysis typically happens month to month without trending. Three consecutive months of 10 percent volume shortfalls might be reported as three separate misses rather than a pattern that needs structural response. Strkr tracks variance per component per period as a trend so patterns surface.

The three-variance decomposition

How volume, price, and mix variance separate.

The three cards below describe each variance component. The combined formula isolates the driver of a budget-to-actual revenue gap into three distinct levers so finance and sales conversations get specific.

Volume variance

(Actual volume - budget volume) x standard price.

Volume variance measures the revenue impact of selling more or fewer units than planned, holding price and mix constant. Formula: (actual volume minus budget volume) times standard price. If budget was 1,000 units at 50 dollars standard price and actual was 900 units, volume variance equals (900 - 1,000) x 50 which is negative 5,000. The 5K unfavorable variance comes purely from selling 100 fewer units.

Price variance

(Actual price - standard price) x actual volume.

Price variance measures the revenue impact of selling at a different price than planned, holding volume and mix constant. Formula: (actual price minus standard price) times actual volume. If standard price was 50 dollars and actual average was 46 dollars across 900 actual units, price variance equals (46 - 50) x 900 which is negative 3,600. The 3.6K unfavorable variance comes from discounting at 4 dollars below standard.

Mix variance

Volume variance across SKUs with weighted standard price.

Mix variance measures the revenue impact of selling a different product mix than planned. If the plan was 60 percent high-tier (100 dollars) and 40 percent low-tier (30 dollars) but actual was 40 percent high-tier and 60 percent low-tier, mix variance captures the revenue shortfall from the mix shift at constant volume and price. The formula sums (actual mix percentage minus budget mix percentage) times volume times standard price per SKU across all SKUs.

How to run variance analysis monthly

Six-step monthly workflow.

The six cards below describe the monthly variance analysis workflow. In Excel this takes finance 2 to 4 days per month. On Strkr the workflow runs continuously with the full analysis available at month close rather than days later.

Step 1 · Reconcile actuals

Confirm closed-won deals and billings.

Reconcile actuals by confirming closed-won deals for the period match billings. Returns and credits adjust the actuals. In Excel this takes 2 to 4 hours of CRM-plus-invoice reconciliation. In Strkr this runs continuously because actuals update per deal close.

Step 2 · Pull budget baseline

Confirm current budget version.

Pull the current budget baseline. Budget version drift is common (which version is current, were there mid-period adjustments). In Excel this requires locking the baseline file. In Strkr budget data lives in the same platform as actuals so the baseline is explicit.

Step 3 · Calculate volume variance

(Actual - budget) x standard price.

Calculate volume variance per SKU per segment. Multiply the volume gap by the standard price. Sum across SKUs for total volume variance. In Excel this takes 1 to 2 hours. In Strkr this runs natively.

Step 4 · Calculate price variance

(Actual price - standard) x actual volume.

Calculate price variance per SKU per segment. Multiply the price gap by actual volume. Sum across SKUs for total price variance. The price gap often reveals discounting patterns that are the real driver of the miss.

Step 5 · Calculate mix variance

Weighted mix impact across SKUs.

Calculate mix variance across SKUs with the weighted formula. The mix component is often the hardest to compute in Excel because it requires per-SKU volume and price data cross-referenced with budget mix. In Strkr the mix variance runs natively off the CRM data.

Step 6 · Narrate for leadership

The variance story in 3 bullets.

Narrate the variance for leadership: the volume component, the price component, the mix component. The three bullets drive the next-period conversation. Strkr runs an AI-drafted variance narrative that finance edits before sending to the CFO and CRO.

How Strkr runs variance analysis

Six capabilities that make variance analysis continuous.

The six cards below describe how Strkr runs variance analysis natively. The practical point is that variance analysis moves from a monthly manual exercise to a continuous surface that supports in-period intervention.

Live variance decomposition

Volume, price, mix variance live per period.

The variance decomposition runs live on CRM data. Volume variance, price variance, and mix variance update per deal close. Finance sees the variance pattern 20 days into the month rather than 5 days after close. Intervention windows exist.

Per-segment variance

SMB, mid-market, enterprise variance separately.

Variance decomposition runs per segment natively. Teams see which segment is driving the volume shortfall versus which is driving the price erosion. The segment-level view supports specific intervention: enterprise volume shortfall needs AE pipeline work; SMB price variance needs discount discipline.

Per-product variance

SKU-level volume, price, mix tracking.

Variance decomposition runs per SKU. Teams see which products contributed to the volume gap versus which contributed to the price gap. SKU-level data supports product strategy decisions (where to invest, which to simplify, which to retire).

Variance trend over time

Monthly variance history with pattern detection.

Variance history tracks per component per period. Three consecutive months of 10 percent volume shortfalls flag as a pattern rather than three separate misses. The pattern detection supports structural response rather than month-by-month firefighting.

AI variance narrative

Strkr AI drafts the variance story.

Strkr AI drafts the variance narrative from the decomposed data. The output: the volume driver, the price driver, the mix driver, and the recommended next-period focus. Finance edits the narrative before sending to leadership. The pattern replaces the hand-written variance commentary that typically takes an hour per month.

Budget-variance workflow

Budget data in the same platform.

Budget data lives in Strkr alongside actuals. Budget versions track with effective dates. Mid-period budget adjustments encode as versioned changes rather than file revisions. Variance analysis always runs against the current baseline without reconciliation work.

Head-to-head

Strkr versus Excel-based variance analysis.

The head-to-head below is Strkr with native variance analysis against the common pattern of finance running variance analysis in Excel after month close.

Feature Strkr Excel-based variance analysis
Analysis timing Live during the period 2-4 days after month close
Three-variance decomposition Native volume, price, mix split Often just total variance
Per-segment analysis Native slicing Rebuild per segment manually
Per-SKU analysis Native per-product variance Separate pivot per product
Budget data location Same platform as actuals Separate planning file
Trend tracking Variance history with pattern Month-by-month in isolation
Variance narrative AI-drafted, finance edits Hand-written each month
In-period intervention Possible (live data) Not possible (data lands late)
Budget version management Versioned with effective dates File-based, drift common
Finance time per month Hours (review and narrate) Days (reconstruct and calculate)
How teams use Strkr

Teams running variance analysis natively.

The four playbooks below are from finance and RevOps teams who moved sales volume variance analysis from Excel to Strkr. Each describes the structural change and the measurable improvement in cycle time and decision quality.

B2B SaaS, 50 reps

Variance analysis cycle time dropped from 3 days to 2 hours.

A 50-rep B2B SaaS team ran variance analysis in Excel after month close. The analysis typically took 3 days of finance time to reconcile CRM data, pull budget baseline, calculate the three variances per segment, and draft the narrative. The team moved to Strkr with budget data colocated with actuals. The variance analysis available at month close required 2 hours of finance review and narrative editing. The CFO said the structural change was that finance could support in-cycle decisions rather than retrospective reports.

Mid-market services, 30 reps

Price variance decomposition revealed discounting pattern.

A 30-rep mid-market services firm had been missing revenue targets by 12 to 18 percent for 3 consecutive quarters. The variance was attributed to volume (SDR hiring). The team moved to Strkr and ran the three-variance decomposition. The actual driver was 60 percent price variance (persistent discounting) and 40 percent volume variance. The intervention shifted from more SDR hires to discount approval thresholds and pricing training. Price variance closed to near-budget in the following quarter. The CFO said the structural change was that the right driver got the right intervention.

Enterprise B2B, 90 reps

Mix variance surfaced product strategy signal.

A 90-rep enterprise B2B team had been seeing flat revenue despite 10 percent volume growth. The team ran mix variance analysis in Strkr. The analysis showed negative mix variance equal to the volume growth: the mix was shifting toward lower-tier SKUs faster than overall volume was growing. The pattern drove product strategy work (repositioning the mid-tier SKU, retiring the lowest-tier SKU, new discount discipline). Mix variance returned to flat in two quarters. The CFO said the structural change was that mix shift became a measurable business driver rather than a feeling.

Growth stage, 20 reps

Variance trend tracking caught volume pattern early.

A 20-rep growth stage SaaS team used Strkr variance trend tracking from day one. In month 2 the volume variance pattern flagged as declining: month-over-month volume variance had moved from plus 5 percent to minus 8 percent to minus 12 percent. The pattern surfaced before quarterly review. The team investigated and found the inbound-to-outbound ratio had drifted below plan due to a marketing campaign ending. The team adjusted outbound sequencing to cover. Volume variance returned to plan in the following month. The VP of RevOps said the structural change was that variance patterns surfaced in-cycle rather than at QBR.

Run variance analysis continuously instead of monthly.

Start a 14-day trial on Strkr with the three-variance decomposition (volume, price, mix) ready to run on your CRM data. See what variance analysis looks like when it runs live rather than after close.

Start free trial See pricing
Common questions

What buyers in this bucket ask most.

What is sales volume variance?

Sales volume variance measures the revenue impact of selling more or fewer units than budgeted, holding price and mix constant. Formula: (actual volume minus budget volume) times standard price. A positive variance means more units sold than planned (favorable); a negative variance means fewer units sold (unfavorable). The metric isolates the volume component of a budget-to-actual revenue gap so finance and sales conversations get specific about the driver.

How does volume variance differ from price variance?

Volume variance measures the impact of selling more or fewer units at standard price. Price variance measures the impact of selling at a different price than standard, holding volume constant (actual price minus standard price times actual volume). A revenue miss can be driven by volume (sold fewer units), price (sold at a discount), or mix (sold more low-tier SKUs). The three-variance decomposition separates the drivers so the intervention matches the problem. A volume problem needs more pipeline; a price problem needs discount discipline; a mix problem needs product strategy work.

What is mix variance?

Mix variance measures the revenue impact of selling a different product mix than planned. If the plan was 60 percent high-tier and 40 percent low-tier, but actual was 40 percent high-tier and 60 percent low-tier, mix variance captures the shortfall from the mix shift at constant volume and price. The formula sums (actual mix percentage minus budget mix percentage) times volume times standard price per SKU across all SKUs. Mix variance often signals pricing pressure or product-market fit shift.

How does Strkr calculate variance in real time?

Strkr runs the three-variance decomposition natively on the CRM data. Actuals update per deal close. Budget data lives in the same platform as actuals with versioned effective dates. The formulas calculate per SKU per segment per period continuously. Finance sees the variance decomposition 20 days into the month rather than 5 days after close. The pattern supports in-period intervention when variance signals that targets are at risk.

Can we compare variance across periods?

Yes. Variance history tracks per component per period. Three consecutive months of 10 percent volume shortfalls flag as a pattern rather than three separate misses. The trend view shows volume variance, price variance, and mix variance as separate trend lines. Pattern detection surfaces persistent variance drivers so structural response happens rather than month-by-month firefighting. The trend view is particularly useful for identifying slow-building issues like gradual discount erosion or mix shift.

What finance teams typically own variance analysis?

Variance analysis is typically owned by the FP&A (Financial Planning and Analysis) team working closely with RevOps or Sales Operations. In smaller companies without a dedicated FP&A function, the CFO or Controller runs the analysis directly. The variance report typically goes to the CFO, CRO or VP of Sales, and CEO monthly. Strkr's native variance analysis typically reduces the FP&A time per month from 2 to 4 days to 2 to 4 hours of review and narrative editing, freeing FP&A for forward-looking planning work.

Also built for

Related audiences.

Sales Volume Definition Sales Velocity Definition Sales Tracking CRM Sales System For RevOps For Sales Managers

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing