One hour per newsletter. I stopped accepting that.

It took an hour of manual work to send a newsletter on Marketing Cloud. Integrating a new module took weeks of development. At some point I stopped asking how to make that process faster — and started asking why it existed in that form at all.

How it worked

At most companies — and at GUESS before this — the workflow looked like this:

The designer creates the template. It goes to developers, or external consultants. Then weeks of back and forth begin: testing across every client and every browser. Sometimes a full month for a single template.

Then every template gets split into separate files, one per template, uploaded manually to Marketing Cloud as content blocks, and wired to the data extension for dynamic data: name, gender, country, language.

Every single send

And every time an email needed to go out: open the platform, assemble the blocks, insert copy and links, duplicate a version for each language, attach to customer journeys, schedule. An hour of manual work. For one email.

A new module? Start over from scratch.

When a workflow is slow, the problem is rarely speed. It's dependency.

Why it existed

The answer: the process was built around development. And development was the part nobody could touch. So I removed it.

What changed

• The email design system now lives in Beefree. Designers build it there and export static HTML — already cross-client and cross-browser. Zero handoff with developers.
• A Marketing Cloud specialist enriches templates with AMPscript to connect them to the data extension. This used to take days from an external consultant. Now I do it with Cursor in 5 minutes — just feed it the data extension context.
• I wrote a vanilla.js generator. Nothing sophisticated. It groups modules, lets you select the ones you need, builds the final HTML, and collects copy, links, and images into clean variables at the end of the body.

The part that matters: the person creating the email no longer scrolls between HTML and AMPscript getting lost in code. They fill in a configuration snippet. That's it.

The result

A business user can do alone in 10–15 minutes what used to take an hour and a technician. Time to integrate a new module: one hour, instead of months.

---

Takeaway

I didn't look for a more powerful tool. I moved the work to the people who actually do it, and removed everything that forced them through technical gatekeepers.

What's the process on your team that everyone accepts as "essential" — but might just be a bottleneck nobody has ever questioned?