CQ Becomes 'Adobe Experience Manager,' and the Suite Era Begins

Two years ago this month, we covered Adobe’s 240 million dollar purchase of Day Software and made a prediction. The company was assembling a content-to-measurement pipeline aimed at large marketing teams, and the pitch would be coherence.

This month, the prediction landed. Adobe has announced the Adobe Marketing Cloud. It is a suite gathering its analytics (the former Omniture), targeting, social, and campaign tools under one brand. The platform formerly known as CQ now carries a new name at the suite’s center: Adobe Experience Manager.

The rebranding is not cosmetic. It is a thesis statement. ‘Web content management’ is what the industry called the category Day competed in. ‘Experience management’ is what Adobe intends to sell. Content, personalization, and measurement built as one system. Bought from one vendor. Integrated by design rather than by your systems integrator.

The thesis deserves serious treatment, because our enterprise readers will be pitched it for the next five years. The right response is neither the vendor’s enthusiasm nor the best-of-breed camp’s reflexive scorn. It is a threshold question, and this post supplies it.

The suite thesis, stated fairly

The integrated pitch has genuine logic. Enterprise marketing runs on a loop. Create content. Deploy it across properties and channels. Measure engagement. Personalize. Repeat.

Assembling that loop from separate products (a CMS here, analytics there, testing from a third vendor) means integration projects and data cleanup. Every workflow crosses the seams daily.

Adobe’s argument: buy the loop as one system and the seams disappear. Your asset flows from Creative Suite into Experience Manager. The targeting engine serves it personalized. The analytics report on it. The vendor owns the whole. One contract, one roadmap, one throat to choke.

For teams whose marketing truly exercises the loop, the coherence is worth real money. Multi-brand portfolios, personalization programs, campaign volumes that make seam-friction costly. Pretending otherwise is best-of-breed romance.

The counter-pitch, which writes itself

And the costs, which the keynote does not linger on. Suite coherence is bought with suite gravity. License weight that starts in six figures and travels upward. Builds measured in quarters, with scarce, costly talent. And the deepest form of the dependency question we have pressed since the Oracle file. Leaving an integrated suite means leaving everything at once.

The best-of-breed path keeps each layer replaceable and competitive, at the price of owning the integration yourself. Neither answer is right for everyone. The honest variables are your scale, your maturity, and your capacity to own the seams.

What we would add from the trenches, and what no vendor deck includes: the unlisted requirements. AEM’s component-based authoring assumes governed component libraries, trained authors, and someone owning brand coherence. The personalization machinery assumes a segment strategy, content variants to serve, and measurement discipline to close the loop.

Platforms of this class do not grant marketing maturity. They assume it. Deployments that skip the assumption become costly shelfware with excellent demos. We have now seen both outcomes at close range, and the deciding variable was never the software.

The threshold question

So the question our enterprise readers should run, before any feature comparison: does your operation sit above or below the suite threshold?

Above it: genuine multi-site or multi-brand complexity. A personalization ambition with staffing behind it. Content operations mature enough to feed the machine. Budget where platform costs are line items rather than events. For that profile, AEM and the Marketing Cloud belong on the shortlist. Weigh them against the integrated offerings the other enterprise vendors are surely assembling, with the unlisted requirements priced in.

Below the threshold, which is most of the market including most mid-market institutions: the open-source tier delivers most of the capability at a fraction of the weight. The suite pitch is financing someone else’s economics.

The threshold is honest self-assessment, not aspiration. The most costly buying mistake in this category is buying the operation you intend to become rather than the one you run. The second most costly is letting the demo, which will be excellent, stand in for the reference calls, which you should make to organizations your size.

What trickles down the market regardless of purchase

Even readers who will never sit through an AEM demo should note what suite eras do to everyone’s expectations. The trickle is predictable and partly useful.

The vocabulary arrives first. ‘Experiences,’ ‘journeys,’ and ‘personalization’ will colonize mid-market RFPs and vendor decks within two years. Buyers fluent in what the words actually require (segments, variants, measurement loops) will negotiate better than buyers who order the vocabulary à la carte.

The capability expectations arrive second, in genuinely useful form. The suite era will push the open-source tier toward better personalization and asset tools, the way enterprise features have always moved down-market in this industry. Our platform coverage will track the arrivals.

And the pitch pressure arrives third. Expect ‘you need an experience platform’ to be aimed at buyers two sizes below the threshold. Keep the question from this post in the drawer for the meeting.

The suite era, in other words, is not only a buying event for the enterprise tier. It is a vocabulary event for the whole market, and vocabulary events reward the prepared reader.

What we’re watching

Three things to watch in our AEM coverage, now properly renamed.

Integration reality versus integration story. Suites integrate on marketing timelines first and engineering timelines second. Checking the actual seams with references, asset flow, data flow, will separate the shipped from the announced for years yet.

The open-source seam. Day was a model open-source citizen. Whether Adobe keeps up those contributions remains our small, telling stewardship signal.

And the category’s pull on everyone else. ‘Experience management’ as a frame will trickle into mid-market expectations and vendor pitches regardless of platform. Our readers below the threshold will still feel this announcement, in vocabulary and in RFP templates, within two years.

The pipeline we outlined in 2010 is assembled and named. Whether it delivers coherence or merely concentration is the question for the next five years, and we intend to follow it honestly. The threshold question is yours. The watching is ours.