Design the tier architecture and per-tier inclusions
Given the format and transformation, reasons how many purchase tiers make sense and what core content and access differences sit at each tier, producing a tier table with rationale.
In / outChosen format, transformation promise, creator capacity → Tier table (tier name, inclusions, access differences, boundary rationale)
You might say…
“Do I do one price or three? And if three, what goes in each one that actually justifies the jump?”
What it does
Given the format and transformation, reasons how many purchase tiers make sense (single SKU vs good/better/best), what core content and permanent bonuses sit at each tier, and the access/delivery differences between them, producing a tier table with a rationale for each boundary. Used to settle 'what do buyers get at each level'.
Trigger: Use to settle what buyers get at each level before price points are set.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation