2017 WCM Marketplace Overview

  • 13-Feb-2017

I'm excited to share some findings from RSG's just-released 2017 Web Content & Experience Management Market Analysis.  Overall, the WCM marketplace is seeing a lot of movement at the higher, platform end of the market, along with some stability (but potential gotchas) in the more product-oriented segment.

This briefing — available exclusively to research subscribers — charts likely 2017 risks and opportunities for both WCM product and platform vendors through two "Reality Check" charts.

WCM Platforms

WCM Platforms Reality Check 2017
RSG 2017 Reality Check for WCM Platforms (click to enlarge)


WCM Products

WCM Products Reality Check 2017
RSG 2017 Reality Check for WCM Products (click to enlarge)


In 2017 the WCM marketplace is evolving in different directions, with significant implications for prospective customers. This briefing delves into four key trends, including complexity-shifting and evolving cloud models.

Subscribers can log in to download the briefing right away.

Not a subscriber and want to sample RSG's evaluation research first? Sure, you can do that.


Our customers say...

"The Web CMS Research was the roadmap for our entire CMS selection process. It truly provided a basis for understanding what we should look for and expect in a CMS. Above all, since we used the report as our guide, we are more than confident in our CMS selection. If we had to go through the process all over again, we'd still rely as heavily on this report as we did the first time."

Michele McDonald, IT Project Manager, University of Oklahoma

Other Web Content & Experience Management posts

TeamSite Marriage Counseling

  • August 12, 2019

Was reminded recently in a call with an RSG subscriber that some TeamSite implementations linger on, like a really bad relationship you can't seem to end. Maybe it's time for counseling?...

What Is a Real Quadrant?

  • July 16, 2019

Customers have a love-hate relationship with marketplace "quadrant" diagrams. You suspect there's something not right in the arbitrary positioning...and you're correct!...