Trial Extension

Let an admin give an account more evaluation time, on the record.

moderate Monetization

What it adds

An administrative action that moves a trial's end date, with limits, a reason, and reconciliation against the billing provider.

What your agent is told to do

1
Restrict the action to a specific permission, not merely to anyone with admin access. Extending trials is giving away revenue.
2
Require a reason and a fixed duration on every grant. Free-form date entry with no justification produces trials that never end.
3
Enforce a per-account limit on the number and total length of extensions, and refuse a second extension while one is still running.
4
Write an audit record for every grant and every refusal: who, when, how long, why, and the resulting end date.
5
Push the new end date to the billing provider in the same operation. Do NOT build the trial state machine, reminders, or expiry behaviour here — those are owned by Free Trial Lifecycle; this only moves the date it works from.

Edge cases it handles

Extensions must not stack into an indefinite trial. Cap the cumulative total, not just each grant.
If the billing provider rejects the new date, the app must not show the account as extended. Roll back and tell the admin what failed.
A user who converts to paid during an extension must be charged from the conversion, with the remaining extension days discarded rather than credited.
Extending an already-expired trial has to explicitly restore entitlements, not just set a future date and hope the next job notices.
The user needs to be told their trial was extended, or they will still act on the old expiry warning they already received.
Two admins extending at once must not both apply. Serialise the write and make the second attempt fail visibly.
An extension granted on a cancelled trial should be refused, not silently create an active trial the user did not ask for.

Definition of done

Only holders of a specific permission can grant an extension.
Every grant requires a duration and a reason, and both are stored.
Per-account count and cumulative-length limits are enforced, and overlapping extensions are refused.
An audit record names who granted it, when, why, and the new end date.
The billing provider's trial end date matches the app's, or the grant fails and rolls back.
The affected user is notified of the new end date.
Conversion or cancellation during an extension is handled without leftover trial days.
The feature matches the existing design system.
No existing functionality is broken.

Related features

Usage Limits

Billing Portal

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.