It's also free and built-in. Also, it isn't quite true that this functionality is missing as it is provided by the full Office 365 offering (Office 365 has a fully featured wiki).

Teams wiki is simple, because it's tied to channels that are frequently transient. Regardless, I wouldn't bank on any long-term advantage from having these features. MS could drop a Teams update tomorrow and render your entire business case moot (either by adding those missing features, or changing the API in some detrimental, to you, way, or making their offering better than yours).

I hope you do well, but .. you're directly competing with a core functionality (provided for free) in Teams. And that's a tough spot to be in, short-term and long-term. If you want to make a business from it, I would explore ways to pivot.

Fair enough. But this raises another problem for me .. there's just so many wikis out there! At our company, we have:

- SharePoint Online/Office 365 wiki

- Teams channel wiki

- Confluence

- Zendesk wiki

Do we really need another wiki? Wikis are built into everything these days.

I've actually used the wiki built into Teams, and honestly, it's crap.

I used only the web version, and it was an extremely frustrating experience. Copy and paste seldom works as expected, with text in the page/section often permanently ending up an odd size/font. Once you have more than about 10 words in a page, performance crawls practicality to a standstill, and there are multi-second pauses very frequently. Every so often it would randomly reload the page, losing anything you'd typed recently. Also, images you insert will randomly disappear at a later date. Literally cannot understand how they could release something so fatally broken.

And it doesn't support markdown, which is a total no-go for me[0]

[0] it converts "#" to level 1 and level 2 titles, but that's it. And even that only works as expected half the time