[hampowder]

You state it as if it were a coincidence. The important point is that the author identified the problem and filled the gap.

> I started reading forums, comments, and online discussions. It turned out the built-in Wiki in Microsoft Teams annoyed users really a lot.

[Orygin]

I admit I didn't read the entirety of the post, but I read the following:

> Many of our clients came to us after trying the Microsoft built-in Wiki. It was clunky, inconvenient, and didn’t do the job well. We focused on simplicity: the essential features only, nothing extra — and everything should function inside Microsoft Teams.

So I know it wasn't a coincidence, and rarely are such software built without understanding the needs first.

I just wanted to point out that in this case, the business relies on Microsoft not doing a proper job. Otherwise they would be at a serious risk of being Sherlocked by the provider.

[darkwater]

They already expanded it to Slack and other platforms.

[Orygin]

Slack is, I think, mainly focused on the messaging and relies on third parties to integrate other features. Microsoft is a behemoth that wants to sell their complete software suite and tries to integrate all of them together for a "seamless" experience. They do have an incentive for their own products to be good and used instead of third parties.

Plus once they realize how much data is in these wikis, they will want to ingest them for AI (if not already done), so there is an incentive for them to have more users on their solution instead.

Edit: And even if the OP is not relying only on MS for sales, they still depend heavily on them and their App Store. They are not competing with Confluence or other systems, they are competing with Teams itself.