[mrjn]

Founder here. Struct is designed for both teams and communities. Because the problems affecting Slack and Discord are the same. We already have a bunch of community features, like publicly indexable knowledge base from threads, public-to-internet channels -- which are being used by many OSS companies (list on home page).

Teams is a different product. Companies who use Teams are there because they have tight integration with Microsoft Office, which is the USP there.

[WesleyJohnson]

We switched from Slack to Teams because we were going all in on Office 365 and Teams is included.... so why pay for Slack? But, honestly, we don't use a lot of the integrations, except for maybe the Sharepoint access when adding attachments which is, admittedly, pretty nice.

We also don't use Threads in Teams. Things got lost trying to jump back and forth between the "Chat" tab and the "Teams" tab. So now, we just create a new chat conversation for each project we're working on and add the relevant participates and rename the chat to the Jira Ticket #. That provides enough context/summary for what the chat is about.

All that said, Struct looks really nice and I could see it benefitting our team. Especially the AI portion. We have chats going back years for long-lived projects that get shelved and then picked back up later. Being able to interact with a ChatBot to help find answers within these chats would be killer. I assume there are no plans for a Struct for Teams though.

[mrjn]

Perhaps a good start would be to create a Struct org, for communicating within the team?

We'd surely look into Teams integration at some point. Though, I'm not sure how many takers would be there for Teams/Struct integration. My perception is that Teams users tend to be medium-to-large businesses who are tied to Microsoft Office, and would be very hard to sell to. I might be wrong.

[WesleyJohnson]

I'm sure you're probably spot on. Going to take a deeper look at Struct regardless; it's intriguing.