Software Growth

Paywall

A paywall is the point in a product or site where access stops until the visitor pays, subscribes or upgrades. It can be hard, soft or metered.

A paywall is a gate that asks for payment before letting someone go further. In SaaS it usually shows up as an upgrade screen when a free user hits a limit, tries a locked feature, or reaches the end of a trial. The design question is where to put the gate so that people have seen enough value to pay, but have not already got what they came for.

Types of paywall

Zuora's glossary describes the main types (source). Translated to SaaS:

  • Hard paywall. Nothing is available without paying. It suits established brands with strong demand, and for a new product it usually appears as "start a trial" at signup. See free trial.
  • Soft paywall. Some use is free, then payment unlocks more. This is the model behind freemium.
  • Metered paywall. Users get a fixed amount before being asked to subscribe, such as five projects or 100 contacts. Zuora cites an industry average stop point of five interactions for publishers.
  • Dynamic paywall. The prompt and timing adapt to behavior, so a power user sees an upgrade offer sooner than someone who barely logs in.

Where to put the gate

  • Gate on a limit that tracks value. A cap that matches your value metric (projects, contacts, exports) moves people up as they succeed.
  • Gate after the aha moment. If users hit the wall before they see the benefit, they leave. Show the paid feature working first, as a reverse trial does.
  • Gate features for teams and scale. Permissions, SSO, audit logs, integrations and higher limits are common paid-only features because they matter to larger customers.
  • Do not gate the thing that creates sharing. If free users spreading the product is your growth channel, keep that part free.

What a good paywall screen does

  • Names the exact thing they were trying to do and why it is locked.
  • Shows the plan that unlocks it, with its price, and a link to compare plans.
  • Offers a way back that does not lose their work.
  • Never uses a surprise: if there is a limit, show a usage counter before they reach it.

Measuring it

If 800 users hit your project-limit paywall in a month and 56 upgrade, the paywall converts at 7%. Track it by trigger (limit, feature, trial end) so you know which gates earn their keep. Change one gate at a time, because overlapping changes make the result unreadable.

For a bootstrapped product

Keep the paywall simple, with one or two clear limits and a short upgrade path. A paywall that blocks the product during a user's best moment loses more goodwill than the upgrade is worth. When in doubt, gate later and watch conversion, since it is easier to tighten a limit than to loosen one that customers already rely on.

Sources

Back to the SaaS glossary