Email campaign automation

Who the design was for

Tailwind’s users are not email marketing specialists. They’re small business owners, creators, and independent brands who want results without having to become experts in automation logic.

This distinction shaped every major design decision. Tools like ActiveCampaign or Klaviyo are built for professional marketers who understand triggers, conditions, and subscriber segmentation. Tailwind needed automation that the same person who ran their Instagram account could set up on a Tuesday afternoon without a tutorial.

Templates first — the critical entry point decision

The biggest early design call was making templates the default entry point into the builder rather than a blank canvas.

Starting from a blank automation is hard — you need to already know what you’re trying to build before you can configure it. Starting from a pre-built welcome series or re-engagement sequence is not hard. The template lowers the activation energy to zero: the structure is there, you’re just customising it.

The template library was designed around goals rather than technical categories:

• Welcome series — for new subscribers
• Product announcement — for launching something new
• Re-engagement — for subscribers who’ve gone quiet
• Post-purchase — for customers who’ve just bought

The visual preview on the selection screen was essential. Users needed to understand what they were picking — what the flow looked like, how many emails were in it, what the logic was — before committing to it.

The campaign dashboard

The campaign dashboard gives users a single view of all their campaigns — live, draft, scheduled, and paused — with enough context to know what needs attention without clicking into each one.

Each campaign card shows:

• Status — live, draft, scheduled, paused — immediately visible without opening the campaign
• Campaign title
• Date last updated
• Sent and opened percentages — the two numbers that actually tell you whether an email is performing

The builder — linear, not canvas

The campaign builder handles the automation logic: setting the trigger, building the email sequence, and defining the conditions between steps (whether an email was opened, clicked, or ignored before the next one fires).

The layout was kept linear rather than a freeform canvas. This was a deliberate decision against the pattern established by tools like Zapier or make.com, which use node-and-connector diagrams.

The reasoning: most automations Tailwind users actually need don’t require branching complexity. A welcome series is linear. A product announcement is linear. A linear structure is also much easier to scan and edit when you come back to it later — canvas diagrams sprawl, a list of steps doesn’t.

Side panel editing — keeping the flow visible

When a user needs to configure a step — edit the email content, set the delay, define the condition — the step detail opens in a side panel rather than replacing the view entirely.

This was one of the more important structural calls in the project. Editing a step in full-screen replacement mode means losing sight of where that step sits in the overall sequence. The side panel keeps the flow diagram visible at all times, so users always understand the context of what they’re editing — which step comes before, what triggers this one, what comes after.

AI copy generation in context

AI copy generation sits inside the email editor within the builder — not as a separate tool, not a separate screen. When a user is about to write a subject line or email body for a step in their sequence, the option to generate a draft is already there in context.

This follows the same principle as GhostWriter: AI should appear where the user already is, at the moment they need it, rather than requiring them to go somewhere else to use it.

What user testing confirmed

User testing validated the two most consequential design decisions:

• The template-first entry point — users found their footing quickly when starting from a template and expressed significantly more confidence completing their first automation than when given a blank builder
• The linear builder with side panel — users consistently stayed oriented in the sequence when editing steps via the side panel. In earlier explorations with full-screen step editing, users frequently lost track of where they were in the overall flow

The automation system gave Tailwind’s users capabilities that had previously only been accessible in more complex specialist tools, without requiring them to learn a new mental model before building their first sequence.