The Business of Your Product (Yes, You Have to Think About This)

Let me paint you a picture.

You've built something genuinely useful. Users love it. They tell their friends. The product solves a real problem for real people, and you can feel the momentum building. It's exciting.

And then someone asks: So, how does this thing make money?

If that question makes you want to change the subject, you're not alone. A lot of people who are drawn to product management are drawn to the people side, the problem-solving side, the build cool stuff that helps people side. The business stuff? Feels like someone else's job.

Here's the hard truth: it's not.

One of the most important things a product manager does is sit at the intersection of user needs and business results. Your job isn't just to understand what your customer needs—it's to translate that value into something that keeps the lights on. Products that solve real problems but can't sustain a business eventually die. And nobody wins when that happens.

So let's talk about the business of your product. I promise to keep it human.

First: What's a Business Model, Actually?

A business model is just the answer to three questions:

1. Who is the customer (and who actually pays)?
2. What value do we deliver to them?
3. How do we earn money from that value?

That's it. Strip away all the jargon and that's what you're really asking.

Netflix's answers? Their customers are people who want to watch great content without sitting through commercials or cable contracts. The value is unlimited on-demand entertainment. And they earn money through a monthly subscription. Clean, simple, and repeatable.

Airbnb's answers are a little more interesting. Their customers are actually two groups—travelers who want unique, affordable places to stay, and hosts who want to earn money from their spare space. Airbnb connects those two groups and takes a percentage of every transaction. That's a marketplace model, and it only works if both sides of the equation are happy.

See how the business model immediately shapes the product? Airbnb has to design for two completely different users. A feature that delights a traveler might create a nightmare for a host. Every product decision has to account for both.

That's not an accident. That's the business model doing its job.

The Revenue Model: How You Actually Get Paid

Within your business model lives your revenue model—specifically, how money flows to you. There are a handful of common ones worth knowing:

One-time purchase. You pay once, you own it. Think traditional software before the cloud era, or physical goods. Simple, but you have to keep finding new customers.

Subscription. You pay every month (or year) for continued access. Netflix, Spotify, your gym membership. The beauty here is predictability—if you can keep customers happy and subscribed, you've got reliable, recurring revenue.

Usage-based. You pay for what you use. AWS charges you for compute power. Uber charges you per ride. This model is great for customers who don't want to overpay for capacity they don't need—and it scales naturally with growth.

Freemium. The base product is free; premium features cost money. Zoom and Spotify both play this game. The trick? Your free tier has to be genuinely valuable (or nobody adopts it), but not so valuable that nobody ever upgrades.

Marketplace / transaction fee. You're the platform. Buyers and sellers connect through you, and you take a cut. Etsy, Stripe, and Airbnb all work this way.

Advertising. Free for users, paid for by advertisers who want access to your audience. Google Search, Instagram, Facebook. You're not selling to your users—you're selling your users' attention to someone else.

The model you choose isn't just a finance decision. It shapes your entire product strategy.

Running a subscription product? Your North Star is retention. You need to obsess over onboarding, activation, and reducing churn—because every customer who cancels is money walking out the door.

Running a freemium product? You're playing a conversion game. You have to thread a very specific needle: give people enough value to love you for free, while making the premium tier compelling enough to pay for. Too little free value and nobody signs up. Too much free value and nobody ever upgrades.

The model matters. It changes what you build, what you measure, and what keeps you up at night.

Who Pays vs. Who Uses

Here's a wrinkle that trips up a lot of new PMs: the person using your product isn't always the person paying for it.

Think about enterprise software. A company buys a tool for its employees to use. The employees are the users—they're the ones living in the product every day. But the buyer is some VP or procurement team who signed the contract and cares primarily about ROI, security, compliance, and whether the CFO is going to yell at them.

Users and buyers want different things. The user wants a product that's fast, intuitive, and makes their job easier. The buyer wants cost savings, risk reduction, and a clean dashboard they can show to leadership.

Here's why this matters for you as a PM: if users don't love the product, they won't adopt it—and when renewal time comes, the buyer has nothing to show for their investment. But if the buyer doesn't see value, users never get access to the product in the first place.

You have to serve both. It's a balancing act, and ignoring either side is how products fail.

Pricing: Part Science, Part Art, All Complicated

Okay, so you know how you're going to make money. Now comes the question nobody loves: how much do you charge?

Pricing is one of the most powerful levers in your business. Get it right, and you attract the right customers, capture fair value, and fund your growth. Get it wrong, and you either leave money on the table or kill demand entirely.

And here's what makes it hard: pricing lives at the intersection of data and perception.

The science side includes things like your actual costs, competitor prices, and market structure. If you're building a SaaS tool that competes head-to-head with established players, you can't price wildly out of range without a very compelling reason. Those facts are knowable—you can research them.

The art side is customers' perceived value. And that one is slippery.

Consider this: $10.00 plus $3.99 shipping, versus $13.99 with free shipping. Same total. Completely different customer reaction. Why? Because people hate extra fees, even when the math is identical. Perception isn't rational, but it's real—and it's your job to understand it.

The Value to Price Equation

Here's a framework I love for thinking about where your product lives in the market.

Imagine a simple grid. One axis is the actual price a customer pays. The other axis is the value they perceive they're getting.

If you're in the high price, low perceived value quadrant? You won't survive long. Customers feel ripped off, and they'll leave (or never buy in the first place).

If you're in the low price, low perceived value quadrant? You're a commodity. Think generic products with little differentiation. You can survive here, but you're in a race to the bottom on price with everyone else.

If you're in the low price, high perceived value quadrant? Two things can happen. You build a cult following—think Costco's Kirkland Signature brand, which people genuinely love despite (because of?) its low price. Or, over time, customers start to wonder if something cheap can really be that good, and perceived value erodes.

The high price, high perceived value quadrant? That's where you want to be. That's Apple. That's premium SaaS tools that charge a lot and deliver a lot. Customers feel the price is justified by the value, and that relationship is sustainable.

The goal of your product decisions—features, UX, branding, positioning—is to increase customers' perceived value. The goal of your pricing decision is to capture a fair portion of that value.

What This Means for You

You don't need an MBA to think like a businessperson. You just need to ask the right questions early and often:

Does each customer we acquire actually generate more value than they cost us? Are we pricing in a way that reflects what our product is worth—not just what it costs to build? Does our revenue model make sense for how our customers actually prefer to buy?

These aren't finance questions. They're product questions. And the PMs who get comfortable asking them—and building products with the answers in mind—are the ones who build things that last.

A great product that can't sustain a business isn't just a business failure. It's a failure to deliver long-term value to the very users it was built to serve.

So yeah. You have to think about this. But now you know where to start.