Build a SaaS with recurring subscriptions
Connect signup, plan selection, subscription state, and customer self-service while adding the core feature your SaaS sells.
On this page
Use a subscription when customers pay for continued access to a service. The starter supplies the account and billing journey; your product supplies the recurring value.
How it works
Name the outcome
Describe the task your customer repeats and what each plan includes. Replace the starter's sample offers with your own.
Connect billing and access
Configure Stripe, then check membership and resource ownership in the product operations that require paid access.
Test the full lifecycle
Test successful and failed payments, plan changes, cancellation, and reactivation before offering the service to customers.
Example: a paid product feature
A customer signs in, selects a plan, and gains access to a feature you implement. They later change plans or cancel from billing. This is a proposed product flow, not an additional feature already shipped in the template.
Keep purchasing and daily work connected
Public feature and pricing pages explain the offer. Your product interface completes the task. A visible billing entry lets existing customers manage their plan without going through the public sales journey again.
Limitations
- The template does not decide your pricing, included seats, usage limits, or feature access policy.
- Payment configuration and your core product must be ready before this becomes a service you can sell.
Questions
Can a subscription also use credits?
Both capabilities are available. You must define whether a plan grants credits, how often they are granted, and what happens when a plan changes; do not imply such rules until you implement them.
Is the example billing page already a complete product?
It is a working billing foundation. Customers still need a useful service, clear entitlements, support, and the policies you will operate.