Price Before You Build
Price is a product input. A team that waits until the build is done inherits a segment, a feature set, and a package it never chose on evidence.
The Core Insight
Price is a product input. A team that sets it after the build has already locked the decisions the price existed to inform.
Most teams build the product first, then ask what it is worth. By then the features exist and the roadmap carries inertia. The sales story is half written, and the business case rests on guesses. Then someone asks what to charge.
Price shows what a customer values, how badly they want it, and what kind of business you are building. Those answers change what you build. Read them after the build and they only explain the miss.
The Framework
Market and price come first, then design, then build. The evidence must arrive early enough to change the product, and rough math is enough to act on.
- Define the segment by need, value, urgency, current alternative, and willingness to pay.
- Run willingness-to-pay conversations before engineering locks the roadmap.
- Sort features into leaders that drive value, fillers that support the package, and killers that add cost without payment.
- Choose the packaging before the product becomes a bundle of internal opinions.
- Choose the pricing metric before usage behavior hardens.
- Connect value, price, volume, and cost in one business case.
- Give one person authority over monetization.
Packaging is the step that gets postponed, and it tells the customer what the product is for. Good, better, best works when every tier has a real fence. When the tiers turn to mush, sales becomes discount negotiation.
A single monetization owner is easy to write down and easy to skip. The courage note asks who receives the result of this choice. Ask it about the price. When the answer names a committee, the decision is already blurred.
Key Ideas
Who Owns the Price
Price belongs to product, strategy, sales, marketing, engineering, and customer research at once. It is where all of those functions meet reality.
A company that asks for pricing help is usually asking a late question. The early one is whether it built the correct thing for the correct customer. That question covers the feature set, the reliability, the story, the metric, and the model.
If those answers are wrong, a price change hides the product problem for one quarter. The Psycho-Cybernetics note called this correction beating willpower. A wrong price is feedback, and the correction runs on the product.
Four Product Failures
Feature shock arrives when the team tries to please everyone. The product collects features, use cases, and internal opinions, and it collects almost no customer truth. It ends up hard to explain and expensive to build.
Minivation happens when the company builds something valuable and then prices it low or draws the opportunity too small. No leader anchors the package, so the number gets set against build cost. The product works and the business collects a fraction of the value.
A hidden gem is a valuable capability trapped in the wrong package or treated as a side feature. The leader sits inside a tier as a filler, so no fence makes anyone pay for it. The company holds value it has no way to charge for.
An undead product is one the company must kill before launch. It survives because internal momentum is easier than honest customer evidence, and because the kill sits with a committee.
Willingness to Pay Is a Product Input
Asking a buyer to name a price gets you a number that costs nothing to say. The stop-pitching note named the mechanism: interest is atmosphere, and behavior is evidence.
Ask what they do today, what it costs, and what breaks. The next question is which feature matters most. Then walk the price: which number is acceptable, which is expensive, and which is impossible. Ask why after each one, because the why matters more than the number.
These conversations hand you a product shape. They tell you which value the customer already recognizes, and which package makes that value obvious.
Segmentation Decides What to Build
The average customer does not exist. Two customers who value different things and pay for different things are not one segment because they share a company size.
Good segmentation changes the product, the packaging, the message, the channel, and the price. A segmentation that changes no decision is a label.
The Pricing Metric Outranks the Price
Seat, transaction, usage, credit, take rate, project, and outcome each teach the customer a different behavior. The metric decides how value scales, who carries risk, and whether the business improves as the customer succeeds.
For an AI product the metric decides more. Every use carries compute cost, and the value can run far above the usage. Selling access is a different business from selling usage, completed work, or an achieved outcome.
Practical Applications
Knowing the method changes nothing by itself. The hard part is making no an acceptable answer inside the company. No to features nobody pays for, no to the undead product, no to the bundle that hides weak thinking. Test the story, the packaging, the segment, and the proof before you cut the price.
- Run ten value conversations before the roadmap debate.
- Build a feature value map: leaders, fillers, killers.
- Draft three packaging options with real fences.
- Build the ROI model inside the proof of concept: time saved, errors reduced, delay avoided, revenue opened, risk removed.
- Write the value story in customer language.
- Put the business case on one page, and name the guess each line rests on.
- Decide what you will do if sales are weak, before sales are weak.
A proof of concept that only shows the technology works is too small. The goal is a buyer who can defend the value.
Who This Is For
Read This If
- You plan to build the product now and set the price after launch.
- You keep adding features and cannot name the ones customers pay for.
- You build an AI product and have not decided whether you sell access, usage, work, or outcomes.
Skip This If
- You want a price point and no change to any product decision.
- You will not cut a feature that customers do not value.
The Test
Before the next product review, bring willingness-to-pay evidence, a feature value map, and the pricing metric. Bring the business case that connects value, price, volume, and cost. Without those four, the product is not ready for a roadmap debate.
The Decision
Pick one product idea today and write the decision it needs: build, change, price, package, pilot, or kill.
Let value evidence shape the segment, the feature set, the package, and the business case while the product is still soft.
Then name the metric and put a date on it, before engineering finishes and picks one for you. Charging the highest number a buyer tolerates is a different job, and a smaller one. The work is to make price, value, proof, and customer trust point in the same direction.
Price settles what one customer pays. The next number to earn is how many customers you can prove you reached.