business model thinking

Most PMs treat the business model as someone else’s problem. Finance builds the spreadsheet. The founder picks the pricing. The PM builds features.

This is a career-limiting mistake. The business model is not a spreadsheet — it is a product decision. It determines what you build, who you build for, and what “success” means for every feature on your roadmap. A PM who does not understand the business model is flying blind, making prioritization decisions with no understanding of what actually creates value.

The business model is a product decision

Here is the simplest definition: a business model describes how your product creates value, delivers it, and captures a portion of that value as revenue.

Three parts. Value creation. Value delivery. Value capture.

Most PMs are good at the first two. They understand user problems, design solutions, ship features. Where they fall apart is value capture — the mechanics of how money flows from the user to the company.

Before you build anything, run what I call The Tick Test: identify the single metric that mechanically makes your business run. Not a vision statement. A mechanical truth. OYO = room nights booked × occupancy rate. Swiggy = orders per delivery partner per hour. Razorpay = transaction success rate × total payment volume. If you cannot name your tick, you do not understand your business model well enough to make product decisions about it.

And this matters because value capture shapes the product in ways that are not obvious until it is too late.

If you do not understand how your company makes money, you cannot make good product decisions. You will build features that are expensive to serve, price things that erode margins, and prioritize work that does not move the metrics your CEO cares about.

The business model canvas — what it actually is

Alexander Osterwalder’s Business Model Canvas is the most widely taught business model framework. You have probably seen it. Nine boxes on a page. Value proposition in the center, customer segments on the right, key activities on the left, revenue streams at the bottom.

Here is what the nine boxes cover:

The canvas is useful as a thinking tool, not as a deliverable. Nobody ships a business model canvas. Its value is in forcing you to articulate assumptions you have not examined — particularly the relationship between what you build (left side) and who pays for it and why (right side).

Where most PMs go wrong with the canvas: they fill it in once and file it away. The real value comes from filling it in, then asking “what if this box changed?” What if our customer segment shifted from SMBs to enterprise? What happens to every other box? That second-order thinking is where the canvas earns its keep.

Unit economics — the numbers PMs must know

Unit economics is the profit or loss generated by a single unit of your business — typically a single customer or a single transaction.

Two numbers matter above everything else:

CAC (Customer Acquisition Cost): How much does it cost to acquire one customer? Include marketing spend, sales team cost, onboarding cost, everything it takes to get someone from “never heard of you” to “paying customer.”

LTV (Lifetime Value): How much revenue does one customer generate over their entire relationship with you? Include subscription revenue, upsells, expansions — and subtract churn.

The fundamental rule: LTV must be significantly greater than CAC. In SaaS, the benchmark is LTV > 3x CAC. If it is lower, you are spending more to acquire customers than they are worth. If it is much higher, you might be underinvesting in growth.

Here is what this looks like in practice. A real example from an Indian SaaS context:

A cloud-based project management tool targeting Indian SMBs. Three pricing tiers:

Now the unit economics for each tier:

• Basic tier CAC: Rs 1,500 (mostly self-serve, content marketing). Average lifespan: 8 months. LTV: Rs 4,000. LTV/CAC ratio: 2.7x. Below the 3x benchmark. These customers churn too fast for the acquisition cost.
• Professional tier CAC: Rs 8,000 (sales-assisted). Average lifespan: 18 months. LTV: Rs 36,000. LTV/CAC ratio: 4.5x. Healthy.
• Enterprise tier CAC: Rs 50,000 (dedicated sales, custom onboarding). Average lifespan: 3 years. LTV: Rs 75,000. LTV/CAC ratio: 1.5x. Dangerous. High touch, low return.

As a PM, this changes your roadmap priorities entirely. The Basic tier needs better onboarding to reduce churn. The Enterprise tier either needs a price increase or lower-touch onboarding — building self-serve provisioning might be more important than any feature request. The Professional tier is your growth engine — invest there.

This is why unit economics is a product skill, not a finance skill. The numbers directly tell you what to build.

Revenue models PMs encounter

Different revenue models create different product incentives. You need to understand these because the revenue model shapes what “good” looks like for your product:

