[m] Mailbox Mode
Templates · Lifecycle journey · Brand case studies · Simulator
THE REFERENCE COLLECTION / 01

Ten emails.
Ten different starting points.

See how real brand emails inform original work—from a fashion drop to a developer digest. Each example pairs an exact reference with the pattern we studied and a new HTML composition.

Prepared case studies. Fictional sender brands. Original copy. No live generation or conversion claims.

01 / Fashion / collaboration

Adidas
→ FIELDWORK

The exact email

adidas Originals x Hellstar Superstar II

Inspect original reference ↗

The pattern

Product photograph → collaboration story → one action → second visual

What changed

The centered reveal and restrained copy become a fictional Fieldwork colorway launch. New name, product image and copy; no Adidas logos or claims.

Example prompt

Create an original fashion / collaboration email for FIELDWORK. Use the structure of the referenced Adidas email: product photograph → collaboration story → one action → second visual. Use my confirmed product facts, original branding and approved assets. Do not copy the source’s claims, names or tracking links. Return responsive HTML and plain text.

Reference and output proof

Reference: Public archive; visually inspected. Layout version: case-study-v1.

Output SHA-256: da31791533982551d09b32d2904037e392037ee926dded6e775ab6781f367294

Open full email ↗
02 / Fashion / product education

Nike
→ FIELDWORK

The exact email

The Nike Vomero 17 has arrived.

Inspect original reference ↗

The pattern

Lifestyle lead → short headline → product feature stories → category navigation

What changed

The staggered feature narrative becomes a Fieldwork product guide. Each section answers a different question instead of repeating a promotion.

Example prompt

Create an original fashion / product education email for FIELDWORK. Use the structure of the referenced Nike email: lifestyle lead → short headline → product feature stories → category navigation. Use my confirmed product facts, original branding and approved assets. Do not copy the source’s claims, names or tracking links. Return responsive HTML and plain text.

Reference and output proof

Reference: Public archive; visually inspected. Layout version: case-study-v1.

Output SHA-256: 91f4a7d8e9fdf8e85bcee18c8a5061e45129260b328c2ff2a170d6c0b3ce6d4d

Open full email ↗
03 / Beauty / customer communication

Sephora
→ FORME

The exact email

Steps we’re taking to address COVID-19

Inspect original reference ↗

The pattern

Black-and-white masthead → signed customer letter → separated actions → reassuring close

What changed

A historical service letter informs an original studio update. We retain the editorial hierarchy, not the health claims or crisis context.

Example prompt

Create an original beauty / customer communication email for FORME. Use the structure of the referenced Sephora email: black-and-white masthead → signed customer letter → separated actions → reassuring close. Use my confirmed product facts, original branding and approved assets. Do not copy the source’s claims, names or tracking links. Return responsive HTML and plain text.

Reference and output proof

Reference: Public archive; visually inspected. Layout version: case-study-v1.

Output SHA-256: 14c9bec76d61fed5eba9ea6c4f369e217e8b2e8e33f49b2e104841d04ab91214

Open full email ↗
04 / Hardware / product collection

Arlo
→ nook

The exact email

Security that's ready in minutes.

Inspect original reference ↗

The pattern

In-home hero → central benefit → 2×2 category grid → bundle → reassurance

What changed

The collection-shopping structure becomes Nook, a fictional home sensor system. No surveillance, discounts or safety guarantees are copied.

Example prompt

Create an original hardware / product collection email for nook. Use the structure of the referenced Arlo email: in-home hero → central benefit → 2×2 category grid → bundle → reassurance. Use my confirmed product facts, original branding and approved assets. Do not copy the source’s claims, names or tracking links. Return responsive HTML and plain text.

Reference and output proof

Reference: Public archive; visually inspected. Layout version: case-study-v1.

Output SHA-256: 1f92f638ac9a9822e2b60b4dfdbd85571057c0bc2d3bd1230cd415b7d0c061da

Open full email ↗
05 / Software / feature invitation

Shopify
→ Folio

The exact email

Congrats, Smiles Davis! You’ve been selected to apply for Shopify Credit

Inspect original reference ↗

The pattern

Centered invitation → isolated product visual → benefit checklist → repeated action

What changed

The invitation-to-benefits sequence becomes a software workspace preview. No financial offer, reward rate, approval or testimonial is reused.

Example prompt

Create an original software / feature invitation email for Folio. Use the structure of the referenced Shopify email: centered invitation → isolated product visual → benefit checklist → repeated action. Use my confirmed product facts, original branding and approved assets. Do not copy the source’s claims, names or tracking links. Return responsive HTML and plain text.

Reference and output proof

Reference: Public archive; visually inspected. Layout version: case-study-v1.

Output SHA-256: a08fb44d87100f3b253bd738bcde8bbadb0992978090f97044cd6a1e0a4dc7af

Open full email ↗
06 / Software / event broadcast

Salesforce
→ Folio

The exact email

Live now. Stream it free on Salesforce+.

Inspect original reference ↗

