Simplicity, Robust Functionality, Affordability even for scale, Maturity.
Many content systems focus on solving the problems of one business function or use case. Bloomfire is useful for many common sales, marketing, training, HR, community business functions, users and their use cases.
Simplicity means general users can create web pages, insert documents of any kind from any online source or through upload. But it also manages links to articles. Pages can include images and video - even self-recorded webcam video.
Functionality means content can be organized for many purposes, grouped for specific audiences and communities. Beyond management, it's a full collaboration system to comment and request content assistance.
Affordability means you don't have to choose between (near) free generic platforms that you have to develop into usable applications, and expensive, fully functioning specialty applications. Bloomfire's business model fits in-between, with pricing designed to accommodate scale.
Maturity means these folks have been at this for awhile, and the system is robust, with feature enhancements well in the "nice to have" category, more than "must have".
I'm sure there are little nits that frustrate me. But I'm hard pressed to name them. I always like to see more robust tagging capability, because as content volume grows, search becomes so important.
I'd like to see delivery with tracking and notification included somehow. Pages can be public, and can be shared, but tracking requires users to be registered (paying) as part of the "community".
This system must be on your short list. Defining content use case requirements is part of our business. It's important to define specifically the use cases, and associated functionality, required of any of the many communication, content and collaboration systems that are available today.
We use this application for general content management, sales enablement, and training. Since it's fast and easy to add content to pages -- in many different ways -- it's easier to capture, file and tag 3rd party (articles or documents) as well as our own, into one central repository. We continue to put document files in Box (legacy) but use Bloomfire as a front end.
So this saves time curating and finding content assets. We find them easier, therefore use them more frequently than with Box or internal file storage. Content is now a real asset for us.
We also refer clients to Bloomfire when working on content operations projects.