Plan Comparison
Show what each plan includes and what would actually change for this account.
What it adds
A side-by-side plan table driven by real entitlements, marking the current plan and the transitions this account can make.
What your agent is told to do
5
What your agent is told to do
5-
1
Build every comparison row from the live entitlement definitions. Hard-coded marketing copy drifts from what the app actually enforces, and the table becomes a lie.
-
2
Mark the current plan unmistakably, and render only the transitions this account is eligible for. A disabled button with no explanation is worse than no button.
-
3
Show limits as numbers with the account's current usage against them, so a downgrade that would break something is visible before it is chosen.
-
4
Cover interval (monthly versus annual), add-ons, and whether displayed prices include tax. A price that changes at checkout destroys trust.
-
5
Do NOT build the contextual single-feature upsell — that is owned by Upgrade Modal. Subscription state and payment methods are owned by Billing Portal, and the money delta of a change is owned by Proration Preview. Link to them; do not duplicate them.
Edge cases it handles
7
Edge cases it handles
7- A grandfathered plan may not appear in the current lineup at all. Show it as the current plan anyway, with what would be lost by moving off it.
- Custom or negotiated plans must not be flattened into the nearest public tier. Show the real entitlements or defer to a contact route.
- A downgrade that would exceed the target plan's limits must warn with specifics — which items, how many over — before the user commits.
- Currency and tax vary by region. Show the account's own currency rather than a converted approximation.
- Annual and monthly rows are not comparable at a glance. Show the interval explicitly rather than relying on a toggle the user may not notice.
- A plan the account cannot buy — region-restricted, sales-only, deprecated — must be hidden or labelled, not shown as an option that fails at checkout.
- Rows must be honest about degree. 'Included' versus 'included up to 5' versus 'paid add-on' are three different answers and a tick mark gives all three the same one.
Definition of done
9
Definition of done
9- Every row is generated from live entitlement data, not static copy.
- The current plan is clearly marked and only eligible transitions are offered.
- Limits show the account's current usage alongside each plan's allowance.
- Billing interval, add-ons, currency, and tax treatment are stated on the table.
- Grandfathered and custom plans render correctly rather than being mapped to a public tier.
- A downgrade that would breach a limit warns with specifics before confirmation.
- The table links to the upgrade, billing, and proration surfaces instead of reimplementing them.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
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
Upgrade Modal
Upgrade Modal
Sell the upgrade at the exact moment someone wants it.
What it does
A focused upsell that appears when a free user reaches for a paid capability.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/upgrade-modal
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.