← Back to blog

Junior Analyst · Finance Basics for Operators

Diagnose a KPI Drop in 1 Session: Finance Basics for Operators

Pinpoint root cause of a KPI drop in one focused session. No fluff, just action.

Who This Helps

This is for junior analysts who need to ship clean analysis with clear recommendations. You're staring at a number that tanked, and your boss wants answers by Friday. The Finance Basics for Operators program gives you the framework to stop guessing and start diagnosing.

Mini Case

Imagine you're Viktor, a junior analyst at a SaaS company. Your weekly report shows a 12% drop in contribution margin. Revenue is flat, but costs jumped. You have 7 days to explain why and recommend a fix. Using the Unit Economics Snapshot mission from Finance Basics for Operators, you calculate contribution margin per customer and spot the weak line: customer support costs spiked 30% for your top 10 accounts. That's your root cause.

Do This Now (5 Steps)

  1. Grab the data. Pull revenue and variable costs for the last 4 weeks. Focus on the KPI that dropped.
  2. Calculate contribution margin. Subtract variable costs from revenue per unit. Use the formula from the Unit Economics Snapshot mission.
  3. Compare to baseline. Your baseline is last month's margin. If it dropped 12%, that's your red flag.
  4. Find the cost driver. Look at each variable cost line. Which one changed most? In Viktor's case, support costs jumped 30%.
  5. Write one recommendation. Suggest one control move, like capping support hours for top accounts. Keep it simple.

Avoid These Traps

  • Don't blame everything on revenue. Revenue might be fine. Check costs first.
  • Don't overcomplicate. Stick to one KPI and one root cause. You're not solving world hunger.
  • Don't skip the baseline. Without last month's number, you're guessing.
  • Don't ignore small numbers. A 5% cost spike in one line can tank margin.
  • Don't forget the fun part. You get to be a detective. That's way cooler than updating spreadsheets.

Your Win by Friday

By Friday, you'll have a one-page analysis that says: "Contribution margin dropped 12% because support costs rose 30% for top accounts. Recommendation: cap support hours to 10 per account per week." Your boss will nod, and you'll ship clean analysis with clear recommendations. That's the Finance Basics for Operators way.