Subscription (SaaS). Revenue comes from recurring payments. Your job as PM: reduce churn, increase expansion revenue, optimize pricing tiers. Feature decisions are about stickiness — what makes users unable to leave? In India, annual billing with discounts works better than monthly for B2B because procurement cycles are long and renewal fatigue is real.

Transaction-based. Revenue comes from each transaction (payment processing, marketplace commissions). Your job: increase transaction volume and average transaction value. Razorpay takes a cut of every payment. Their PM incentive is to make checkout so seamless that merchants never switch — and to add financial products (lending, payroll) that increase transactions per merchant.

Advertising. Revenue comes from attention. Your job: increase time spent and engagement without destroying user experience. This is the hardest model to do well because the product incentive (more engagement) and user interest (get things done quickly) are in direct tension.

Freemium. Revenue comes from converting free users to paid. Your job: build enough value in the free tier to attract users, but create clear upgrade triggers. The art is in the gate — what sits behind the paywall. Gate too aggressively and you kill adoption. Gate too loosely and nobody upgrades. Notion nailed this in India by making the free tier genuinely useful for individuals, then gating collaboration features for teams.

Marketplace. Revenue comes from connecting buyers and sellers and taking a commission. Your job: solve the chicken-and-egg problem, then optimize take rate. In India, marketplaces like Swiggy and Urban Company face a specific challenge — the supply side (delivery partners, service providers) has low switching costs and high price sensitivity. Your business model thinking must account for supply-side economics, not just demand.

When the business model and the product conflict

The hardest moments in a PM’s career come when the business model pulls the product in one direction and users pull it in another.

The Indian context — why it changes everything

Business model thinking in India is different from Silicon Valley for specific, structural reasons:

Price sensitivity is not just “lower prices.” Indian users will pay — but the value must be unmistakably clear. Zomato Gold worked not because it was cheap, but because the discount was immediately visible on every order. Abstract value (“better analytics”) is harder to monetize than concrete value (“save Rs 200 on every order”).

Payment infrastructure shapes the model. UPI changed what is possible. Micro-transactions that were uneconomical with credit cards became viable. This is why daily subscription models (Rs 5/day for a newspaper app) work in India in ways they do not elsewhere. As a PM, your pricing model must account for the payment rails your users actually use.

The “jugaad” factor in B2B. Indian SMBs are resourceful. If your tool costs Rs 5,000/month and a combination of WhatsApp groups plus Google Sheets does 80% of the job, many will choose the free option. Your business model must either deliver value that cannot be replicated with free tools, or price at a point where switching to free is not worth the effort.

Gross margins vary wildly. A pure SaaS tool might run 85% gross margins. A marketplace with physical fulfillment (Dunzo, Zepto) might run 15%. A fintech product earning float on deposits might run 95%. The gross margin determines how much you can spend on acquisition, which determines your growth model, which determines your feature priorities. Same country, wildly different business model physics.

Connecting business model to roadmap

Here is a practical framework for making the connection between business model and product decisions:

Step 1: Know your unit economics. CAC, LTV, gross margin, payback period. If you do not know these numbers, ask finance. If finance does not know, build a rough model yourself. You do not need precision — you need directionality.

Step 2: For every feature on your roadmap, ask one question. “Does this feature improve value creation, value delivery, or value capture?” If you cannot answer, the feature is not connected to your business model and may not be worth building.

Step 3: Model the second-order effects. Adding a free tier to acquire users is a value-creation move. But it also changes your cost structure (more infrastructure), your support load (more users, fewer paying), and your conversion funnel (now you need upgrade triggers). One business model change cascades through every box on the canvas.

Step 4: Revisit quarterly. Business models are not static. Your customer segments shift. Competitors force pricing changes. New payment infrastructure emerges. A PM who set-and-forgot the business model in Q1 is making decisions based on stale assumptions by Q4.

Test yourself

Where to go next

• Apply business model thinking to strategy: Product Vision and Strategy
• Learn to prioritize with business impact in mind: Prioritization Frameworks
• Understand the metrics that track business model health: Metrics and KPIs
• See business models in action: Pricing and Monetization Case Studies