Chapter 3
Design the value ladder and pricing
Part of How to Increase Order Value With Bundles and Upsells.
Finish this chapter with a good-better pricing comparison you can use immediately to design the value ladder and pricing, while avoiding adding extras that dilute the core outcome.
What you’ll get
- A completed good-better pricing comparison, not a list of abstract ideas.
- One explicit decision rule for design the value ladder and pricing.
- A 45-minute execution sequence you can repeat yourself or hand to a teammate.
- A quality gate that tells you whether to move forward, run one small test, or revise the input.
Use this chapter as a working session
Open the document, spreadsheet, or Tapmy workspace where this decision will live. Replace sample language with the exact offer, buyer, channel, price, and evidence you have today. If a fact is missing, label it as an assumption and assign the smallest test that can resolve it.
| Time | Work | Concrete output |
|---|---|---|
| 0–10 min | Collect buyer words, traffic data, sales conversations, support questions, and current page copy. | A short evidence list with source and date. |
| 10–20 min | Make the single decision this chapter is designed to resolve. | A one-sentence decision and reason. |
| 20–35 min | Build the good-better pricing comparison with real names, numbers, links, and owners. | A usable operating asset. |
| 35–45 min | Review it from the buyer’s point of view and run the quality gate. | A keep, test, or revise decision. |
Create a clear good–better choice
A two-option ladder is often enough:
- Core: the essential self-serve solution;
- Complete: core plus complementary tools, deeper examples, or support.
Do not make the core offer intentionally frustrating. The premium option should add value, not remove a problem you introduced.
Price from standalone value and customer logic
List each component’s real standalone price, if it is genuinely available alone. Then choose a bundle price that gives a visible reason to buy together while protecting margin, time, licensing obligations, and support cost.
For service or coaching additions, account for delivery capacity. A “high-margin” upgrade can become expensive if every buyer requires manual support.
Show the comparison clearly
| Decision point | Core offer | Complete offer |
|---|---|---|
| Best for | Buyers who want the essential asset | Buyers who want the full implementation path |
| Includes | Main template | Template + examples + tracker + review |
| Creator time required | Low | Medium due to review component |
| Delivery | Instant digital delivery | Instant files + scheduled service |
| Price role | Accessible entry | Higher-value outcome |
Make each difference specific. Avoid vague rows such as “More value” or “Premium support” without explaining what happens.
Decision gates
| Evidence state | What it means | What to do next |
|---|---|---|
| The input is specific, current, and tied to a real buyer action | The good-better pricing comparison is ready to use. | Put it into the Tapmy journey and measure the next observable behavior. |
| One important input is assumed | The direction is testable, not yet proven. | Run the smallest test that can confirm or reject that assumption. |
| The asset serves several audiences, offers, or goals | The scope is too broad. | Narrow to one buyer, one job, one offer, and one reporting window. |
| The result depends on a claim you cannot show or deliver | Trust and delivery risk are higher than the upside. | Rewrite the promise around a supportable outcome. |
Quality standard
- The good-better pricing comparison names one buyer and one job.
- Every number has a timeframe, currency, or denominator where needed.
- Every link and handoff has an owner.
- The next action is visible without rereading the chapter.
- The decision can be measured through customer behavior.
- No claim is stronger than the evidence.
