Who This Helps
This is for founders who see a sudden dip in a key number—like revenue per user—and need to know why before the week is out. It’s a core move from the Founder Finance Basics Mission Pack, turning panic into a clear plan.
Mini Case
Ben’s weekly revenue per active user dropped 18% last month. His gut said ‘seasonality,’ but his unit economics snapshot showed the real story: a new feature increased support tickets, causing a 22% rise in service costs per user. The revenue dip was a symptom, not the disease. He fixed the onboarding flow instead of launching a discount campaign.
Do This Now (5 Steps)
- Grab last month’s and this month’s numbers for your wobbly KPI.
- List the three core costs directly tied to that KPI (like support, hosting, or transaction fees).
- Calculate the profit per unit for both time periods. (Revenue minus those direct costs).
- Spot the biggest change in the cost columns. That’s your likely culprit.
- Ask your team one question about that specific cost driver. You’ll have a hypothesis in 20 minutes.
Avoid These Traps
- Don’t blame ‘the market’ first. Look internally for cost or process changes.
- Avoid adding more metrics to the dashboard. You’re diagnosing, not decorating.
- Don’t skip calculating actual profit per unit. Revenue alone hides the truth.
- Stop the meeting if it becomes a brainstorming session. You’re hunting for one root cause.
- Never make a decision based on the KPI movement alone. Always check its unit economics first. It’s like checking the oil, not just the gas gauge.
Your Win by Friday
By Friday, you’ll have a one-page unit economics snapshot for your troubled metric. You’ll know if the drop is a pricing issue, a cost creep, or something else entirely. You’ll walk into your next team sync with a clear ‘here’s what we fix first’ instead of a fuzzy ‘things are down.’