But users such as Chuck Hollis, vice president of technology alliances at EMC, say there are major considerations to weigh as companies invest more in products.
Hollis is maintaining a blog about his experience working out a social media strategy at the company.
"There's a big difference between some engineering group putting in a wiki for their team, and a large corporation making a strategic decision for all their employees," he wrote in a recent post. "If I'm selling to a small group, I'd want an offering that's focused on price, ease of installation, price, ease of management, price -- and maybe price."
But there are different considerations for company-wide deployments, he noted: "I want my new social software to work with everything I have -- not as another free-standing entity, but as a 'layer.' I don't want to create a separate, distinct and isolated content domain -- one that's arguably much less functional than the one I've already got."
And the new class of tools will likely never replace major enterprise infrastructure components, he added. "If you dig into any modern content management system, you'll find a very fine-grained environment for controlling different aspects of a document -- far beyond what any social software vendor is prepared to implement."