1. The reported development
Speaking at ADWEEK's Brandweek 2026 in Atlanta, Bruce Williams, CEO of Dentsu X North America, described a distinction between two approaches to campaign delivery, according to ADWEEK. The first, which Williams called "experience planning," involves creating consumer experiences by stitching together media, data, content, and tech in a siloed method. The second, which he termed "experience platforming," involves melding teams and capabilities so they all work systematically together to bring a campaign to life.
Williams cited Heineken as a client that had built systems enabling bidirectional collaboration across markets and from agency to brand. According to ADWEEK's reporting, the resulting strategy brought together competitive data, store data, and local market intelligence, giving teams the ability to funnel that information directly into decision-making and activation at scale at local market levels. Outcomes flowed back to the brand, franchisees, stakeholders, stores, and divisions.
"It’s just different ways in which we can think about using scale solutions and point ourselves to, ‘How are we building for that?’ But also be scrappier and nimbler"
2. Why the distinction matters for MarTech operations
Williams's framing maps directly onto a problem that enterprise marketing operations teams encounter daily. Most organizations running Oracle Eloqua, Adobe Marketo, Salesforce Marketing Cloud, or HubSpot alongside a CRM, a CDP, paid media platforms, and analytics tools are, in practice, doing experience planning: each system produces its own outputs, and a human operator or a batch integration stitches the pieces together after the fact.
The result is familiar. Campaign data lives in the marketing automation platform. Store or product data sits in the CRM or ERP. Competitive intelligence lives in a separate dashboard. Attribution is reconstructed weeks later. This is the integration-layer failure pattern we explored in our analysis of why analytics projects fail at the integration layer. The dashboard is rarely the bottleneck. The connections between systems are.
Williams's "experience platforming" concept implies that the integration layer itself becomes the platform: a shared data backbone that feeds every activation channel in near-real time, rather than a set of point-to-point connectors bolted on after each tool is configured.
3. Practical recommendations for enterprise teams
Consider auditing your current stack for the number of one-directional data flows versus bidirectional ones. Williams specifically noted that the Heineken system worked "bidirectionally, from agency to brand." Most enterprise MarTech stacks push data in one direction (CRM to MAP, MAP to analytics) but rarely loop activation outcomes back into the source systems that inform the next decision. Mapping these flows is the first step toward identifying where your team is still in "experience planning" mode. Our platform integrations practice exists precisely for this kind of architectural review.
We recommend evaluating whether your campaign execution workflows require manual handoffs between teams that could be eliminated by shared data objects. If your competitive intelligence, local market data, and campaign performance metrics live in three different tools with no common key, your teams cannot make the kind of in-cycle decisions Williams described. A data management audit that inventories every system of record and every integration touchpoint will surface the gaps.
Consider treating your CRM integration not as a one-time implementation task but as a living system that requires ongoing governance. The Heineken example, as reported by ADWEEK, describes outcomes flowing back to franchisees, stakeholders, and stores. That pattern requires maintained, monitored CRM integration with clear data ownership rules. When AI agents begin writing back to CRM records, the governance question becomes even more urgent, as we discussed in our piece on AI and CRM record governance.
4. The harder question behind the framework
Williams's language is appealing, but enterprise teams should be honest about the organizational cost of the shift he describes. Moving from siloed experience planning to systematic experience platforming is not a technology project alone. It requires shared KPIs across teams that traditionally operate with separate dashboards and separate incentive structures. It requires strategic planning that treats the integration architecture as a first-class deliverable rather than an afterthought of platform selection.
The Heineken example suggests this is achievable. But Williams also acknowledged the need to "be scrappier and nimbler," per ADWEEK's reporting. That tension, between systematic infrastructure and organizational agility, is where most enterprise MarTech transformations stall. The teams that succeed tend to start with a single bidirectional data flow that proves the value of the model before attempting a full architectural overhaul.
