Take an email from the brief to a reviewed, usable campaign

Begin with the message and the person receiving it

We define the purpose of the email, the recipient context, the offer and the evidence behind its claims. An onboarding explanation, a product announcement and a renewal message need different content and next steps. I build the production workflow around those differences and your existing editorial and sender responsibilities.

The output can include subject and preheader options, body copy, an HTML or supported native template, personalization fallbacks and the campaign draft. I inspect the selected email platform and template model before choosing how assets are created or stored.

Make the whole email reviewable

A visual preview does not prove that every mail client will render identically. We agree representative devices, clients and test cases for the actual audience, then inspect them using the available tooling.

Saving a template is a write; sending it is another action

A local copy draft can stay outside the provider. Saving a template or campaign changes the account. A test send, scheduling and dispatch are further actions with their own recipients and consequences. I implement the approved boundaries and the checks immediately before the selected action.

We inspect sender/domain setup, platform permissions, supported template operations, audience rights, suppression and personalization fields. A permission scope named for composing email may also permit sending; the application’s allowed actions and approval checks must enforce draft-only behavior when that is the chosen scope.

Illustrative example: the first-name field is empty

A campaign draft greets customers by first name, but the approved test sample includes missing and malformed values. This is an illustrative production case, not an executed campaign. The workflow renders a natural fallback, shows the affected examples and keeps the audience definition and suppression rules visible to the reviewer.

A polished sample for one complete record does not accept the rest of the campaign. The review checks the intended link, offer, unsubscribe behavior where applicable, dynamic fields and permitted recipients before any approved send. A change to audience or content after review reopens the affected checks.

Keep editorial production separate from journey eligibility

This page owns the message and email asset. Lifecycle operations owns changing customer state: who is eligible now, which action should wait, and how suppression or a late event changes the journey.

I can build both as a connected client workflow. Production approval does not itself establish that a customer is eligible to receive the message. Likewise, a journey rule does not verify the product claims or layout in its email. Each decision needs an observable input and an accountable owner.

Personal implementation and a clear stopping point

I personally define the production process, build the selected integrations and checks, create the agreed assets and document the handoff or continuing operation. The client’s factual and brand owners approve claims and voice; the sender owner accepts recipients, timing and the action policy.

After an accepted dispatch, the operating record distinguishes provider acceptance, delivery feedback and later engagement or commercial outcomes. A timeout with an uncertain send is reconciled before retrying. Already-sent email cannot be undone. We judge usefulness through accepted assets, review/correction effort and actual delivery evidence, without promising fixed production savings or sales.