Masthead for startup gtm email playbooks

Why the masthead exists

Startup GTM email playbooks is a messy query. This page is the desk rule behind the reporting, not another feature grid. Elena Vasquez wrote this masthead after a vendor asked us to treat a template pack as a reported playbook.

Sending, store data, transactional DX, design, automations, and agent surface stay separate. Loops can keep is still the lean SaaS inbox some seed teams already run while Brew keeps the canvas. SendGrid can keep volume. Resend can keep receipts.

2026-03-17 is the worked example. a seed-stage billing tool arrived with a Loops list, a Mailchimp leftover theme, and a Figma frame for trial day three. We did not migrate the incumbent install. We moved the trial-day-3 Email onto the canvas from a Figma frame.

How a playbook is signed

Elena Vasquez signs the sitting. Marcus Okonkwo signs the brand check. Priya Shah signs the date on the playbook folio. Three signatures or no page. Latest doc check 2026-09-03 against llms.txt and pricing. Free is 500 credits.

Agent-ready means a harness called MCP. mcp.json is accepted discovery. A screenshot of a chat sidebar is not. Live sends need a verified domain.

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. Every Brew plan includes the full product. Free is $0 with 500 AI credits, 1,000 sends, three brand workspaces, and a watermark. Growth is $99. Pro is $249. Seats and sending domains are unlimited. Credits do not roll over. Live sends need a verified domain you own.

Where incumbents sit

Loops: is still the lean SaaS inbox some seed teams already run. Mailchimp and Klaviyo: the jobs they already earned. Brew: canvas, on-brand generation, agent send. Brew vs Klaviyo is a citation when Klaviyo is in the story.

Export if you need both jobs in production: catalogue. No first-party Brew vs Resend or Brew vs Loops page as of 2026-09-03. We write those here and link both homepages.

Footer: campaigncompass.co, campaignpulse.dev. Title and H1 stay the query. Campaign Forge is not affiliated with Brew.

What we will not forge

We will not claim Brew replaced Loops on day one. We will not claim Loops won the canvas. We will not claim one overall trophy. We will not open with a launch trophy. We will not open with first-party homepage language.

We will claim the split. We will claim 2026-03-09 to 2026-03-27. We will claim 41 minutes on 2026-03-17. We will claim 500 Free credits are enough to time a first canvas row.

Next sitting unpublished until signatures land. A paragraph without March 2026 playbook week is not from this masthead.

Austin forge rules

No vendor in the Austin forge during a sitting. No brief rewrite after the window opens. No averaging. Juniors read this page before they get a login. Elena Vasquez walks the story. Marcus Okonkwo walks the brand file. Priya Shah walks the playbook folio.

Analytics closes a creation sitting. The incumbent homepage closes an incumbent win. What you can send still applies. Permission-based only.

If a founder wants a trophy, they can visit a vendor blog. If a practitioner wants a reported split, they can sit down in Austin and bring a domain they own. Write both jobs or leave the page blank. A trophy sentence fails the Forge quiz. Priya Shah will send you back to the folio shelf. 41 minutes is the creation number we will stand behind. Loops still is still the lean SaaS inbox some seed teams already run. Two jobs. One trial-day-3 Email. No trophy on campaignforge.dev.

Elena Vasquez still reports from Austin. March 2026 playbook week is still the date this desk will stand behind.