I am a software developer and team leader, I have always enjoyed working in happy teams, so culture and interaction is very important to me, in my team we usually have a lot of interactivity during work hours, especially in the creative process, we like fast feedback and solving problems even faster.
Because of this, I have always liked working in person, but this changed radically due to the situation we are experiencing and I must say that at the beginning it was a bit difficult for me to lose the direct communication that I had in the office since it helped me to Being aware of the environment and culture of the team, which as I mentioned earlier for me is very important.
We started to make work stack changes, we went from slack to discord, teams, among others. We felt much more comfortable using only discord than the other tools, they were very "corporate" for us. However Discord is not focused on work teams, so it lacked features that were necessary for us.
So we said, what the hell, let's do something with which we are satisfied, and so Holis was born.
Holis facilitates real-time communication without leaving out all those chatters that add spice to your conversations.
We can say that Holis is a mix of Discord and Slack functionalities, united with the needs of our team.
Features.
Roadmap:
We are in a closed beta phase, while we adapt the infrastructure according to the demand that we are having.
If you are interested in the product, you can subscribe from the web to be the first to test the development, additionally if something like us has happened to you, I would love to hear your story.
I agree with @WarrenOF regarding the focus on integrations. Many companies will have an issue pulling away from Slack to use a product that doesn't have the same integrations they use. I can also say one of the reasons I moved a team to Slack in the early days was the reliability of their mobile app compared to other solutions we had tried. HipChat was well-liked by our engineering team until they tried to use it on the subway where the signal went in and out.
Yes, we are thinking of developing an SDK for third-party and own integrations through a Store. This would allow us greater integration with a possible community of clients.
At the beginning we would develop the most requested ones ourselves, but third parties would have the freedom to develop their own integrations.
Thank you very much for taking the time to help us.
I really like the vision of "slack for small close-knit teams". I would struggle to deploy it in my work team (60 people in 5 units), as we need something that is common across them all. But for a startup with 5 people, I can see how this would be great.
Personally I would focus on how your interface integrates with other solutions, rather than building out dedicated functions (e.g. link to google hangouts, not built-in video), as for me, that was what made Slack great. I would also try to make a really efficient UX for desktop/mobile, as it is usually a big part of winning teams over.
I would also consider making this more niche to a certain type of team, e.g. Developers, with specific integrations focused on things like code reviews, or snippet sharing.
Good luck, sounds exciting!
Thanks for the amazing feedback.
As you say the integrations will exist, but after a lot of feedback we decided to have a base product that would cover most of the communication problems, and then from there, give the client freedom to integrate other services.
I love how you described our vision: "slack for small close-knit teams".
Thanks for taking a few minutes to help us.
This comment was deleted 4 years ago