Executive use case 01

Explain margin and production variance - back to the drivers behind it.

The board does not want to know that margin missed. They want to know why, which lever moved it, and whether it is structural or one-off. Helm traces every variance through the twin's value-driver model and returns a ranked, plain-language explanation - with full lineage to source.

What it does

From "we missed" to "here is exactly what moved it."

A variance is rarely one number. It is a stack of offsetting effects - volume up, price down, a cost overrun masking an otherwise strong month. Helm decomposes the result into the drivers that actually explain it, separates the favourable from the adverse, and keeps each component tied to the model and the underlying data. Two worked examples follow: one at the financial P&L level, one at the operational driver level.

Financial variance · P&L decomposition

Why did we beat the Profit After Tax target?

The Analyst takes a top-line financial result - WMC's Profit After Tax of $14.8M actual against a $6.4M budget, a +$8.4M favourable variance - and decomposes it into the P&L drivers pulling in each direction. The beat was real, but the waterfall shows it was held back: logistics and admin overruns quietly absorbed a chunk of the upside.

  • Favourable: Turnover +$7.5M, Stock Movement +$4.6M, Production Costs +$3.8M, FX +$2.3M
  • Adverse: Logistics Costs –$4.9M, Head Office & Admin –$1.9M, Other –$1.8M, Commission –$1.2M
  • Each driver carries its baseline, target and absolute variance, ranked by contribution
  • Conclusion: a genuine beat, but logistics cost control is the next question to drill into
helm.managedanalytics.ai
DEMO A - P&L-level decomposition of Profit After Tax into its driver contributions.
Operational variance · Shapley decomposition

What moved turnover by grade - volume, price, or grade itself?

Here the variance sits inside a multiplicative revenue formula - volume × grade × price × compliance × FX - where the drivers interact and cannot simply be added up. Turnover by grade came in at $31.5M against a $24.3M budget, a +$7.2M favourable variance. The Analyst applies Shapley decomposition so each driver receives a fair share of the result.

  • Sales Volume +$13.6M - the dominant effect; volume more than doubled (132k → 268k tons)
  • Partly given back by FX Rate –$2.5M and lower Grade –$2.1M
  • Price –$1.4M and Compliance –$0.4M were comparatively minor
  • The headline is overwhelmingly a volume story - not a pricing or grade story
helm.managedanalytics.ai
DEMO B - Driver-based decomposition of a non-additive revenue formula via Shapley.
How the analysis is generated

Not pattern-matched text. Decomposition through the model.

Both explanations are produced the same way - the difference is only how the driver structure is wired in the twin. The Analyst reasons over the model, not over a table of numbers.

STEP 01 · RESOLVE

Resolve & retrieve

The question is resolved against the twin's financial and operational vocabulary. The Analyst identifies the metric, the entity and the period, then pulls actuals and budget straight from source - with lineage attached to every figure.

  • Intent mapped to twin entities
  • Actual vs budget retrieved
  • Source lineage preserved
STEP 02 · DECOMPOSE

Decompose through the driver model

Variance is split through the twin's value-driver structure. Additive structures decompose directly; multiplicative or formula-based structures - where drivers interact - are decomposed with Shapley, so each driver gets a fair, defensible attribution.

  • Driver tree, not flat arithmetic
  • Shapley for non-additive formulas
  • Favourable and adverse separated
STEP 03 · EXPLAIN

Rank, narrate & cite

Drivers are ranked by contribution and direction, a plain-language narrative is drafted, and the result is laid out as a waterfall and table. Every number stays traceable to source data and twin lineage - ready for board, audit and regulator scrutiny.

  • Ranked driver contributions
  • Auto-drafted commentary
  • Full provenance for review
Used by

CFO. COO. Divisional GMs. FP&A teams.

Anyone who runs a monthly business review and is tired of the diagnostics taking longer than the action items - and anyone who has had to explain a variance to the board without a defensible breakdown behind the number.

Outcomes our customers report
  • Days, not weeks to diagnose material variance.
  • Defensible driver attribution, with lineage to source data.
  • One method across financial and operational variance alike.

NoteBoth demo animations are extracted from live AI Analyst query sessions. Run-time has been compressed for display purposes — actual query durations typically range from one to three minutes. The data shown is simulated.

Where this lives

Variance analysis is part of the Understand pillar.

Live performance, explained by the model - variance, value drivers and causal explanations, all grounded in the twin.

See it on your own variance pack.

We'll show Helm decomposing a variance on a business that looks like yours - same value chain, similar reporting cadence, real numbers redacted as needed.