Updated · 7 min read
The email copywriting pyramid: write for the 5-second reader first
Picture the moment your email actually reaches a person. They are on a phone, half-walking, glancing at the preview pane between two other things. Five seconds. That is the budget. Newspaper writers solved this same shape of problem a century ago with a structure called the inverted pyramid — conclusion at the top, supporting detail underneath, background at the bottom. Email has the same scanning pattern and almost none of the same discipline. Most lifecycle emails (the automated, behaviour-triggered sends every CRM program runs — welcomes, reminders, win-backs) bury the point in paragraph three, then wonder why nobody clicks. Here is the structure that wins the 5-second read without short-changing the rare 60-second one.

By Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
Three readers open every email — and only one of them is paying attention
Before any structure makes sense, picture who is on the other end. Eye-tracking and engagement studies from Litmus and Nielsen Norman keep landing on the same three reader modes — three distinct people, three different attention budgets, all opening the same email.
The Scanner (60–70% of opens). Subject line, maybe the first line, a glance at the call-to-action — the button or link asking them to do something. Three to eight seconds and they are gone, either clicked or closed.
The Skimmer (20–30%). Subject, headline, first paragraph, eye flicks down to the CTA. Ten to thirty seconds. Clicks if the top half is compelling.
The Reader (5–10%). End to end. Thirty seconds or more. High intent, almost always converts.
Write for all three, in that order. Scanner makes the email work at 5 seconds. Skimmer gets enough to click. Reader earns the reward for sticking around.
The inverted pyramid is just the structural answer to that hierarchy. Most important thing first, supporting detail after, background last. The Scanner gets the whole message in the first frame. The Skimmer gets enough to act. The Reader gets the depth they showed up for. One email, three jobs, no forking.
The pyramid: four tiers, in the order the eye actually moves
Tier 1: subject line, preheader, visible first line — the 5-second read. The preheader is the snippet of text that sits next to the subject in the inbox preview, typically 40–90 characters. Together with the subject and the first visible line of the body, those three elements carry the entire message. The Scanner will not read anything else. If the point is not in those three, the point is not received. Worked example — Subject: "Your trial ends Friday" / Preheader: "Upgrade by Thursday to keep your workspace" / First line: "Your [product] trial ends at 11:59pm on 2026-04-25. To continue, you'll need to upgrade." That is a complete message at five seconds.
Tier 2: primary CTA plus a one-line "why now". The Skimmer has decided the topic is relevant. Now they need somewhere to click and a reason to do it. Place the CTA within the first 400 vertical pixels — roughly one phone-screen height — so it sits above the fold without scrolling. Support it with a single line: "Upgrade takes 30 seconds" or "All your workspace data carries over". One sentence, one job.
Tier 3: supporting context for the Reader. The detail that rewards staying. Plan details, FAQ on what happens at expiry, a customer testimonial, what to do after the upgrade. This is where marketing instinct usually wants to start the email. Don't. Put it at the bottom, where it serves the people who actually want it without blocking the people who don't.
Tier 4: secondary CTAs and resources. Help docs, contact support, the preference centre — the page where users adjust which emails they get. Below the fold. They are useful escape hatches; they are not the main act, and they shouldn't fight the primary action for attention.
First lines that earn their place — and the four warm-ups that don't
The first sentence of the body is the most expensive sentence in the email. It either confirms to the Scanner that the subject was true, or it loses them. Good first lines do one of four things, fast:
1. State the conclusion. "Your trial ends at 11:59pm on April 25." No setup. The most important fact is the first thing the reader sees.
2. Reference a concrete event. "Thanks for your order — here's what's in it." Context is established immediately; the reader knows why the email exists.
3. Answer the implicit question. For a "how do I use X?" topic: "Here's the 2-minute version of how to use X." Direct answer, no preamble.
4. Open a loop worth closing. For content sends: "The most interesting thing we learned from 1,000 A/B tests last quarter…" Tells the reader there is a payoff for continuing.
,
The CTA rules: one button, one job, visible without scrolling
One primary CTA per email. Two CTAs split attention and dilute action. Any secondary action goes as a text link below the button — never a second button competing for the click.
CTA copy tells the user what happens next. "Upgrade my account" beats "Click here". "See my order" beats "Go". First-person phrasing ("my") often wins against imperative phrasing ("your") in tests, though not universally — worth running on your own audience before treating it as gospel.
CTA above the fold on mobile. Roughly 400 vertical pixels is the typical phone viewport — what the user sees before scrolling. The primary CTA needs to fit inside it. Make them scroll to find the button and the Skimmer's ten-second window has already closed.
Repeat the CTA at the bottom. Readers who scroll all the way through shouldn't have to scroll back up to act. A second instance at the end captures them without adding clutter to the top.
The mobile email design guide covers CTA sizing and positioning on phones in detail.
Content sends — newsletters, educational pieces — can defend a lower CTA position because the value is the reading itself, not the click. Even there, one upper CTA option is worth the space it takes.
Length is what comes out, not what you set in advance
"How long should an email be?" is the wrong question. The right one is "how much detail does this specific message actually need?" A transactional confirmation is three sentences. A feature announcement might be 150 words. An educational piece might be 500. The answer is whatever survives a brutal cut.
What matters is whether the length is earned. Every paragraph does work. Nothing is padding. An email that is 200 words of filler plus a good CTA performs worse than 60 words of nothing plus the same CTA. Cut aggressively; what is left has to survive the cut.
The test, paragraph by paragraph: read it, ask "if this were deleted, would the email be worse?" If the answer isn't a clear yes, it is dead weight. Delete it.
A note on long-form. A 1,000-word newsletter is really several pyramids stacked — one for the whole email at the top, then one per section, each leading with its own point. Readers should be able to scan, get the headline takeaways, and choose where to dive deeper. Same structure, fractal.
Legal or compliance text — privacy disclosures, terms references, the regulatory bits — sits in the tier-3 supporting layer, below the primary content and above the footer. Don't lead with it. Don't hide it behind a link unless the regulatory framework actually allows that. Users expect to see it; they just don't want to see it first.
Promotional emails follow the same pyramid, only stricter. The offer goes in the subject line and the first line. Conditions and fine print come later. A promo that hides the offer in paragraph two has wasted its Scanner audience entirely — and the Scanner is most of the audience.
If the email is one CTA with no supporting content, it is tier 1 plus tier 2 and nothing else. That is fine. Shorter is better when the message is genuinely short. Don't pad a simple email with paragraphs of "context" to make it feel weighty. The Scanner sees through it, and the Reader resents it.
uses the pyramid as its default copy structure. It is the pattern that consistently outperforms narrative-style copy in lifecycle work — and the Scanner thanks you for it. If you only take one thing from this guide into Monday: rewrite the top 50 words of your highest-volume email so the Scanner gets the whole message. The rest is detail.
Read to the end
Scroll to the bottom of the guide — we'll tick it on your reading path automatically.
This guide is backed by an Orbit skill
Related guides
Browse allPersonalisation that doesn't feel creepy
There's a line between personalisation that earns trust and personalisation that breaks it. It's not where most people think it is — it's about how you signal what you know, not what you know. Here's the line, how programs cross it without noticing, and the patterns that keep you on the right side.
Subject line anatomy: the four parts every line that performs shares
Most subject-line advice is decoration tips — emoji, length, numbers. The lines that actually get opened share a structural pattern. Four parts in a specific order, the three distortions that ruin it, and the four rules that keep A/B tests honest.
Preheader text: the second subject line most programs ignore
The preheader is the snippet shown next to the subject line in the inbox preview. Treat it like a second subject line and you double your hook. Treat it like an afterthought and it says 'View this email in your browser'. Here's how to write preheaders that actually earn the open.
Brand voice in lifecycle: how to sound like you, not the generic SaaS CRM voice
Lifecycle emails — the automated sequences that go out on signup, after a purchase, when a cart is abandoned — drift toward a polished, generic SaaS voice because it's the default in every template library. Here's how to actually write in your brand's voice across an entire program.
Emojis in subject lines: when they help, when they hurt
One well-placed emoji lifts open rate a few percent. Three reads as spam and drops it. The honest version of the emoji question is smaller and more specific than the debate suggests — here's the pattern that actually survives testing.
Push notification copy that actually gets tapped
Push is the highest-interrupt channel in the stack. A bad push burns goodwill in under a second; a good one feels like a useful nudge from a friend. This is the copy discipline — specific words, specific structures, specific anti-patterns that reliably get a user to turn your notifications off for good.
Found this useful? Share it with your team.
Use this in Claude
Run this methodology inside your Claude sessions.
Orbit turns every guide on this site into an executable Claude skill — 63 lifecycle methodologies, 91 MCP tools, native Braze integration. Free for everyone.