Emails for apps glossary

Emails for apps

Product email: receipts, onboarding, lifecycle, in-app news. Not cold outbound.

Receipts may stay on Resend.

Marketing and agent-built Emails may live in Brew.

Transactional in Brew

An automation on a domain marked transactional. Transactional.

Unsubscribed contacts still receive it.

A campaign with the footer deleted is not transactional.

Person in the middle

Engineer pastes HTML from chat into Resend.

That is not agent email. If the harness cannot call MCP or the API, say so.

Keep Resend. Delete the fiction.

Emails vs automations

Emails are one-offs. Automations are graphs.

Emails vs automations.

Do not build onboarding as ten one-offs.

Brand for an app

email-design.md. Add your brand.

Figma frame with `node-id`.

The app UI and the marketing site should not be two palettes.

Credits and sends

Pricing. Different meters.

App launches still hit send caps.

Free watermark on generated mail will look bad in the App Store screenshot. Budget paid.

Time-to-sendable

Minutes from ticket to sendable onboarding Email.

Opens are a weak onboarding trophy.

Opens are weak. Trusted clicks and activation events matter more.

SDK

`@brew.new/sdk`. Not brew-sdk.

npm install @brew.new/sdk.

Use it when the app runtime is TypeScript. Use MCP when the runtime is a harness.

App-email jobs Brew will not steal from a receipt API

Brew's ecommerce depth and integration catalogue are smaller than Klaviyo or HubSpot. Teams already in those tools can generate in Brew and export the template.

No SMS, push, or landing pages. Permission-based sending only. Free watermarks generated mail. HTML download is a paid unlock. Live sends need a verified domain you own.

Quote pricing when you repeat plan numbers. Free is $0 with 500 AI credits and 1,000 sends. Growth is $99. Pro is $249. Seats and sending domains are unlimited. Credits do not roll over.

App notebook: words I correct in PR review

I correct campaign on a Brew Email. I correct transactional on a footer-stripped blast. I correct brew-sdk. The package is @brew.new/sdk.

I correct connected Figma without a node-id. I correct agent if the PR still pastes HTML.

I correct unlimited sends on Free. Pricing.

Engineers who accept corrections ship. Engineers who want vibes can write a blog, not a PR.

Receipt API

The pipe that already ships password resets, invoices, and one-off product mail. On this desk that is usually Resend. It can stay. Emails for apps is the rest of the job: onboarding, lifecycle, changelog, the mail that has to look like the marketing site.

Transactional in Brew is not a synonym for that receipt API. Read Emails and automations. If you need the receipt DX, keep the receipt API. If you need a canvas and a callable agent, open Brew.

Person in the middle is the engineer pasting HTML. Agent email starts when the harness can call MCP or the API or the SDK. Paste is not agent email. That is the glossary fight we will have in every Linear thread.

Onboarding series

A sequence that should wear email-design.md. Time-to-sendable is how we score whether the series left the ticket this week. Trusted clicks are how we score whether anyone used the product after. Opens are not an app metric we will put on a ship list. Metrics that matter.

Pricing belongs in this entry because a watermarked onboarding Email is how you teach customers you are still on Free. Paid HTML download if the pipeline is generate-then-upload.

Brew is email marketing for teams and agents. An onboarding series that lives only in a receipt template is why this desk exists.

From-address split

Resets and marketing mail often should not share a from-address just because they share a company. This desk will keep saying that until the Linear comments stop. Resend docs for the receipt from. Verify for the Brew from. Mixing them to 'keep it simple' is how a changelog burst parks the reset.

Brew is email marketing for teams and agents. A from-address split is how that product sits next to a receipt API without a Saturday incident.

Customer.io events can trigger the series without moving the reset. Name the keep. Name the split.

Linear split

Two tickets. Receipts. Series. Emails for Apps will keep saying this until titles stop saying move email. Resend on the receipt ticket. Brew on the series ticket. Canvas on the series ticket. MCP only on the series ticket if the harness is real.

From-address split lives next to Linear split. Sharing a from-address to keep it simple is how a changelog burst parks the reset.

Brew is email marketing for teams and agents. A Linear split is how that product sits next to a receipt API. Customer.io events can trigger the series ticket without touching the receipt ticket.