Validate Offer Pricing Before You Build Anything
Validate offer pricing first: most new offers die because price was an afterthought. Use three questions and thirty conversations before you build a thing.
In most service businesses, the pricing decision happens last. The new certification tier gets designed, the diagnostic module gets built, the advisory program gets packaged — and then, days before launch, somebody finally asks: "So what do we charge for this?"
That ordering is the mistake. Not the number you eventually pick. The fact that you picked it at the end. The way out is to validate offer pricing before you build.
Madhavan Ramanujam, working from data on more than 10,000 monetization projects at Simon-Kucher, puts a number on what this sequencing costs: 72% of innovations fail because of monetization errors. Read that carefully. The dominant cause of new-offer failure isn't weak delivery, missing demand, or a broken market. It's pricing decided too late, with too little evidence, by the wrong method.
For founders of consultancies, agencies, and training businesses, this is uncomfortable but liberating news: the thing most likely to kill your next offer is also the thing you can fix in a week.
Where the Number Usually Comes From, and Why to Validate Offer Pricing Instead
Three Pricing Methods That Feel Rigorous and Aren't
When the price gets set at the end, it gets set by one of three methods — and every one of them leaves the buyer out of the equation.
Cost-plus. "Delivery costs us X, we need Y in margin, therefore charge Z." This feels disciplined because it involves a spreadsheet. But your cost structure is invisible and irrelevant to the buyer. They aren't paying for your inputs; they're paying for their outcome.
Competitor midpoint. One rival lists $5,000. Another lists $8,000. You split the difference and call it positioning. Except you have no idea whether those competitors priced correctly, whether anyone actually pays those listed rates, or whether your offer occupies the same value category at all.
Gut feel. "This seems like a $3,000 kind of thing." The most honest of the three, because it admits it's a guess.
The shared defect: none of these methods involves asking a single prospective buyer a single question. The founder's assumptions stand in for the market's actual willingness to pay. And the data the founder needs simply isn't available through introspection — it lives in conversations with the people who would write the cheque.
Ramanujam's remedy inverts the standard build process: validate offer pricing before you commit to building. The price isn't the last decision. It's the first piece of market evidence.
Three Questions, Thirty Conversations to Validate Offer Pricing
The Whole Research Method, In Under a Week
"Willingness-to-pay research" sounds like something you'd commission from a firm. In reality, the working version is three questions, put to 30-50 plausible buyers, about a one-paragraph concept.
First: "At what price is this an obvious yes — a great deal?" You're locating the floor. Everyone converts down there, which means you're probably undercharging. As a bonus, the answer tells you what this buyer considers cheap for the category — competitive intelligence you can't get from a website.
Second: "At what price would you start to hesitate?" Not refuse — hesitate. This marks the beginning of resistance, the point where the buyer needs more proof before saying yes. The territory between the first answer and this one is your real pricing range: the band where most buyers convert if you communicate value well.
Third: "At what price is it a hard no, no matter how good it is?" This is the ceiling. Past it, no testimonial, case study, or positioning move rescues the sale. If you want to price above this line, you aren't adjusting a price — you're choosing a different buyer.
One conversation tells you almost nothing. Thirty conversations, mapped together, reveal structure no individual answer can show.
Two patterns matter most. The first is clustering. Ramanujam segments buyers by behavior rather than demographics: credential seekers with modest willingness-to-pay but real volume potential, revenue builders sitting in the middle band, and strategic buyers — fewer in number, willing to pay premium rates. Each cluster points to a separate tier, which is exactly why mature service offers come in multiple configurations instead of one flat price.
The second is the price cliff — a threshold where demand falls off sharply. Suppose your map shows a cliff somewhere between $3,000 and $5,000. Then your price needs to land decisively on one side of it. Park your offer inside that dead zone and it won't fail loudly; it will simply stop selling and nobody will tell you why.
"The best outcome of willingness-to-pay research isn't the offers it prices well. It's the offers it kills before you spend six months building them."
And that's the real payoff. If the research shows the market won't support a price that covers the build, you haven't failed — you've been spared. A week of conversations just cancelled half a year of wasted development.
A Field Guide to Dead Offers
Ramanujam's Four Failure Types, Translated for Service Businesses
Skip the work to validate offer pricing and your offer doesn't just "fail" generically. It fails in one of four specific ways, each with its own symptoms — and crucially, its own (different) cure.
Feature shock is over-building. So many tiers, modules, and add-ons that the buyer can't locate the value inside the noise. The service-business version is the 20-page proposal listing every conceivable engagement variant. Confronted with everything, the buyer chooses nothing — or requests the stripped-down version you never designed.
Minivation is under-building. A small methodology refresh, a supplementary worksheet, a modest add-on diagnostic — useful, sure, but not wallet-opening. It eats development time and returns trivial revenue. The cure is never a discount; it's folding the thing into a bigger package, or retiring it.
Hidden gem is a positioning failure wearing a product costume. The offer is genuinely strong — for a specific segment. But the marketing addresses everybody, so the right buyers never hear themselves described. A certification tier built for enterprise practitioners, promoted with copy written for solo consultants, dies of misdirection, not weakness.
Undead is the offer that should be dead and isn't. The economics fail, the signals are negative, but sunk cost and emotional investment keep it breathing. In methodology businesses this is usually the certification level no one enrols in, still listed on the site "just in case," quietly consuming attention that a viable offer deserves.
Notice what's missing from those four cures: "lower the price" fixes only one of them. Yet a price cut is the reflexive founder response to any underperforming launch — and for three of the four failure modes, it actively deepens the damage.
When Cheap Reads as Weak
The Failure Mode Ramanujam Didn't Name
There's a fifth pattern that service founders hit constantly, and Beckwith captured it with a story about Timberland. The struggling boot company moved its prices above the competition — and sales rose. Nothing about the boots changed. The higher price supplied a quality signal the product alone hadn't managed to send.
In expertise businesses the effect is stronger still, because there's nothing to inspect before buying. No prospect can test-drive a consulting engagement or sample a certification in advance. With quality invisible, price becomes the loudest available proxy for it. A diagnostic priced at $15,000 reads as deep and rigorous; the same questions priced at $2,000 read as a checklist.
Which produces the inverted failure: a price too low to believe. Buyers infer that something must be cut — a thin methodology, junior delivery, a surface-level assessment. The discount you offered to win them is the very thing pushing them away.
Simon's research draws the conclusion bluntly: undercutting competitors doesn't signal value. It signals lesser capability.
This is the under-appreciated gift of the three-question map you use to validate offer pricing. It marks the ceiling, yes — but it also marks the floor beneath which trust collapses. Overprice and you bleed volume. Underprice and you bleed credibility. The map shows you both edges.
The Inverted Launch Sequence
So for your next certification tier, diagnostic module, or group advisory program, run the launch in this order:
1. Write the concept, not the spec. One paragraph: the outcome it delivers, who it serves, the problem it removes. Resist the urge to design further — the paragraph is all the research requires.
2. Run the three questions across thirty buyers. Map every answer. Find the clusters, find the cliffs, mark the viable range.
3. Build to the price the map supports. If buyers will pay $8,000 for a premium certification, engineer an experience worth $8,000. If the map tops out at $2,000, design something you can deliver profitably at $2,000 — or decline to build at all.
4. Let the clusters define your tiers. Base tier for credential seekers, enhanced for revenue builders, premium for strategic buyers — each priced against that segment's willingness to pay, never against your cost of delivery.
5. Engineer the free-to-paid jump on purpose. If a free diagnostic or introductory module sits at the front of your funnel, treat the transition with respect. Simon's research flags the trap: free anchors the buyer's reference price at zero, and the psychological leap from $0 to any number at all dwarfs the leap from $5,000 to $7,500. Make free visibly temporary, and make the paid delta explicit.
Most founders run this list backwards — build, package, then price. The 72% figure is the documented cost of that order of operations.
Reverse it. Validate offer pricing first, then construct the offer that earns it. It feels less like inspiration and more like engineering — which is precisely why it works three times as often.