The company I work for has multiple SaaS products. What’s the best ways and practices to manage multiple products through Fibery?
Hello, @Akshay155
Great that you asked! To be honest, there’s no one and only correct way of doing that, but I’ll try to give you some suggestions for setting up the structure of your Workspace.
So, let’s start from the basics: in Fibery, data is stored in the Databases (I believe you already know it) and can be visualized with multiple different Views depending on what you need to see. Databases are connected with different Relations to ensure that data is connected inside and creates a logical structure. ‘Slicing’ your processes (=all your data) is the main question here and the way it’s structured can help you decide what Databases to create. On a higher level, databases are organized into Spaces. Each Space is a certain process (e.g. Product Development, Marketing, Software Development, etc.).
From what you said, there are different Products in your company that might share or not share some common structure. What I mean by that:
a) they share a common structure = they consist of similar parts, e.g. all your products have their Product Development, Marketing, Software Development, etc. processes.
b) they don’t share a common structure = you’ll have different processes going on for each product that are unique and don’t repeat from product to product.
Case ‘A’
It will be a bit easier because all your processes will revolve around a product in its general sense. So you can create as many processes as you have (BTW, you can go to the Template Gallery and install the ready templates and modify them according to your needs to save some of your time without having to create everything from scratch) and connect them with each other. Let me share an example:
In this simple example, you can see that we have a Product Database that will have all products inside. These products will have their own features, insights, tasks, etc. All of them will share common Databases, but each entity will be related to the necessary product, like that:
But note that it’s just a Database that stores all your data. Not to mix all products together, you can create a View that has only features and insights that belong to SaaS Platform 1:
Case ‘B’
This one will require a separate ecosystem for every product. Depending on the differences that lay in the structure of the products, you might need to create completely independent Spaces that don’t interact with each other. Here I have a very rough example of two structures that live completely autonomously in different Spaces:
So the main question you need to answer is whether your products have the same backbone. If yes — use A approach, if no — use B. If you have any questions on how to implement this, feel free to ask, I’ll be happy to help 
4 Likes