How do I implement a three-plan SaaS flow with Memberstack spanning a Webflow signup site and custom-coded app?
Heeeey, quick question on Memberstack best practices.
I’m trying to set up a standard SaaS flow with 3 paid plans:
- User selects a plan on the pricing page
- They’re sent to a signup page and create an account
- After signup, they’re taken to Stripe checkout for the selected plan
- Once payment is complete, they’re redirected to a separate .app where they log in using the account they just created
Is this flow fully supported in Memberstack, and do you guys have a recommended setup or video that walks through this exact sequence?
I know this is a common SaaS pattern, I just want to make sure I’m implementing it the intended way rather than hacking something together.
Comments
3 comments
Hey Markese Straughter,
1-3 points you specified is a standard flow and you should be able to set it up as well.
If you want to install same Memberstack account on multiple sites (so that the member base is the same for your signup site and .app site), you can do so and here's a short guide on things you might want to consider.
Currently the in-built redirects feature does not allow us to redirect to another site / domain by default but if you want to do it, you can probably set a signup redirect to a default page where you have a simple script to redirect the user to the .app site based on the purchase made by the user, in case you want to redirect them to different pages based on the plan purchased. If all plan signups should lead to the same .app site you can just have the script on a blank page (which you set up as signup redirect in the memberstack dashboard) and this script could redirect the users to the .app site.
In case you have the same root domains (which I believe you don't), for example website.com is where your users signup and app.website.com is where you want to send them to after they purchase, then you can also enable cross-domain login feature so that they don't have to login again but if that's not the case for you, then you can go ahead with the flow you have planned out with some customization as shared above and it should work for you.
Hope this gives you some idea.
A J This is exactly what I needed! Appreciate it 🫡
I’m looking to embed the login component into my custom-coded .app application. Do you offer an embeddable version of this component, or is it only available as a clonable component for Webflow? If it’s Webflow-only, how are others typically handling the transition from a Webflow .com site to a custom-coded .app experience?
Markese Straughter, I believe you can use the Memberstack's DOM package and setup any authentication flow that you offer email-password, passwordless, social auth etc.
Here's the developer docs that you can explore for this as well.
Hope this helps.
Please sign in to leave a comment.