Probe how feature gating and option structure steer self‑selection by willingness to pay. Use versioning levers to widen reach without racing to the bottom.
Versioning relies on self‑selection via ______
random coupon drops
cost‑plus markups only
fences that separate high and low willingness to pay
single universal bundles
A classic fence in SaaS usage tiers is ______
the corporate logo color
rate limits or caps on key resources
weekend email blasts
CSV file names
An ethical decoy option should ______
clarify trade‑offs without hiding essential value
force dark patterns
remove the affordable plan
conceal total cost
For APIs, monetizing by primary value metric typically means pricing per ______
email open
log‑in event only
downloaded brochure
successful call or unit of core output
Freemium should reserve premium for features that are ______
high‑WTP and low externalities when locked
legal compliance notices
security updates
mission‑critical basics
A warning sign that tiers are poorly separated is ______
predictable add‑on uptake
heavy downgrades from top tiers to entry tiers
stable ARPU growth
clear upgrade paths
Bundled add‑ons work best when they ______
pad release notes
repeat core features
solve adjacent jobs that magnify core value
increase onboarding friction
Good‑Better‑Best versions should step up along a ______
mix of unrelated metrics
single dominant value axis users care about
random feature list
nonfunctional aesthetic changes only
If a mid‑tier is rarely chosen, it likely needs ______
extra colors in the UI
either stronger differentiation or price repositioning
higher cancellation fees
more jargon in names
Per‑seat pricing works best when value scales with ______
downloaded PDFs
brand awareness alone
historical sunk costs
number of active users creating outcomes
Starter
Your versions blur; clarify boundaries so users self‑select.
Solid
Nice tiers; adjust fences and decoys to capture surplus.
Expert!
Masterful versioning—clear fences, clean trade‑offs, strong capture.
