Turning days of email design into minutes

Lead Designer · Design Systems, Email

Problem

Every SearchKings email started as a duplicated Figma file with disconnected components, loose styles and mixed icon sets. Branding drifted from email to email, and an email that doesn’t look like the company starts to look like a phishing email.

Outcome

An end-to-end design and template system behind every email SearchKings has sent for three years. Teams build on-brand, client-ready emails in minutes instead of days, each with its MJML attached and ready to hand off to developers.

A design system built to flex without breaking

Rather than a fixed template for every email, I built the system as modular, auto-layout sections with variants for each use and screen size. Teams stack them to fit any message, and every combination stays consistent.

A design system built to flex without breaking

Rather than a fixed template for every email, I built the system as modular, auto-layout sections with variants for each use and screen size. Teams stack them to fit any message, and every combination stays consistent.

A design system built to flex without breaking

Rather than a fixed template for every email, I built the system as modular, auto-layout sections with variants for each use and screen size. Teams stack them to fit any message, and every combination stays consistent.

Starting with an audit

Before designing anything, I audited the emails going out and the process behind them. Three problems kept coming up across billing, sales and onboarding, and each one shaped what the system had to fix.

Starting with an audit

Before designing anything, I audited the emails going out and the process behind them. Three problems kept coming up across billing, sales and onboarding, and each one shaped what the system had to fix.

Starting with an audit

Before designing anything, I audited the emails going out and the process behind them. Three problems kept coming up across billing, sales and onboarding, and each one shaped what the system had to fix.

Mixed branding, mixed messaging

Logos, colours, buttons and copy changed from email to email, so nothing felt like it came from the same company.

Inconsistent structure across emails

Nothing used auto layout, so type sizes and gaps were set by eye and every email followed its own scale.

Hours lost on every email

Rebuilding and copying old files kept designers on each email far longer than needed, adding time and cost to every send.

Foundations as the single source of truth

The audit traced every issue back to missing foundations. Colour, text and effect styles, a 4pt spacing scale and two breakpoints were defined first, within email client limits, so every component inherits them.

Foundations as the single source of truth

The audit traced every issue back to missing foundations. Colour, text and effect styles, a 4pt spacing scale and two breakpoints were defined first, within email client limits, so every component inherits them.

Foundations as the single source of truth

The audit traced every issue back to missing foundations. Colour, text and effect styles, a 4pt spacing scale and two breakpoints were defined first, within email client limits, so every component inherits them.

A type scale built on email-safe fonts

Satoshi is the brand font, but most inboxes can’t load it, so Helvetica became the closest email-safe match, set in one fixed scale.

Auto layout on a 4pt grid

Components are built with auto layout on a 4pt spacing grid, so gaps are set once and repeat exactly in every email.

Colour for every mode and service

Brand and service colours are tested against light and dark text, with SK Grey in place of pure black, so emails stay readable in either mode.

Two sizes, every component

Every component ships as a 600 desktop and 360 mobile pair, so each email can be previewed and tested at both breakpoints before it’s sent.

Patterns built around how clients read

Clients skim emails between jobs, so each recurring need was designed as a pattern around one question: what does the client need to know, and what should they do next? Every pattern answers that first.

Patterns built around how clients read

Clients skim emails between jobs, so each recurring need was designed as a pattern around one question: what does the client need to know, and what should they do next? Every pattern answers that first.

Patterns built around how clients read

Clients skim emails between jobs, so each recurring need was designed as a pattern around one question: what does the client need to know, and what should they do next? Every pattern answers that first.

One primary action per section

A standard across every template: each section gets a single primary button, so the next step never competes with another.

Progress clients can see

Clients see which steps are done and what’s next on the way to Google Guaranteed, so they always know where they stand.

An invoice that reads like a summary

Each service, its amount and one clear total come first, so clients understand what they’re paying for at a glance.

Templates, voice and a file system built to scale

Every new email starts from a template chosen by its purpose, is written in shared language every team uses, and is filed under one naming convention, so nothing gets rebuilt and nothing gets lost.

Templates, voice and a file system built to scale

Every new email starts from a template chosen by its purpose, is written in shared language every team uses, and is filed under one naming convention, so nothing gets rebuilt and nothing gets lost.

Templates, voice and a file system built to scale

Every new email starts from a template chosen by its purpose, is written in shared language every team uses, and is filed under one naming convention, so nothing gets rebuilt and nothing gets lost.

Built from templates, not from scratch

Each email type has a template designers start from, and the same template is built in code, so developers reuse it too.

Every email sounds like SearchKings

Shared greetings, calls to action and sign-offs make emails familiar to read and instantly recognisable as the real thing.

Past emails become a playbook

Documenting every live email gives the team a full record to reference, so a new partner or franchise starts from what already worked.

A process, not just a system

Built with our developers and signed off by leadership, the system came with a way of working: designers start each email the same way and developers receive the same code, so nothing reaches launch on guesswork.

A process, not just a system

Built with our developers and signed off by leadership, the system came with a way of working: designers start each email the same way and developers receive the same code, so nothing reaches launch on guesswork.

A process, not just a system

Built with our developers and signed off by leadership, the system came with a way of working: designers start each email the same way and developers receive the same code, so nothing reaches launch on guesswork.

From new file to first draft in minutes

Every file follows the same setup, so any designer can open it, pick a template and start on-system from the very first frame.

What’s designed is what ships

Each component carries its MJML in Dev Mode, so developers build from the same source as design, with nothing lost in translation.

What I’d build today

Built before AI was production-ready, the system is now its guardrail. A composer on top would turn a short brief into an on-brand draft, assembled only from approved components, styles and voice.

What I’d build today

Built before AI was production-ready, the system is now its guardrail. A composer on top would turn a short brief into an on-brand draft, assembled only from approved components, styles and voice.

What I’d build today

Built before AI was production-ready, the system is now its guardrail. A composer on top would turn a short brief into an on-brand draft, assembled only from approved components, styles and voice.