The plain truth about email design (and why “pretty” is not the point)

Design is a promise. If the design says “this will be easy” and the layout fights the reader, the promise breaks. If the design says “this will help” and you hide the next step, the promise breaks. The design practices below exist for one reason: keep promises. That is how we build for brands like PrettyLitter and REM Beauty, where beauty matters, but usefulness decides the sale.

What follows is not theory. It is a set of choices we use every week. They are steady, testable, and kind. They respect the person holding the phone and the platforms guarding the inbox. They are not clever in the way that trends are clever. They are clever in the way that trust is clever.

Five design principles that never betray you

1. One job per message. Every extra job lowers the chance of any job getting done. If you want to sell, sell. If you want to teach, teach. If you want to learn, ask one question. Not five.
2. Proof before perk. Lead with a single sentence of proof and one detail that removes doubt. You can offer a perk later if the math proves it pays. Proof builds long-term conversion. Perks build dependency.
3. Live text wins. Put real words in real text. Do not wrap your headline in an image. Machines cannot read it. Many people will not see it. Live text is faster, clearer, and safer for deliverability.
4. Fewer modules, stronger modules. Four excellent blocks beat nine average ones. Attention is not a buffet.
5. Respect wins in the long run. Readable type, honest subject lines, one unsubscribe click, and real quiet hours are design decisions. People notice kindness even when they do not say so. Platforms notice it as complaint rates that stay low. That is not soft. That is good business.

Strategy plus storytelling: how to build a message that converts

Start with the mini brief from the top of this page. Then build the story around it. A good email is a three-beat story:

1. Context: one sentence that names the problem or the desire. For PrettyLitter, that might be “A cleaner box without the guesswork.” For REM Beauty, “Color that actually stays where you want it.”
2. Proof: two pieces, nothing more. One review line that sounds like a person, and one specific detail that removes friction. “No perfume, no cloud. Just crystals that clump fast.” Or “Twelve-hour wear on a humid day. Two swipes. One wash to remove.”
3. Next step: one clear call to action. If a reader wants to learn more, offer one alternative that is not the product page. Examples: a “how to choose shade” guide for beauty, a “how to start” guide for a litter newcomer. The design should make both visible without shouting.

We resist the urge to show every offer and every category. If the story is strong, one product line and one decision aid beats an everything store.

Structure: the layout that carries the story

Use a layout that tells the story without needing a designer in the room to explain it. Here is the structure we reach for most often:

• Subject line and preheader: tell the truth quietly. They should read like the first sentence and the second sentence, not like two billboards competing for attention.
• Header: small logo, generous breathing room, and a link to manage preferences. No huge banners that push content below the fold.
• Hero block: a single, clear headline in live text and a sub-line that adds one specific detail. An image can carry mood, but the words must carry meaning.
• Proof block one: one human sentence from a review, with a first name and city when appropriate.
• Proof block two: a friction-killer: size chart, ingredient clarity, return window, or shade match. This removes the “I want it but I am not sure” feeling.
• Primary call to action: on its own line, with real button text that names the action. “Find your shade.” “Start with one bag.” Avoid “Shop now” unless you truly have no better words.
• Secondary call to action: for curiosity. Place this beneath the primary. Not side by side. We are making a ladder, not a maze.
• Footer: readable address, privacy link, preference center, and a one-click unsubscribe header enabled behind the scenes.

This structure is not glamorous. It is honest, and honesty is what people recognize at a glance when they open a message on a crowded train.

Typography that respects eyes and inboxes

Type is hospitality. Make it feel that way.

• Body size: treat sixteen pixels as a floor, not a ceiling. Smaller sizes punish real readers and reward screenshots.
• Line length: aim for forty to sixty characters on a phone. If you stretch lines across the entire screen, you raise cognitive load for no reason.
• Headlines in live text: the hero line must be text, not a picture of text. If the image fails to load, the promise still loads.
• Weight and rhythm: not every word needs to be bold. Use weight sparingly to draw the eye down the page.
• System fonts first: custom type can work, but it often backfires in email clients. Choose safe families or provide reasonable fallbacks. Beauty is nothing if the letters fail to render.

Color, contrast, and dark color scheme-safe design

Color is mood. Contrast is respect. Many people read in a dark color scheme. Design for that on purpose. If you do not, your soft gray text on pale lavender will become an unreadable whisper on a black background.

• Contrast minimums: treat the strict standard as a design constraint worth keeping. When you call something important, make sure it is actually easy to see.
• Buttons: a solid background color with a clear border and real text. No transparent buttons over a photograph. The button text must be readable in both light and dark color schemes.
• Logos: prepare a version for a dark color scheme so it does not disappear. Many email clients will invert parts of your design automatically; test and adjust.
• Do not rely on color alone: when something is interactive, design shape and contrast, not just hue. Color-blind readers should not have to guess.

Images that tell the truth (and what to do when images do not load)

A good image does three things: it clarifies what the product looks like in real life, it makes scale obvious, and it shows the result of using it. A bad image does the opposite: it confuses size, hides detail, or makes the body text do extra work. Here is how we avoid that.

• Compression with care: keep file sizes light. Faster messages convert better. Beauty survives under a good compressor.
• Alternative text that reads like a human wrote it: “Vanilla shade on deep skin, direct sunlight, no filter.” Not “image_003.jpg.”
• Always put the crucial line in live text: if the image fails to load, the promise remains.
• Use a single moving picture rarely and only when it earns its weight: motion is a spice, not a meal.

Reusable modules that pay the rent

We rely on a small set of blocks that carry most of the load. These are easy to build in platforms like Klaviyo or Braze, and they travel well across product lines.

