Core-Input KPI Tree
Trace one dated goal back to the few inputs that create it
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 97%
Kagan starts with one measurable goal and a date, then works backward to the smallest useful KPI tree. For AppSumo's revenue goal, the top-level equation is traffic multiplied by conversion rate and average order value. Those outputs can then be traced to a more controllable core input: the number of strong software deals offered each month. The company posts leading metrics regularly, but Kagan says a spreadsheet is enough for an early business. The value of the model is not the dashboard's complexity; it is the explicit link between daily work and the singular result. Teams can inspect subordinate drivers when needed while preserving a simple top-level view that supports prioritization and course correction.
Origin
Kagan explains AppSumo's daily metric post, annual revenue goal, three revenue KPIs, and core monthly deal input.
Core principles
- 01Start with one measurable goal and a deadline
- 02Keep the top-level KPI set small
- 03Use arithmetic to connect inputs to the outcome
- 04Find the core controllable input beneath output metrics
How to run it
- 1
Set one destination
Define one numerical goal and the date by which it should be reached.
Pro tip Write the target so progress can be compared with an actual value.
Watch out A direction such as 'grow' or 'get healthier' is not measurable enough.
- 2
Write the outcome equation
Identify the few factors that combine to produce the goal.
Pro tip For commerce, start with traffic, conversion rate, and average order value.
Watch out Do not begin with a dashboard full of disconnected metrics.
- 3
Find the core input
Ask which controllable recurring activity most reliably moves the output equation.
Pro tip Work backward from outcomes to work the team can perform.
Watch out A lagging revenue number alone does not tell the team what to do.
- 4
Publish the cadence
Review actual versus goal and the leading indicators daily or weekly.
Pro tip Automate later; a spreadsheet is sufficient first.
Watch out Automation does not repair a weak metric model.
- 5
Inspect subdrivers selectively
Break a KPI into subordinate causes only when the top-level number requires diagnosis.
Pro tip Keep the executive view simple while allowing deeper analysis.
Watch out Do not let submetrics replace the singular objective.
In the wild
AppSumo set a $45 million annual net-revenue goal. Kagan reduced the top-level model to traffic, conversion rate, and average order value, then identified roughly 35 strong software deals per month as the core business input.
→ Daily and monthly work could be related to one annual destination.
Common mistakes
Automating before simplifying
A Slack bot or data warehouse can distribute metrics, but it cannot decide which metrics matter.
Tracking outputs without inputs
Revenue reports progress but does not identify the recurring action that creates it.
Is it for you?
Best for
Businesses with a measurable outcome and enough operating data to connect inputs to revenue, growth, or delivery.
Not ideal for
Exploratory work where the desired outcome and causal inputs are not yet understood.
From the transcript
“Have one singular goal.”
“Traffic, so how many people are coming to the site, how many people actually buy, which is our conversion rate and then how much do…”
“For every business out there, what's the core input that leads to your main outputs?”
From the episode
#717: Noah Kagan — How to Launch a Million-Dollar Business This Weekend
Noah Kagan