The pattern

Dark broadcast hero → light agenda panel → stacked session cards → closing action

What changed

Broadcast hierarchy becomes a fictional Folio studio session. Original agenda; no invented speakers, partners or live stream.

Example prompt

Create an original software / event broadcast email for Folio. Use the structure of the referenced Salesforce email: dark broadcast hero → light agenda panel → stacked session cards → closing action. Use my confirmed product facts, original branding and approved assets. Do not copy the source’s claims, names or tracking links. Return responsive HTML and plain text.

Reference and output proof

Reference: Public archive; visually inspected. Layout version: case-study-v1.

Output SHA-256: 593393ef32725c5617858ba96cc15b2b5c8772a69dbe367a19470ff531e6abeb

Open full email ↗
07 / Software / founder digest

Y Combinator
→ Fieldnotes

The exact email

How To Build The Future: Sam Altman

Inspect original reference ↗

The pattern

Issue masthead → lead story → supporting stories → compact community list

What changed

An editorial digest becomes Fieldnotes, a fictional founder publication. Original topics, no copied interviews or portfolio claims.

Example prompt

Create an original software / founder digest email for Fieldnotes. Use the structure of the referenced Y Combinator email: issue masthead → lead story → supporting stories → compact community list. Use my confirmed product facts, original branding and approved assets. Do not copy the source’s claims, names or tracking links. Return responsive HTML and plain text.

Reference and output proof

Reference: Public archive; visually inspected. Layout version: case-study-v1.

Output SHA-256: bbadb3c8acbc56610368a14de37c833f6c9462ac7e493a70c21f34db8e11ec83

Open full email ↗
08 / Hardware / developer education

NVIDIA
→ Relay

The exact email

Post-train NVIDIA Cosmos for your physical AI use case

Saved from the brand’s email sender. Original HTML retained privately.

The pattern

Technical hero → two-column learning resources → dark on-demand section

What changed

The learning-resource grid becomes a fictional open tooling digest. Original concepts and examples; no GPU performance or vendor affiliation claims.

Example prompt

Create an original hardware / developer education email for Relay. Use the structure of the referenced NVIDIA email: technical hero → two-column learning resources → dark on-demand section. Use my confirmed product facts, original branding and approved assets. Do not copy the source’s claims, names or tracking links. Return responsive HTML and plain text.

Reference and output proof

Reference: Stored mailbox HTML; visually inspected. Layout version: case-study-v1.

Source: mailref_f5f520f2967bc1f1
SHA-256: fd51b406db0269106dabeef3f9f97db3653cb2854ad3c2fc1abc2d974a79c25d

Output SHA-256: 4da9580cbf5cee0680fc37abd0c35fdef211b678e67b46c04ac50e8e7a89a61c

Open full email ↗
09 / Hardware / developer community

AMD
→ Relay

The exact email

AMD ROCm™ Software 10.0 Is Here. See What’s Next for AMD AI

Saved from the brand’s email sender. Original HTML retained privately.

The pattern

Programme masthead → dense linked release notes → community spotlight → opportunities row

What changed

The community newsletter becomes a fictional Relay developer update. Original changelog, no fabricated user testimonials or event dates.

Example prompt

Create an original hardware / developer community email for Relay. Use the structure of the referenced AMD email: programme masthead → dense linked release notes → community spotlight → opportunities row. Use my confirmed product facts, original branding and approved assets. Do not copy the source’s claims, names or tracking links. Return responsive HTML and plain text.

Reference and output proof

Reference: Stored mailbox HTML; visually inspected. Layout version: case-study-v1.

Source: mailref_a902a8b90bae2bf0
SHA-256: e3752c6fee3bf827d83c81f53bdf14c7202d173bfc7ec1d42b58bd85887f035c

Output SHA-256: a803b42e56f04022771c95cf282412287769c3aa29bb619d48431c20de38c5b2

Open full email ↗
10 / Media / editorial roundup

TechCrunch
→ Fieldnotes

The exact email

Building AI guardrails should be part of the process

Saved from the brand’s email sender. Original HTML retained privately.

The pattern

Centered issue title → editor introduction → separate story cards with repeated read actions

What changed

The modular roundup becomes a fictional Fieldnotes edition. Original commentary and typographic art replace source articles and photographs.

Example prompt

Create an original media / editorial roundup email for Fieldnotes. Use the structure of the referenced TechCrunch email: centered issue title → editor introduction → separate story cards with repeated read actions. Use my confirmed product facts, original branding and approved assets. Do not copy the source’s claims, names or tracking links. Return responsive HTML and plain text.

Reference and output proof

Reference: Stored mailbox HTML; visually inspected. Layout version: case-study-v1.

Source: mailref_c6fa800d4846eea8
SHA-256: dedb056253423017a2b1f74059eef67bdca76581b00fee9c15b07f4e33e70a2f

Output SHA-256: e839d1d1b09d1d090b8926ac989ccc1d034d523ef30db8a97c546bf0e20c054b

Open full email ↗