Book: Monetizing Innovation: How Smart Companies Design the Product Around the Price Author: Madhavan Ramanujam & Georg Tacke (Simon-Kucher & Partners) In one line: Have the price and willingness-to-pay conversation with customers before you build - then design the product around what they will actually pay for.
1 · Design around the price
Most teams build the product, then bolt a price on at the end and hope. Flip the order: make price a design input from day one. Every feature, tier, and packaging choice gets tested against what customers will pay - so the product is shaped by the wallet, not just by engineering ambition.
2 · Willingness to pay is the compass
Willingness to pay (WTP) is the single most important number in the whole effort, and - the book’s key claim - you can learn it before you build. Ask customers early and often, in plain money terms, while the answer can still change what you make rather than just explain the disappointment.
3 · Great products still fail to earn
A product can delight users and still flop commercially. Simon-Kucher found roughly 72% of new products miss their revenue or profit goals. Failure almost always traces to one of four preventable patterns - and an early pricing conversation defuses all of them.
Innovation rarely fails because the product is bad. It fails because nobody checked whether people would pay for it - and by launch it is far too late and too expensive to find out. The authors, pricing consultants at Simon-Kucher, argue that most companies run the process backwards: they invest months building, then hand a finished product to a pricing team and ask “what should we charge?” By then the die is cast. Features customers do not value are baked in; features they would happily pay a premium for were never prioritised.
The fix is to move the money conversation to the front. Treat willingness to pay as the compass that guides the entire design: which features to build, how to segment customers, which pricing model to choose, and how to tell the value story. When you know early what customers value and what they will spend, you build the right thing, price it with confidence, and reach launch already knowing the product will earn its keep.
This is not about squeezing customers. It is about aligning what you build with what people genuinely value - so innovation reliably turns into revenue instead of praise that never shows up in the numbers.
The method has two halves that lock together. First, a design-around-the-price process that puts WTP at the front. Second, a diagnosis of the four failure types that appear whenever teams skip that conversation. Learn to name all four and you can spot which trap your own project is walking into.
The process, in short:
Have the WTP conversation early. While the design is still open, ask customers - directly and in monetary terms - what the idea is worth to them. Not “would you like this?” (everyone says yes) but questions that surface real trade-offs and price sensitivity.
Rank and prioritise features by value. Sort features into leaders (drivers people pay for), fillers (nice but not decisive), and killers (things that actively destroy WTP if bundled or charged for). Build the leaders; drop or hide the rest.
Segment by willingness to pay and needs. Different customers value different things. Group them by value and need - not demographics - so you can serve each with the right offer.
Choose the monetization model, then the price level. Decide how you charge (subscription, per-use, freemium, bundle, tiers) before you fix the number, because the model shapes everything downstream.
Build the business case and value story. Assemble a value-based case and a clear reason-to-pay so the launch team never falls back on reflex discounting.
The four ways innovations fail to monetize:
Feature shock
An overloaded, unfocused product crammed with features for everyone - and therefore compelling to no one. Cost and complexity balloon, the core value gets diluted, and customers cannot see what they are paying for. Cause: building without asking which features actually drive WTP.
Minivation
A genuine breakthrough launched too timidly - priced too low, scoped too small, or marketed too quietly - so it leaves most of its value on the table. The innovation was real; the ambition and the price were not. Cause: underestimating WTP and playing safe.
Hidden gem
A feature or product with real willingness-to-pay that the organisation fails to recognise or never takes to market - often because it does not fit the existing business, or nobody championed it. Value that existed but was left buried. Cause: not listening for value in the right places.
Undead
A product that should have been killed at concept but was launched anyway - customers did not want it, yet it shipped and limps along consuming resources. The most common and most wasteful failure. Cause: never testing demand and WTP before committing.
The Porsche Cayenne
The flagship example. Porsche designed its SUV around the price - starting from what Porsche buyers would pay for a Porsche-branded SUV, then engineering to hit that value. It became one of the most profitable vehicles in the industry and helped fund the whole company. Proof that “design around the price” scales to a bet-the-brand product.
WTP is knowable before you build
The book’s core, counter-intuitive claim: you do not have to guess. Structured customer conversations and pricing research (trade-off questions, feature value, price-sensitivity checks) reveal WTP while the design is still fluid. This is what makes “design around the price” possible instead of aspirational.
Leaders, fillers, killers
A practical lens for the feature list. Leaders are the few features that drive willingness to pay; fillers add little; killers (often a poorly received charge or an unwanted bundle) reduce it. Concentrate investment on leaders and you kill feature shock at the root.
Segment by value and need
Group customers by what they value and what they will pay - not by age, size, or industry. Demographics are easy to collect and weak at predicting the wallet. Real value segments let you build good-better-best tiers and bundles that each fit a distinct set of needs.
Choose the monetization model
How you charge matters as much as how much. Subscription, pay-per-use, freemium, dynamic pricing, and a la carte versus bundling each fit different value patterns. Match the model to how customers actually receive and measure value - recurring value suits subscriptions, variable usage suits per-use.
Value communication over discounting
Build a value-based business case and a crisp story for why the price is fair before launch. Reactive discounting trains customers to wait, signals you did not believe your own price, and quietly erases the margin you designed for.
Behavioural pricing tactics
Buying is psychological. Anchoring, framing, the way choices are packaged, and how a price is presented all shift what feels reasonable - independent of the raw number. Design the choice architecture, not just the figure.
Willingness-to-pay first, always
The connective thread: WTP is not one step, it is the organising principle behind feature choices, segmentation, model, and price. Get it early and everything downstream sharpens.
Part one makes the case: why so many innovations fail to monetize and what the four failure types look like. The middle chapters walk the design-around-the-price method step by step - having the WTP conversation, prioritising features, value-based segmentation, choosing a monetization model, setting the price, and building the business case and value communication. Later chapters cover behavioural pricing tactics and how to embed all of this as a repeatable capability, with case studies (Porsche, Optimizely, LinkedIn, Uber and others) threaded throughout to show the principles in action.
Talk price before you build. While the concept is still changeable, ask target customers - in monetary terms - what the idea is worth to them. Design the conversation to surface trade-offs, not polite yeses.
Sort features into leaders, fillers, and killers. Keep and invest in the leaders, trim the fillers, and remove the killers. This single move prevents feature shock.
Build value segments. Group customers by willingness to pay and need, then design good-better-best tiers or bundles that map to those segments.
Pick the monetization model on purpose. Decide whether subscription, per-use, freemium, dynamic, or bundling best matches how value shows up over time - before you argue about the number.
Set the price against WTP, and check for the four traps. Ask explicitly: are we feature-shocking, minivating, sitting on a hidden gem, or building the undead?
Write the value story and business case before launch. Put the reason-to-pay and the numbers on paper so nobody defaults to a discount under pressure.
Make it a habit, not a one-off. Bring WTP into every innovation cycle so pricing becomes a design capability rather than a launch-week panic.
The authors write from Simon-Kucher, the world’s largest pricing consultancy, so the book doubles as a showcase for their method - the frameworks are practical but also a shop window. It leans B2B and product-launch heavy; a solo founder or a purely consumer app may need to adapt the customer-conversation techniques. And the headline promise - that you can reliably learn willingness to pay before building - depends on doing the research well; sloppy or leading questions produce confident numbers that are simply wrong. Read alongside behavioural-pricing work (Kahneman, Ariely) for the psychology behind the tactics chapters. B2B-leaning Practitioner playbook
Design the product around the price - not the price around the product.
Willingness to pay is the most important number in your business, and you can learn it before you build.
If customers will not pay for a feature, it is not a feature - it is a cost.
A discount is a decision you failed to make earlier, priced.
Segments are groups of wallets that behave alike, not groups of people who look alike.
The undead is the product you should have killed at the whiteboard, walking around the market draining your resources.