Skip to content

Growth feature pattern

In-product upgrade prompt feature pattern

In-product upgrade prompts are the contextual nudges that appear inside the product when a user could benefit from upgrading. Done well they convert at high rates because intent is implicit; done badly they read as constant nagging and damage retention.

Verified · editorial policy

How the pattern works

Triggered when a user hits a paid-tier capability or a usage signal that correlates with upgrade benefit. Surface as inline banner, modal, tooltip, or feature spotlight. Always include a clear upgrade CTA and a dismiss option.

Best for

SaaS with clear free-to-paid feature differentiation. Products where users naturally hit upgrade-trigger moments during normal use. Mature products with established usage patterns.

Worst for

Products without clear upgrade triggers (every feature available on free). Products where the prompts would fire constantly (every page). Pre-PMF products where users have not yet learned the core value.

Target growth metric

Prompt-to-upgrade rate per trigger type. 0.5-3% is realistic; higher (5%+) suggests strong feature-fit; lower (<0.5%) suggests the trigger is firing in the wrong moments.

Implementation considerations

  1. Fire on real intent signals, not random page views. 'User tried to use feature X' beats 'user has been logged in 7 days'.
  2. One prompt per session at most. Multiple prompts in the same session train users to dismiss without reading.
  3. Dismiss should be permanent (or 30-day cooldown) per prompt type. Re-firing dismissed prompts on next session is the most-hated upgrade UX.
  4. Surface the specific feature the user wanted, not generic 'upgrade now'. 'Unlock CSV export' beats 'Upgrade to Pro'.
  5. Track prompt-shown-but-not-clicked rate. If prompts are shown 100x but clicked 0-1x, the prompt content or timing is wrong.

Common misuses

  • Prompts on every page. The constant-nag pattern damages retention more than it improves conversion.
  • Generic 'Upgrade to Pro' CTAs without naming the specific value. Lower conversion than feature-specific CTAs.
  • Modal prompts that block product use. The forced-modal pattern frustrates users mid-task.
  • Prompts that bypass user preference. If the user dismissed a prompt 3 times, stop showing it.

Realistic outcomes

Done well: contributes 20-40% of upgrades for products with paid-feature mix. Done badly: contributes <5% of upgrades and increases churn 10-20% via accumulated friction.

Frequently asked

Should free-tier users see ANY upgrade prompts?
Yes, but timed to feature-attempt moments, not session-time. Free users hitting a Pro feature should see a clear unlock prompt; free users browsing the dashboard should not see generic upgrade ads.

Test the pattern's lift on your product

Growth feature patterns produce different lift on different products. The experiment recipes show you how to test the actual impact before committing to long-term implementation.

🚀 Explore Our Network

Full disclosure: UnlockSaaS is one of ten small products built and run by one independent operator. These are the other nine.

60 days
To First Paying Customer
7 steps
Proven Playbook
100%
Money-Back Guarantee
$49
Founding Price /mo

You shipped. Nobody paid. The playbook breaks the pattern or the code refunds you automatically.

Get Free Diagnosis

Refund runs from your dashboard, not a support ticket — the server re-checks eligibility and issues it through Stripe automatically.