Metric tree examples for every business model

If you have already read our guide to what a metric tree is, you know the core idea: start with one North Star metric, then decompose it into the drivers and sub-drivers that explain how that number moves. The theory is simple. The challenge is applying it to your specific context.

Every business model has different revenue mechanics, different funnel shapes, and different team structures. A SaaS company cares about expansion revenue and churn. An e-commerce brand cares about sessions and average order value. A marketplace has to balance supply and demand. These differences mean the metric tree structure must change too.

The metric tree examples below give you a concrete starting point. Use them as templates, adapt the metrics to your own context, and follow our step-by-step building guide to turn the template into a living system that drives real decisions.

For most SaaS businesses, Annual Recurring Revenue (ARR) is the North Star. It captures growth, retention, and expansion in a single number. This SaaS metric tree decomposes ARR into three first-level drivers: new business, expansion within existing accounts, and churn.

New ARR is driven by the volume of qualified leads, the percentage that convert to paying customers, and the average revenue per user (ARPU). Marketing owns lead volume. Sales owns conversion rate. Product and pricing own ARPU. Each team has a clear metric they influence.

Expansion ARR captures upsells, cross-sells, and seat expansions from your existing customer base. This is often the most capital-efficient growth lever and belongs to customer success and account management.

Churned ARR splits into voluntary churn, where customers actively decide to leave, and involuntary churn, which happens through failed payments or expired cards. The distinction matters because the teams responsible and the actions required are completely different. Product and support can reduce voluntary churn through better onboarding and engagement. Engineering and payments can reduce involuntary churn through retry logic and dunning flows.

This metric tree template makes it immediately clear where ARR is growing, where it is leaking, and who should act. That is the power of mapping cause and effect rather than simply reporting a single revenue number.

An e-commerce metric tree typically starts with Revenue as the North Star and decomposes it into the classic formula: Sessions multiplied by Conversion Rate multiplied by Average Order Value. This simple equation is powerful because it separates three fundamentally different challenges: getting people to the site, persuading them to buy, and maximising the value of each transaction.

Sessions break down by acquisition channel: organic search, paid media, direct traffic, and email. Each channel has different economics and different owners. Your SEO team drives organic sessions. Your performance marketing team drives paid sessions. Breaking traffic into channels lets you see where growth is coming from and where your spend is efficient.

Conversion Rate decomposes into a funnel of its own: add-to-cart rate, checkout rate, and payment success rate. This is where many teams discover their biggest opportunities. A small improvement in checkout rate can have a larger revenue impact than a large increase in traffic. The metric tree makes that tradeoff visible.

Average Order Value can be further broken into items per order and average item price, or influenced by bundling, upsells, and free shipping thresholds. Your merchandising and product teams own this branch.

This e-commerce metric tree example helps every team understand not just their own numbers, but how their work connects to revenue. When your paid media team sees that conversion rate is dropping, they know that more spend will not solve the problem. That shared understanding is what a well-structured metric tree creates.

Marketplaces have a unique challenge: they must grow supply and demand simultaneously. Gross Merchandise Value (GMV) is the natural North Star because it captures total transaction volume across the platform. This marketplace metric tree decomposes GMV into four first-level drivers and then branches into the supply side and demand side of the business.

The first level tells you that GMV is a function of how many sellers are active, how many listings each seller maintains, how often those listings convert into transactions, and the average value of each transaction. It is a multiplication chain, so improvement in any single factor lifts the whole.

Supply side metrics focus on seller acquisition and retention. Your marketplace operations and seller success teams own this branch. The key question is whether you are adding enough new sellers to replace those who leave, and whether existing sellers are listing enough inventory to meet buyer demand.

Demand side metrics focus on buyer engagement. Active buyers multiplied by orders per buyer gives you total order volume. Your growth, marketing, and product teams own this. If demand outstrips supply, you get poor buyer experience. If supply outstrips demand, sellers churn. The metric tree makes this balance visible so leadership can allocate resources to whichever side needs attention.

