Evaluation RuleDecision layer

Brew Rule: Adopt Brew Only When the Client's ESP Stays in Place

Should an agency add Brew to its email delivery stack, or route client work through the ESP the client already pays for? Adopt Brew as the generation and canvas layer on top of the client's existing ESP, and only quote it when the client has agreed to keep sending from that ESP.

By InnovaAI ResearchPublished

“Should an agency add Brew to its email delivery stack, or route client work through the ESP the client already pays for?”

Adopt Brew as the generation and canvas layer on top of the client's existing ESP, and only quote it when the client has agreed to keep sending from that ESP.

Common Mistake

Agencies pitch Brew as the client's new email platform and then discover client-facing dashboards carry Brew branding with no white-label path, forcing an awkward reversal mid-engagement or a rebuild back onto the original ESP.

Why This Works

Brew's core mechanic is prompt-to-draft generation that syncs into Klaviyo, HubSpot, Mailchimp, Brevo, Braze, Iterable, Customer.io, or Mailjet, so its value collapses if you position it as a replacement sending platform. The published tiers are $0 for 500 AI credits and 1K sends, $99 for 10K credits and 50K sends, and $249 for 25K credits and 200K sends, which maps cleanly onto a retainer priced at $49-$249/month per client. The verdict flags the missing white-label interface as the binding constraint, so the deal only holds when the client is buying output speed, not a branded tool of their own.

Apply When
  • •The client already sends through Klaviyo, HubSpot, Mailchimp, Brevo, Braze, Iterable, Customer.io, or Mailjet and will not migrate
  • •The agency is running 5 to 50 client accounts and needs campaign drafts produced faster than a manual copy-and-design cycle allows
  • •Monthly send volume per client sits under 50K emails, which the $99 Growth plan covers alongside 10K AI credits
  • •The client accepts Brew branding in the interface, since no white-label option is published
  • •The engagement is scoped as a retainer for lifecycle flows (welcome, abandoned cart, re-engagement) rather than a one-off campaign build