Pricing pages get designed. What happens after someone clicks Upgrade mostly doesn't: the proration maths, the downgrade that should wait, the cancel screen that's either a guilt trip or a single red button.
Monokit 1.7 builds that part. The block above is Change plan. Pick Business and it shows the credit for the days already paid, what's due today and what the next invoice will be. Pick Starter and it waits for the period to end, and warns you about the seats you'd lose.
One flow, start to finish
In the demo app, the workspace starts on a Pro trial, with a banner counting the days. Make a fourth project and the upgrade dialog tells you why you can't, with the plans that lift the limit. Pay, and Billing shows the new plan and the first invoice.
Then change your mind. Upgrades start now and charge only for the days left. Anything cheaper starts when the period ends, so nobody pays twice.
Cancelling, honestly
The cancel flow asks why first, and answers the reason. "It costs too much" gets half price for three months. "We don't use it enough" gets the free plan. Then it says exactly what cancelling does: when access ends, what becomes read-only and how long the data stays.
Four blocks, one store
The flow is four new blocks (trial banner, upgrade dialog, change plan and cancel subscription) plus the usage meter and payment methods that were already there. Each takes its data as props, and the demo keeps that data in the browser. Swap the store for your billing provider and the screens stay as they are. That makes 46 blocks.
The demo app has real docs now too: how to install the kit, theme it and take updates.
If you bought it
Run git pull. CHANGELOG.md lists every change. Next up are team invites and data import. If the kit is missing a screen your product needs, ask for it.