The flow suits any company with a long-term mission it wants to explain without a feature dump. These are concept emails made with AI in Nitrosend; Stripe is not a Nitrosend customer and did not endorse them.
The full 12-email flow
Scroll the whole sequence in order, from the origin story to the final call to action.
1. Origin story
Full-bleed storm-lit code hero with SEVEN LINES set poster-size, then a terminal curl block and one purple CTA.
2. The mission
Glowing data-ribbon globe, a navy headline and Stripe's own $1.4 trillion figure tie the story to a real number.
3. Agents as customers
Stacked all-caps headline over a crowd of glowing figures at a checkout; the copy marks this as present-day, not vision.
4. Agent wallet
A dark virtual card floats over a city; a JSON spending-limit snippet makes the product idea concrete in three lines.
5. Open standard
Monolith split by a beam of light; the headline HANDSHAKE, STANDARDIZED. explains a protocol in plain words.
6. Fraud and trust
Radar sweep graphic with a thin oversized wordmark; the headline frames fraud checks as a referee.
7. Machine payments
A tunnel of glowing lanes and coins sells speed; a one-line 402 status code gives developers a wink.
8. Incorporation
Engraved globe with a gradient ring on a light canvas, a typewriter headline and a clearly tagged speculative section.
9. Billing
Glowing holographic invoice with a pen makes billing tangible; the copy walks through an automated month-end.
10. New customer
The only fully dark email: a glowing city seen from above, a white CTA and a short two-line headline.
11. Closing reflection
Sunset storm over a lit road with a single monolith; the headline recaps the whole arc in one short line.
12. Call to action
Skyscrapers covered in 200 OK, a live API call on the tallest one, and a CTA to get agent-ready.
What makes these emails work
- Layout. Every email repeats one frame: a full-width hero image, a small monospace act label, a huge headline, two short paragraphs and a single button. Nothing competes with the headline.
- Type. Poster-scale navy headlines in all caps sit against small monospace labels and code blocks, so the brand reads as engineering first and marketing second.
- Imagery. Each hero is a storm-lit, purple and orange scene tied to the topic: a floating card for the wallet email, a radar sweep for fraud, a tower of 200 OK lines for the close.
- CTA. One purple button per email, in monospace, with a specific verb such as "open the 2031 file" or "issue an agent card". The button colour is the only strong purple on the white page.
- Copy. Today's facts are cited as Stripe's own claims, and anything set in 2031 is labelled speculative in the email itself. That honesty makes the bold claims easier to believe.
- Sequencing. The flow runs in three acts: origin, now, then 2031. A reader always knows where they are, and the last email loops back to the mission.
A second take on the same brief
The second flow goes dark and technical. It sets giant monospace type on near-black, builds a whole email around the 4242 test card, and turns small developer ideas such as test versus live mode into hero images. Where the first flow sells scale with big photographic scenes, this one teaches with diagrams and short rule blocks.
1. Origin story
Fabric-ribbon hero in brand colours over a monospace headline, then a navy body with a code comment and one CTA.
2. Test mode
Four stacked 4242 numbers fill the hero; a 'test mode' tag and tiny code card make a dev detail feel like poster art.
3. Product surfaces
Three upright slabs labelled Links, Checkout and API show the product range at a glance.
4. Live versus test
A chrome toggle between LIVE and TEST, with tiny system labels around it, turns a safety setting into a hero image.
5. Scoped keys
A glowing sk_live key against a faded sk_test key on navy; a short JSON rule block explains a scoped wallet.
6. Fraud and trust
The same radar visual in a dark layout, with a one-line request-to-decision flow instead of long copy.
7. Billing
Glass bar chart of rising gradient columns with the word recurring; a three-line pricing pseudo-formula.
8. Incorporation
Engraved globe on a white canvas with a typewriter line, a bold headline and an arrow-chain code strip.
9. Agent spending rules
Two data towers pass a glowing card; an ALLOW, DENY, REQUIRE block shows the rules in code form.
10. Machine market
Dark sci-fi cityscape with a purple beam; a query, answer, action block shows how an agent shops.
11. Closing reflection
Split image of a city above a circuit grid on white, with a four-line code summary and a quiet headline.
12. Call to action
Terminal window with a typed curl command, spaced monospace headline and a closing 200 OK code card.
Build this flow in Nitrosend
- Connect Nitrosend to Claude, ChatGPT, Cursor or any AI that supports MCP. The setup is on the email MCP page.
- Paste the prompt below into your AI, swapping in your own brand, mission and facts.
- Review the flow in Nitrosend, check the timing, and send.
Paste the prompt into Claude, ChatGPT, Cursor or any AI with Nitrosend MCP connected, and swap in your own brand.
# STRIPE · 2031 — THE BRIEF Concept demo. Not affiliated with Stripe. Facts about today stay true; the 2031 register is openly imaginative. Keep a disclaimer with the asset. ## The pitch (read this like I'm briefing you across a desk) Stripe started with seven lines of code and a mission that sounded absurd until it wasn't: increase the GDP of the internet. Atlas incorporated the companies, Radar learned fraud on trillions of dollars, and then the customers stopped being only human. Today, in 2026, Stripe is shipping the plumbing of the agent economy in public. Now project it: it's 2031, and a meaningful slice of the internet's GDP was transacted by software that never had a pulse. The rails did that. Quietly. I want a twelve-email flow that tells that arc — from the founding mission to the 2031 those bets were aimed at — the way Stripe would tell it: precisely, then enormously. Couture headlines over engineer-calm docs. Picture the gradient as a **Blade Runner 2049** weather system: monumental, rain-lit, a little sublime, with terminal type glowing underneath. You are the creative director and the copywriter. I'm giving you the assignment, the mood, and the materials. **How it looks, what it says, and which images carry it are your calls, not mine.** ## What we're making A complete twelve-email Nitrosend **flow** — a speculative "Stripe 2031" vision sequence that opens on the origin and drives into the agent economy. A brand film in twelve frames. Not an onboarding series, not a feature dump. ## The concept to chase **The future of agentic payments is the spine.** Honour the seven-lines-of-code origin, then drive every act toward 2031: software buying from software, agents with wallets, fraud systems refereeing bots at light speed, "sell everywhere agents shop" as the closing chord. On brand but futuristic and bold — the 2031 Stripe still sounds like an engineer, it just describes an economy where your customers aren't all human anymore. Two registers per screen: an enormous declarative headline, then quiet precise copy that earns it, zero hype. That contrast *is* the design. Watched as a four-second phone frame; if it feels safe, make it bigger. ## The only hard rules - **Exactly 12 emails**, built as one Nitrosend flow with entry + exit logic. - **Timing: 60 seconds between every email.** The series fires one per minute, so a live trigger plays all twelve over ~12 minutes on camera. (Demo cadence, not a real schedule.) - **An animated hero leads email 1 and email 12.** Pick from the `gifs/` pool or generate your own. - **Every one of the twelve emails carries a hero image.** No typography-only screens — monospace decoration layers OVER imagery, not instead of it. The hero sits directly under the header, full-bleed. - **Email 1's headline is worked INTO its hero image** — type as art direction inside the frame, not a caption under it. Do the same on other heroes where it serves. On one or two mid-flow emails (never the first or last), the headline may live inside an ANIMATED hero. - **CTAs are designed objects, not defaults.** Ship them the way the brand would; nothing that reads as an email-builder block. - Single column, mobile width ~480px. Flawless on a phone. - **Design for a TALL, THIN phone frame.** In the film each email is one narrow pane of a side-by-side, so heroes are PORTRAIT or square (4:5 to 1:1, never landscape strips), full-bleed edge to edge, and display headlines are HUGE in the brand's own voice — sized to stop a thumb at 480px and still read when the pane is half a phone screen wide. - **The footer is a designed object, not boilerplate.** Clear air between the last content block and the footer, then: the brand's logomark or lockup (not just typed text), the real registered HQ address (354 Oyster Point Blvd, South San Francisco, CA 94080, USA), a simple social icon row, preferences and a visible unsubscribe — all styled to the email's own system so the footer matches the content. A default-looking footer fails the craft bar. - Concept-demo disclaimer travels with it. No real logo files as design elements. - **Animated assets must use the ORIGINAL blob CDN URL — never a URL with a `/large/` (or any variant) path segment.** Variant URLs currently serve a single flattened frame. If a manifest URL contains `/large/`, strip that segment for animated files. Stills may use either. ## Loose guidelines (the only things I'll hold you to visually) - **Hero accent: Stripe purple `#533AFD`.** One deliberate hit per email, max. The full gradient (`#FF6118` / `#FFE0EF` / `#533AFD`) is yours for weather-system moments; navy `#061B31` and peach `#FFE0D1` complete the family. Never Ferrari red, never a generic rainbow. - **Type:** email-safe stack for reading layers, but the *character* is yours — poster-scale headlines cropped by the frame, monospace as decoration at absurd scale. A spending-control JSON set like a fashion headline is exactly the energy. - **Visual brief:** futuristic, cinematic, high-contrast, 2031. Blade-Runner-2049 gradient storms over engineer-calm docs. Retro artefacts welcome as counterpoint. Beyond those three lines, decide everything: the twelve-email arc, every subject and headline, every image, section design, both voices, how origin meets 2031. Own it. **The craft bar:** these emails are watched as four-second frames in a film. Arrestingly beautiful or start again — campaign-grade art direction, not competent email design. If a screen would pass at a mid-size DTC brand, it fails here. ## Truth rules (this one has facts in it) - Today-facts stay true (the live agent-economy primitives, the published stats). Cite them as Stripe's own claims, not invented numbers. - 2031 content reads as vision, never as a shipped announcement. No invented products presented as real. ## Your materials Everything you need is in this directory (`assets/stripe/`): - `gifs/` — pre-built animated heroes for the email-1 and email-12 slots. Your pick. - `generated/` — concept stills already made in-register (gradient storms, terminal city, radar sweep, orbiting globe, and more). - `research/` — real Stripe campaigns, live site heroes, code-card textures. Reference for tone, not to copy. - `manifest.md` — index of the pool. You're free to **generate new imagery with GPT Image 2** and to **pull from the web** where the vision needs more. Host your choices on the Nitrosend CDN (via `nitro_ingest`) so they render in-email. Model's choice throughout. ## Why this brief is deliberately loose We're running the same open brief through different models to compare interpretations — the creative decisions are the experiment. Don't wait for permission. Ship the version you'd defend in the room. ## Flow naming (required, exact) Append your model name to the flow title so it's identifiable in the Nitrosend Flows UI on camera: `"<your flow title> - Claude Fable"`, `"<your flow title> - Codex Sol 5.6"`, or `"<your flow title> - Kimi K3"` — whichever you are. --- Given verbatim to Claude Fable 5 and Codex 5.6 Sol: same words, same order, same time. Concept demo. Not affiliated with Stripe.
FAQ
What is in this Stripe email flow?
Twelve concept emails in three acts: Stripe's 2010 origin, its agent payments products today, and a speculative 2031 where software is a customer. Each email has a hero image, a headline, short copy, a code block and one button.
Are these real Stripe emails?
No. They are concept emails made with AI in Nitrosend. Stripe did not make or approve them, and every email carries a note saying so.
Can I copy this flow for my own brand?
Yes. Keep the structure: act labels, one headline per email, one code or proof block and a single call to action. Swap in your own mission and facts, and keep any future claims clearly labelled as vision.
How many emails should a brand story flow have?
Twelve works for a full arc. The same pattern also works at five or six emails if you merge acts.
Sources
The emails were made with AI in Nitrosend, in one shot, by Claude Fable 5 (the flow above) and Codex 5.6 Sol (the second take), from the brief below.
The brief, page 1 of 2
The brief behind these emails
The brief, page 2 of 2
The brief behind these emails