I work for an agency that helps clients implement HubSpot instances. Generally an implementation has all of the following:
- Meetings and transcripts
- Tasks
- Sales and process flow charts (whiteboard)
- SOP’s
We also created an integration (as a test) that queries the client’s hubspot instance and pulls in their Objects, Workflows, and Properties as actual entities in Fibery. This way we can @ mention these properties when discussing or documenting features.
My question is, since we have many clients, how are we to structure fibery in a way to handle all of them? Right now I’m leaning towards a full fibery instance for each client for the following reasons:
- The Hubspot integration really only works at the top level and it would be hard to scope it to client. ie if I @ mention the
statusproperty on a Deal, I’ll see dozens since all clients have astatusproperty - It seems like it would be impossible to scope Fibery AI to a specific client and their data if we kept everything in one instance. Ideally we could store all our transcripts, documentation, and tasks, the ask the AI question like “Who are we supposed to assign deals to when they are created?” based on past conversations
- When the project is finished, we’d want the client to have persistent access to this for documentation, and also if they decide to do future work with us. I’m not sure how the licensing model works in this case
I see the following drawbacks to keeping each client separate:
- Becomes more difficult for our team to see all their tasks across clients
- Licensing would become very expensive (2-3 of our team members x 12 clients….seems excessive). Also what to do once the project ends and how to keep licensing
- Constant context switching as we work on many clients at once (not a huge deal, we already do this with trello)
Any advice on how we could make this work or a best path forward? Fibery seems like the ideal tool to bring all of this together since we currently are using about 3-4 different tools (Figjam, Trello, MS Word/Excel, PM software) to manage these implementations.