1. Review tile: one line in quotation marks, first name and city, one sentence beneath that connects the review to a result.
2. How it works tile: three steps, each with a short line and a tiny picture or icon. Keep it literal.
3. Comparison tile: a table with three rows and two columns. No snark. Just facts that help a person decide if this is for them.
4. Progress header: a simple line above the hero that tells a loyalty story without shouting. This encourages a second item in the cart without a discount.
5. Frequently asked questions tile: three collapsible questions that remove friction: “How do I choose a shade?” “How do returns work?” “Is this safe for…?”
6. Starter path tile: “First week” and “Week four” side by side, to make the journey feel believable.

For PrettyLitter, that might look like a “how to switch” tile that addresses smell, dust, and how long a bag lasts. For REM Beauty, it might be a “shade match in one minute” tile with three faces, three lines, and a direct path to the right product.

Accessibility is not charity; it is conversion

Emails that work for more people get read by more people. Accessibility is not something you tack on later. It is the base layer. Here is the minimum we ship:

• Real words in HyperText Markup Language: headings, paragraphs, and lists that screen readers can understand.
• Clear link text: “See shade guide” is better than “Click here.”
• Tap targets that respect hands: a real button with height and breathing room. No tiny text links stacked on top of each other.
• Alt text as a promise, not a label: what will the person learn from this picture if it does not load?
• Readable type over a photograph: do not put important words on top of a busy image. If you must, put a color behind the words and make sure the contrast is generous.

Design for the hand first: the mobile-first reality

Most people will meet your message on a phone. This is not a trend. It is the default. Design for the hand first. Then make the desktop version feel roomy, not different.

• One column: let the eye move straight down. Two columns are for tables and rare comparison moments.
• Thumb reach: primary call to action placed where a right-hand or left-hand reach is natural.
• Short rhythm: headline, sub-line, one supporting sentence, call to action. Repeat.
• Weight budget: keep the whole message lean so the person on cellular data does not wait.

Design choices that quietly protect inbox placement

Placement is not a mood; it is a license that gets renewed every send. Some of that license is technical and lives with your engineering team. Much of it is design.

• Consistent “From” identity and subject line honesty: the design should never make the person feel tricked. Trust keeps complaint rates low.
• Live text over giant pictures of words: when a mailbox provider can parse your message, you look like a trustworthy sender.
• One-click unsubscribe headers and a visible link: let people leave easily. The ones who stay are the people you can grow with.
• Engagement band rules baked into the workflow: design for people who actually open and act. Do not ship to the unresponsive just because a calendar says “big week.”
• Steady cadence: do not train people to expect a fire drill every Friday. Your design does not have to shout to be heard when the inbox expects you.

Copy patterns that work: side-by-side rewrites

Scenario: a person browsed eye shadow, added once, bounced.

Scenario: a person is curious about switching to a new litter but is unsure about smell and dust.

Design across a calendar: rhythm without noise

The calendar is where good design either lives or dies. Volume alone is not the problem. Random volume is the problem. Here is a rhythm that holds up for beauty and for consumables:

• Week one: a proof-first education story and a light nurture for people who just bought.
• Week two: one offer-lite message with a loyalty progress header and a single alternative for the curious.
• Week three: a community or values note—short, kind, not a manifesto—plus a product story for a repeat buyer segment.
• Week four: one clear launch or seasonal push with honest urgency, surrounded by quiet. Let the important thing stand alone.

Flows do the heavy work in the background. Campaigns decorate the house. If a campaign drags revenue per recipient down two cycles in a row, we retire it or rewrite it. That discipline is design.

Testing without superstition

The goal is not to collect charts. The goal is to change next week with confidence. Here is how we test without turning the team into statisticians.

• Split tests for structure: change the order of modules or the length of a section. Measure add-to-cart rate and revenue per recipient, not just clicks.
• Bandit tests for framing: let more traffic flow to the line that wins while you are still learning. Keep exploration on so the list does not get stuck in last month’s taste.
• Randomized controls for expensive decisions: if the send includes a significant perk or a big segment change, keep a group that does not receive it. If it does not make money after cost, it does not stay.

How small teams and big teams can ship this without chaos

Small team

• One owner writes the mini brief, designs from a modular template, and ships two stories per month. That is enough if the stories are honest.
• Reuse blocks. Change words, not bones.
• Run one test at a time and write a two-line note about what changed and what you will try next.

Enterprise team

• A producer protects the calendar and the quality gates, a strategist chooses dials, a designer writes and lays out, an analyst runs the readout, and a deliverability lead guards the domain.
• Language packs for multilingual programs. Translators edit keys, not HyperText Markup Language. If you run global brands on Klaviyo or Braze, this pattern prevents drift and makes experiments portable.
• Change-freeze during risk windows. A rollback plan that names a human, not a committee.

Frequently asked questions

Do we really have to put headlines in live text?

Yes. When images do not load, the promise still arrives. Screen readers can understand it. Mailbox providers can parse it. Live text is a kindness that also protects placement.

What font should we use?

Use a system family with generous size and weight. If you choose a custom face, provide a sane fallback and test on the email clients your audience actually uses. A beautiful message that fails to render is not beautiful.

How many modules are too many?

Fewer than you think. Four excellent blocks beat nine average ones. If you find yourself adding a seventh section, you probably have a second email trying to get out.

Where does short messaging fit?

Short messaging is the nudge. Email is the story. If you use a platform like Attentive or Postscript, stagger the nudge fifteen to thirty minutes away from the email or choose the single channel that best fits the moment.

Who can help us build a system like this?

If you want a partner who measures with receipts and designs with kindness, we do this daily. Read our public thinking at stickydigital.io or talk to us about a practical plan at stickydigital.io/contact. If your stack includes loyalty with Yotpo, subscriptions with Recharge, on-site recommendations with Rebuy, or helpdesk context from Gorgias, this design approach travels cleanly across all of it.