1. Create the recurring structure first
Use /dashboard/series/new to define the recurring identity, description, cadence, and base price. This is where Cammonly creates the Stripe product and recurring price backing the series.
Think of the series as the subscription shell. Individual event occurrences, tiers, and later supporter access all inherit from that foundation.
2. Launch club-style memberships carefully
Public club pages at /clubs/[slug] expose membership plans, progress toward minimum launch size, and upcoming member-only events. A club can be active, paused, or still launching.
The membership threshold matters: people can join before the club is fully active, but access and recurring behavior may stay pending until enough members have joined.
3. Explain subscription states to supporters
Supporters manage their recurring memberships in /dashboard/subscriptions. They may see active, trialing, inactive, or incomplete states depending on threshold progress or payment authentication.
Use the success and follow-up messaging to explain whether the subscription is already live or still waiting for the minimum-member threshold. That avoids false expectations about immediate access.
Checklist
- - Cadence and price confirmed before creating tiers
- - Minimum members set to a number you can realistically reach
- - Supporter messaging explains pending vs. active membership states