Who This Helps
You are a product manager who needs to explain why a feature is worth building. You have data, but stakeholders want numbers that connect to cash. The Finance Basics for Operators program gives you the language to turn product questions into decisions that get approved.
Mini Case
Viktor runs a SaaS product. Last week, profit looked great, but cash was tight. He used the Cash vs Profit Reality mission to show his VP that a 12% drop in collections caused the gap. The VP approved his request to extend payment terms by 7 days. Viktor turned a confusing question into a clear action.
Do This Now (5 Steps)
- Grab your unit economics snapshot. Open your product's revenue and cost per customer. If you don't have it, estimate from your last 3 months of data.
- Find your contribution margin. Subtract variable costs from revenue per unit. If it's below 40%, you have a weak line to fix.
- Run a break-even scenario. Pick one feature you want to build. Estimate how many new customers you need to cover its cost. Write down your assumptions.
- Identify your top cost driver. Look at your biggest expense. Ask: can I reduce it by 10% without hurting the product? If yes, propose it this week.
- Check your runway. Divide your cash by monthly burn. If you have less than 12 months, flag it to your team. This is a decision, not a problem.
Avoid These Traps
- Don't confuse profit with cash. Profit is an opinion; cash is a fact. Always show both.
- Don't use vague terms like "good growth." Use numbers: 15% month-over-month or 3x payback period.
- Don't assume stakeholders know unit economics. Teach them with one simple table.
- Don't ignore pricing sensitivity. A 5% price change can shift your break-even by weeks.
- Don't wait for perfect data. Use your best estimate and update as you go.
- Don't present without a decision ask. End every update with one clear choice for your audience.
- Don't forget cost structure triage. Not all costs are equal. Focus on the top three.
- Don't skip the runway baseline. It's the one number that keeps you honest.
Your Win by Friday
By Friday, you will have one page that answers: "Should we build this feature?" Your stakeholders will see the unit economics, the break-even scenario, and the cash impact. They will say yes because you made the decision measurable. And you will sleep better knowing your product questions have clear answers.