
Track overview
About this track
Decision practice for pricing owners, founders, and operators who sell one product to customers who value it very differently — and keep leaving money on the table with a single list price. Where Value-Based Pricing finds the one best price on a demand curve, Price Structure & Segmentation is what you reach for when no single number can be right for everyone: design the structure of pricing — versioned tiers, fences, and bundles — so different customers sort themselves into different prices, capturing heterogeneous willingness-to-pay without cutting the price for all. You build a Good/Better/Best line whose fences make each segment self-select into its intended tier and whose premium anchor protects the top; offer a targeted discount behind a fence that holds against leakage; and decide when to sell separately, bundle, or do both. The goal is never the simplest price or the most-bought tier — it's the most contribution, captured by charging each segment closer to its own value. This is the pricing-decisions domain's second course, after Value-Based Pricing.
How each module works
Every module in this course runs the same three steps, from the first lesson to the debrief. The loop is what makes Decyde a place to practise, not just to read.
Step 1
Read
The lessons. Read the situation, the evidence and the shape of the trade-off before you commit.
Step 2
Size
The simulation. Put numbers on both sides of the trade-off, then make the call against the engine.
Step 3
Defend
The debrief and report. See what your call bought and why, so you can defend it or change it.
The same loop in every module, and a new decision each time. Judgment compounds.
Modules · In order
Three modules in this track
Each module is one decision: short readings, the decision itself, then a debrief and a replay in a shifted world.
01/03
Good-Better-Best: Designing a Line So Customers Sort Themselves
Arclight sells one analytics product to three very different customers (a price-sensitive Basic segment of 5,000 seats, a growing Pro team of 3,000, and a deep-pocketed Enterprise buyer of 2,000) on a single flat price that overcharges the small and undercharges the large. You're Head of Pricing, and the annual packaging review is your chance to replace that flat price with a proper Good/Better/Best line. The reflex is to keep one simple number, or to price the tiers off cost, but the lever isn't the price of a plan, it's the shape of the line: three tier prices, set so each segment self-selects into the tier that leaves it the most surplus (willingness-to-pay minus price). Sales, Finance and Product each want something different, and the line is locked for the coming cycle. How do you design it?
12 lessons · 2 mini-sims · ~30 min
Begin module02/03
Fencing the Discount: How to Offer a Lower Price Without Cutting Your Price
Arclight sells one analytics product at a single $150/seat/mo list, and every month thousands of startups and students sign up, love it, and vanish at the paywall: they value it at about $60, not $150, so today Arclight earns $0 from all of them. You're Head of Pricing: Sales wants a discount to win them, and Finance is terrified a discount will leak to the 4,000 enterprise accounts happily paying $150. Is the answer 'discount' or 'don't'? Or is there a third thing, a rule (a startup-only plan, a .edu check, an annual-commit tier) that lets the price-sensitive segment buy low without the full-price crowd slipping across? Two loud instincts are on the table: 'a discount just means cutting the price', and 'make it deep so they can't refuse'. And any fence you build can leak, and leakage drifts. You set the discount and the fence tightness, and decide: how low, and how tight?
12 lessons · 2 mini-sims · ~30 min
Begin module03/03
Bundle or Unbundle: When Wrapping Two Products Beats Selling Them Apart
Arclight sells two products, Analytics and Reporting, à la carte at separate prices, and across a base whose tastes differ sharply it captures far less than it could: some accounts live in Analytics and barely touch Reporting, some are the reverse, some value both, and a large segment wants only Analytics. One price per product can't be right for all of them. You're Head of Pricing, and the coming-cycle packaging review is finally yours: the question isn't 'what price?' but 'what shape of offer?': sell the two apart, wrap them into one bundle, or offer both the pieces and the pair. The real lever is the structure, not the price of either product. Two loud instincts are on the table: the CFO's 'a bundle is just a discount for buying two', and the reflex to wrap on autopilot. Then the replay flips the base's tastes. You place the two products into separate, bundle and both zones and set the prices: which shape, and how priced? The capstone of Price Structure & Segmentation: it closes the Version, Fence, Bundle arc.
12 lessons · 2 mini-sims · ~30 min
Begin moduleAuthored on Decyde Practice loop curated for decision discipline
Vocabulary
What you'll engage
The decision skills you'll practice are paired with the underlying patterns you'll learn to recognize. Both vocabularies compound across the Pricing Decisions domain.
Decision skills you'll practice
Tier designDiscount disciplineValue-vs-price positioningSegment-specific pricingAnchor pricingElasticity reading
Patterns you'll see
Practice evidence recorded on Decyde
Every decision practiced builds your Decision Profile
Replays supported
Practice the same decision differently · iteration builds judgment
English
Additional languages on v1.3+ roadmap
What's next · One recommendation
The other Pricing Decisions courses each practise a different kind of decision.
Begin practice →FAQ
Questions about this track
Common questions about Price Structure & Segmentation and how this track works.
Related · Other tracks




