The exact point where free access ends and paid access begins, its placement and firmness directly shape conversion.
A paywall is the boundary that withholds part of a product until payment. It is the precise point where free access ends and revenue begins, and where it sits, how firmly it holds, and what it lets through decide whether visitors convert or bounce.
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 variantVariantGrowthA 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 capabilityCapabilityStrategyAn ability that enables value deliveryView reference →. That shift, from a perimeter to placement, moved the design questionDesign 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 needNeedUserA 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.
Ramanujam and Tacke argue that willingness to pay must drive product design rather than follow it — that featuresFeatureProduct SpecificationA product capability or featureView reference → should be packaged around what each customer segment is actually prepared to pay for, not decided first and priced later. By that logic, a paywall placed at a feature a specific segment values highly is not a pricing decisionDecisionStrategyA recorded decision with context, rationale, and consequencesView reference → bolted onto a finished product; it is the product configuration itself, and getting it wrong in the other direction — loading too many features into a single undifferentiated gate — produces what they call a "feature shock" that dilutes the value signal for every segment.
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-funnelFunnelGrowthA conversion funnel tracking user progressionView reference → grows. Placement, more than the height of the wall, moved the number.
In the Unified Product Graph, paywallpricing_strategypricing_strategy_gates_via_paywallpricing_tierpricing_tier_gated_by_paywallpaywall_gates_feature
Worked example: Trellis
Governance, SSO, and audit sit behind the Business tier paywall, which is precisely the gate Marcus and Sam care about most when a tool moves beyond a single director into a team-wide deploymentDeploymentEngineeringA deployment eventView reference →. The paywall is not arbitrary friction: it maps directly to the needsNeedUserA user need, pain, desire, or constraintView reference → captured in their customer relationshipCustomer RelationshipBusiness ModelA type of customer relationshipView reference →, controlled visibility over what the agent touches and the ability to enforce it.
Type-specific fields on BaseNode
paywall_typeenumHow restrictive the paywall is
triggerstringUser action or threshold that triggers the paywall
conversion_ratenumberPercentage of users who convert at this paywall
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
3 edge types connected to this entity.
pricing_strategy_gates_via_paywallpricing_tier_gated_by_paywallpaywall_gates_feature