You can't feature your way out of a pricing problem.

Here is a request that will eat a quarter of your roadmap if you let it: users aren’t inviting their teammates, so let’s build a better invite flow. It sounds like a product gap. You can wireframe it. You can ship it. And it will very likely do nothing — because in a lot of these products, the reason people don’t invite teammates is that every teammate is another seat on the bill. You are trying to solve, with a button, a problem that lives one floor down, in the pricing.

This is the trap I want to name: the feature that is actually a business-model problem in disguise. Product teams are extremely good at reaching for a feature, because a feature is the tool in our hands. But some resistance you feel from users isn’t the absence of a capability. It’s the presence of an incentive pointing the other way. And when the incentive opposes the behavior, a feature on top of it is just a nicer cage.

The tell is almost always the same: the behavior you want costs the user something the moment they do it. Not effort — money, or risk, or a worse deal for themselves.

Once you have the tell, you can spot the pattern everywhere. Your most engaged users ration the product because they’re metered and afraid of the overage — so “engagement” features bounce off people who are deliberately holding back. The person who gets value is not the person who pays, so the buyer optimizes for control and reporting while the user quietly starves. Growth stalls at a plan boundary, and every “why won’t they expand” feature dies because expanding means crossing a price cliff they can see coming. In each case the product surface is fine. The model is doing exactly what it was designed to do, and what it was designed to do is fight you.

So the discipline is a diagnostic question you ask before the spec exists: is the behavior I want aligned with how we make money, or opposed to it? If it’s aligned and people still don’t do it, good — that’s a real product problem, go build. If it’s opposed, no feature will win, because you’d be asking the user to act against their own interest out of enthusiasm for your UI. That enthusiasm does not exist.

When it’s opposed, the fix lives in a different toolbox, and it’s usually one of four levers: price (does doing the right thing have to cost more?), packaging (is the good behavior trapped behind the wrong tier?), who pays versus who uses (is the payer’s incentive pointed away from the user’s?), and metering (are you charging for the exact thing you want people to do freely?). None of these is a screen. All of them are more powerful than a screen.

The reason this is hard has nothing to do with intelligence and everything to do with ownership. Product teams own the product surface; the model usually lives with pricing, finance, or the founders. Reaching for a feature keeps the problem inside your walls. Naming it as a business-model problem means walking into a harder, more political room. That’s exactly why it’s worth learning to see — the cheap move is almost always another feature, and the cheap move is why the number never budges.