screenroveUpgrade modal examples: name the blocked action, not the plan
Upgrade modal examples from 64 real feature gates: only 20 name what the user tried to do. How Postman, VEED, Typebot and Jitter write the line that matters.
We read the headline of every feature gate and usage limit in our paywall library that appears at the moment someone tries to do something: 64 screens from 34 products. Only 20 of them (31%) say what the user just tried to do or which limit they just hit. The rest name a feature, run a tagline, say "Upgrade" in some form, or have no headline at all. This piece collects the upgrade modal examples that get that line right, shows where the specific wording gets lost one click later, and argues that the cheapest fix is often rewriting one line.
The count: 20 of 64 gates name the action
We took every screen typed as a feature gate or usage limit (74 in total), and kept the 64 that appear on a locked feature or at a limit. The 10 we dropped are credit meters and plan pages opened from settings, not reactions to an action. Each of the 64 headlines went into one bucket:
- Names the action or limit: the headline has the verb the user attempted or the quota they hit ("to invite people", "Need more lists?", "You've run out of credits").
- Names the feature: a feature noun, but not the act ("Filters", "Brand kit", "Private collections are a premium feature").
- Pitch: a benefit line that names neither ("Good data deserves a way out").
- Generic: would read the same on any gate ("Premium feature", "Upgrade to Splitwise Pro", "This feature is available on paid plans").
- No headline: the lock is only a badge, or a button swapped on the real UI.
| Headline type | Screens | Share | Examples |
|---|---|---|---|
| Names the action or limit | 20 | 31% | Postman, Eraser, Superlist, Runway, Ideogram |
| Names the feature | 19 | 30% | TickTick, Dub, StackBlitz, Netlify audit log |
| Pitch | 6 | 9% | SurveyMonkey, Grammarly, Glide |
| Generic | 7 | 11% | Adobe Express, Netlify, Splitwise |
| No headline | 12 | 19% | Kittl, Leonardo, Relume, Runway |
The split by type is the real finding. All 15 usage-limit screens name the limit, because the product already knows which counter ran out. Of the 49 feature gates, only 5 name the action. Feature gates tend to be written once per feature, like a small landing page, rather than once per moment. One caveat: Mermaid Chart (5 screens) and Runway (4) account for 9 of the 15 limit screens, so the limit side reflects 8 products, not 15.
Upgrade modal examples: one modal, one rewritten line
The products that do this well don't build a modal per feature. They reuse one plan modal and pass the trigger into the headline.
Postman is the clearest case. Clicking Invite opens the standard plan modal, headlined "Upgrade to the Team plan to invite people", with Team already selected and the button reading "Continue with Team Plan". The headline, the preselected plan and the CTA all point at the one thing you tried to do.
VEED shows the reuse plainly: the same three-tier picker (Creator $12, Pro $22 marked Recommended, Studio $39) appears for brand kits and for privacy settings, and only the headline changes: "Upgrade To Build Your Brand Kit" on one, "Unlock Advanced Privacy Settings" on the other.
Typebot goes a step further. "You need to upgrade your plan in order to create folders" is the headline, it repeats in an info strip, and the Starter card lists "Create folders" among its features. The reader can check the claim without leaving the modal.
Others follow the same idea in different ways:
- Jitter's export menu ends with "Free exports have a Jitter watermark. Remove it with Pro", and the modal it opens is headlined "Go watermark-free on exports", with a live order line (£15 × 1 editor × 12 months, £180 against a struck £228).
- Ideogram answers an out-of-credits moment with "Upgrade to create" and highlights "2,400 credits/month" in the benefit list.
- Superlist asks "Need more lists?" and states the number: "You've hit your limit with 5 free lists."
- Canny titles its inline Pro card "Limit changelog access to specific users", the exact option you just picked.
- Eraser replaces search results with "Upgrade to search inside diagrams, notes, and canvas elements across all your files."
Two products put the action in the subtitle instead, which our headline-only rule doesn't count. Adobe Express keeps "Go premium with a free trial" as the headline, then opens with "Upgrade to Acrobat Express to resize your project for any size or platform", and even swaps in a customer quote about resizing. Kapwing uses "Upgrade your workspace" with the subtitle "to select and change video privacy settings".
Where the specific wording gets lost
A gate can name the action and still hand off to a modal that doesn't. Across the whole wall, 22 plan pickers, upgrade modals and trial offers opened from an action (see them). 12 had a generic headline, 5 named the action and 3 named the feature.
Any.do is the clearest handoff. The tag picker says "Upgrade to Any.do Premium for more tags & colors", which is specific. The modal it opens says "Level up. Go Premium.", and colour tags are one tile out of six.
Runway does the same at the credit limit. The home prompt box says "You've run out of credits. Upgrade to keep creating with Runway." The modal behind the Upgrade button is headlined "Upgrade to Pro", and credits appear only in the last of seven bullets. Leonardo opens "UNLOCK THE POWER OF LEONARDO.AI" from Make All Private. The answer is in the table: the Free column reads "All images and videos are public", and Essential lists "Private creations". Users have to find that themselves.
Splitwise has a cheaper version of the fix. Its headline stays "Upgrade to Splitwise Pro", but when charts trigger the sheet the list moves "Charts and graphs" to the top in bold. Changing the list order costs nothing, and the reader sees the trigger first.
Put the lock on the input
Only 16 of the 64 gates are modals. 21 are inline, 9 are banners, 8 popovers, 5 side panels and 5 full pages. Most gates live in the UI, and the strongest put the lock where you act.
In Runway's video tool, the Generate button itself becomes a blue Upgrade, in the same spot. Kittl leaves SVG and PDF in the export format dropdown, greyed with a gold crown. Leonardo keeps Make All Private, Download All and Delete All in the normal menu with a small gem icon. Netlify replaces locked settings with a card: the feature title in grey ("Shared environment variables"), a padlock tab in the corner and an "Upgrade to unlock" button (see it).
These badge-only locks are the 12 "no headline" screens in our count. They work for scanning. The headline matters at the next step, when someone clicks the crown.
What to steal
- Keep one modal and pass the trigger in. Postman, VEED and Typebot show the headline is the only part that has to change. "Upgrade to [verb] [object]" is enough.
- Make the plan list prove the headline. Typebot ticks "Create folders" under Starter. VEED's privacy version names privacy in the headline, but the three tier lists never mention it, and only the Enterprise row lists "Privacy controls".
- Preselect the plan that unlocks it. Postman opens on Team because inviting people needs Team.
- Carry the wording through the click. If the inline gate names tags or credits, the modal it opens should too. Any.do and Runway lose it there.
- Put the number in limit copy. "5 free lists" tells people what they used and what they're paying to remove.
- Lock on the control, not on a separate page. Crowns on formats, a gem on a menu item, Upgrade in place of Generate.
How we counted
All screens were captured in desktop browsers with research accounts between September and October 2026. A vision model recorded each screen's type, trigger moment, layout and headline, and you can check them on each screen's page. We sorted headlines by hand using the rules above, and counted the headline field only, so subtitles like Adobe Express's and Kapwing's don't count. Some products have several screens in the set. We record what we saw, not A/B results, so none of this says which wording converts better.
To use these as references while you build, connect the Screenrove MCP server and ask your agent for feature gates that name the blocked action.