A marketplace metric tree is especially valuable because it prevents the common mistake of optimising one side of the marketplace at the expense of the other. When both branches live in the same tree, the tension between supply and demand becomes a healthy, data-driven conversation.

B2B and enterprise businesses face long sales cycles, multiple stakeholders, and complex handoffs between marketing and sales. A B2B metric tree brings structure to that complexity. Revenue is the North Star, decomposed into Pipeline, Win Rate, and Average Deal Size, with separate branches for marketing contribution and sales execution.

Pipeline is the total value of qualified opportunities. The marketing branch shows how pipeline is built: Marketing Qualified Leads (MQLs), the rate at which MQLs become Sales Qualified Leads (SQLs), and the rate at which SQLs become real opportunities. This metric tree makes the marketing-to-sales handoff measurable. If the MQL-to-SQL rate is low, either marketing is generating the wrong leads or sales is not following up effectively. Either way, the data points to where the conversation needs to happen.

Win Rate is owned by the sales team and can be further decomposed into demo-to-proposal rate and proposal-to-close rate. Each stage represents a different skill: discovery, solution design, negotiation, and procurement navigation. When win rate drops, this decomposition shows exactly where deals are stalling.

Average Deal Size can be influenced by targeting strategy, product bundling, and pricing. If your average deal size is falling, the metric tree helps you determine whether it is a targeting problem (smaller companies entering the funnel) or a packaging problem (fewer products per deal).

The power of a B2B metric tree is that it forces marketing and sales to share a single model of how revenue is generated. When both functions see the same cause-and-effect chain, finger pointing gives way to problem solving.

The examples above are starting points. Your metric tree should reflect how your business actually works, not how a textbook says it should work. Here is how to adapt them.

1. 1

   Start with your North Star

   Pick the single metric that best represents value creation for your business over the next 12 to 18 months. For most companies this is some form of revenue, but it could also be active users, transactions processed, or another metric that captures your core value proposition.

2. 2

   Decompose using real equations

   Every level in your metric tree should be connected by real mathematical relationships: multiplication, addition, or subtraction. If you cannot write the equation, the decomposition is not rigorous enough. This discipline is what separates a metric tree from a list of KPIs.

3. 3

   Match branches to teams

   The deepest level of your metric tree should map to the teams or individuals who influence those numbers. If a metric does not have a clear owner, it is either too abstract or it sits at the wrong level. Ownership is what turns a metric tree from a diagram into a management system.

4. 4

   Keep it to three or four levels

   More than four levels of depth usually means you are mixing strategic metrics with operational ones. The goal is clarity, not completeness. You can always expand a branch later when a team needs to dig deeper into their specific area.

These metric tree examples are useful as templates, but a diagram on a whiteboard only goes so far. The real value comes when you connect your metric tree to live data, assign ownership to every node, and track the actions people take to move each metric.

When a metric tree is connected to real numbers, something changes. Teams stop debating what is happening and start discussing why it is happening and what to do about it. The cause-and-effect structure makes it obvious which driver is pulling revenue up or dragging it down. That shared understanding is what creates alignment without the need for endless status meetings.

Ownership turns passive reporting into active accountability. When every node in the metric tree has a person or team responsible, there is no ambiguity about who should investigate a drop or capitalise on an improvement. People pay more attention to metrics they own, and they take better action when they understand how their metric connects to the bigger picture.

Tracking actions alongside metrics closes the loop. It is not enough to know that conversion rate fell. You need to know what experiments are running, what changes were deployed, and which initiatives are in progress. When actions are tracked against the metric tree, you create a feedback loop between decisions and outcomes. That feedback loop is how organisations learn and improve over time.

KPI Tree is built to bring metric trees to life. You can explore the platform to see how teams connect their metric trees to live data, assign ownership, and track the actions that move their numbers.