Why do the best operators settle pricing before the product is finished?
Madhavan Ramanujam's position, from Simon-Kucher and Monetizing Innovation, is that willingness to pay is a product design input, not a launch decision. He names four ways teams get it wrong: feature shock, where the product does too much and lands with nobody; minivations, where it works but is priced too low to matter; hidden gems, where a real opportunity dies inside the company; and undead, products that should never have been built. His other line worth keeping is that how you charge matters more than how much, which is why the packaging and the pricing metric usually deserve more thought than the number. The practical move is to have the willingness to pay conversation with customers early and often, well before you are ready to sell.
Go deeper
3 resources, 1 India-specific, 3 link-checked.
📄 Article
✓ Link checkedFreeIntermediate
The four failure modes (feature shock, minivations, hidden gems, undead) give you vocabulary for a conversation most teams keep having vaguely. Still the best single read on treating pricing as a design input.
Goes deeper than the article on how to actually run a willingness to pay conversation, plus the maximise, penetrate and skim choice. The transcript is on the page if you would rather skim.
The counterweight if you have decided Indian customers will not pay: Unicommerce runs 10,000 to 12,000 dollar contracts with enterprise customers, has been profitable since FY18, and IPO'd. Useful when you are setting India pricing.