Designing a KPI Tree: From One North Number to Team Levers
A virtual CFO's method for a KPI tree: decomposing one north number into the arithmetic drivers and the lever each team owns, without dashboard sprawl.
Most businesses do not have a KPI problem; they have a KPI-collection problem. Dashboards fill with dozens of metrics, everyone watches all of them, and nobody can say which two or three actually move the business. A KPI tree fixes this by working the other way: start from the single number that matters most and decompose it into the handful of drivers beneath it, each owned by someone who can act on it. This is a virtual CFO’s method for building one, and it is decomposition, not collection.
Published: July 2026
A KPI tree starts with one number at the top: the north number that best captures whether the business is winning. For a SaaS business that might be net new recurring revenue; for a services firm, revenue or gross profit; for a product business, contribution. The choice matters less than the discipline of picking exactly one, because a business with three north numbers has none, and when two goals conflict the single north number is what breaks the tie.
From that top number you decompose downward, and the rule of the decomposition is that it must be arithmetic: each level should multiply or add up to the level above it, so the tree is a genuine breakdown of the number rather than a loose collection of related metrics. Below the north number sit its three or four direct drivers, the things that arithmetically produce it. Below each driver sit the levers a specific team can actually pull to move it. The result is a tree that connects the one number the founder watches all the way down to the daily actions of the people who influence it. This is the reporting-design companion to the live board reporting cornerstone and a common 90-Day Number output, and it pairs with the two-number board meeting.
Take net new ARR as the north number. It decomposes arithmetically into new-business ARR plus expansion ARR minus churned ARR. That is the first level, three drivers that literally sum to the top number.
Each driver then decomposes further into levers a team owns. New-business ARR breaks into leads times conversion rate times average contract value, owned by marketing (leads), sales (conversion), and pricing or sales leadership (contract value). Expansion ARR breaks into the number of accounts eligible to expand times the expansion rate times the expansion size, owned by customer success and product. Churned ARR breaks into accounts at risk times the save rate, owned by customer success and onboarding. Now the founder can look at a disappointing net new ARR and trace it precisely: not “sales is down” but “conversion held, but expansion rate dropped because the mid-tier upgrade path stopped working”, which points at a specific team and a specific fix. That traceability is the entire value of the tree. It connects directly to net revenue retention, which is the expansion-and-churn part of the same tree.
For a services firm the north number is often revenue, and it decomposes into capacity times utilisation times realised rate. Capacity is the billable headcount and their available hours, owned by resourcing and hiring. Utilisation is the share of those hours that become billable, owned by delivery leads and the resourcing function. Realised rate is what the firm actually collects per hour after write-downs, owned by pricing and engagement management.
This tree makes a stalled revenue number diagnosable in the same way. Revenue flat despite a full team? The tree asks whether utilisation slipped (a bench is forming, business development needs attention), whether realised rate fell (write-downs are eroding value, an engagement-management problem), or whether capacity is truly maxed (the constraint is hiring). Each answer points at a different team and a different action, which is what turns a vague “we need more revenue” into a specific intervention. The capacity leg draws directly on capacity modelling for services firms.
The single most important design rule is that every leaf of the tree, every bottom-level lever, has exactly one owner. A metric owned by everyone is owned by no one, and a tree whose levers float without ownership becomes wallpaper like the dashboards it was meant to replace. Assigning each lever to a named person or team does two things: it makes the tree actionable (someone is accountable for moving each number), and it makes the reporting meaningful (a movement in a lever has a person to explain and address it).
This ownership discipline is also what keeps the tree honest. If a proposed lever has no natural owner, it is probably not a real lever, and it should be pruned. The tree should map cleanly onto the organisation, so that reading the tree top to bottom traces from the founder’s north number down to the specific people whose work moves it.
The discipline that keeps a KPI tree useful is ruthless pruning, governed by a simple test: if nobody would act on a metric weekly, it does not belong in the tree. Interesting is not the bar; actionable is. A great many metrics are worth knowing occasionally but do not drive weekly action, and putting them in the operating tree buries the few that do. The tree is not a data catalogue; it is the small set of numbers the business steers by, and every metric in it should earn its place by changing what someone does.
Applied, the sprawl test usually shrinks a proposed tree dramatically, which is the point. A tree with a north number, three or four drivers, and two or three levers under each is legible and actionable. A tree with forty metrics is a dashboard by another name. Keeping it small is harder than making it big, and it is what separates a KPI tree that runs a business from one that merely decorates a wall.
A KPI tree earns its value through rhythm. The north number and its drivers are reviewed at whatever cadence matches the business, typically weekly for the operating levers and monthly for the higher branches, and the review is structured by the tree: start at the north number, and where it is off, walk down the branch that explains why. This turns a review meeting from a tour of every metric into a targeted diagnosis, which is faster and more useful. The tree, reviewed this way, becomes the operating instrument the dashboard never was.
What is a KPI tree?
A structured decomposition that starts with the single most important number in the business, the north number, and breaks it down arithmetically into the few drivers that produce it and the levers each team can pull to move them. It connects the one number the founder watches to the daily actions of the people who influence it, replacing a sprawling dashboard with a legible, actionable structure.
How is it different from a dashboard?
A dashboard collects metrics; a KPI tree decomposes one number. A dashboard shows you everything and lets you work out what matters; a tree starts from what matters and shows only the drivers and levers beneath it. The tree is arithmetic (each level produces the one above) and owned (each lever has one accountable person), which a dashboard usually is not.
How do I choose the north number?
Pick the single number that best captures whether the business is winning: net new ARR for SaaS, revenue or gross profit for services, contribution for a product business. The specific choice matters less than picking exactly one, because a business with three north numbers has none, and the single number is what breaks the tie when two goals conflict.
Why must the decomposition be arithmetic?
Because an arithmetic tree is a genuine breakdown of the number rather than a loose collection of related metrics. If each level multiplies or sums to the level above, you can trace a disappointing top number precisely to the driver and lever responsible. A non-arithmetic collection of “important metrics” cannot do that, which is what makes it wallpaper.
What is the ownership rule?
Every bottom-level lever has exactly one owner. A metric owned by everyone is owned by no one. Assigning each lever to a named person or team makes the tree actionable and the reporting meaningful, and it keeps the tree honest: a proposed lever with no natural owner is probably not a real lever and should be pruned.
How do I stop the tree sprawling?
Apply the sprawl test: if nobody would act on a metric weekly, it does not belong. Interesting is not the bar; actionable is. Applied, this shrinks a proposed tree dramatically, leaving a north number, three or four drivers, and two or three levers each, which is legible. A forty-metric tree is a dashboard by another name.
Can a virtual CFO design my KPI tree?
Yes. Designing the tree, choosing the north number, decomposing it arithmetically, assigning ownership, and pruning to the actionable few, is a defined deliverable and a natural 90-Day Number. The output is a tree you own, mapped onto your organisation, plus the review cadence that turns it into an operating instrument rather than another dashboard.
Sydney Virtual CFO is a Sydney-based virtual CFO service for founders running $2M to $15M businesses across SaaS, ecommerce, professional services, construction, and other low-volume, high-value industries. We deliver fixed-scope CFO engagements with a named deliverable on day 90: a 13-week cashflow forecast, a fundraise-ready financial model, a unit economics build, or a board reporting pack you can run on your own.
Our front-door product, the 90-Day Number, is fixed scope at $17,850 plus GST. We are one of the few project-based virtual CFOs in Australia, in a market built almost entirely on monthly retainers. No retainers without a deliverable. No 80-page reports. No theatre.
Visit Sydney Virtual CFO | The 90-Day Number | Book a Call
This content is general information only, written for Australian founders running businesses in the $2M to $15M revenue range. It does not constitute tax, financial product, investment, or legal advice and should not be relied on as such. The work referenced is led by a Chartered Accountant (CA ANZ), but Sydney Virtual CFO is not a licensed tax agent, not a licensed financial adviser, and not authorised to provide personal financial advice. Tax obligations, accounting treatments, fundraise terms, and statutory requirements depend on your individual circumstances. For advice specific to your business, contact the team directly or consult a registered tax agent, licensed financial adviser, or qualified lawyer. Information was current at the time of publication and may change without notice. We review and update guides periodically.
