Jff, thanks. Well I probably won't be the best person to explain you why should a company use it, but here are some of the reasons why I like snipsnap:

Being a Bliki it gives you two main platforms, a blog and a wiki.\\
How can such tools help a company in one or more projects? Well it's not that hard, a wiki by definition is a collaborative tool that can be used for knowledge sharing and collaborative developing. The blog plataform can also help in such cases like milestones publishing, change logs, etc where the team wants to give a special focus - and meaning - to a given page (being just a simple wiki page as any other can make it blend in the background).

Another interesting feature is that SnipSnap allows in its core to be created Taxonomies and map any content you want inside the system into that taxonomy, although the interface isn't the best to do it, the functionality and the idea it's there.

Also another interesting functionality, and that in my opinion is pretty handy, is that any snip within the wiki can have comments. This is interesting because a wiki only can generate collaborative content, although, to generate collaborative content __and__ discussion about that content it's not that easy, snipsnap does it very well.

It supports extension through macros and filters, both types can be easily created by anyone with the basic knowledge of Java. 

These were the points I can recall now... but I'm sure there are probably many more.