Why: the goal or problem
Different customers need different capabilities. A single package can charge light users for functions they do not need.
How: work toward a solution
A fictional workspace has three seats and 120 monthly exports. Basic costs 20 and includes exporting; Pro costs 35 and adds approval workflows. Both cover this baseline, up to five seats and 200 exports. The static table contrasts features, not per-unit discounts. All prices are fictional; taxes, fees and refunds are omitted.
Illustrative example
Feature-tiered pricing
Initial workspace · 3 seats · 120 exports/month
| Feature | Basic · 20 | Pro · 35 |
|---|---|---|
| Exports | Included | Included |
| Approval workflow | Not included | Included |
Both: up to 5 seats and 200 exports/month. Features differ; these are not quantity-price tiers.
Fictional amounts. Taxes, fees and refunds omitted.
What: the concept
Feature-tiered pricing offers packages with different capabilities. These tiers describe what customers receive, unlike quantity tiers that change a unit price.
Combine with subscription billing or per-seat quantities while keeping each axis explicit.
Discuss this idea
Comments are shared across languages. GitHub login required to post.