Turn Your Analysis into Action with a Runway Forecast

Who This Helps

This is for junior analysts who have crunched the numbers but need to get their boss, like a founder, to actually do something about it. It’s part of the Founder Finance Basics Mission Pack, which helps you build the financial clarity founders need to make calm decisions.

Mini Case

Ben’s revenue was up 20% last quarter, but his cash balance hasn’t budged. He’s worried. You run the numbers and see his Customer Acquisition Cost (CAC) payback period has stretched from 5 months to 8 months. That’s eating his cash. Your job is to show him exactly how this impacts his runway and what to do next.

Do This Now (5 Steps)

1. Start with the headline number. Calculate the current cash runway. If you have $120k in the bank and a monthly burn of $15k, your runway is 8 months. Lead with that.
2. Connect one key driver. Link that runway number directly to one main finding, like the stretched CAC payback. Say: "Our runway is 8 months because our payback period grew by 3 months, locking up cash."
3. Show the simple scenario. Model one change. "If we improve payback by 1 month, we add 6 weeks to our runway." Use real numbers from your analysis.
4. Give a single, clear recommendation. Don’t list five ideas. Pick the biggest lever. "Pause spending on the underperforming ad channel for 30 days to test impact on payback."
5. Make the next step tiny. End with the immediate action. "I’ll set up a check-in next Friday to review the channel data with you." This makes saying "yes" easy.

Avoid These Traps

• The data dump. Don’t show every spreadsheet tab. You’ll lose them in the weeds.
• Presenting problems without a path. A founder feels stress, not insight, if you just highlight fires with no hose.
• Using jargon without translation. Saying "CAC:LTV ratio deteriorated" is less clear than "it now costs us more to earn a customer than they pay us back."
• Being neutral. Your job isn’t just to present facts; it’s to recommend a course of action. Take a stand.
• Forgetting the ask. Always finish with what you need from them—approval, a decision, or a next meeting.
• Hiding the uncertainty. If your runway forecast has assumptions, state them plainly (e.g., "This assumes flat revenue").
• Making it a lecture. This is a conversation. Frame it as "Here’s what I found, and here’s what I suggest we do."
• Skipping the story. Numbers need a narrative. "Revenue is up, but cash is flat" is the story that makes the runway number matter.

Your Win by Friday

By Friday, you can walk out of a meeting with a clear "go" decision on your recommendation. No more analysis sitting in a deck, gathering digital dust. You’ll have a stakeholder who trusts your numbers and is ready to act on them. That’s how you move from reporting to influencing—and it feels pretty good.