Revenue decline hypothesis tree
A revenue decline hypothesis tree separates the main drivers of a commercial result into claims that can be checked. A team can distinguish acquisition, conversion, retention, price and reporting explanations rather than react to the total alone. Each branch should lead to a measurable comparison, such as cohorts, pipeline stages, discount records or the finance close. The tree is useful in a business review because it clarifies what is known, what is only assumed and who will validate each assumption.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
A commercial team investigates a month-over-month revenue decline.
Key decisions
- Validate reporting: Confirm that periods and source data are comparable.
- Test acquisition: Separate lead volume from conversion and sales capacity.
- Test retention: Segment cancellations and spend contraction.
- Test price: Compare realized price and discount changes.
When to reuse this
Use when a revenue result needs structured diagnosis before a commercial response.
Frequently asked questions
What are common revenue drivers?
Should I include actions in the tree?
Who should review it?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.