Here's one non-abstract idea that you can get for free, even though I might try myself as well:
Give Confluence a run for its money.
Confluence is so bloated that a clean install takes longer to start than it takes to boot my laptop and log in.
Plugin SDK documentation is a mess.
As far as I can see it only sells because of the brand and because of network effects.
If anyone could manage to create a real wiki (remember, it means quick!) and market it they might have a chance at some nice cash that would otherwise flow to a company that keeps wasting peoples time.
I would adjust this. No company will buy products just because they are a bit better. You have to completely knock that out of the park to be compelling.
OTOH, I'll grant if you really fail on support etc. you will probably fizzle out anyway.
I've bumped into two organizations which use Confluence for developer reference rather than Github's own repo-based wikis. Why??? In one case a manager even made us move an extensive github wiki to Confluence. After that, developers stopped using the reference and that had an impact on code quality. WTF.
There are already some good general purpose wiki providers out there, too!
Give Confluence a run for its money.
Confluence is so bloated that a clean install takes longer to start than it takes to boot my laptop and log in.
Plugin SDK documentation is a mess.
As far as I can see it only sells because of the brand and because of network effects.
If anyone could manage to create a real wiki (remember, it means quick!) and market it they might have a chance at some nice cash that would otherwise flow to a company that keeps wasting peoples time.
End of rant ;-)