Separate sites to manage subscriptions or a central portal?
Let's say I have two SaaS products for the same industry. Do I launch them separately and handle all subscriptions independently? Or do I have a central subscription "portal" where accounts/subscriptions are managed for either/both products?
Would there be a benefit to having some sort of shared branding?
Are people likely to purchase both products or use both at the same time? (ie. are they complimentary to each other)
Are you likely to create more SaaS products in the same industry going forwards?
If that is the case, it would make sense to have one central place to view, purchase and manage an account
Yeah, they would be within the same "ecosystem" and be complimentary to each other.
What are your thoughts about a similar branding between the apps?
How come you want to combine them? It is the cost-saving? Duplication of code?
I try and keep everything separate if it's for different products for a few reasons:
You can always try and share code etc between projects etc. It does mean if you find a bug you need to fix it in 2 places but I find that's generally a lot less risk. If you are going to have a combined portal, I would advise you to make sure it has thorough tests for each product so you can be sure any changes won't break anything.
If you are thinking about combining part of the products, could it be possible it might be an idea to combine them into one product?
All great questions. I don't think I asked the question clear enough, so I'll try to rephrase it.
Product A and B are separate apps (separate domains, server, etc), but they are part of the same industry (education). Typically you would manage your subscription inside of each product.
What I'm asking is, what if there was a "main" site, like part of a marketing site that contains information about both products, from which you manage the subscriptions rather than managing the subscriptions independently. Perhaps I'm over thinking it.