Who This Helps
Founders and operators in the Finance Basics for Operators program. If you've built your unit economics snapshot but feel stuck explaining it, this is for you. You'll move from having the numbers to getting the green light.
Mini Case
Viktor just calculated his SaaS contribution margin. The core product is strong at 72%, but one add-on feature is dragging it down at just 18%. He needs to explain this to his co-founder to decide whether to fix, raise the price, or kill the feature. The clock is ticking on next quarter's roadmap.
Do This Now (5 Steps)
- Start with the one-line story. Before any spreadsheet, write one sentence. Example: "Our main engine is profitable, but Feature X is burning cash for every new customer."
- Show the single weak line. From your unit economics work, isolate the one metric that needs attention. Don't show all ten. Just show the 18% margin.
- Frame three possible next moves. Always give options. For the weak feature: (A) Fix its cost structure, (B) Increase its price by 30%, or (C) Sunset it.
- Attach a concrete timeline. Propose a 7-day decision window and a 30-day implementation period for the chosen path. Specificity builds trust.
- Schedule the 15-minute follow-up. End your update by locking in the next micro-meeting to decide. This turns analysis into a process.
Avoid These Traps
- The Data Dump: Sending a full financial model without a narrative. It's overwhelming. Your stakeholder's eyes will glaze over.
- Presenting Problems Without Options: Saying "we have a problem" forces them to do the solution work. Bring the options, you've done the analysis.
- Using Jargon: Words like "variable cost ratio" can confuse. Say "what it costs us to deliver this, per customer."
- Hiding the Ask: Burying what you need. Be blatant: "I need your approval to test a price increase next week."
- Waiting for Perfect Data: Your unit economics snapshot is a tool for decisions, not a museum piece. Use the 80% complete version.
Your Win by Friday
By this Friday, you will have taken one insight from your financial work—like identifying a top cost driver—and presented it to one stakeholder with a clear recommendation. You'll get a yes, a no, or a refined question, which is still a win because you're now talking about execution. Finance isn't about counting beans, it's about planting the right ones. Go get that decision.