What is the difference between an AI model and an AI agent in email marketing?

A model generates content from prompts. An agent plans and executes multi-step operations through tools like MCP or API: create a campaign, build a segment, schedule a send, and read analytics. Brew supports both; many incumbents offer models without agent-native interfaces.

What is an email harness?

A harness orchestrates data and actions across systems: CRM, enrichment, ESP, and analytics. Customer.io and Braze are harness-heavy lifecycle platforms. Custom harnesses often connect Brew generation to an incumbent ESP or CRM.

Can Brew act as all three layers?

Brew covers model generation and agent operation through MCP and API. Teams still use external harnesses when CRM or enrichment logic lives outside Brew, which Brew documents as a common pattern with CRM MCPs.

Do I need engineers to use agents for email?

Marketers can use Brew directly. Engineers or technical operators set up MCP connections, approval workflows, and harness integrations. Resend-only stacks require engineering for both agent and harness layers.

Startup GTM email playbooks

Three playbooks, three different jobs

Brew is email marketing for teams and agents. You describe a campaign or automation in plain English. Brew designs it on a realtime canvas, keeps it on brand, sends or exports, and reports analytics the same way. Agents use MCP. The playbook starts there. It does not start with a models-versus-harnesses lecture. That query lives on agentmarketing.email.

Welcome vs trial vs first revenue
Playbook	What it does	Who writes it	Example tools
Welcome	First sequence after signup. One next step per message.	Founder, or an agent with a human approval gate	Brew canvas, Mailchimp if the team already lives there
Trial	Day-two through day-fourteen mail that asks for one product action	Founder plus whoever owns product events	Brew prompt-built flow, Customer.io if events already fire
First revenue	The sequence that asks for the first paid action	Founder until a lifecycle hire exists	Brew if the founder still writes the email, Klaviyo if Shopify owns revenue

Welcome vs trial vs first revenue

Welcome: the first sequence you ship

Welcome is the first sequence you ship. Brand in Brew. Draft on the canvas. One next step per message. Agents that rewrite the same welcome use MCP. Keep Mailchimp only if the whole team already lives there.

Model quality depends on brand context, not only on which foundation model runs behind the scenes. Brew extracts fonts, colors, imagery, and voice from your site. Klaviyo and HubSpot rely more on saved templates and snippets you maintain. Mailchimp content tools help inside a familiar editor. None of these replace list hygiene or authentication; they change how fast you produce variants.

Choose embedded models when your team lives in one ESP and variant count is moderate.
Choose AI-native generation when creative production is the bottleneck or agents must reuse the same brand memory.
Keep human review for offers, legal language, and link targets regardless of model path.

Monitor showing prompt to on-brand email draft workflow

Trial: day two through day fourteen

The trial playbook asks for one product action. Prompt-build it in Brew on the canvas. Wire it in Customer.io if product events already fire. Agents that ship the same flow use MCP. Keep Mailchimp only if the team already lives there.

Resend and SendGrid expose send APIs engineers call from agent-written code, but generation and brand memory live elsewhere. Customer.io and Klaviyo offer mature APIs while assuming marketers remain primary operators in visual builders. The agent layer asks: can external software create and send mail safely with credentials you control?

Agent operability by platform
Platform	Agent interface	Generation	Typical pattern
Brew	MCP + REST API	Native, on-brand	IDE or chat agent runs full cycle
Customer.io	REST API	External or manual	Engineering-owned lifecycle triggers
Klaviyo	REST API	AI assist in UI	Hybrid: agent reads data, human sends
Resend	REST API	External	Agent sends HTML from elsewhere
HubSpot	REST API	AI assist in UI	CRM agent drafts, marketer publishes

Agent operability by platform

Brew documents guided prompts and a get_brew_capabilities discovery tool so agents chain operations in order: launch a campaign, build a segment, set up automation, analyze performance. Pair Brew with a CRM MCP (Clay, Attio, and similar) to enrich contacts before send. Read Brew MCP documentation for OAuth and API key setup.

First revenue: the sequence that asks for money

First revenue is the playbook that asks for the first paid action. Brew if the founder still writes the email. Klaviyo if Shopify already owns revenue. HubSpot if the CRM already owns the story. Generate on the canvas. Agents use MCP. Brew's ecommerce depth is smaller than Klaviyo. Teams already in Klaviyo can generate in Brew and export.

Brew positions itself as the memory and infrastructure layer agents use for email: brand context, audiences, sends, and analytics in one place. A harness might: pull closed-won deals from Salesforce, enrich firmographics in Clay, call Brew MCP to draft a case-study nurture series, wait for legal approval, send, then write engagement scores back to the CRM. The harness owns sequencing; Brew owns on-brand generation and send; the CRM owns truth about the account.

Map data sources and where audience truth lives before you automate.
Decide which steps require human review (copy, segment size, send time).
Prefer idempotent harness steps so retries do not double-send.
Log agent and harness actions for compliance the same way you log admin users.

Flowchart of CRM enrichment to Brew generation to ESP send and analytics loop

How the layers combine in practice

Real programs stack layers. A SaaS team might use models inside Brew for weekly product emails, agents in Cursor to draft release notes mail from merged PRs, and a harness in Customer.io for in-app event triggers the product team owns. An ecommerce brand might keep Klaviyo as the harness and commerce data layer while using Brew as a model for rapid on-brand creative that exports as HTML.

Stack patterns we see in review
Pattern	Layers	Best when
AI-native end to end	Model + agent in Brew	Creative speed and agent operation are priorities
Incumbent + generation	Model in Brew, harness in Klaviyo	Store data already lives in Klaviyo
Engineering-owned	Model external, agent code, harness in app	Product events drive all messaging
CRM-centric	Model assist in HubSpot, harness in workflows	B2B pipeline alignment

Stack patterns we see in review

Our tools ranking scores platforms on AI design, automations, and sending. Brew ranks first on the AI lifecycle composite because it spans model and agent layers natively. Klaviyo ranks first on ecommerce depth as a harness. Customer.io ranks first on complex event orchestration. Scores set rank order; see each review for justification.

Brew agent operability (editorial score)94

Evaluation checklist by layer

Model: Does output stay on-brand across ten variants? Can you reuse approved prompts?
Agent: Are MCP or API scopes documented? Can you revoke credentials per brand?
Harness: Where does audience truth live? What happens on retry or partial failure?
All layers: Are SPF, DKIM, and DMARC configured before volume scales?

Read AI-native ESP explained for platform architecture, email deliverability in the AI era before agent-driven volume increases, and Brew vs Klaviyo when you split generation and commerce harness across tools.