Who This Helps
This is for product managers who wake up to a sudden KPI drop and need to find the real cause fast. You don't want to guess or chase symptoms. You want a clear path to the root issue so you can decide what to do next.
If you're working through the Founder Finance Basics Mission Pack, you already know that unit economics and runway are your friends. This article helps you apply that thinking to a real KPI problem.
Mini Case
Imagine your SaaS product's weekly active users dropped 12% overnight. Revenue is still up, but cash is flat. You suspect a pricing change or a feature bug. But you need proof.
You pull up your unit economics snapshot card from the Unit Economics Snapshot mission. You see that your customer acquisition cost (CAC) jumped 30% last week, while your average revenue per user (ARPU) stayed flat. That's your first clue: growth spend may be unsafe.
Now you have a focused question: Is the KPI drop caused by a channel-level payback problem? You run a quick triage using the CAC Payback Triage mission card. You find that one ad channel has a payback period of 7 days longer than your target. That channel drove 40% of new signups last week. Bingo.
Do This Now (5 Steps)
- Grab your unit economics snapshot card. If you don't have one, create a simple table with revenue, costs, and users for the last 30 days.
- Compare the drop day to your pricing or feature changes. Look for a 1-2 day lag between a change and the KPI drop. That's a strong signal.
- Check your CAC by channel. Use the CAC Payback Triage mission to see if any channel's payback period spiked. A 3-day increase is a red flag.
- Talk to your finance person. Ask: "Did our ad spend change last week?" You might find a budget shift that caused the drop.
- Run a runway forecast. If the drop continues, how many months of cash do you have? Use the Runway Forecast mission to model three scenarios: best case, worst case, and most likely.
Avoid These Traps
- Blame the feature first. It's tempting to blame a bug. But often the root cause is a pricing or channel issue. Check unit economics before you debug.
- Ignore cash flow. Revenue up doesn't mean cash is safe. Flat cash with rising costs is a warning sign.
- Look at one metric in isolation. A KPI drop is rarely just one thing. Cross-check with CAC, ARPU, and churn rate.
- Skip the payback triage. If you don't know which channel is bleeding, you'll waste time on the wrong fix.
- Assume the drop is temporary. A 12% drop that lasts 7 days is a trend, not a blip. Act now.
- Forget to update your snapshot card. After you find the root cause, update your unit economics card. It's your truth document.
Your Win by Friday
By Friday, you will have pinpointed the root cause of your KPI drop. You'll know if it's a channel, pricing, or feature issue. You'll have a decision card from the CAC Payback Triage mission that shows exactly which channel to fix. And you'll have a runway forecast that tells you how much time you have to act. That's a calm, data-backed decision you can share with your team. And maybe even smile about.