Show HN: Feature Rich Wiki for Microsoft Teams

1. You're stuck with another subscription for a "one use" product. Even though MS products often suck, you get a lot of functionality for one reasonable price. You might argue "$3.50 per month is nothing". Well, you're not going to be using a wiki and only have one person able to make changes. Otherwise you'd create a page some other way. You're going to have to pay on a per-person basis for a wiki that they might edit only a couple times over the course of the month. Carry that out to five years, and the math doesn't work.

2. You have to give your data to a company you don't know and storing it in an alternative location.

3. You're dealing with a second, small company you've never heard of.

Specifically, their editor is a separate component: https://github.com/outline/rich-markdown-editor

I assumed this was a clever marketing product from the outline team, but it seems to be entirely separate.

Wikis do not have any enforced navigation structure. Navigation is implicit (defined by Editing and Linking).

OneNote, "PerfectWiki", Teams built in "wiki", and many many others rely on a hierarchical page structure to function.

This would be fine were it an optional navigation mechanism, but it rarely is. Usually this is also how content is stored and managed. This ultimately makes the content itself VERY brittle to change, very difficult to refactor, and rarely navigable for long term use.

It's a much more approachable UI paradigm for beginners, but I have yet to see a large knowledgebase that didn't collapse under its own weight over time when using an enforced tree-structure to content.

It's incredibly rare that knowledge fits into a hierarchical taxonomy. Doing so at a UI level creates conflict and cognitive dissonance that accrues over time.

1) If you want feature rich thick document storage like this, there is already the ability to use onenote for these purposes.

2) I don't think you'll find that many companies that have gone through the effort to integrate all their services into office 365 would be happy about having to pump all of this into a 3rd parties google cloud instance.

3) There are a large number of all in one 3rd party backup systems for office 365 that backup everything, this would be outside that, and the backup options are exporting to html/pdf?

I'm just wondering if this could have been backed by azure/sharepoint/onedrive which would keep the data stored where most people would feel more comfortable. But I suppose if it did, it would be hard to justify as a SAAS that way.

— One note on your pricing, my sense is that you aren’t charging enough.

One thing I’ve learned over the years is that you owe it to your customer to charge enough for you to stay in business. 100 users for 50/m makes me nervous for you.

Ok - Some notes.

1. Blogs are a very good source of evergreen SEO especially if you focus on the keywords that work for you. So please make sure you do weekly or more posts on a blog that only has one every 1.5 months so far. I suggest you Make a commitment to yourself to do say 1 a week for the next year. Blogs that look given up are as negative an indicator as a git repo with last updates in 2016.

(cf Rand Fishkin - there was a really good microconf episode on this. His new startup might help you find likely wiki owners, it i suggest just listening for the mindset !)

2. English is not your first language - this can be a hinderance or an advantage. You can probably find someone to brush up the text - but I suggest that you aim for also having a look at near-English markets - India being an interesting example - a Hindi landing page might make an interesting SEO tactic, yet still allow you to expect many readers can bounce into the English blog.

https://www.news18.com/news/tech/microsoft-teams-sees-signif... https://etr.plus/articles/no-slack-by-teams

3. I honestly don't know your product market fit. Till now Teams always seemed a bit also ran, but they do seem to have real growth- and if you have some paying customers happy to put blurb on your site you are doing something right :-)

Good luck - keep the faith :-)

1. Regarding Pricing may be it could be bundled with Teams and get price per user from Microsoft.

2. If it works only with Teams, my concern is I am coupling my solution with Teams. What if I decide to switch to slack or Discord?

3. All the security concerns others have brought are going to block me from going for this solution.