Metric trees for finance teams

You close the month. Then the arguments start.

Finance teams spend the month assembling numbers and the meeting defending them. The work that actually matters, explaining what drove the miss and getting someone to act on it, happens afterwards, by email, if it happens at all.

Variance analysis that stops at the gap

Revenue missed by 8%. But was it volume, price, mix or churn? Your spreadsheet tells you the size of the gap. It does not tell you which operational metric three levels down actually moved. You present the shortfall, the board asks why, and you promise to follow up.

A plan and actuals that cannot agree on the maths

Your budget lives in a planning tool with its own aggregation logic. Your actuals live in the warehouse with another. When the two diverge, the first twenty minutes of every review are spent arguing about whose number is right, and the reforecast adds a third version. Nobody discusses why the number missed, because nobody trusts the number.

Every miss becomes finance's chase

The period closes. A target is missed. Nothing happens until someone in finance spots it, works out who to chase, and starts an email thread. By the time an owner is found and an action agreed, the next period is half gone, and there is no record of whether the last fix worked.

Decompose your P&L into a causal model

Build a metric tree that mirrors your P&L, then extends into the operational metrics that drive each line. Revenue breaks into channels, channels into volume and conversion, conversion into the activities that move it. Every relationship is a directed driver edge with a confidence level and statistical significance, tested against your data nightly, and your team prunes the correlations that are coincidence. When a number moves, you follow the tree to find out why.

Map every P&L line to the operational drivers beneath it, across sales, marketing, product and operations
See a confidence level and statistical significance on every driver relationship, recalculated nightly as new periods land
Drill from a board-level variance to the team and activity that caused it
Metrics stay current automatically, synced from your warehouse and semantic layer

Run the plan through the same pipeline as the actuals

Business models hold your budgets, forecasts, targets and ramp profiles inside KPI Tree, aggregated by the identical calculation pipeline as your actuals. Plan and reality can never disagree about how they were computed, so a variance review starts at the variance rather than at an argument about the maths. And because both sides live in one model, your team, and the AI agents they use, get the same answer when they ask how performance stands against plan.

Compare plan against actuals directly on the canvas, at any date, granularity or comparison period
Model ramp profiles for new initiatives, so growth follows a realistic adoption curve rather than a flat assumption from day one
Switch to the grid view when you want rows and columns, a familiar spreadsheet layout with the comparison at every date
One calculation pipeline computes both plan and actuals, so no meeting opens with whose number is right

Break any variance into the drivers that caused it

When a metric misses, a waterfall chart breaks the movement into what each driver contributed, colour-coded by whether it helped or hurt. From there you trace the chain level by level to the operational input that actually moved, with confidence levels and statistical significance attached at every step. The follow-up you used to owe the board is already on the canvas.

Waterfall charts show what each driver added to or took away from the variance
Trace a miss through every level of the tree to the input that moved, not just one hop
Driver contributions carry confidence levels and statistical significance, so you can say how sure the model is
Distinguish an isolated blip from a systemic shift building across several levels of the tree

Close the period and the misses route themselves

Every metric carries RACI ownership, so a miss already has a name on it. A period-close trigger fires when a metric ends the period short of its target, within a tolerance you set, and notifies the named Accountable owner with the drivers attached. Workflows carry the response from there: approvals are first-class steps, escalation follows your live org chart, and every action is tracked against the metric it was meant to move, with the impact verified against the numbers at the next close rather than taken on trust. When the response is funded work, initiatives carry their budget and spend, and the Portfolio view shows whether the money moved the metrics it targeted.

Period-close triggers fire when a metric misses its target and notify the named Accountable owner, not a channel
Approvals are first-class workflow steps, so the next action only runs once the named reviewer signs off
Escalation moves up the live org chart automatically when nobody acts
Actions are tracked against the metric they were meant to move, and the impact is verified rather than self-reported

“Your FP&A tool holds the plan. Your BI tool reports the actuals. Neither can break the variance into drivers, put a named owner on the miss, or prove the fix worked.”

Beyond variance reporting

Spreadsheets and BI dashboards are built to report the numbers. They flatten your P&L into rows and charts with no explicit connections, no plan context and no owners. KPI Tree gives finance a causal model of the business that is measured, owned and verified.

Causality with the workings shown

Every relationship in the tree carries a confidence level and statistical significance, statistically proven over time rather than asserted in a meeting. Your team prunes the false positives, so what remains is a model you can stand behind when the board asks why.

One pipeline for plan and actuals

The same calculation pipeline that computes your actuals computes your budgets, forecasts, targets and ramp profiles, at every granularity and comparison period. Plan versus actual becomes a comparison, not a reconciliation project.

Misses that route themselves

When a metric misses its target at period close, crosses a threshold or goes quiet, the push goes to the named Accountable owner and escalates up the live org chart until someone acts. Finance stops being the chasing function.

Common questions

How does this connect to our existing financial data?

KPI Tree connects to Snowflake, BigQuery, Databricks, Redshift, Azure SQL and PostgreSQL, and syncs metric definitions from dbt, Looker and Snowflake Semantic Views. Google Sheets covers the numbers that live outside the warehouse, and any MCP-compatible tool, such as Stripe or HubSpot, can feed metrics too. Metrics are calculated where the data lives, so the numbers always match your warehouse.

Is this a replacement for our BI or FP&A tools?

No. Your BI tool stays for dashboards and ad hoc queries, and you can keep building budgets wherever you build them today. KPI Tree adds the layer neither provides: a causal model of what drives each P&L line, your plan and actuals computed by one pipeline, a named owner on every metric, and verification that the actions taken actually moved the numbers.

How do budgets and forecasts get into KPI Tree?

Through business models. A business model holds budgets, forecasts and targets alongside your actual metric values, aggregated in exactly the same way, so you can compare plan against reality across any time period, granularity or comparison directly on the canvas. Each metric can carry its own ramp profile, so a new initiative follows a realistic adoption curve rather than a flat line from day one.

What happens when a metric misses its target at period close?

A trigger fires at the end of the period, with a tolerance you set for how far the metric can slip, and notifies the named Accountable owner through Slack or email with the driver context attached. If nothing happens, escalation follows your live org chart to their manager. Every run is recorded, so you can see the exact path each miss took from trigger to action.

Can we see whether the money we spent actually moved the numbers?

Yes. Initiatives carry a budget, actual spend, an owner and milestones, and link to the metrics they are meant to move. The Portfolio view reads across all of them, scoring each initiative by how far its target metrics have moved since the work began, in the direction it intended. Because execution is tracked separately from outcome, you can see immediately where money was spent, work was delivered and the number still did not move.

Can we model different P&L structures for different business units?

Yes. You can build separate metric trees for different business units, geographies or product lines. Each tree has its own structure, owners and targets while rolling up to a consolidated view. The model adapts to how your business is actually organised.

Related guides