Updated · 7 min read
The email copywriting pyramid: write for the 5-second reader first
Newspaper writers learned the inverted pyramid a century ago: conclusion first, supporting detail after, background last. Email has the same scanning pattern and almost none of the same discipline. Most lifecycle emails bury the point in paragraph three, then wonder why engagement is poor. Here's the structure that reliably wins the 5-second read while still rewarding the 60-second one.
By Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
How people actually read email
Research on email reading patterns (Litmus, Nielsen Norman) consistently shows three reader modes:
Scanner (60–70% of opens). Subject, maybe the first line, the CTA. 3–8 seconds total. Engages or moves on.
Skimmer (20–30%). Subject, headline, first paragraph, glance at the CTA. 10–30 seconds. Clicks through if the top is compelling.
Reader (5–10%). End to end. 30+ seconds. High intent, usually 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 with you.
The pyramid structure
Tier 1: Subject + preheader + visible first line (5-second read). These three elements carry the entire message. The scanner will not read anything else. If the point isn't in these three, the scanner misses it. 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." Complete message at five seconds.
Tier 2: Primary CTA + one-line "why now". For the skimmer who's decided the topic is relevant, the CTA needs to be immediately visible and the motivation clear. Place the CTA within the first 400 vertical pixels so it's visible without scroll. Support with one line: "Upgrade takes 30 seconds" or "All your workspace data carries over".
Tier 3: Supporting context (for the reader). The detail that rewards users who stay. Plan details, FAQ about trial expiry, testimonials, next-step guidance after upgrade. This is where marketing instinct usually starts the email — put it at the bottom where readers can find it without blocking the primary action.
Tier 4: Secondary CTAs + resources. Help docs, contact support, preference centre. Below the fold where they don't compete with the primary action.
The specific opening formulas
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 immediately established; 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 teasers: "The most interesting thing we learned from 1,000 A/B tests last quarter..." Tells the reader there's a payoff if they continue.
,
The CTA rules
One primary CTA per email. Two CTAs dilute action. Secondary action goes as a text link below the button, not a second button.
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 ("your") in tests, though not universally — worth testing for your audience.
CTA above the fold on mobile. 400 pixels is the phone viewport. Primary CTA needs to fit there. If the user has to scroll to see the CTA, the skimmer's 10-second attention is already spent.
Repeat the CTA at the bottom. Readers who scroll all the way down shouldn't have to scroll back up. A second CTA at the end captures them without adding top-of-email clutter.
The mobile email design guide covers CTA sizing and positioning on phones specifically.
For content emails (newsletters, educational), a lower CTA position is defensible — the value is the reading, not the click. Even then, having one upper CTA option is worth the space it takes.
Length is an output, not an input
"How long should an email be?" is the wrong question. The right one is "how much detail does this specific message need?". Transactional confirmations are three sentences. Feature announcements might be 150 words. Educational content might be 500.
What matters is whether the length is earned. Every paragraph does work. Nothing is padding. An email that's 200 words of padding plus a good CTA performs worse than 60 words of nothing plus the same CTA. Cut aggressively; what's left has to survive the cut.
The test: read each paragraph and ask "if this were deleted, would the email be worse?". Anything that isn't clearly worse when deleted is dead weight.
A note on long-form: a 1,000-word newsletter is really multiple pyramids — overall (top-of-email summary) plus one per section (lead with the point). Readers should be able to scan, get the key points, choose where to go deeper.
Legal or compliance text sits below the primary content and above the footer — the tier-3 supporting context layer. Don't lead with it. Don't push it to a link unless the legal framework allows. Users expect to see it; they just don't want to see it first.
Promotional emails: same pyramid, more strictly. Offer in the subject line and first line. Conditions and fine print later. A promo email that hides the offer in paragraph two has wasted its scanner audience entirely.
If the email is a single CTA with no supporting content, it's tier 1 and tier 2 and nothing else. That's fine. Shorter is better when the message is genuinely short. Don't pad a simple email with paragraphs of "context" to make it feel more substantial.
uses the pyramid as its default copy structure. It's the pattern that consistently outperforms narrative-style copy in lifecycle contexts — and the scanner thanks you for it.
Related guides
Browse allMobile email design: 65% of opens are on a phone — design for that
Two-thirds of email is opened on mobile. Most designs still start with desktop and hope it collapses. Here are the mobile-first rules that reliably produce emails that read, click, and convert on a phone.
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.
Email dark mode: the four render modes and how to not break any of them
Dark mode in email isn't one feature — it's four different render behaviours across major clients, each with its own logic. Design without knowing which mode you're hitting and roughly half your audience sees something you never approved. Here's what each client does and the defensive rules that survive all of them.
Email accessibility: the seven rules that make your emails readable by everyone
Email accessibility isn't a compliance tax — it's the difference between reaching 100% of your audience and the 85% who have easy sight, steady hands, and full-volume screens. Seven rules cover 90% of what actually matters, and most of them are cheap.
Transactional email anatomy: the five sections every transactional needs
Transactional emails open at 3–5x the rate of marketing and carry more brand signal per send than anything else in the program. Most teams treat them as ops artefacts and miss the leverage entirely. Here's the five-section anatomy that works across every transactional type.
Brand voice in lifecycle: how to sound like you, not the generic SaaS CRM voice
Lifecycle emails drift toward a generic 'polished SaaS CRM voice' because it's the default in every template library and every agency deliverable. Here's how to actually write in your brand's voice across an entire lifecycle program.
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 — 54 lifecycle methodologies, 55 MCP tools, native Braze integration. Pay what it's worth.