craft
Craft: the writing and building of lifecycle messaging
Craft is the difference between an email that functions and one that gets remembered. Same information, same audience, same infrastructure. The craft layer is what determines whether it converts. These guides cover the writing, design, and production decisions that make lifecycle messages actually work.
Lifecycle operators talk in systems. Subject lines, preheaders, and copy are where those systems meet a human. A flawless Braze configuration, perfect segmentation, and healthy deliverability all collapse if the email itself reads as generic. Craft is the last-mile work: the tight layer between what you're trying to say and what the reader actually sees.
The guides in this category start with the inbox. Subject line anatomy: the four-part structure that survives the 2-second scan. Preheader text: the second subject line most programs still waste on 'view in browser'. Emoji discipline: when they lift open rate, when they trigger filters, and why the effect is smaller than the vendor case studies suggest. Then the reading experience: mobile-first design (65% of opens happen there), dark-mode render-mode trade-offs, accessibility as the baseline that happens to also survive image blocking.
From there, into production. Transactional template anatomy: the five-section structure that keeps these emails functional without making them look like marketing. The email copywriting pyramid: conclusion first, so the 5-second reader gets the point before the 60-second reader gets the detail. Brand voice discipline, because every lifecycle program eventually drifts toward the generic SaaS CRM voice. Personalisation that doesn't feel creepy. SMS, push, and content-block naming conventions that scale.
Read these when specific emails aren't performing. More often, read them before designing the next template. Craft decisions are cheaper to make at the start than to retrofit.
All 21 guides in this category
Browse all categoriesConnect Claude to Braze: the read-only-first setup
Connecting Claude to Braze is two strings and a list of checkboxes: a REST API key, your cluster endpoint, and the permissions you tick when you create the key. Those checkboxes are the whole security model. Here is which ones to grant first, which to withhold, and how to verify what the integration can actually see.
9 min read
IntermediateBraze naming conventions that survive a Friday afternoon
Every Braze workspace eventually becomes an archaeological dig. The convention that actually holds is four dimensions, six seconds to apply, and enforced by tooling rather than a Notion page nobody reads.
9 min read
IntermediateLiquid for lifecycle marketers: the complete Braze reference
Every personalised field in every Braze message runs through Liquid. Get it right and personalisation quietly improves every send. Get it wrong and 50,000 people see 'Hi {{${first_name}}}'. This reference covers the syntax and the production habits that stop that happening.
11 min read
IntermediatePersonalisation 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.
9 min read
IntermediateThe SMS playbook from the operator's seat
SMS is the highest-engagement and highest-risk channel in the lifecycle stack. Here's the compliance architecture, the copy discipline, and the frequency rules that keep SMS from destroying the goodwill it's uniquely positioned to create.
10 min read
BeginnerSubject 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.
8 min read
IntermediatePush 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.
8 min read
BeginnerPreheader 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.
7 min read
IntermediateEmail dark mode: the four render modes and how to not break any of them
Dark mode in email is 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.
9 min read
IntermediateMobile 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.
8 min read
IntermediateEmail accessibility: the seven rules that make your emails readable by everyone
Roughly fifteen percent of your audience opens your email with a screen reader, on a cracked phone in direct sunlight, or with images blocked at the corporate gateway. Most programs accidentally design around them. Seven rules, most of them cheap, all of them learnable in an afternoon, close the gap.
8 min read
IntermediateTransactional email anatomy: the five sections every transactional needs
Transactional emails, receipts, password resets, shipping updates, 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.
8 min read
BeginnerClaude with Orbit vs Claude without: same model, one of them can check its work
On its own, Claude writes fluent lifecycle work it has no way to verify: plausible Liquid, plausible Braze steps, HTML that looks right and clips in Gmail. Here is a task-by-task comparison of what changes once the model can open the email, read the platform's real constraints, and tell you it was wrong.
10 min read
BeginnerBrand 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.
8 min read
BeginnerThe email copywriting pyramid: write for the 5-second reader first
Most recipients give an email five seconds before they engage or delete. The email has to land its point at that depth and still reward a longer read. The inverted pyramid, conclusion first, detail after, is how.
7 min read
BeginnerEmojis 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.
6 min read
BeginnerPlain-text email versions: why they still matter in 2026
Every HTML email should ship with a plain-text twin: the same email rendered as bare text, no styling. Most ESPs auto-generate one, and most of those auto-generated versions are garbage. Here's why the plain-text version still matters in 2026 and how to make the version you ship actually work.
6 min read
IntermediateCustom attributes: the data design that decides what your program can do
Custom attributes are infrastructure. Designed well, they enable every future campaign. Designed badly, they become the reason "can we segment on X?" is a multi-week engineering project instead of a 15-minute one. Here's the design discipline that prevents the mess.
7 min read
AdvancedGenerative AI for lifecycle content: where it earns its place and where it embarrasses you
Generative AI inside lifecycle ESPs has moved from novelty to default in 18 months. BrazeAI (formerly Sage AI), Iterable Copy Assist, Klaviyo's subject line generator: they all promise per-message copy at scale. Some uses are genuinely useful. Others are a fast path to brand drift, factual errors, and reputational damage. Here's the line.
8 min read
IntermediateStripo, natively: connect your account, sync your modules, compose emails through the API
If you build emails in Stripo and edit them with Claude, you've probably been running a clipboard relay: copy HTML out, paste in, paste the result back. Orbit's native Stripo integration ends the relay. This guide walks through how the loop closes: pulling your saved Stripo modules into Orbit, letting Claude compose new emails from them, pushing the result back as an editable Stripo email, plus the two setup gotchas everyone hits the first time.
13 min read
IntermediateHow to build Stripo emails with Claude, and push them straight to Braze
Stripo is one of the most-used email builders going, and most teams still drive it by hand: drag blocks in the editor, copy the HTML out, paste it into an AI tool, paste the result back. Orbit connects Claude directly to Stripo's API instead. This guide walks the full workflow, sync your Stripo modules, compose an email in chat, verify it renders, and export it to a Braze template by name, without leaving the conversation.
11 min read
Frequently asked questions
- What matters more: subject line, preheader, or body?
- Subject gets you opened, preheader backs it up, body earns the click. They're a stack: weakness at any layer wastes the work of the others. Most programs over-invest in subject-line A/B testing and under-invest in preheader craft; the preheader is often the highest-ROI change you can make to an existing template.
- How long should an email be?
- Length is an output, not an input. Transactional confirmations are 3 sentences. Feature announcements might be 150 words. Educational content might be 500. What matters is that every paragraph does work: an email that's 200 words of padding plus a good CTA is worse than 60 words of nothing plus the same CTA.
- Do I need to worry about dark mode?
- Yes. Roughly 30–50% of email opens happen in some form of dark rendering, and the render behaviour differs across clients. Minimum: use #FAFAFA backgrounds and #111 text instead of pure white/black, so partial-invert clients don't produce unreadable contrast. See the dark mode design guide for the four render modes and the defensive rules.
- How do I write good subject lines?
- Lead with specificity, not cleverness. 40 characters of the most important information. Avoid padding ('we hope this finds you well'), false urgency, and ambiguity about what the email is for. The subject line anatomy guide covers the four-part structure that consistently outperforms.
- Should emojis be used in email?
- Sparingly: one at the start of a subject as a visual anchor for category, not as content. Emoji-heavy subjects read as spammy and the effect decays as adoption spreads. Certain emoji (💰, 🎰, 💯) still trip filters. For consumer-casual brands they help; for B2B, finance, and healthcare they usually hurt.
- What's Braze Liquid and do I need it?
- Liquid is the templating language Braze uses for dynamic content: personalisation tokens, conditional logic, date formatting, loops. Any program with more than basic first-name personalisation will need it. The Liquid reference guide covers the patterns that actually come up, not the full specification.