Accenture

Production Hub

How a seven-person creative hub at Accenture Song produced Stellantis e-mail and WhatsApp at scale, across brands, with one shared way of working.

I ran the hub end to end. I took each brief from strategy, decided what shipped first, made the art, checked every HTML before it went out and read the results to shape the next round.

The hub's ClickUp board, 'Produção Stellantis', with requests organized by stage
Role
Hub lead, from brief to results
Company
Accenture Song
Client
Stellantis, Brazil
Period
2022 to 2023

More channels, more brands, the same team

Stellantis talked to clients through e-mail lead nurturing and, more and more, WhatsApp business messaging. As the hub grew, the work needed a model everyone could follow: who does what, how a request flows and how long it takes.

600+
e-mails produced in 2022
610+
e-mails produced by June 2023
55+
WhatsApp active notifications by June 2023, up from 30+ in 2022
7
people: strategy, governance, content, design and development

Seven people, five roles

Each role owned a clear part of every request. Mine was design, plus keeping the whole hub running as its focal point.

RolePeopleWhat they owned
Strategy1Content and implementation briefs, link parameters and e-mail performance studies
Governance1Request tracking, communication journeys and campaign tests
Content2E-mail and bot copy, flow improvements, the product data sheet behind the bots and model-year updates
Design2, including meDesign systems for every brand and for WhatsApp, e-mail art, templates, research pages and KV adaptation
Development1HTML and CSS for every piece, and adaptations

One request, end to end

This is how a single e-mail moved through the hub, and where I sat in it. The steps in red were mine.

StepWhoWhat happened
BriefMeReceived the brief from the strategy team.
PriorityMeDecided what shipped first, second and next.
CopyCopywritersWrote the messages from the brief I handed over.
DesignMe, with a second designerMade the art and briefed the other designer on extra pieces.
BuildDeveloperTurned the approved pieces into HTML.
HTML checkMeValidated every HTML myself before it went out.
SendCRM operationsUploaded the HTML to Salesforce Marketing Cloud and scheduled the send.
ResultsMeCame back to CTR, CTO and other CRM KPIs and turned them into insights for strategy, copy and design.

Two flows, one hub

E-mail and WhatsApp followed different paths, with the same two gates: Stellantis validation, then an Accenture review before anything went out.

Diagram of the two flows, described in the lists below
E-mail lead nurturing:
  1. Strategy, Alignment and communication brief
  2. Governance, Journey design and rules
  3. Content, Copy and e-mail art
  4. Stellantis, Client validation
  5. Accenture, Adjustments and review
  6. Build, HTML, Marketing Cloud upload, links and test sends
  7. Business, Performance analysis
WhatsApp messaging:
  1. POs, Campaign or request direction
  2. Content, Bot content and the model-year sheet
  3. Design, Image selection and KV adaptation
  4. Stellantis, Branding and client validation
  5. Build, Platform development, active notification and tests
  6. Accenture, Adjustments and review

A brief and a size for every request

Requests arrived through templates, so nobody started without the material. Each one was then sized, from PP to GG, to set a realistic deadline.

Campaign content

Landing page or spec sheet, final campaign conditions, tagline or branding notes, and the key visual.

Bot updates

Updated landing page, spec sheet of the new versions, branding notes, photos or KV and any new media.

Tests

Environment, WhatsApp number for testing, navigation script and the CTA to check.

Hours per step

A sheet estimating hours for each stage of each request type, so deadlines came from data.

Request sizes PP, P, M, G and GG on a lead-time scale from 1 to 15 days

Validation went from four hours to one

A Jeep Compass journey had 6 versions with 7 e-mails each. The old way meant editing subjects and snippets, exporting PNGs and pasting them into slides, seven times per version. I replaced it with one interactive validation page.

35 minutes per version became 10. The link expired to create urgency, adjustments happened in real time and errors dropped.

The interactive validation page in Figma, with every e-mail of the journey side by side
The WhatsApp design system file with palette and type styles
A design system for WhatsApp messaging, with its own palette, type and file structure.
A validation PDF showing a WhatsApp active notification next to the Jeep campaign key visual
Active notifications validated in a single PDF, next to the campaign key visual.

What the data suggested next

Beyond producing, the hub read its own results. Open rates from two Fiat journeys led to four proposals for the next cycle.

What we sawWhereWhat we proposed
Open rates fell along the journeyFiat Fastback: 23.15% and 25.59% on averageShorten the first-contact journey
Subjects written as questions seemed to open lessFiat Fastback, even early in the journeyAvoid questions; write more direct subjects
E-mails with a price in the subject opened moreFiat Pulse offers: 29.9% to 37.4% on the first e-mailUse price as the hook

Next project