Paywall

Origin & evolution

The paywall took its recognisable modern form in digital publishing. The Wall Street Journal charged for online access from its 1996 launch, an early hard paywall that gated almost everything. The Financial Times pioneered the metered model in 2007, letting visitors read a set number of articles before requiring payment. The model that spread industry-wide arrived when The New York Times launched its metered paywall in March 2011, granting 20 free articles a month before asking readers to subscribe, later tightened to 10.

Three shapes settled out of that period. A hard paywall blocks all content until payment. A soft paywall withholds some content while leaving the rest open, often gating premium pieces. A metered paywall, a variant🆎VariantGrowthA variant in an A/B testView reference → of the soft model, allows a fixed quota of free access before the gate closes. The trade is legible: hard paywalls maximise revenue per reader and minimise reach; metered paywalls preserve reach and discovery at the cost of leakage.

Software adopted the same vocabulary. In product-led SaaS the paywall is rarely one wall at the front door; it is many small gates placed at the moments a user reaches for a paid capability💪CapabilityStrategyAn ability that enables value deliveryView reference →. That shift, from a perimeter to placement, moved the design question💭Design QuestionExperience DesignAn open design problem to exploreView reference → from "do we charge?" to "where, in the flow of value, do we ask?" Contextual paywalls shown at the point of felt need🫀NeedUserA user need, pain, desire, or constraintView reference → convert better than blanket ones shown on arrival, because the user has already met the value being withheld.

How it works in practice

A design tool offers unlimited free editing but gates exporting to high-resolution formats. A user spends forty minutes building a poster, then clicks Export. The paywall appears here, at peak intent, and converts at 14%.

The team tests moving it forward, prompting for payment at signup before any value is felt. Conversion collapses to 2% and signups themselves fall, because the gate now reads as a toll. They revert, then test a soft variant on the export gate: a single free watermarked export, then payment. The watermarked exports circulate, pull in new signups, and overall paid conversion holds within a point of the hard version while top-of-funnel⬇️FunnelGrowthA conversion funnel tracking user progressionView reference → grows. Placement, more than the height of the wall, moved the number.

Paywall vs. its neighbours

• Trial config🆓Trial ConfigPricing & PackagingConfiguration for a free trialView reference → governs temporary full access on a clock or quota; the paywall governs the standing boundary between free and paid. They meet when a trial ends, where the paywall decides whether expiry means lockout or downgrade.
• Pricing tier🥉Pricing TierPricing & PackagingA pricing tier or planView reference → is what lies on the paid side of the wall: a named package at a price. The paywall is the gate; the tier is the room it opens into. One paywall can lead to a choice among several tiers.
• Feature⭐FeatureProduct SpecificationA product capability or featureView reference → is the unit the paywall actually gates. A well-placed paywall sits at a specific high-intent capability, so the line between free and paid is drawn feature by feature rather than as a single perimeter.

In the graph

In the Unified Product Graph, paywall🛂PaywallPricing & PackagingA paywall gating premium features sits in the pricing sub-domain of the Business, GTM and Growth region. A pricing_strategy💱Pricing StrategyPricing & PackagingAn overarching pricing strategyView reference → reaches it through pricing_strategy_gates_via_paywallPricing Strategygates viaPaywallhierarchy, and a pricing_tier🥉Pricing TierPricing & PackagingA pricing tier or planView reference → connects through pricing_tier_gated_by_paywallPricing Tiergated byPaywallcross-domain, so the gate is tied to both the governing logic and the package it protects. The defining edge is paywall_gates_featurePaywallgatesFeaturecross-domain: it records exactly which capability each wall withholds, making placement an explicit, queryable fact. That structure lets a team see, across the whole product, where every gate stands and what value sits behind it, which is the information the conversion question actually turns on.