Topic 17 — Business and financial acumen

Goal: Understand the money side of products: unit economics, pricing, and business cases.

Lesson 17.1 — The question Maya couldn't answer

Maya pitched a feature she loved. The Lumi CEO listened, nodded, then asked one question: "And what does this do for the business?"

Maya froze. She had user quotes, a clean design from Priya, an estimate from Sam. What she didn't have was a single sentence about money.

That gap has a name. Business acumen is the ability to reason about whether a product makes money and is worth its cost. It's the skill that lets you answer the CEO's question without flinching.

This one skill carries more weight than almost anything else you'll learn. A junior PM thinks about features and users. A senior PM connects those features to revenue, cost, and growth. That connection is the single biggest step up in this whole job, and it's why senior PMs get trusted with bigger calls. The bigger the decision, the more it gets weighed in money, and the people approving it want to hear that you've already done the weighing.

You don't need an accounting degree. You need a handful of ideas, held clearly enough to make a decision and defend it in front of an executive. No spreadsheets full of formulas. Just honest thinking about value and cost.

Speak the language of the business, and suddenly executives lean in instead of glazing over.

Lesson 17.2 — Do we make money on each customer?

After that meeting, Maya asked Sam a blunt question: when Lumi signs up a new user, does the company actually come out ahead?

Sam pulled up two numbers. They're the heart of unit economics — the revenue and cost of a single "unit," which here means one customer. Unit economics answer the most basic business question there is: do we make money on each customer, or lose it?

The two headline numbers (you met these back in Topic 9):

• LTV (Lifetime Value) — the total profit one customer generates over their whole relationship with you.
• CAC (Customer Acquisition Cost) — what it costs in marketing and sales to win that one customer.

The rule that holds everything together: LTV must be comfortably greater than CAC. A common healthy benchmark is LTV at least about 3× CAC.

Picture it with real numbers. Spend $100 to acquire a customer who brings $300 of lifetime profit, and the math works. Spend $100 to acquire one who brings $80, and you lose money on every single customer.

That second case is the trap. If you're losing money per customer, growing faster doesn't fix it. It just loses money faster. A PM who reads unit economics can tell which features and which customer segments are actually carrying their weight.

Lesson 17.3 — The levers you can pull

Those numbers aren't carved in stone. The PM moves them. Four levers matter most.

Retention raises LTV. A customer who stays twice as long is worth roughly twice as much, which is exactly why keeping customers (Topic 9) so often beats chasing new ones.

Monetization raises LTV too, through pricing, upsells, and expansion. That's the next lesson.

Margin is the profit left after the cost of serving a customer. Software usually has high margins, which is forgiving. Low-margin products demand tighter discipline.

CAC payback period is how long until a customer's revenue repays what you spent to acquire them. Shorter is healthier, because you get your cash back sooner.

Now the insight worth carrying around. Improving retention and monetization of the customers you already have is often the highest-leverage work available to you, quietly more valuable than pouring new users into a leaky bucket. Plug the leaks first. The customers are already paid for, so every extra month they stay and every upsell they take is almost pure upside.

Lesson 17.4 — Pricing, the lever nobody touches

Dan from sales kept saying customers would pay more for Lumi. Maya assumed pricing was someone else's job, set once and locked forever. She was wrong on both counts.

Pricing is one of the most powerful levers a business has, and one of the most ignored. A small pricing change can move revenue more than months of feature work. Yet most teams pick a number on day one and never revisit it. A PM should know the basic models:

• Subscription — a recurring fee, the default for most SaaS.
• Usage-based — pay for what you actually use.
• Tiered — good / better / best plans at different prices.
• Freemium — a free tier plus a paid upgrade, exactly like the platform you're reading this on.
• One-time — pay once, own it.

The idea that changes how you think about all of them is value-based pricing: set the price according to the value the customer gets, rather than working up from what it costs you to build. Customers pay for outcomes. A tool that saves a business $10,000 a month can charge far more than its cost to run, because what they're buying is the $10,000.

Two more things to keep in mind. Tiers create an upgrade path, so customers can start small and grow, which lifts LTV through expansion. And willingness to pay varies by segment — some customers value the product far more than others, and pricing research plus experiments (Topic 10) help you find the right number.

You won't always own pricing. But understanding it lets you weigh in on one of the highest-impact decisions any company makes.

Lesson 17.5 — Turning "I want to build this" into "this is worth it"

Maya now had the pieces. The last one ties them together: how do you actually get a real project approved?

You build a business case — a plain argument that the value outweighs the cost. It runs on ROI (return on investment): what will this cost in time, people, and money, and what will it return in revenue, savings, retention, or strategic value?

A solid business case does four things.

It estimates the upside in business terms, even with rough numbers ("this could lift retention about 2 points, worth roughly $X a year").

It estimates the cost — engineering and design time, plus any direct spend.

It states its assumptions out loud. You're estimating, not promising, and saying so honestly is what builds trust.

It compares to the alternative — is this really the best use of those same weeks and people?

You don't need a precise spreadsheet, especially early. You need to reason in terms of value versus cost and say it clearly. That move turns "I think we should build this" into "here's why this is a good investment for the business," and that's how PMs win resources and influence (Topic 12). Pair it with everything else in this course and you can argue an idea is more than good. You can argue it's a good bet.

Worked example — Maya makes her case

A few weeks later, Maya wants Lumi to build a "team plan" so households and small groups can budget together. The old Maya would have called it cool. This Maya builds a business case grounded in unit economics.

She starts with today's numbers: CAC about $120, LTV about $200. It works, but it's thin.

Then she lays out what the team plan changes. First, it raises prices for roughly 15% of accounts through a natural upgrade path — that's more monetization, so higher LTV. Second, it improves retention, because teams are stickier than individuals; once a household sets up shared budgets, nobody wants to unwind it. Together she estimates these push LTV toward about $320, widening the gap over the $120 CAC.

The cost: roughly 6 engineer-weeks.

She's honest about the soft spot. That 15% upgrade rate is a guess, so she proposes validating it cheaply with a fake-door test first (Topic 10) before committing the build. And she names the alternative: those same six weeks could go into acquisition instead.

Her pitch isn't "let's build team plans." It's "here's an investment that should improve our unit economics, here's what it costs, and here's how we'll de-risk the one assumption it rests on." The CEO doesn't have to ask what it does for the business. Maya already answered.