Plans defined in code become a change request every time you adjust pricing. Held as data, a plan change is an edit, and the trial to paid path runs itself.
What's Included
- Plans as editable records with limits and price on each.
- Trials with a real end date and a sequence that runs before it.
- Upgrade and downgrade handled including what happens to excess data.
- An assistant that spots the trials worth a personal message.
How To Use
- Keep plans as data. Every pricing change otherwise becomes a rebuild.
- Decide what happens on downgrade before you launch, not during.
- Contact trials that are engaged but silent. That is where conversion is.
- Never delete data on downgrade. Restrict access to it instead.
Collect the money with subscription billing, and enforce the limits with usage metering.