Feature Tier Design¶
Method — instantiates Arbitrage Prevention Mechanism Design
Differentiates versions by features, support level, flexibility, capacity, timing, or convenience so segments self-select into appropriate offers.
Feature Tier Design prevents cross-segment leakage by building the fence into the product itself. Rather than policing who may buy the cheap version, it engineers a deliberate gap between versions — features present or absent, capacity capped or generous, support fast or best-effort — so that each segment finds a different tier obviously best for it. Its defining discipline is the balancing act at the center of versioning: the low tier must be genuinely worse for the high-value segment (or that segment cannibalizes the premium), yet still genuinely good enough for the low-value segment (or the low tier collapses into uselessness and nobody buys it). The whole method lives on that knife's edge — calibrating the distance between tiers rather than raising a barrier around them.
Example¶
A project-management SaaS serves two very different buyers: a two-person freelance studio that needs shared task lists, and a 400-person enterprise that needs audit logs, single sign-on, role permissions, and a dedicated support line. Charging both the same price leaves money on the table; charging the freelancers the enterprise price loses them entirely. Feature Tier Design solves it by shaping the versions. The Free/Starter tier carries the core boards and a cap of five projects — everything the studio needs, nothing the enterprise can run on. The Business tier adds unlimited projects and integrations. The Enterprise tier adds SSO, audit trails, granular permissions, and an SLA. The enterprise cannot simply run 200 seats on Starter, because Starter genuinely lacks the governance features its security team requires — the missing features are the fence. Meanwhile the studio isn't insulted by a crippled product; Starter does its job well. Each buyer reaches for the tier built for it, and the price gap holds without a single eligibility check.
How it works¶
- Map the segments to what they actually value. Enumerate the buyer groups and the specific capabilities, capacities, or service levels each one will and won't pay for — the input that tells you which dimension to differentiate on.
- Differentiate on a dimension the high-value segment cares about. Put the enterprise-critical capability (governance, capacity, SLA) behind the premium tier, so its absence is a real cost to them and a non-issue to the low tier.
- Calibrate the similarity gap deliberately. Set the distance between tiers wide enough that the premium buyer won't downgrade, narrow enough that the budget buyer still finds the low tier worth buying.
- Avoid gratuitous crippling. Degrade the low tier only along dimensions the target segment doesn't need; degrading a shared-value feature just to punish downgraders damages the offer without improving the fence.
Tuning parameters¶
- Differentiating dimension — features vs. capacity vs. support vs. flexibility. Choosing a dimension the premium segment genuinely needs makes a self-enforcing fence; choosing one they don't invites downgrade.
- Tier gap width — how far apart adjacent tiers sit. Too narrow and the premium cannibalizes down; too wide and the middle empties out into a "good enough" cheap tier or an unreachable expensive one.
- Number of tiers — more tiers capture willingness-to-pay more finely but multiply confusion and the risk that adjacent tiers blur.
- Low-tier floor — how usable the cheapest version is. Raising the floor wins the price-sensitive segment but risks leaking premium value downward.
When it helps, and when it misleads¶
Its strength is that the fence needs no enforcement, no verification, and no monitoring: the product's own shape does the sorting, and there is nothing to police because there is nothing to evade. Done well, every segment is better served than a single blended product could manage.
Its two failure modes sit on opposite sides of the knife's edge. Set the tiers too similar and the premium segment quietly downgrades — cannibalization — collapsing the price gap. Set the low tier too degraded and you get "damaged goods,"[n1] a version deliberately hobbled below usefulness, which alienates the very segment it was meant to serve and invites reputational backlash. The classic misuse is degrading a shared-value feature — throttling something both segments need — which spends goodwill without improving segmentation, since it doesn't change any buyer's relative preference between tiers. The guarding discipline is to differentiate strictly along dimensions the high-value segment values and the low-value one doesn't, and to sanity-check that the cheapest tier is still a product someone would happily choose on its own merits.
How it implements the components¶
substitution_similarity_limit— the core: it sets and holds the deliberate distance between versions, keeping the low tier far enough from the premium to prevent downgrade while close enough to remain worth buying.segment_value_map— the method begins by mapping which buyer group values which capability, so the differentiating dimension is chosen where the segments genuinely diverge.differential_offer_set— it names exactly what differs across tiers — features, capacity, support level, SLA — making the protected difference explicit and designed rather than incidental.
It does not add a timing gate bounded by a friction budget (customer_friction_budget) — that's Advance-Purchase or Time-Window Restriction — nor restrict where the offer is valid (access_channel_boundary), which is Geographic or Channel Restriction.
Related¶
- Instantiates: Arbitrage Prevention Mechanism Design — builds the fence into the product so segments sort themselves by version rather than by policed eligibility.
- Sibling mechanisms: Advance-Purchase or Time-Window Restriction · Geographic or Channel Restriction · Identity-Bound Entitlement · Non-Transferable Terms and Refund Rule · Usage Quota or Rate Limit · Bulk-Purchase and Resale Monitor · Exception, Appeal, and Manual Review · Credential Verification Workflow
Editorial Notes¶
Form Classification¶
Form family: Structure, Architecture & Configuration
Rationale: The mechanism configures an enduring offer architecture with differentiated features, support, flexibility, capacity, timing, and convenience so segments self-select.
Nearest alternative: Analysis, Modeling & Optimization — Analysis can inform tier boundaries, but the deployed mechanism is the maintained configuration of the tiered offers.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Economics & Finance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Differentiated product tiers and self-selection derive from price discrimination and mechanism-design reasoning in economics.
Related originating lineages:
- Innovation & Entrepreneurship — Product and go-to-market practice shaped feature packaging for distinct customer segments.
- Organizational & Management Science — Marketing and product-management practice materially developed the concrete tier architecture.
Review resolution: Both reviewers agree that economics_finance is primary. I retain organizational_management, innovation_entrepreneurship only as formative origin lineage(s), without treating every later application as an origin. cross_disciplinary_synthesis is appropriate because the exact artifact combines contributions from multiple professional lineages. Reach is multi_domain as a separate applicability judgment: it does not widen or narrow the recorded provenance. Encyclopedia synthesis is false because the artifact is already established enough that encyclopedia-specific synthesis is not required. The secondary differences are reconciled with no unresolved primary-provenance ambiguity.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
Feature Tier Design is the one fence in this family that creates value while it segments — a better-shaped product for each buyer — rather than only imposing a cost. That is also its trap: because the tiering is intrinsic, a mis-set gap is expensive to change once customers have anchored on the current versions, so the similarity limit is worth getting right before launch rather than after.
[n1] "Damaged goods" — the strategy, analyzed by Deneckere and McAfee, of offering a deliberately degraded version of a product to segment price-sensitive from price-insensitive buyers. It works when the degradation costs the seller little and matters only to the high-value segment; it backfires when the low version is hobbled past usefulness or degraded along a dimension both segments value. ↩