Upgrade Modal
Sell the upgrade at the exact moment someone wants it.
What it adds
A focused upsell that appears when a free user reaches for a paid capability.
What your agent is told to do
4
What your agent is told to do
4-
1
Trigger it at the point of intent — when they click the locked thing — not on a timer or on page load.
-
2
Name the specific feature they just tried to use. A generic pricing modal converts far worse.
-
3
State the price plainly and give one button to upgrade.
-
4
Make it easy to dismiss, and don't show it again immediately.
Edge cases it handles
4
Edge cases it handles
4- Never show it to a user who already has the plan.
- Do not show it repeatedly in one session — that's harassment, not marketing.
- The modal must not be the only path to pricing.
- Dismissing must return them exactly where they were.
Definition of done
7
Definition of done
7- It triggers on intent, not on a timer.
- It names the specific feature that was blocked.
- It never shows to users who already have the plan.
- Frequency is capped per session.
- Focus is trapped and restored on dismiss.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Billing Portal
Billing Portal
Let people manage their own subscription.
What it does
A billing area where users can see their plan, change payment method, get invoices, and cancel.
How it works
- 1 Use the payment provider's hosted billing portal if it has one. Do not rebuild card management — it's a PCI liability you don't need.
- 2 Show the current plan, renewal date, and payment method on your own account page.
- 3 Make cancelling possible without emailing support. Dark patterns here generate chargebacks.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/billing-portal
Booking Deposits
Booking Deposits
Take a partial payment at booking so the slot is held against a real commitment.
What it does
A deposit charged during booking, tracked against the remaining balance and the cancellation policy.
How it works
- 1 Show the deposit amount, the remaining balance, and the refund terms on the booking screen before payment, not in the confirmation afterwards.
- 2 Hold the slot while payment is in progress, and confirm the booking only once the payment provider reports settlement. Treat an unsettled payment as no booking at all.
- 3 Reuse the app's existing hosted checkout and the callback handling that already confirms payments. Do not add a second payment integration for bookings, and do not confirm on the browser redirect alone, because a user who closes the tab never returns to it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/booking-deposits
Usage Limits
Usage Limits
Cap what free accounts can do — visibly and fairly.
What it does
Per-plan usage limits, enforced server-side, with the user always able to see where they stand.
How it works
- 1 Define limits per plan in one place. Do not scatter magic numbers through the codebase.
- 2 Enforce on the server at the point of creation. A client-side check is decoration.
- 3 Show current usage BEFORE the user hits the wall — surprise limits feel like a bug.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/usage-limits
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.