
Pricing
This framework was generated using the Framework Builder methodology. It demonstrates the five-layer DNA architecture applied to pricing for products and services.
Built with the Framework Builder methodology
Download markdownThis framework was generated using the Framework Builder methodology. It demonstrates the five-layer DNA architecture applied to pricing for products and services.
Layer 1: Principles Foundation
Principle 1: Price is a message about value, not a recovery of cost. A low price signals low value whatever the quality. A high price with no justification signals arrogance. Decide what position you want in the market, then let the number say it.
Principle 2: Willingness to pay varies by segment and context. Two buyers can get identical value and have very different thresholds. One price for both means you overcharge one or undercharge the other.
Principle 3: Price reflects the gap between your outcome and the buyer's next best alternative. Not your hours, not your costs. A person who solves a large problem in ten hours should not be penalized for being efficient.
Principle 4: Pricing is the highest-leverage lever most businesses ignore. An improvement in price lands on every transaction immediately. Most teams will spend months on a small conversion lift and leave pricing untouched for years.
Principle 5: The buyer should never be surprised by the total. Predictability builds trust and removes the incentive where a longer engagement helps you and not the client.
Layer 2: Systematic Approach
Step 1: Quantify the value delivered. For each offer, write the outcome in the buyer's terms: revenue gained, cost avoided, time saved. If you can't put a number on it, pick a proxy metric the buyer already tracks.
Step 2: Segment by willingness to pay. Name the two or three variables that move it most (company size, urgency, available alternatives). Each segment gets its own pricing logic, not a discount on one list.
Step 3: Route to a pricing model. Branch on what you sell. Products: one-time, subscription or usage-based. Services: if the value ties to a measurable outcome, price on value (a share of the projected impact). If it executes a known scope, use a fixed fee. If it is ongoing counsel, use a monthly retainer. Hourly billing is the fallback, not the default.
Step 4: Set specific price points. Start from the value gap, then position against the next best alternative. Write the price and the one-sentence reason for it. A price nobody on the team can defend will be discounted.
Step 5: Test and adjust. Show different prices to different cohorts where you can. Measure conversion, revenue per customer and satisfaction, then change one variable at a time.
Layer 3: Force Multipliers
Multiplier 1: Anchor before you quote. Present the highest-value option first. The middle option then feels reasonable. Without the anchor, the same number feels expensive.
Multiplier 2: Build three tiers and design the middle one. Good, better, best works because buyers want a reference frame. Most pick the middle, so you control volume by controlling what sits above and below it.
Multiplier 3: Use a decoy on purpose. If a lower plan and a higher plan both exist, a third plan priced close to the higher one with fewer features makes the higher plan the obvious choice. The decoy exists to redirect, not to sell.
Multiplier 4: Bundle for perceived value, and consider removing the cheapest entry. Combine items so the bundle feels worth more than its parts. Removing the lowest tier often moves those buyers up instead of out.
Multiplier 5: Change the frame when you change the number. A price increase on the same offer with the same story triggers resistance. Pair it with new packaging, added value or a different tier structure.
Layer 4: Success Metrics
Positive indicators:
- Revenue per customer rises over time, tracked by segment and not only in total
- Win rate holds as price rises on a tier, or falls only where positioning is weak
- Fewer than 20% of deals carry a discount
- Buyers choose the tier you designed to be chosen
Failure signals:
- Total revenue grows while revenue per customer is flat (volume is masking weak pricing)
- Win rate is high at every price point (you are probably too cheap)
- Your team discounts by reflex and cannot explain the price (the logic is not landing)
- Customers ask for hourly or itemized breakdowns (the value story is unclear)
- Price has not been reviewed in six months or more
Layer 5: Implementation Guidance
Roll out on one line first. Pick the product or service where you have the best data on customer behavior and the clearest read on value. Apply all five layers there, measure for 90 days, and use the result to justify the next line. Changing everything at once stalls.
Review quarterly, and name what triggers an early review. A competitor move, a discount rate above 15% of proposals in a quarter, or a major product change should each force a review before the date. Put it on the calendar, not in someone's memory.
Give your team a one-page pricing card. Routing logic, tier structure and the value formula, so the framework works without the full document. The owner of the first five proposals under the new model should log what worked and what needs adjustment.
Common mistake: pricing on cost. Cost-plus is comfortable because the math is simple, and it has no link to what the buyer receives. Price to the value gap.
Edge case: the buyer who wants a discount. Don't cut the number. Remove scope or move them to a lower tier, so the price stays tied to what they get.
Edge case: a new market with no reference price. Anchor on the buyer's next best alternative and the cost of doing nothing. Start with one segment and treat the first deals as price tests.
Edge case: you are competing on price and winning. Check positioning before celebrating. If cheaper is your only edge, you have a positioning problem, and the price will keep sliding.
Built with the Framework Builder methodology. Get the skill →