Email Design · Case Study

Grow Email System

Redesigning an onboarding email sequence for a fintech platform: one design system, a clearer sequence and sharper copy across six emails.

Fintech Email Design 6 Emails HubSpot 2026 Platform: Responsive Web
6
Emails designed
1
Shared token and component system
HubSpot
Build and send platform
1
2
3
4
Step 01 — Discovery

What was broken and why

The client had a working product but users weren't sticking around long enough to see its value. I audited their existing email flow and found three core problems killing engagement before it even started.

Generic subject lines

Subject lines were generic, with no personalization and no reason to open now.

Users not activating

Emails arrived late, with no clear next step toward activating the account.

No visual system

Each email looked different. No brand consistency, no trust signals.

Key insight: The problem wasn't just design — it was sequence logic. Users were getting the wrong email at the wrong time. The redesign had to fix both the visuals and the flow.
Step 02 — Design

One system, six jobs

Before designing any single email, I built a design system first — tokens, components, layout rules. This made every email feel like one product, not separate files.

Design tokens

Brand blue, white, and a strict type scale. Used consistently across all emails.

Component library

Header, hero block, CTA button, footer — built once, reused across every email.

One job per email

Each email type has one job and one primary action, so the reader always knows what to do next.

Copy direction

Rewrote subject lines and CTAs to be action-oriented and specific, not generic.

Step 03 — Copy

From generic to specific

Subject lines and CTAs were the clearest lever. The direction was to name the user, say what is ready, and make the button describe the action it triggers.

Before — generic

Subject: "Welcome to Grow — get started today"

CTA: "Go to dashboard"

After — specific

Subject: "Your Grow account is ready, [name]"

CTA: "Activate my account"

Why it matters: a personalized subject sets expectation before the open, and a CTA that names the action tells the reader what happens next. This is the design rationale; no open-rate comparison is reported here.
Step 04 — Outcome

A system the client can extend

The deliverable is a complete onboarding sequence built on shared tokens and components, so new emails can be added without redesigning from scratch. Engagement data was not part of this write-up, so no performance figures are claimed.

8
Emails, one visual language
4
Stages, each with a clear trigger
1
Component library, built once

Have a similar project?

I'm available for email design work.