Paywalls and Upgrade Prompts Inside the Product

Show the upgrade prompt at the moment the limit costs the user something real - the report they need is on the next tier, the seats ran out mid-invite - and make the prompt a fair offer: the limit stated, the tier that removes it, its price, and a clear way to continue without upgrading where a free path exists. Prompts fired on a timer, on every login, or before the user has felt any value convert resentment, not revenue. The paywall is part of the product's honesty system: users judge the whole company by how it behaves at the moment it has leverage.

The sequence that works: the user accomplishes something, reaches for the adjacent capability, and meets the prompt with the accomplishment visible behind it. The sequence that fails: the prompt arrives at login, at first click, or mid-task on unrelated work. Frequency discipline matters as much as timing: a dismissed prompt should rest - days or until the limit is hit again - because repetition reads as desperation and trains blind dismissal of every dialog the product shows, including the important ones about data and billing.

State the price in the user's own accounting: per month on annual, per seat, with the renewal terms and how to downgrade later. 'Later' matters: a user who trusts they can step down upgrades sooner. Where the tier boundary is confusing, the prompt should explain it by the user's goal ('Teams who need X usually move to Y') rather than by the full tier table. And the free path, when one exists (export instead, archive old items), should be named in the prompt itself; hiding it wins one upgrade and loses the account's trust account-wide.

When pricing or limits change for existing users, the in-product message is a trust event. Give notice measured in billing cycles, state exactly what changes for this account, and grandfather where the economics allow - or say plainly why not. Users forgive price rises communicated like adults; they do not forgive discovering a shrunken limit at the moment of need. Log plan-change communications like pricing page changes, with dates: the audit trail is what lets support answer 'when did this change' with a sentence instead of an apology.

Report per prompt: shown, dismissed, upgraded, and the account's state 90 days later. The shadow metrics are the point: churn among frequently prompted accounts, support sentiment, and prompt-blindness (dismissal speed trending to instant). A prompt programme that lifts upgrades while lifting prompted-account churn is borrowing revenue from next quarter. Review prompts quarterly with the same severity as pricing pages, retiring the ones whose only evidence is that they are old.

Never block a user's access to their own data behind an upgrade prompt. Never pre-select paid options, hide the continue-free route, or phrase the dismissal as a confession ('No, I hate saving time'). These are dark patterns; the audits bench covers why they cost more than they pay, and in-product they cost most of all, because the user is a customer with a billing relationship and a review account. The prompt's restraint is precisely what its conversions are made of.

Prompt wording deserves the copy bench's full discipline. Weak: 'You have reached your limit. Upgrade now to continue enjoying premium features.' It names no limit, no price, no consequence, and 'enjoying' does the reader's feeling for them. Working: 'This workspace has 5 of 5 projects on the Starter plan. Team adds unlimited projects at 24 dollars per editor a month, billed annually, and you can step back down any time. Your existing projects stay exactly as they are.' Limit, arithmetic, reversibility, safety - in three sentences. Write prompts at that standard, review them whenever prices change, and read them aloud as the user who just hit the wall: the prompt is the product speaking at its most commercial moment, and it should sound like the company at its best.