Pricing Architecture Is Product Architecture
An energy cap, a free allowance or a tier limit shapes the rhythm of the product before it shapes revenue. The price is also the tutorial.
Pricing architecture is product architecture.
Take something as simple as an energy cap in a game. Yes, it limits how much someone can consume. But it also starts shaping the rhythm of the product: how long people play, when they leave, when they return, and whether unused capacity feels wasted.
The same thing happens with free allowances, bundles, and tier limits. Over time they establish expectations around what normal usage looks like and what feels valuable. The price is also the tutorial.
Reading a pricing test
Where this gets interesting is when you test one of those levers.
If you tighten a free allowance and conversion improves, that improvement matters. But I wouldn’t read it in isolation. You may also have changed how quickly someone encounters friction, how much of the product they experience before paying, which features they discover, and even who stays around long enough to convert.
That means the pricing test changed part of the product experience before it measured the commercial outcome.
So I’d look at both sides of the test: what happened to revenue or conversion, and what changed in the behaviour leading up to that result.
Sometimes better pricing is better product design. But you need to measure both to know.