Disclosure: I work on Crownerr, and this is the Crownerr blog, so I am not a neutral referee. I will still tell you where other tools beat us. If you have an engineering team and a complex product, a custom build gives you more control than any hosted platform, ours included. Most creators do not have that team, and most do not need it. The phrase subscription website hides a lot of plumbing. The homepage was never the hard part. The hard part is everything that happens after someone types in their card details and expects to still have access next month.
What a subscription website actually needs
People picture a subscription site as a paywall bolted onto a normal website. It is closer to a small bank that also happens to host content. Four systems have to work, and three of them are invisible until they break.
- Recurring billing is charging the same card on the same day every month, then doing it again next month without you lifting a finger. That sounds simple until a member upgrades mid-cycle and you owe them a prorated credit, or downgrades and you have to decide whether the change lands now or at renewal. Add cancellations, reactivations, annual plans, tax in different regions, and card-network rules about how you store and reuse a card, and you are looking at a genuine billing engine. Get the proration maths wrong and you either overcharge people, which triggers chargebacks, or undercharge them, which quietly bleeds margin.
- Gated access means a paying member sees the content and a lapsed member does not. It has to flip the instant a payment clears and the instant a subscription ends. A few minutes of lag and people share logins or screen-record the lot. Get it wrong in the other direction, locking out someone who paid, and you get an angry support ticket and a refund request the same hour. The access check has to be the source of truth, not a cached flag that drifts out of sync with billing.
- Dunning is what you do when a card fails, and cards fail constantly. Expired cards, hit limits, fraud blocks, banks declining a recurring charge they do not recognise. It runs at roughly 5 to 10 percent of monthly charges, every month, forever. With no automatic retries and no reminder emails, every one of those is a silent cancellation you never see coming. Good dunning retries on a schedule that respects card-network rules, emails the member with a one-click way to fix their card, and only cancels access once it has genuinely given up. This single system is often the difference between a subscription business that grows and one that leaks.
- A member portal lets members update a card, switch plan, download an invoice and cancel without emailing you. Skip it and you become a human billing desk, answering the same five requests by hand. Worse, a member who cannot find the cancel button disputes the charge with their bank instead, and a chargeback costs you the revenue plus a fee plus a ding on your processor account. A self-serve portal is cheaper for you and less infuriating for them.
The routes you can take
There are three honest ways to get all four of those working. None is correct for everyone.
- Custom-coded. You wire up Stripe Billing, the access logic, the portal and the dunning flows yourself. You get total control: any pricing model, any access rule, any integration you can imagine. The cost is that this is a real engineering project, not a weekend. Webhooks have to be handled idempotently, failed payments reconciled, edge cases tested, and someone has to be on call when a renewal misfires at 2am. It earns its keep when subscriptions are your core product and you have a team to keep it running. For most people it is a lot of plumbing to rebuild something that already exists.
- Site-builder plugins. A membership add-on on top of a general website builder. Cheap to start, familiar if you already run a site there. The trouble shows up later. You are stitching a billing plugin, a content gate and an email tool into something that was never designed as one system, and when a renewal breaks you are the integrator who has to work out which of the three is at fault. Fine for a simple, low-volume setup. It gets fragile as you add tiers and your member count climbs.
- Hosted no-code platforms. Billing, gating, dunning and the portal come pre-wired and maintained for you. You give up some of the deepest customisation, and you are tied to whatever the platform supports. In exchange you never touch payment infrastructure, and the failure modes above are someone else's job to handle. For most creators that trade is the right one, because the parts you would be giving up are parts you were never going to build well by hand anyway.
Step by step on a hosted Space
Here is the actual path on a hosted Space, start to finish. It is short on purpose, because the platform is doing the heavy lifting underneath each step.
- Create your Space. You get a hosted site with pages, content and members built in, so there is nothing to provision and no plugins to reconcile.
- Connect payments through Stripe. Payouts arrive via Stripe Connect, straight to your own account. Stripe UK charges 1.5% + 20p per transaction, which sits separately from any platform fee, so you always know the processing cost per charge.
- Define your tiers. Resist the urge to launch with five. Start with a single paid tier, learn what people actually pay for, and add more once you have evidence. See how to set up memberships on Crownerr.
- Gate your content. Mark what is members-only. Access flips automatically when someone subscribes and locks when they lapse, so you are not maintaining a manual list of who is allowed in.
- Confirm dunning is switched on. This is the highest-leverage setting on the whole site and the one people forget. Left off, you lose that 5 to 10 percent of monthly charges quietly. Left on, the platform retries failed cards and emails members to update them before you ever notice.
- Check the member portal. Test it as a member, not as the owner, because the owner view hides half the journey. Update a card, switch plan, find the cancel button. If you struggle, your members will too.
- Publish, then run it end to end with a real card. Subscribe, confirm access opens, then cancel and confirm access locks. Do not trust that it works because the settings look right; trust it because you watched a charge land and an account close.
For the site structure itself, how to create a membership website pairs well with this.
Owning your audience
Decide early where your member relationship lives. If your subscribers only exist inside someone else's app, you are renting access to your own audience, and the rules can change overnight: a fee rise, a policy shift, an algorithm that buries you. Having members and their billing on a site you control means the relationship is yours to keep. More in how to own your audience.
Where Crownerr fits
If you want recurring billing, gated access, dunning and a member portal out of the box with no code, a Crownerr Space gives you all four. Free is £0/month with a 6% fee, Creator is £79/month with 3%, and Studio is £149/month with 0%. Stripe's 1.5% + 20p applies on top of whichever you pick. Start free, prove the model works, and move up once the lower fee saves you more than the plan costs. There is a clean break-even point where the maths flips, and you can wait for it. See the pricing page.