Who This Helps
Junior analysts who need to present board-level finance insights without the fluff. If you're tired of vague feedback like "this needs more context," this is for you. The Board Finance & Runway Narrative course is built for analysts like Viktor who must define runway triggers and action branches.
Mini Case
Viktor, a junior analyst at a SaaS startup, ran the numbers on cash runway. He found that if monthly burn stays at $120K, the company has 14 months of runway. But if a key customer churns (12% chance), burn jumps to $135K, cutting runway to 11 months. Viktor presented this with a simple trigger: if churn hits 10%, freeze hiring immediately. The board approved his recommendation in one meeting.
Do This Now (5 Steps)
- Pick one board-level signal. Start with the single metric that matters most this cycle—like monthly recurring revenue growth or cash burn rate.
- Build a scenario envelope. Write down three scenarios: base case, upside, downside. For each, list explicit assumptions (e.g., churn rate, hiring pace).
- Define runway triggers. For each scenario, set a clear trigger (e.g., "if cash drops below $500K, pause all non-essential hires").
- Choose one tradeoff. Decide between two options—like hiring a senior engineer vs. extending runway by 3 months. Defend your choice with numbers.
- Write a one-page memo. Summarize your analysis, triggers, and recommendation. Keep it to one page—boards love brevity.
Avoid These Traps
- Overcomplicating scenarios. Three is plenty. More than five and you'll confuse everyone.
- Ignoring assumptions. If you don't state them, someone will ask—and you'll look unprepared.
- Hiding bad news. Boards respect honesty. If runway is tight, say it early.
- Skipping the recommendation. Analysis without action is just noise. Always end with a clear "do this."
- Using jargon. "Capital allocation tradeoff" is fine in a memo, but explain it in plain English during the meeting.
Your Win by Friday
By Friday, you'll have a board-ready finance memo with triggers and a defended tradeoff. Your boss will say, "This is exactly what we needed." And you'll feel like the analyst who actually gets things done—no more revisions, just approval.