All testsAli Demirbaş - Lab

SaaS & B2B

Paywall Timing: Show Early or at the Limit A/B Test

An early upgrade prompt presents the offer before a user reaches a limit; a prompt at the actual limit is more directly relevant but may interrupt active work. Compare timing with the same offer and usage entitlement, using paid upgrades among all eligible assigned users as the primary outcome.

A/B test scenario. This page is a test plan, not the result of a real experiment.

  • SaaS & B2B
  • Upgrade rate

Option A vs Option B

The moment is the variable, not what appears.

Changed
Timing
Page
SaaS & B2B
Difference
changed

Hypothesis

An early prompt may introduce the offer while users keep working, while a prompt at the limit arrives when the need is clearest but may interrupt active work. If users make up their minds ahead of time, the early prompt could bring the higher upgrade rate; if they only feel the need at the limit, the limit prompt could.

Test plan

When to run this test

Sessions that end right at the usage limit, support requests that follow the limit message, or users who near the limit and never return all suggest free users walk away instead of upgrading. If the early prompt is the better option, users upgrade before the limit and activation does not drop; if the limit prompt wins, most early prompts simply get dismissed. If users leave because a message shows remaining usage incorrectly, fix that first, and settle any planned price change before you start, since timing can only be read with the price fixed.

How to measure success

Upgrade rate

Measure paid upgrades per eligible assigned user over the same follow-up period, including users who never see the prompt.

Also track

  • Activation rateCompare core product use using the same start event and follow-up period.
  • Prompt dismissal rateAmong users shown the modal, report dismissals as a diagnostic; keep the primary analysis on all assigned users.
  • Seven-day retentionUse the same definition of active use on day seven after assignment.
  • Support requestsTrack questions about the limit or upgrade prompt using the same visitor denominator.

How to set it up

  • TimingCompare one predefined early trigger with the actual usage-limit trigger.
  • EntitlementsKeep the free usage limit and feature access the same.
  • ContextKeep usage information and offer wording accurate and unchanged.
  • DismissalKeep the ability to dismiss and continue within existing entitlements consistent.
  • EligibilityDefine which users are eligible to upgrade; report trial and paid cohorts separately if relevant.

What to watch when reading the result

  1. 1Decide on paid upgrades per eligible assigned user; the prompt dismissal rate is measured only among users who saw the prompt, so treat it as a diagnostic. If upgrades rise while activation, seven-day retention or support requests cross the limits you set, do not roll it out.
  2. 2The early prompt should stay a prompt that users can close and that lets them keep working within their current entitlements. If it stops work before the limit or reopens again and again, you are measuring pressure, not timing.
  3. 3Only this pair of triggers and this offer are covered by the result. If relevant, review trial and paid cohorts separately; a different early trigger needs its own comparison.
  4. 4More users may see the prompt in the early arm, but assignment should stay balanced, so when the difference is unclear, first check that arm sizes match the planned split (sample ratio mismatch). Because upgrades are a rare event, use the sample size calculator to find how many eligible users each arm needs at the current upgrade rate and the lift you care about. Keep the test running until each arm reaches that number and the follow-up window closes.

Frequently Asked Questions

Does the early-warning group lose any usage rights?

No. Keep free limits, feature access, usage information and offer copy identical. Only warning timing changes. Do not turn the early warning into a premature paywall.

Why is modal dismissal not the decision metric?

Only exposed users can dismiss it, and exposure populations can differ. Report dismissal diagnostically. Use paid upgrades per eligible assigned user as the primary outcome.

How can I tell whether the warning harms product usage?

Track activation, retention, core usage and support contacts over a common window. Do not roll out an upgrade lift that exceeds predefined usage-harm limits.

Can I change the price in the same test?

No. Keep price fixed to interpret timing. Allow dismissal, avoid repeated reopening and show remaining usage accurately. Review relevant trial and paid cohorts separately.