Pricing is a product decision, not a finance decision.
How a product is priced changes how it's used, who it attracts, and what it's for — which makes pricing a design choice.
Pricing shapes who uses a product, how they use it, and what they expect from it — which makes it a product design decision, not a line item decided after the product is finished. Treating price as something to bolt on at the end usually means the product and the price were designed for two different users, and the mismatch shows up as confusion or churn later, when it’s far more expensive to fix.
Price changes behavior, not just revenue
A free tier attracts a different kind of user than a paid-only product — often someone earlier in their evaluation, less committed, more likely to churn quietly without ever engaging deeply. A usage-based price encourages different behavior than a flat monthly fee, because it makes the cost of each action visible in a way a flat fee never does. The price isn’t just a number — it’s an instruction to the user about how the product wants to be used, whether or not anyone intended it to communicate that.
This means two products that are functionally identical can end up serving completely different audiences and producing completely different usage patterns, purely because of how they’re priced. Pricing isn’t neutral packaging around a fixed product experience — it’s part of the experience itself.
Pricing as a signal, not just a cost
Price also signals what a product is for. A very low price can suggest a utility — something lightweight, replaceable, not meant to be depended on for anything consequential. A considered price can suggest a serious tool built for people who depend on it, worth the investment because the outcome matters. Neither is automatically right — but the mismatch between price and positioning is where trust breaks down, because it creates a gap between what the price implies and what the product actually delivers.
A product priced like a casual utility but positioned as mission-critical infrastructure will struggle, because the price is quietly telling users not to take it too seriously, no matter what the marketing says. The reverse mismatch — an expensive price on something that behaves like a lightweight utility — creates resentment instead.
Why we think about this early, not late
This is why pricing deserves the same early thinking as the interface or the onboarding flow, not a decision deferred until the product is “done.” Deferring it usually means the product was built without a clear answer to who it’s actually for, because pricing forces that question to be answered concretely — a question that’s easy to leave vague when there’s no number attached to it yet.
Common questions
Should early-stage products worry about pricing before they have significant usage? Yes, at least directionally — even a rough pricing hypothesis forces useful clarity about who the product is for, well before enough usage data exists to optimize the number precisely.
Is a free tier always the right way to reduce friction for new users? Not always. Free tiers reduce friction to try a product, but they can also attract users who were never going to be a good long-term fit, which adds noise to your understanding of who your product actually serves.
How often should pricing be revisited once it’s set? Regularly enough to reflect real changes in who’s using the product and why, but not so often that it erodes trust with existing users who priced their own usage around your current terms.
Takeaway: decide who a product is for before deciding what it costs — the price should follow from that answer, not the other way around.