Recommendations to others considering KnowledgeOwl:
Evaluate the needs of your company as well as your budget. Knowledge Owl is a great tool if your needs revolve around a smaller organization or smaller number of authors, you want something that makes creating content relatively easy (compared to something like a wiki) and you have a relatively limited budget to work with. Be aware that the product may not be completely mature though, which is offset by the lower cost of the product. Review collected by and hosted on G2.com.
What problems is KnowledgeOwl solving and how is that benefiting you?
I'm roughly 6 months in to beginning the service and due to not being able to have many authors for content, have held off in letting our end users know that this knowledge base exists so they wouldn't go look and then decide that content was so sparse they would never return. It's a tough crowd of a few hundred potential readers who are based in the "field," often have spotty Internet access and don't have much time to waste (a stark contrast from some people in an office who may have a little knowledge base.) I'm actually presenting roll out to users tomorrow!
If similar projects I've worked on have shown anything, there will be slow adoption by users, so it will likely take at least another 6 months before there is any hope of deriving some sort of possible improvement in our support case data that we track (i.e. "did having knowledge owl make a difference?") There are often no second chances to make first impressions with these kinds of things. Hoping that this builds value and prevents our users from having to make return travel visits to customer accounts and helps them resolve issues with knowledge rather than deciding to RMA equipment that has nothing wrong with it. Review collected by and hosted on G2.com.