3 KEY STATS

ECOSYSTEM ARCHITECTURE

PRUDENTIAL: CMS IN REGIONAL TEAMS

IT WAS LIKE AN EPISODE OF "SAY YES TO THE CMS"

PROJECT OVERVIEW

Prudential’s regional markets in South America and Southeast Asia all used different CMS solutions to manage their consumer-facing websites. Some of those systems didn’t support their own language’s characters, some only had U.S.-based customer support, and pretty much all of them were frustrating to use, and difficult to find in-market developers or agencies familiar with the platform. It was messy. Prudential tasked us with finding one solution that met all of these markets’ needs. Other agencies had told them it would take six months to do that. We did it in one.

TECHNOLOGIES

CHALLENGE

We had a Goldilocks problem: these markets needed a CMS that didn’t have too many bells and whistles, or too little functionality, but just the right amount. It needed to support each market’s language. It needed customer support in, or at least near, each market. It needed on-premise or hybrid hosting so that customers’ data would be secure. And it couldn’t be exorbitantly expensive. Our challenge was finding a CMS that balanced all of those needs equally without breaking the bank.

APPROACH

First and foremost, we talked to the people who’d actually be using this backend. We spoke with business users who shared their frustrations and gripes about the systems they were using. Like therapists, we worked through their anger to determine their actual needs. And from there, we developed a full picture of what this backend would have to offer in order to make users’ lives easier.

After nailing down that criteria, we measured 9 vendors against this list of more than a dozen requirements, and we tested each one extensively. We actually understand what a CMS needs to do, because we’ve used them (and we don’t get tricked by their salespeople). Rather than thinking about it theoretically, we put ourselves in the shoes of the people we knew would actually be using them day-to-day as we tested each one, measuring each against their needs, priorities, and must-haves — not ours.

OUTCOME

After all that testing, we landed on Kentico, a CMS that met all of the criteria and offered just the right level of sophistication for business users. Oh, and we did it in a month.

EXPERIENCE

Prudential’s regional markets in Korea could build webpages in Korean, ask for help in Korean, work with developers in Korea, and run their sites without tearing their hair out. We consider that a win.

CAPABILITIES

MARKETING OPERATIONS

VENDOR ANALYSIS

ECOSYSTEM ARCHITECTURE

MARKETING PROCESS DESIGN

NERD OUT WITH US

KENTICO

SHAREPOINT

EPISERVER

ACQUIA

+