Pricing Tier

Origin & evolution

Tiering is applied price discrimination, the economics of charging different customers different prices for substantially the same product based on willingness to pay. The software-specific form is "versioning", analysed by Carl Shapiro and Hal Varian in Information Rules (1999), who showed that because the marginal cost of a digital copy is near zero, a seller can profitably offer deliberately limited and premium versions of one product to capture more of the demand curve.

The plain-language "good, better, best" framing comes out of retail and was brought into management practice by Rafi Mohammed, whose The Art of Pricing (2005) argued that most firms leave money on the table by selling a single version. A 2018 Harvard Business Review article by Mohammed made the case directly: a "good" tier defends against cheaper rivals, while a "best" tier captures customers who were always willing to pay more.

Madhavan Ramanujam and Georg Tacke's Monetizing Innovation (2016) pushes the design question💭Design QuestionExperience DesignAn open design problem to exploreView reference → earlier: their argument is that willingness-to-pay conversations should happen during product development, not at launch. A tier built without first segmenting customers by willingness to pay risks🎲RiskComplianceA risk to the product or businessView reference → what they call a "feature shock" — a single over-loaded offering that satisfies no segment cleanly, or a tier ladder whose rungs do not correspond to any real price ceiling in the market. By that reading, the feature placement decisions⚖️DecisionStrategyA recorded decision with context, rationale, and consequencesView reference → described by Mohammed are only sound if they follow a prior segmentation step.

Freemium pushed the bottom tier to zero. After the term was coined in 2006 (following Fred Wilson's description of the model), the free tier became a standard lowest rung whose job🔨JobUserJob To Be Done: what the user is trying to accomplishView reference → is acquisition rather than revenue, with the paid tiers above it carrying the economics.

How it works in practice

A project tool ships three tiers. Free supports up to three projects. Pro, at 10 GBP per user per month, lifts that to unlimited projects and adds time-tracking. Business, at 18 GBP, adds single sign-on and audit logs. The single-sign-on placement is the lever. It costs little to build, and no individual cares about it, but procurement at a 200-person company treats it as mandatory, which pulls that buyer straight to the 18 GBP tier.

Six weeks after launch the team sees most upgrades stop at Pro, and Business sits empty. The fix is a tiering decision, not a discount: move audit logs down to Pro and add usage-based seat analytics to Business, giving larger teams a reason to climb. The tiers are the product's negotiating surface, and editing them is how the team steers who lands where.

Pricing tier vs. its neighbours

• Pricing strategy💱Pricing StrategyPricing & PackagingAn overarching pricing strategyView reference → is the overall logic (value-based, cost-plus, penetration) that decides how prices are set. The tier is one concrete output of that strategy: a named package at a number. Strategy is the why; the tier is the what.
• Revenue stream💵Revenue StreamBusiness ModelA source of revenueView reference → is the mechanism a tier belongs to, such as a subscription🔂SubscriptionSales & RevenueA recurring subscriptionView reference →. Several tiers can sit inside one stream. The stream answers how money arrives; the tier answers in which package.
• Subscription is a single customer's actual commitment to a tier. The tier is the public offer; the subscription is the private contract one buyer signs against it.

In the graph

In the Unified Product Graph, pricing_tier🥉Pricing TierPricing & PackagingA pricing tier or plan lives in the Business, GTM and Growth region, in the pricing sub-domain. It attaches two ways: under a strategy via pricing_strategy_offers_pricing_tierPricing StrategyoffersPricing Tierhierarchy, and under a stream via revenue_stream_tiered_as_pricing_tierRevenue Streamtiered asPricing Tierhierarchy. Downstream, subscription_subscribes_to_pricing_tierSubscriptionsubscribes toPricing Tiercross-domain connects each real customer to the tier they chose, and experiment_run_tests_pricing_tierExperiment RuntestsPricing Tiercross-domain lets a tier be the unit of a pricing test. That wiring makes a tier traceable from the strategy that designed it down to the individual subscriptions it earns, so a tier that nobody subscribes to is queryably visible as a dead rung on the ladder.