KPI tree is a diagram that decomposes one headline metric into the smaller metrics that feed it.

How it works

Start with a root KPI — for a SaaS company, net new ARR this quarter. Branch one: new ARR from new customers (logos × average contract value). Branch two: expansion from existing customers. Branch three: churn (negative). Each node splits until you reach metrics a team can directly influence — outbound meetings booked, activation rate, support tickets per account.

When the root misses plan, the tree shows whether the problem is acquisition, conversion, expansion, or retention — not guessing in a leadership meeting.

Why it matters

• Founders: Align functional leads on shared drivers instead of siloed OKRs that conflict.
• Investors: A credible KPI tree in a board deck signals operational maturity and makes variance explanation faster.

Walk the tree in monthly reviews: if net new ARR missed, drill to whether pipeline generation, win rate, or sales cycle slipped. Operators assign each leaf metric to one owner to avoid diffusion of responsibility.

Investors sometimes ask for a KPI tree slide in Series B diligence to test whether the CEO understands drivers or only repeats headline growth.

Common mistake

Building a tree so deep it becomes unmaintainable. Three to four levels is usually enough for a startup.

Practical takeaway

Rebuild the KPI tree when strategy shifts — a marketplace pivot may change the root from GMV to contribution margin. Outdated trees misallocate team focus and produce board conversations that chase the wrong levers.

Related ideas

• KPI
• North star metric
• Driver-based forecasting