Revenue Driver Tree

Revenue driver tree

This driver tree breaks subscription revenue into two practical levers: the size of the customer base and the revenue earned from each customer. The customer-base branch points to acquisition, churn, and expansion. The revenue-per-customer branch points to price, packaging, and mix. That structure helps a team discuss revenue without treating it as one unexplained number. Add a formula and current value to each leaf when the tree becomes a planning model. For example, active customers may be prior customers plus new customers minus churned customers. Use consistent definitions so finance, sales, and product teams are analysing the same drivers. It gives readers a concise reference they can reuse when discussing the result with colleagues.

유형 의사결정 트리표준 Howard-Raiffa / CART-sklearn / taxonomy엔진 schematex-decisiontree업데이트됨 2026. 9. 24.

요청 내용

“A revenue driver tree for a subscription business. Split revenue into Customer base and Revenue per customer, then include acquisition, churn, expansion, price, packaging, mix, usage, and retention.”

그렇다면Add a separate annual versus monthly plan branchAdd a metric to each leaf

이 도면에 담긴 내용

그 이면의 의사결정을 읽어 보세요.

01Customer base

Separate acquisition, churn, and expansion effects.

02Revenue per customer

Separate price and product-mix effects.

03Measures

Attach an owner and metric to each leaf.

Use for a SaaS revenue plan or a monthly operating review.

모든 의사결정 트리 템플릿 보기 →

자주 묻는 질문

What is a driver tree?

A hierarchy that shows the measurable factors contributing to a top-level metric.

Why split revenue this way?

Customer count and revenue per customer are distinct levers with different owners.

Can I add formulas?

Yes. Add the equations and metrics that match the business model.