Decomposing the variance
Total variance = price variance (rate changed) + volume variance (usage changed) + mix variance (workload shifted between services) + unexplained variance (the residual nobody owns yet). A $40K monthly variance that is 80% volume is a product/engineering conversation; the same variance that is 80% price is a procurement / commitment-discount conversation.
Favorable vs unfavorable
Favorable variance (actual < budget) isn't always good — it can mean a launch slipped, a customer churned, or a feature wasn't released. Unfavorable variance (actual > budget) isn't always bad — it can mean a customer onboarded faster than expected. Variance is a signal, not a verdict.
Related concepts
Who tovin.io is for
Frequently asked
How often should variance be reviewed?
Monthly during close, weekly during a budget-sensitive period (pre-funding, pre-board, post-launch). Daily review usually adds noise without signal.
What's a reasonable variance band?
Most SaaS finance teams flag variance over ±5% of budget for explanation, ±10% for action. The right band depends on cloud bill size and revenue volatility.