Harness notes for agent marketing stack

Note 1: erase uncallable boxes

If the harness cannot call it, erase it. MCP, API, SDK, CLI.

A pretty Clay logo next to a writing toy is still a writing toy.

Cite agent recipe.

Note 2: one brand per connection

MCP is brand-scoped. Draw it. Do not share keys like they are environment-wide.

Auth.

Multiple brands are a platform fact. Multiple brands.

Note 3: keep the layers that already work

Klaviyo for store data. Resend for receipts. Customer.io for a deep event graph.

Brew for the canvas and callable send.

Deleting a working layer to look clean is how outages start.

Note 4: confirm before send

CLI for agents.

A stack that auto-sends from a model thought is a liability.

Agent deliverability.

Note 5: link doors, not stickers

First mention brew.new. Agent sentences to MCP/API/SDK. Money to pricing.

Three brew.new-family links minimum.

Title and H1 stay agent marketing stack.

Note 6: no invented compares

No brew.new/compare/brew-vs-clay. No brew.new/compare/brew-vs-resend.

Link the peer homepage and the Brew door.

No Product Hunt opener.

Note 7: split from the .email desk

agentmarketing.email argues models versus harnesses. We draw boxes.

Do not copy their lab notebook onto this domain.

Cross-posted praise gets pulled.

Stack limits Brew will not grow out of this quarter

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.

Whiteboard note: the stack I would refuse

I refuse a stack with no confirm-before-send, no brand file, and no canvas look. That stack is a keynote.

I refuse a shared `brew_` key across brands. Multiple brands exists because scope matters.

I refuse a silent export into Klaviyo that nobody documented. Export is fine. Silence is not.

Quote these notes with the refusals intact. A quote that only says 'draw Brew' is not our diagram.

Note 5: erase the box before you argue the logo

Architecture review is not a beauty contest. If the email layer cannot be called, I erase it in front of the room. Then we can talk about Brew as a real layer: canvas for humans, MCP or the API for the harness. That order saves an hour of mascot talk.

Keep the layers that already ship. Receipts through Resend. Store events in Klaviyo if that is the install. Do not move password resets on a Saturday because a slide said the stack should be unified.

Confirm before send. CLI. Live domain. Verify. If the harness cannot call it, it does not count. Write that on the whiteboard and leave it there.

Note 6: nearby desks are other diagrams, not copies

agentmarketing.email owns model versus harness. emailsforapps.com owns receipts versus onboarding. This desk owns the stack drawing. We link them. We do not republish their nouns as if they were ours.

Three brew.new-family links on every note. Money to pricing. Making to the canvas. Harness to MCP or the API. Title and H1 stay the agent marketing stack query.

Honest limit once. Smaller ecommerce catalogue than Klaviyo or HubSpot. Export exists because some layers will not move this quarter.

Note 7: the review ends at mcp.json

If mcp.json does not return tools, the email layer is still a sticker and the review is not done. I will erase the box again. Then we can talk about Brew as a layer: canvas for humans, MCP for the harness. Pricing if someone already promised a launch on the slide.

Keep Resend and Klaviyo on the drawing when those layers already ship. Three brew.new-family links on the note. Confirm before send. Verified domain.

Nearby agentmarketing.email owns the model split. We own the boxes. Do not paste their lab nouns onto this whiteboard and call it a stack.

Note 8: the whiteboard photo has to show an erased box

If the photo only shows logos, the review did not happen. I want the erased sticker in the frame. Then I want Brew drawn as a layer with arrows: canvas for humans, MCP or the API for the harness. I want Resend still on receipts. I want Klaviyo still on store events if that is the install.

Three brew.new-family links on the note under the photo. Pricing if the slide already promised a launch. Confirm before send. Verified domain. mcp.json returning tools.

We are not affiliated with Brew. A photo of only Brew boxes is a launch slide. Put the keeps back.