Acquisition creates demand. Pricing captures value.
A price change is not a personality test. It is a controlled operating decision about what the customer values, what the offer removes, and whether the business can deliver the promise at a healthy contribution.
Four checkpoints from guess to power.
Select a checkpoint to inspect the operating intervention. The sequence is illustrative; your price depends on segment, alternative, costs, and delivery capacity.
Test willingness to pay
Start with observed behavior and a falsifiable price question. Hold the offer and experience steady while you learn whether the price changes revenue, margin, retention, and segment mix.
question → test → contributionMove price without creating new failure modes.
Combine interviews with purchases, discounts, win/loss patterns, sales friction, and retention. Stated preference is not the same as observed buying.
Use cost of delay, real alternatives, and service differences as references. A credible anchor clarifies the decision.
Use good/better/best when tiers map to distinct customer needs. Use one offer when the problem and outcome are narrow.
Track revenue, gross profit, refunds, sales effort, support load, retention, and segment mix together.
A price that raises conversion but attracts low-fit customers, increases support burden, or lowers durable contribution is not a pricing win. Calibrate the decision against the whole customer lifecycle.
What usually breaks pricing power.
The founder changes the number and cannot explain what the test was meant to learn. Fix: name the variable, metric, segment, and guardrail before launch.
The reference price is invented or irrelevant. Fix: connect the frame to cost of delay, real alternatives, or meaningful service differences.
Three packages contain the same work with different labels. Fix: build tiers from real constraints or use one clear offer.
Conversion rises while margin and retention fall. Fix: read revenue, gross profit, refunds, sales effort, and customer quality together.
Read the price change across the whole system.
The most common pricing mistake is to stop at the checkout event. A higher price changes who enters the funnel, how much work sales must do, what customers expect, how support is used, and whether the account renews. The price decision should therefore be read as a system signal, not an isolated conversion number.
Compare segment, use case, urgency, acquisition source, and expected service load. A price can improve customer fit even when raw volume falls.
Track sales-cycle length, discount requests, approval layers, proposal revisions, and founder involvement. Price power should reduce the need to subsidize uncertainty with labor.
Review onboarding, support, customization, refunds, and escalation patterns. Higher willingness to pay is not permission to make a promise the operating system cannot keep.
Read renewal, expansion, contraction, usage, and customer feedback after the initial purchase. The best price is not the highest opening number; it is the one that supports a durable exchange.
Before changing price, write the customer segment, value hypothesis, reference point, offer difference, primary metric, guardrail metrics, test window, rollout limit, and rollback condition. After the test, record what changed, what did not, and what the next decision should be.
Measure the price signal. Then strengthen it.
Write the hypothesis, frame value honestly, choose the smallest credible menu, and roll out with guardrails.
OPEN PRICE TRACE