Financial literacy for technical people — why finance matters, the three statements (income statement/P&L, balance sheet, cash flow), the crucial profit-vs-cash distinction, unit economics (contribution margin, CAC/LTV), SaaS/recurring-revenue metrics (MRR/ARR, churn, NRR, Rule of 40), budgeting and forecasting, and reading financial health to make better decisions.
Finance is the language business uses to talk about itself, and most engineers are functionally illiterate in it — which quietly caps their influence. The decisions you disagree with (why we're not hiring, why that project got cut, why the company is pushing revenue over polish) usually make perfect sense once you can read the financial reality behind them. Learning to read that reality — the P&L, the cash position, the unit economics — turns you from someone decisions happen to into someone who can shape them.
Finance is the language business uses to talk about itself, and most engineers are functionally illiterate in it — which quietly caps their influence. The decisions you disagree with usually make sense once you can read the financial reality behind them. Learning to read that reality turns you from someone decisions happen to into someone who can shape them.
The income statement is the one financial document every engineer should be able to read, because it's the scoreboard everyone above you is watching. It answers, for a period of time, the most basic business question — did we make money? — but the real value is in its structure: the journey from "money customers paid us" at the top to "profit we actually kept" at the bottom, with every cost that eats into it along the way. Once you can read that journey, a huge amount of business behavior stops being mysterious.
The income statement is the one financial document every engineer should be able to read — it's the scoreboard everyone above you is watching. The real value is in its structure: the journey from 'money customers paid us' at the top to 'profit we actually kept' at the bottom, with every cost that eats into it along the way.
If the income statement is a movie of what happened over a period, the balance sheet is a photograph — a snapshot of what a company owns and owes at a single moment. It answers a different question than "did we make money?": it answers "what is the financial position right now?" And it rests on one elegant equation that always balances, by definition — an equation that, once you understand it, makes the whole document readable.
If the income statement is a movie of what happened over a period, the balance sheet is a photograph — a snapshot of what a company owns and owes at a single moment. It rests on one elegant equation that always balances by definition, and once you understand it, the whole document becomes readable.
"Profitable companies don't go bankrupt" is one of the most expensive misconceptions in business. They do — routinely — because profit and cash are different things, and it's cash that pays salaries, suppliers, and rent. A company can be profitable on paper and still die when the bank account hits zero. The cash flow statement is the document that tells the truth about the money actually moving, and understanding it — and the profit-versus-cash gap — is what separates real financial literacy from the illusion of it.
'Profitable companies don't go bankrupt' is one of the most expensive misconceptions in business. They do — routinely — because profit and cash are different things, and it's cash that pays salaries and suppliers. The cash flow statement tells the truth about the money actually moving, and understanding it separates real financial literacy from the illusion of it.
A company can grow revenue explosively, raise huge rounds, and dominate headlines — and still be doomed, if it loses money on every customer. Unit economics is the question underneath all the aggregate financials: does a single customer, on its own, make money? Get that right and scale is the amplifier of a good thing; get it wrong and scale just multiplies the losses. It's the most important economic idea for judging whether a business actually works — and the one flashy growth numbers most often hide.
A company can grow revenue explosively, raise huge rounds, and dominate headlines — and still be doomed, if it loses money on every customer. Unit economics is the question underneath all the aggregate financials: does a single customer, on its own, make money? It's the most important test of whether a business actually works.
Subscription businesses changed what "revenue" means. When customers pay every month instead of once, a whole new vocabulary appears — MRR, ARR, churn, net revenue retention, the Rule of 40 — and these metrics, not the raw P&L, are how SaaS companies are actually judged. For any engineer working at or evaluating a subscription business (which is most software today), these are the numbers that matter, and the logic behind them explains why SaaS companies behave the way they do.
Subscription businesses changed what 'revenue' means. When customers pay every month instead of once, a whole new vocabulary appears — MRR, ARR, churn, net revenue retention, the Rule of 40 — and these metrics, not the raw P&L, are how SaaS companies are actually judged.
Financial statements tell you what already happened; budgets and forecasts are how a business reasons about what's going to happen — and that forward view is where finance stops being accounting and starts being strategy. A forecast is a model of the future you can steer by: it tells you when you'll run out of cash, whether a plan is affordable, and what happens if things go better or worse than hoped. For engineers, it's a familiar idea in unfamiliar clothes — building a model, running scenarios, and updating on new data.
Financial statements tell you what already happened; budgets and forecasts are how a business reasons about what's going to happen — and that forward view is where finance stops being accounting and starts being strategy. For engineers, it's a familiar idea in unfamiliar clothes: building a model, running scenarios, updating on new data.
Financial literacy pays off in two moments: when you look at a business and can quickly tell whether it's healthy, and when you face a decision and can reason about it in the numbers. Both come down to synthesis — pulling the statements, metrics, and economics together into a judgment. This closing post is about that synthesis: reading a company's financial health at a glance, using finance to make and understand decisions, and the mindset that turns financial knowledge into better judgment.
Financial literacy pays off in two moments: when you look at a business and can quickly tell whether it's healthy, and when you face a decision and can reason about it in the numbers. Both come down to synthesis — pulling the statements, metrics, and economics together into a judgment.
This series is part of a larger body of work by Pratik Dhanave, an Agentic AI Architect writing about production AI systems, distributed systems, and cloud-native engineering. Explore all course series, browse every post, or find topics via the tag index.