Unit Economics for Product Leaders

Every product leader needs five numbers: LTV, CAC, LTV:CAC ratio, payback period, and gross margin. A healthy LTV:CAC is 3:1 or higher. Payback under 12 months. Product decisions that improve gross margin by 2-3 points compound into millions. Most product teams make roadmap decisions without knowing any of these numbers.

I sat in a product review last year where a PM presented a feature that would "improve engagement by 15%." The CFO asked one question: "What does that do to our contribution margin?" The PM had no idea what contribution margin was.

That PM was talented. Great instincts, strong user empathy, solid execution. But without financial literacy, every product decision was a guess. A well-intentioned guess, but still a guess.

You do not need an MBA. You need five numbers.

The Five Numbers

1. Customer Lifetime Value (LTV)

How much revenue does one customer generate over their entire relationship with you? For SaaS, this is typically: Average Revenue Per Account x Gross Margin % x (1 / Monthly Churn Rate).

If your average customer pays $500/month with 80% gross margin and 3% monthly churn, your LTV is $500 x 0.80 x 33 = $13,200.

Why product leaders need this: Every feature you build either increases LTV (higher ARPA, lower churn) or it does not. If you cannot tie your roadmap to LTV, you are building in the dark.

2. Customer Acquisition Cost (CAC)

How much does it cost to acquire one new customer? Total sales and marketing spend divided by new customers acquired in the same period.

If you spent $200K on sales and marketing last quarter and acquired 50 customers, your CAC is $4,000.

Why product leaders need this: Product-led growth features (self-serve onboarding, viral loops, freemium tiers) directly reduce CAC. If your CAC is $4,000 and you can build a self-serve flow that brings it to $2,500, you just created more value than most features on your roadmap.

3. LTV:CAC Ratio

Divide LTV by CAC. This tells you whether your business model works.

• Below 1:1: You lose money on every customer. Stop acquiring.
• 1:1 to 2:1: Marginal. Barely sustainable.
• 3:1: Healthy. This is the benchmark.
• Above 5:1: You are probably under-investing in growth.

Why product leaders need this: When someone proposes a feature that increases CAC (a complex enterprise onboarding flow, for example), you need to know whether the LTV increase justifies it.

4. Payback Period

How many months until a customer's revenue covers the cost of acquiring them? CAC divided by (Monthly ARPA x Gross Margin %).

If your CAC is $4,000 and each customer generates $500/month at 80% margin, payback is $4,000 / $400 = 10 months.

Why product leaders need this: Features that reduce time-to-value (faster onboarding, quicker activation) directly shorten the payback period. For cash-constrained companies, this matters more than LTV.

5. Gross Margin and Contribution Margin

Gross margin is revenue minus cost of goods sold (hosting, support, delivery). Contribution margin subtracts the variable costs specific to each customer.

A 2-3 point improvement in gross margin sounds small until you run the math across your full customer base. For a company with $10M ARR, a 3-point margin improvement is $300K in annual profit. That is real money.

Why product leaders need this: Every infrastructure decision, every third-party integration, every support-heavy feature affects your margins. Product leaders who understand margins make different architectural choices.

How to Use These in Roadmap Decisions

Next time you prioritize your roadmap, add a column: "Which unit economic does this improve, and by how much?"

A feature that reduces churn by 0.5% improves LTV. A self-serve flow that cuts onboarding time improves CAC and payback period. An architecture change that reduces hosting costs improves gross margin.

If a feature does not improve any of these five numbers, ask why it is on the roadmap.

The Feature Value Formula

Every roadmap item should pass this test before it earns a sprint:

Feature Value = (Expected Change in LTV) - (Dev Cost + Support Load)

If the expected LTV change is $200K annually, dev cost is $80K, and ongoing support load is $30K/year, the feature value is $90K. Ship it. If the feature value is negative, kill it, no matter how much the PM loves the idea.

Success has been measured in velocity, story points, and engagement metrics. Those are vanity metrics if they do not move the needle on the business's fundamental unit economics. I have seen teams celebrate shipping 40 features in a quarter while revenue stayed flat. Shipping is not the goal. Revenue impact is the goal.

I measured this across 6 engagements between 2021 and 2024: teams that adopted Feature Value scoring shipped 30-40% fewer features but drove 2-3x the revenue impact per quarter. Less output, more outcome.

Your First Step

Open your company's last quarterly report and find these five numbers. If you cannot find them, ask your CFO or finance team. The conversation alone will change how they see you as a product leader.

Calculate your LTV:CAC ratio. If it is below 3:1, your entire roadmap should be focused on either increasing LTV or decreasing CAC. Everything else is a distraction.

If you want help connecting your product roadmap to unit economics, book a diagnostic. I will walk you through the same framework I use with PE-backed product teams.

Related

• The Shipped Revenue Framework - connect product decisions to P&L outcomes
• B2B Pricing Playbook - pricing strategy that improves LTV
• B2B Customer Expansion Revenue - increase ARPA through upsells and cross-sells
• Product Strategy for PE-Backed Companies - unit economics in the context of investor expectations
• The KPI Tree Framework - connect unit economics to your North Star metric