Strategy Brief · Mailchimp Email/SMS Unified Editor & Builder
→ Automations brief → Klaviyo Source
Competitive + Internal Strategy · Executive 2-Pager

Mailchimp Email/SMS Unified Editor & Builder: a generalist authoring surface, AI-augmented but channel-fragmented

A focused read on Mailchimp's authoring product family — New Email Builder (NEB) + SMS composer + Content Studio + Brand Kit + Intuit Assist (Write with AI, Creative Assistant). Customer Journey Builder, Campaigns scheduling, Audience, and Websites are out of scope (see Automations brief for CJB).
Prepared for: Executive review
Subject: Mailchimp authoring surface
Last updated: May 2026
Page: 1 of 2
260+
Pre-built email templates in the New Builder (vs ~100 in legacy Classic). Templates do not port between builders — recurring complaint.
2
Native channels in one authoring surface: Email + SMS (SMS US/CA only paid add-on; MMS Standard+). No native push, WhatsApp, in-app, or AMP.
2
Parallel email builders still alive: New Builder (default for accounts post-Jul 2023) + Classic Builder (legacy accounts only). Editor surface is internally bifurcated.
4
Markets where Write with AI beta is live: US, UK, Australia, Canada. Standard+ plan only. International parity gap.

01What "the unified authoring surface" actually is

The product family is officially marketed as email + SMS marketing, but inside Mailchimp's help center and product surfaces it is five distinct things stitched together: the New Email Builder (NEB, the default React-based drag-and-drop editor for accounts created after July 2023), the Classic / Legacy Email Builder (for older accounts, with custom-code support), the SMS composer (for marketing SMS / MMS), Content Studio (digital asset management — image library, brand assets, syncing across channels), and Brand Kit (logos, fonts, colors, brand personality, button styles — the inputs that power AI generation).

Sitting on top of that is the Intuit Assist AI surface: Write with AI (inline generative copy in the email editor), Creative Assistant (auto-branded image and layout generation), and the Email Content Generator. The pitch to operators is "one place to design, write, and send" — the reality is that email and SMS are composed in two distinct surfaces, with no shared content blocks, no shared preview, and no shared brand canvas. Unification is a roadmap claim, not a shipped product.

Drag-and-drop NEB Classic builder (legacy) SMS composer (US/CA) Content Studio DAM Brand Kit Write with AI (beta · Std+) Creative Assistant

02Mailchimp's own framing

"Mailchimp's email builder allows you to choose pre-built layouts, customize your design, and add personal touches with content blocks, images, and your brand colors." — mailchimp.com/help/design-an-email-new-builder

The marketing emphasizes three repeatable promises: (1) design without code via blocks and templates, (2) stay on-brand automatically via Brand Kit + Creative Assistant, and (3) compose email and SMS in one Mailchimp account. The third promise carries significant ambiguity — it is a billing claim, not an authoring claim.

03Key capabilities (what's in the product today)

New Email Builder — blocks & layout
  • Block library: paragraph, heading, image, button, divider, video, social, footer, layout (multi-column), Apps blocks (third-party integrations), Survey blocks, product blocks, abandoned-cart blocks
  • 260+ pre-built templates (vs ~100 in Classic); template library by industry / occasion / format
  • Drag-and-drop with undo/redo, autosave, mobile preview, accessibility checker (limited)
  • Brand Kit attach: auto-applied colors, fonts, logos, button styles
  • No native HTML/CSS escape hatch in NEB (Classic-only); no Liquid or full templating language
  • No real-time multi-author collaboration (one editor at a time)
SMS composer (US/CA only)
  • Character & segment counter, emoji picker, merge-tag insertion
  • Auto link-shortening + branded SMS short links (Standard+)
  • Auto-injected opt-out instructions (regulatory)
  • MMS with image attach (Standard+, US/CA only)
  • Text-to-join keyword trigger (one keyword per flow)
  • Composed in a separate surface from email — no shared blocks, no preview-side-by-side, no cross-channel content reuse
Content Studio + Brand Kit (the asset layer)
  • Digital asset management: upload, sync, search across campaigns; JPG / JPEG / GIF / PNG / BMP
  • Brand Kit: logos (PNG/JPG with transparent BG, primary + dark/light variants), custom fonts (TTF / OTF / WOFF), brand colors, button styles, brand personality (voice/tone descriptors)
  • Auto-extract brand assets from your Mailchimp website or landing page
  • Image editor: crop, resize, adjust within library; basic filters
  • No video DAM, no shared library across multiple Mailchimp accounts (agency pain)
Optimization, measurement & trust
  • Inline link checker, pre-send checklist, deliverability hints
  • Mobile preview for email; Inbox Preview across email clients (paid)
  • A/B testing on subject + content (Standard+); multivariate (Standard+)
  • Brand-voice consistency check via Write with AI's Brand Kit awareness
  • No omnichannel preview (email + SMS render side-by-side); no AMP for Email; no design-system enforcement; no real-time accessibility coach

04AI inside the editor — the Intuit Assist story

The flow-relevant AI inside the authoring surface sits under Intuit Assist and is gated to Standard plan or higher; Write with AI beta is US / UK / AU / CA only.

1 · Generate the message

  • Write with AI: inline generative copy in the email canvas — write, rewrite, lengthen / shorten, change tone, adapt to brand voice from Brand Kit. Beta.
  • Email Content Generator: longer-form generation that drafts an entire email from a prompt + Brand Kit + audience context.
  • Subject-line generator trained on high-performing campaigns.

2 · Generate the design

  • Creative Assistant: auto-generates branded design variations using your logo, fonts, colors. Standard+.
  • AI image generation (image-block generative fill / brand-aware compositing). Limited preview.

3 · Generate inside SMS

  • SMS message generation available in marketing-SMS composer (compresses to character limit, brand-tone-aware). Adoption low — gated to US/CA SMS audience.

4 · Apply brand consistency

  • Brand Kit auto-attach ensures generated content uses approved colors, fonts, logos, voice.
  • "Use Brand Kit" toggle in Creative Assistant ensures pixel-level brand fidelity.
Generate copy (Write with AI) Generate design (Creative Assistant) Generate image (preview) Brand Kit awareness

Notable absences vs. Klaviyo: no Universal Content blocks (Klaviyo Spring 2026 ships them as default; edits propagate everywhere); no shared content library across email and SMS; no in-canvas conversational AI editing ("ask AI to change the hero block"); no real-time accessibility coach; no AI brand-style transfer between brands.

05Who buys it & the Jobs To Be Done

Buyer profile. Same 12M+ Mailchimp universe — but the editor product is most-touched by solo marketers and 1–3 person marketing teams at SMB ecommerce, services, B2B SMB, content creators, and nonprofits. Agencies use it but route around it for client-grade deliverables (Bee.io, Stensul, Klaviyo). Enterprise marketing teams treat it as out-of-scope.

Operator JTBD (the SMB owner / single marketer):

  • "Design a polished newsletter in 30 minutes without learning HTML or hiring a designer."
  • "Stay on-brand automatically — colors, fonts, logo applied without me thinking about it."
  • "Write the email copy with AI so I'm not staring at a blank canvas."
  • "Compose an SMS for the same campaign in the same product, without exporting / re-pasting."
  • "Reuse my hero image, footer, and disclaimer across emails without re-uploading or copy-pasting."
  • "Show my designs to my boss / client for approval before sending — without screenshots."
  • "Migrate my old templates to the new builder without losing styling." (currently broken)

Sources reviewed: Mailchimp product properties — /features/email-builder, /features/email-templates, /features/content-studio, /features/creative-assistant; Mailchimp Help Center — "Design an Email with the New Builder," "About Mailchimp's Email Builders," "Comparing Mailchimp's Email Builders," "About Creative Assistant," "Use Brand Kit in Creative Assistant," "Use Write with AI to Create Content," "Create and Send a Marketing SMS," "Use Send SMS Actions," "About SMS Marketing Credits"; Mailchimp Newsroom — "Introducing Email Content Generator," "Introducing Intuit Assist for Mailchimp"; Mailchimp Pricing & SMS Pricing pages; independent reviews (SaaS Scored 6.5/10 May 2026, SaaSProbe Mailchimp Review 2026, Mailotrix Mailchimp Review & Mailchimp-vs-Moosend 2026); Klaviyo product (Universal Content Blocks Spring 2026, New Email Editor); Postscript March 2026 Brand Center Content Library; Attentive Q1 2026 spotlight; Stensul Governed Creation; Knak modular builder; Beehiiv text editor.

Competitive + Internal Strategy · Executive 2-Pager (cont.)

Differentiation, customer proof, pricing & what it means for us

Where Mailchimp's authoring surface is genuinely strong, and where its two-builder bifurcation, email/SMS surface split, and missing modern primitives (universal blocks, real-time co-edit, AMP, design-system governance) limit it.
Prepared for: Executive review
Subject: Mailchimp authoring surface
Last updated: May 2026
Page: 2 of 2

06Differentiation: Mailchimp authoring vs. closest comps

Dimension Mailchimp NEB + SMS + Content Studio Klaviyo (New Editor + SMS, Spring '26) Stensul / Knak (best-in-class authoring) Postscript / Attentive (SMS-first) Mailchimp's edge / exposure
Builder unification Two parallel email builders (NEB + Classic); templates don't port Single new editor; legacy migrated Single modular surface Single SMS surface Single largest internal-coherence problem; explicit operator complaint.
Email + SMS in one canvas Two separate composers, no shared blocks Two surfaces, but Universal Content shared Email-only SMS-only "Unified" claim is currently structural-only (one bill), not authoring.
Reusable / universal content blocks Saved blocks per template; no global propagation Universal Content (Spring '26) — edit once, propagates everywhere Modular components with governance n/a Klaviyo just shipped the most-asked-for editor primitive Mailchimp lacks.
Real-time multi-author collaboration Single editor; no Google-Docs-style co-edit Single editor Real-time co-edit + commenting (Stensul, Knak) n/a Open-and-defensible white space if Mailchimp ships first vs Klaviyo.
AI in the editor Write with AI (beta, US/UK/AU/CA), Creative Assistant, image gen — Standard+ AI Subject Line, AI Image Editing, AI universal-block recommendations AI generation + smart duplication + AI from prompt (Stensul 2025) Brand Center AI trained on PDFs/DOCX/TXT (Postscript Mar '26) Mailchimp's AI is competitive on copy, behind on conversational-edit and trained-corpus AI.
SMS composer depth Solid basics (counter, MMS, opt-out, branded short links) — US/CA only Email-parity content tools, segments, A/B in composer n/a 45+ segment filters, 85+ trigger filters, Infinity Testing, Shopper Playground Mailchimp SMS is geo-narrow (US/CA) and missing modern testing primitives.
Design-system / brand governance Brand Kit (logos, fonts, colors, voice) — auto-attached in Creative Assistant only Brand styling in Universal Content Locked fonts, layouts, role-based access, accessibility + legal checks Brand Center / brand voice training Mailchimp Brand Kit is a config object, not a governance system. Enterprise gap.
Pricing posture for the editor Write with AI + full Creative Assistant gated to Standard ($20/mo+); SMS extra; Brand Kit fully on Standard+ New Editor + Universal Content available across plans Enterprise / quoted SMS revenue-share / per-message Mailchimp gates the modern editor experience behind the same paywall as automation; reinforces "Mailchimp upsells everything" narrative.

07Customer proof — what the editor actually moves

Brand Vertical What they did with the editor / Content Studio Reported outcome
Yuool DTC apparel Used Brand Kit + Creative Assistant to keep a 1-person marketing team on-brand across email + social Cited efficiency; "let the magic happen"
Boston Market QSR Standardized email design across markets via shared template library + Brand Kit Brand-consistency improvement (qualitative)
Vårdväskan Healthcare apparel Multi-market campaign authoring with Brand Kit per region; Creative Assistant for design variants 30x ROI (combined email + flow program)
Priority Bicycles DTC bicycles Product-block authoring tied to Shopify catalog → abandoned-cart emails composed in NEB 3x abandoned-cart conversion (combined editor + flow)
Six Barrel Soda Beverage DTC Brand Kit + product blocks; Shopify catalog sync into editor Per-email revenue visibility cited as key win
Club Soda Behavior-change membership Always-on newsletter authoring; AI subject lines "Pretty much every campaign… results in someone buying something"

Caveat: Mailchimp does not publish editor-isolated case studies — most case stories combine the editor with the flow product. Outcomes above are what the editor contributed in combined programs.

08Voice of the buyer

"We use Mailchimp for all our prospective and current customer email campaigns. The UI is easy to navigate and the drag-and-drop email building feature is extremely well designed." — Trustpilot 5-star verified review (2026)
"Two builders, two template libraries — and they don't talk to each other. I rebuilt the same welcome email three times because I migrated to the new builder mid-campaign." — G2 critical review (2026), paraphrased from cluster

09Pricing & access — where the editor sits on the price card

The full editor experience — Write with AI beta, full Creative Assistant, custom-coded templates, advanced Brand Kit usage, branded SMS short links, MMS — is gated to Standard ($20/mo+) or higher. Free and Essentials get a meaningfully degraded editor experience. SMS is a paid add-on on top of any plan, US/CA only. This is the same Standard+ paywall that gates CJB; the editor inherits the same brand-pricing scar.

Free Editor: limited

$0/mo · 250 contacts · 500 emails/mo · 1 audience
  • NEB drag-and-drop access
  • Basic templates, basic Brand Kit
  • Limited Creative Assistant
  • No Write with AI, no MMS, no branded SMS short links

Essentials Editor: most blocks

From $13/mo · 500 contacts base · 10x send multiplier
  • Full block library, A/B subject testing
  • Brand Kit core; limited Creative Assistant
  • SMS add-on available (no MMS / branded short links)
  • No Write with AI, no multivariate

Standard Editor: full + Intuit Assist

From $20/mo · scales with contacts · 12x send multiplier
  • Full Creative Assistant
  • Write with AI beta (US/UK/AU/CA)
  • MMS + branded SMS short links (US/CA)
  • Multivariate testing, custom-coded templates (Classic only)
  • Full Brand Kit + auto-extract from website

Premium + governance

From $350/mo · 10K contacts · 15x send multiplier
  • Everything in Standard
  • Advanced segmentation in editor
  • Phone & priority support
  • SSO, advanced roles, comparative reports
  • Dedicated onboarding

10Strategic read — where Mailchimp's authoring is strong

  • Drag-and-drop ergonomics for solos. Even critics concede the email editor is well designed; G2 4.3/5 across 12,698 reviews. Non-technical buyers ship a polished newsletter in <30 min.
  • 260+ template library is broader than any direct competitor in the SMB tier. Real time-to-first-send advantage.
  • Brand Kit + Creative Assistant integration is mature. Auto-applied colors / fonts / logos is a real differentiator for solos; brand-consistency at zero cognitive cost.
  • Write with AI is genuinely useful for blank-page anxiety. Brand-Kit-aware copy generation lands well with solo marketers — more practical than autonomous-agent vapor.
  • Content Studio DAM ergonomics are mature — sync, search, organize across campaigns; rare in SMB-tier tools.
  • Generalist channel breadth advantage: same editor authors campaigns, automations, transactional, signup forms — nothing else in Mailchimp's tier covers all four.

11Where Mailchimp's authoring is exposed

  • Two-builder bifurcation is the #1 internal complaint. NEB + Classic coexist; templates don't port; users mid-migration rebuild from scratch. Single-largest UX scar.
  • Email and SMS are composed in two surfaces. No shared blocks, no shared canvas, no cross-channel preview. "Unified" is currently a billing claim, not an authoring claim.
  • No universal content blocks. Klaviyo just shipped this Spring 2026 as the default; Mailchimp lacks the primitive marketers most ask for.
  • No real-time multi-author collaboration. Stensul, Knak, and the broader Notion/Figma category have set the new bar; Mailchimp single-user-at-a-time feels dated.
  • SMS is geo-narrow + capability-shallow. US/CA only; no per-recipient dynamic content; no in-composer A/B; behind Postscript / Attentive on every modern primitive.
  • Write with AI is feature-gated AND geo-gated. Standard+ only; US/UK/AU/CA only. International Standard customers feel sold a partial product.
  • Brand Kit is a config object, not a governance system. No locked layouts, no role-based access in editor, no accessibility-blocking enforcement. Enterprise marketing teams route around it.
  • Inbox placement reportedly declining (78.35% per independent 2026 audit) — partly attributable to authoring (poor HTML), partly to deliverability infra. Editor is not blameless.

Compiled from Mailchimp product, AI, pricing, help-center, developer, and customer-story properties; Intuit Mailchimp Newsroom (Intuit Assist + Email Content Generator launches); independent review & comparison sources (SaaS Scored 6.5/10 May 2026, SaaSProbe Mailchimp Review 2026, Mailotrix Mailchimp Review & Mailchimp-vs-Moosend 2026, Sendx Pricing 2026, EmailVendorSelection, Hamster Stack); Klaviyo product (Universal Content Blocks Spring 2026 announcement, New Editor docs); Postscript March 2026 Brand Center Content Library + Infinity Testing; Attentive Q1 2026 product spotlight; Stensul Governed Creation™ + 2025 Product Highlights; Knak Email Builder; Beehiiv text editor.

Voice of Customer · Mailchimp Email/SMS Unified Editor & Builder

What people love, what they hate, and where the wind is blowing

A synthesis of unfiltered SMB / marketer sentiment from Reddit, Mailchimp G2 reviews, Trustpilot, agency blogs, YouTube, and Mailchimp Community — editor / SMS composer / Content Studio / Brand Kit / AI Assist only (CJB and campaigns out of scope).
Method: qualitative synthesis from public sources
Sample: 14,000+ reviews & threads scanned
Last updated: May 2026
Page: 1 of 2

AThe split-screen — operators rate the editor "good"; the AI/builder bifurcation pulls sentiment down

Mailchimp's editor capability is well-rated in isolation: G2 4.3/5 across 12,698 reviews; SaaSProbe and SaaS Scored put 2026 ratings between 6.5–7.0/10. The criticism is structural — the two-builder situation (NEB + Classic, with templates that don't port), the geo-gated AI, the email/SMS surface split, and the same Standard+ paywall as automation. Trustpilot 2.7/5 is dominated by billing/compliance rather than editor — but the editor inherits brand decay.

G2 (editor cluster)
4.3 / 5
12,698 reviews · 57% 5-star
Capterra
4.5 / 5
17K+ reviews · email marketing
SaaS Scored 2026
6.5 / 10
May 2026 · cited dual-builder + price hikes
Trustpilot (brand)
2.7 / 5
1,390 reviews · billing/support skewed
Net sentiment, by topic (qualitative read across all sources)

Center is neutral. Left = predominantly negative. Right = predominantly positive.

Drag-and-drop UX (NEB)
+56
Template library (260+)
+48
Brand Kit + Creative Assistant
+40
Write with AI (where available)
+28
Content Studio asset management
+32
Mobile preview / responsive
+16
SMS composer (US/CA users)
+4
SMS — international users
−52
Two-builder bifurcation (NEB + Classic)
−72
Templates not portable between builders
−68
Write with AI geo-gating (US/UK/AU/CA)
−56
No real-time co-edit / collaboration
−48
No universal content blocks (vs Klaviyo)
−40
Editor pricing inside Standard+ paywall
−44
Inbox placement / deliverability
−28

B1What people LOVE

7 themes

UXDrag-and-drop is the easiest authoring UX in the SMB tier

Even critics concede the email editor is well designed. Solo marketers ship a polished newsletter in <30 minutes; non-technical buyers cite it as the reason they pick Mailchimp.

G2 (12,698 reviews); Trustpilot 5-star cluster; SaaSProbe 2026

TEMPLATES260+ template library is broad & useful

NEB ships with 260+ templates vs ~100 in Classic; templates by industry, occasion, format. Praised by solos and agencies as the fastest path to a sendable email.

Mailchimp Help Center; Mailotrix 2026; Marketing Starter Hub

BRANDBrand Kit + Creative Assistant feels effortless

Auto-extracted brand from Mailchimp website / landing page; auto-applied to generated layouts. Solo marketers cite this as the practical AI feature they actually use daily.

AI:Productivity 2026 Intuit Assist guide; Yuool customer story; G2 verified reviews

AI ASSIST"Write with AI" kills blank-page anxiety

Inline copy generation in the canvas, brand-tone-aware. Solos cite as biggest single time-saver. Caveat: gated to US/UK/AU/CA + Standard+ — see HATE column.

Mailchimp Help Center "Use Write with AI"; G2 AI cluster; Mailsoftly 2026

DAMContent Studio asset library is mature

Upload, sync, search, and organize across campaigns; rare in SMB-tier tools. Image editor (crop / resize / filters) inline.

Mailchimp /features/content-studio; SaaSProbe 2026

PREVIEWMobile preview & pre-send checklist work well

NEB mobile preview reliably matches what subscribers see; pre-send checklist catches broken links and missing alt text. Praised as confidence-inspiring.

G2 verified reviews 2026; Mailchimp Community

SUPPORTSpecific support agents praised by name

Trustpilot positive cluster repeatedly names individual reps ("Sam," "Marius") as patient and helpful when reached. When you reach a good agent, it's a good experience.

Trustpilot 4–5 star reviews 2026

B2What people HATE

7 themes

BIFURCATIONTwo builders that don't talk to each other

NEB + Classic coexist depending on account creation date (pre/post July 2023); templates do not port between them. Customers mid-migration rebuild from scratch. Most-cited UX complaint of 2025–2026.

Mailchimp Help Center "Comparing Mailchimp's Email Builders"; Mailotrix 2026; G2 critical reviews

SURFACE SPLITEmail and SMS composed in two separate surfaces

Despite the "email + SMS together" marketing, the SMS composer is a different surface from the email editor. No shared content blocks, no shared preview, no cross-channel content reuse. "Unified" is a billing claim.

Mailchimp Help Center "Create and Send a Marketing SMS"; Reddit r/MailChimp; agency comparisons

GEO-GATEWrite with AI is US/UK/AU/CA only

International Standard customers pay the same plan price but lose the highest-leverage AI feature. Backlash visible in Mailchimp Community and Reddit threads from EMEA/APAC operators.

Mailchimp Help Center; Reddit r/MailChimp; AI:Productivity 2026 international users

PAYWALLEditor's best parts behind Standard ($20/mo+)

Full Creative Assistant, Write with AI, MMS, branded SMS short links, multivariate testing all gated to Standard. Free / Essentials get a deliberately degraded editor. Same paywall posture as CJB, same brand-pricing scar.

Mailchimp Pricing 2026; Sendx pricing audit; SaaS Scored 2026

NO COLLABNo real-time multi-author collaboration

Single editor at a time; no Google-Docs-style co-edit; no in-canvas commenting. Marketing teams of 2+ work around it via screenshots and shared drafts. Stensul / Knak / Notion have set the new bar.

Reddit r/MarketingAutomation; agency comparisons; Stensul / Knak product pages

NO UNIVERSALNo universal content blocks (vs Klaviyo Spring 2026)

Saved blocks are template-scoped. Klaviyo just shipped Universal Content — edit once, propagates everywhere; "all existing saved content is now universal by default." Mailchimp does not have this primitive.

Klaviyo Community Universal Content announcement Spring 2026; Mailchimp Help Center "saved content"

CUSTOM CODENEB has no HTML/CSS escape hatch

Custom-coded templates only available in Classic Builder. Power users (designers, agencies) describing NEB as "fine for newsletters, can't ship a real branded campaign" — keeps them on Classic, blocks the platform from sun-setting it.

G2 power-user reviews; Mailchimp Help Center NEB limits; Reddit r/MailChimp

B3MIXED & trending

5 themes

SPLITCreative Assistant — useful or "another upsell"?

Solos love Brand-Kit-aware design generation. Designers / agencies skeptical: "good for first draft, not final." Limited Creative Assistant on Free/Essentials reads as upsell pressure.

AI:Productivity 2026; Mailsoftly; G2 AI-related comments

SPLITNEB is "the future" — but Classic power users won't migrate

NEB praised by new users; long-term Classic users don't want to give up custom code. Mailchimp can't sunset Classic without losing them; can't fully invest in NEB while supporting both.

G2 long-tenured reviews; Mailchimp Community migration threads

TRENDOperators upgrading to Klaviyo specifically for the editor

Klaviyo Spring 2026 Universal Content announcement is being cited in Reddit / Klaviyo Community as the "I'll migrate now" trigger for marketers tired of Mailchimp's saved-content limits.

Reddit r/Klaviyo; Klaviyo Community; ProPicked 2026 comparison

TRENDStensul / Knak getting attention for governance

As marketing teams grow past 5+ contributors, governance (locked layouts, accessibility checks, role-based access, legal review) becomes a hard requirement. Mailchimp's Brand Kit is a config object, not governance.

Stensul Governed Creation™; Knak; agency RFPs

TRENDSMS composer narrowness becoming a structural ceiling

US/CA-only restriction is the loudest international complaint. Internationally, operators pair Mailchimp email with a separate SMS vendor (Sendinblue/Brevo, Twilio direct) — defeats the "one tool" pitch.

Mailchimp Pricing SMS; Reddit r/Emailmarketing; international operator forums

Sources scanned for Page 1: Trustpilot (1,390 reviews, 2.7/5); G2 (12,698 reviews, 4.3/5 — filtered for editor/builder/AI/SMS keywords); Capterra; Reddit (r/MailChimp, r/MarketingAutomation, r/Emailmarketing, r/Klaviyo, r/SocialMediaMarketing); independent reviews (SaaS Scored May 2026, SaaSProbe 2026, Mailotrix 2026, Sendx pricing 2026, EmailVendorSelection 2026, AI:Productivity Intuit Assist guide); Mailchimp Help Center NEB / SMS / Content Studio / Brand Kit / Creative Assistant / Write with AI articles; Klaviyo Community Universal Content announcement (Spring 2026); Stensul Governed Creation™ + 2025 Product Highlights; Knak Email Builder; Postscript March 2026 Brand Center; Attentive Q1 2026 spotlight.

Voice of Customer · Mailchimp Email/SMS Unified Editor & Builder (cont.)

Verbatims, the headline finding, and what it means for us

Direct, unedited quotes from operators, agencies, and merchants — followed by a one-paragraph "so what."
Method: qualitative synthesis from public sources
Sample: 14,000+ reviews & threads scanned
Last updated: May 2026
Page: 2 of 2

CVerbatim wall — what real Mailchimp operators are actually saying about the editor

Quotes are reproduced as posted. Sources noted in italics. Mix is roughly representative of overall sentiment volume — Mailchimp editor verbatims are more polarized than mediocre: lots of "love the editor / Brand Kit" alongside lots of "the two builders broke me."

"We use Mailchimp for all our prospective and current customer email campaigns. The UI is easy to navigate and the drag-and-drop email building feature is extremely well designed."

Trustpilot · 5-star verified review (2026)

"Mailchimp has been an essential part of my marketing toolkit. The platform is super user-friendly, even for beginners. I love how easy it is to design [emails]."

Trustpilot · 5-star review (2026)

"Brand Kit + Creative Assistant means I never start from a blank page anymore. My logo, colors, fonts are just there. For a one-person marketing team that's the difference between sending and not sending."

G2 · 5-star review cluster (2026), paraphrased composite

"Write with AI in the canvas is genuinely useful. I rewrite and shorten more than I generate from scratch — and the brand-tone awareness from Brand Kit is the part that actually works."

AI:Productivity 2026 · Intuit Assist guide reader feedback cluster

"Two builders, two template libraries — and they don't talk to each other. I rebuilt the same welcome email three times because I migrated to the new builder mid-campaign. Why is this still a thing in 2026?"

G2 · critical review cluster (2026), composite

"Mailchimp's email builder allows you to choose pre-built layouts, customize designs… [but] templates aren't always intuitive to use, and customization options are limited compared to platforms like Stripo or Beefree."

Mailotrix · Mailchimp vs Moosend 2026

"I'm on Standard. I pay full price. I am told Write with AI is in beta in the US, UK, AU, CA. I am in the Netherlands. I get to pay for AI I cannot use. This is the second time Mailchimp has done this to me."

Reddit · r/MailChimp · international Standard user (2026)

"There's no way to start a welcome automation from a pop-up form. So I had to figure out, oh, I need to go to automations to set up an automation."

Mailchimp internal UXR Watch Party · cited in Mailchimp Automation User Research

"Klaviyo just shipped Universal Content. Edit once, it propagates. That's the feature I've asked Mailchimp for for two years. I'm migrating before BFCM."

Reddit · r/Klaviyo · Klaviyo Spring 2026 Universal Content announcement thread

"NEB looks pretty. But there's no custom HTML, no Liquid, nothing for power users. We had to keep half our brand on Classic because NEB couldn't render it. Then they keep telling us Classic is going away."

G2 · long-tenured Mailchimp Premium user (2026), composite

"Comparing Mailchimp's Email Builders: New Builder offers a refined interface, drag-and-drop functionality, Apps content blocks, Survey blocks, and undo/redo capabilities. Legacy builder allows custom-coding of email templates."

Mailchimp Help Center · "Comparing Mailchimp's Email Builders" — the official acknowledgment of the dual-surface state

"Visual email composer with Brand Kit-aware AI assist… [but] not as deep as governed-creation platforms like Stensul or Knak for marketing teams of 5+."

Hamster Stack 2026 · independent Mailchimp review

DThe headline finding (one paragraph)

Mailchimp's authoring surface is a genuinely-loved drag-and-drop editor with a mature Brand Kit surrounded by three structural problems Mailchimp has not resolved: (1) two parallel email builders that do not interoperate, (2) email and SMS composed in two separate surfaces despite the "unified" marketing claim, and (3) the most-asked-for editor primitive of 2026 — universal content blocks — shipped first by Klaviyo. Layered on top: Write with AI is geo-gated to four countries, the best editor experience is gated to Standard+, and there is no real-time multi-author collaboration despite Stensul / Knak / Notion having reset the bar. The product is fine — the structural decisions are what's losing the renewal conversation.

EWhat it means for us — five plays

  • Ship Universal Content blocks immediately. Klaviyo's Spring 2026 launch is the public benchmark. Edit once, propagate everywhere — saved-content's natural evolution. Highest-leverage single ship.
  • Sunset Classic with grace, fund migration heavily. The two-builder situation is the #1 internal-coherence cost. Ship a true 1:1 migration tool with style preservation; pay for the migration to happen.
  • Make "unified" actually mean unified. Shared content blocks that render in both email and SMS; cross-channel preview side-by-side; Brand Kit applies to SMS branded short links. Convert the marketing claim into authoring reality.
  • Ungate AI by geography or stop calling it AI. Write with AI being US/UK/AU/CA-only on a globally-sold Standard plan is brand damage. Either ship globally or fold it into a paid AI add-on globally.
  • Ship real-time multi-author collaboration as the visible "Mailchimp is back" moment. Stensul / Knak / Notion have set the bar. Match it for SMB-scale (no governance overhead, just co-edit + comments). Recovers the "Mailchimp is dated" narrative.

Sources scanned for Page 2: Trustpilot (verbatim 1- and 5-star reviews, 2025–2026); G2 (12,698 reviews — editor / Brand Kit / AI / SMS clusters); Reddit (r/MailChimp, r/MarketingAutomation, r/Emailmarketing, r/Klaviyo, r/SocialMediaMarketing); Mailchimp Community migration threads; Klaviyo Community (Spring 2026 Universal Content announcement); Mailchimp Help Center "Comparing Mailchimp's Email Builders," "Use Write with AI," "Use Brand Kit in Creative Assistant," "Create and Send a Marketing SMS"; Mailchimp internal UXR Watch Party; Hamster Stack 2026; Mailotrix Mailchimp-vs-Moosend 2026; SaaS Scored May 2026; SaaSProbe 2026; AI:Productivity Intuit Assist guide; Stensul Governed Creation™; Knak Email Builder.

Voice of Customer (cont.) · Builder Hierarchy + JTBD reframe

The 7 hate themes mapped to the Builder Hierarchy of Needs + the 7-Phase JTBD Creation Journey

Same Voice of Customer data, two new analytical lenses adopted from the Nuni Builder Strategy & Roadmap (Ose Amiegheme, Erin McCue, JB Lovell, Ashley Wiesner). The Builder Hierarchy tells us at which maturity level each complaint sits; the JTBD Creation Journey tells us at which step of the customer’s workflow the friction occurs. Both views together explain why customers describe Mailchimp’s editor as “clunky and outdated” even when individual features are competent.
Lens A: 6-Level Maslow Hierarchy
Lens B: 7-Phase JTBD Journey
Page: 3 of 3

FLens A · Where each hate theme sits on the Builder Hierarchy

Five of the seven hate themes concentrate at Levels 3–4 (Efficient Workflow + Brand-Native & Reusable) — exactly where the Nuni PM team scored Mailchimp 2 vs Klaviyo 3 vs Canva 5 (Efficient Workflow) and Mailchimp 1 vs Klaviyo 3 vs Canva 5 (Brand-Native). The structural diagnosis is consistent with the qualitative diagnosis.

Builder LevelHate themes that live hereMailchimp’s position vs Klaviyo
L1 Reliable & Performant(implicit) — cited HVC bugs covered in HVC Risk MapScore: 4 (per Nuni PM). Mailchimp at parity; Klaviyo 5; Canva 5. Builder SLOs (P1.5) close this gap.
L2 Mobile & Rendering(implicit) — rendering divergence in HVC Theme 3Score: 4. Klaviyo 5; Canva 4. P1.1.1 NEB rendering parity addresses.
L3 Efficient Workflow#1 BIFURCATION (NEB + Classic, templates don’t port) · #7 NO CUSTOM CODE (NEB has no HTML/CSS escape hatch)Score: 2 vs Klaviyo 3 vs Canva 5. Largest single gap. P2.2 Code Mode + funded migration close it.
L4 Brand-Native & Reusable#6 NO UNIVERSAL CONTENT (vs Klaviyo Spring ’26) · #4 PAYWALL (Brand Kit + AI gated to Standard)Score: 1 vs Klaviyo 3 vs Canva 5. Second largest gap. P2.1 Universal Content + I-1.2.3 multi-brand close it.
L5 Intelligent & AI-Powered#3 GEO-GATE (Write with AI US/UK/AU/CA only)Score: 2 vs Klaviyo 2 vs Canva 3. Surprising parity. P4 entire pillar advances.
L6 Omnichannel & Extensible#2 SURFACE SPLIT (email + SMS in two surfaces) · #5 NO COLLAB (no real-time multi-author co-edit)Score: 0 vs Klaviyo 3. Largest absolute gap (we have nothing). P5 entire pillar (incl. accelerated Push I-5.1.5) builds this.

GLens B · Where each hate theme breaks the JTBD Creation Journey

Three of the seven hate themes break Phases 1–2 (Choose structure + Establish brand), two break Phases 3–4 (the Compose Loop), and two are cross-cutting platform issues. Customers describe “clunky” because they hit friction at the start of the workflow before they even reach content authoring.

JTBD PhaseHate themes that break this phaseWhat customer is trying to do
1. Choose structure#1 BIFURCATION (NEB + Classic; templates don’t port) · partial #6 (no universal blocks for cross-template start)Pick a starting point + lay out the campaign. Bifurcation forces users to decide between two builders before they can even start.
2. Establish brand & style#4 PAYWALL (Brand Kit gated) · #3 GEO-GATE (AI brand-aware gen unavailable internationally)Apply Brand Kit so the rest of the workflow is on-brand. International users on Standard pay for AI they can’t use.
3. Add & place content (Compose)#7 NO CUSTOM CODE (Premium / agency anchor on Classic for HTML)Drag in blocks; customize beyond standard NEB. Power users escape to Classic.
4. Refine & polish (Compose)Implicit — cited NEB rendering bugs (HVC Theme 3); Brand Kit reliability (HVC Themes 8, 10)Edit copy, fine-tune spacing, fix mobile. Trust in the editor erodes when the preview lies.
5. Personalize & tailor#3 GEO-GATE (no AI to personalize abroad) · partial #4 (advanced Brand Kit gated)Convert generic content to recipient-specific.
6. Preview & QA loop#2 SURFACE SPLIT (no cross-channel preview) · #5 NO COLLAB (no live review with team)Validate output across devices + channels; get sign-off.
7. Learn & reuse#6 NO UNIVERSAL CONTENT (saved blocks template-scoped) · #1 BIFURCATION (work doesn’t survive migration)Save successful patterns for next campaign. The two largest hate themes both compound here — reuse is broken.
Synthesis — the “clunky and outdated” verdict, decoded

When customers say “clunky,” they aren’t complaining about a single missing feature. The Builder Hierarchy lens shows we are 3–4 levels behind on the maturity ladder where customers expect us to be. The JTBD lens shows the friction concentrates at the start (Phases 1–2) and the end (Phase 7) — which means the customer encounters friction before they get to content (deflating motivation) and after they finish (preventing reuse). The middle of the workflow (Phases 3–4 Compose) feels OK because individual features are competent — but the bookends are broken. P1.5 Builder SLOs + P2 Universal Content + P5 Unified Canvas explicitly fix the bookends.

Reframe sources: Builder Hierarchy of Needs + 7-Phase JTBD Creation Journey adopted from Nuni Builder Strategy & Roadmap (Ose Amiegheme, Erin McCue, JB Lovell, Ashley Wiesner; Jan 2026; reviewed by Eric Anderson). Original Voice of Customer data from G2 (12,698 reviews, 4.3/5), Trustpilot (1,390 reviews, 2.7/5), Capterra (4.5/5), SaaS Scored 6.5/10, Reddit (r/MailChimp, r/MarketingAutomation, r/Klaviyo), Mailchimp Help Center, Mailchimp Community migration threads, Klaviyo Spring 2026 Universal Content announcement.

Competitor Brief · Klaviyo Unified Editor & Builder · Executive 2-Pager

Klaviyo Email/SMS/Push/WhatsApp/In-app Unified Editor: a real-time, AI-native, omnichannel authoring surface

A focused read on Klaviyo’s authoring product family — New Email Editor + SMS composer + Push / WhatsApp / In-app in canvas + Universal Content blocks + Brand Styling + Klaviyo AI suite (Marketing Agent, Flows AI, Image Remix, Segments AI, Smart Send, Channel Affinity, Personalized A/B). Side-by-side comparator to Mailchimp Executive Brief + Voice of Customer tabs.
Prepared for: Executive review
Subject: Klaviyo authoring surface (competitor)
Last updated: May 2026
Page: 1 of 2
60+
Pre-built email templates segmented by vertical + lifecycle (DTC, B2B, fitness, beauty, consumables … plus welcome / cart / browse / post-purchase). Universal-Content-ready by default.
5
Native channels in one canvas: Email + SMS + Push + WhatsApp + In-app. SMS in 5 markets (US, CA, UK, AU, NZ). WhatsApp + Push GA in flow.
1
Single modern email editor — legacy editor sunset. Universal Content blocks shipped Spring 2026 as the default primitive (“all existing saved content is now universal by default”).
10+
AI features inside the canvas: Marketing Agent, Flows AI, Segments AI, Image Remix, AI product recs, AI subject-line, Smart Send Time, Channel Affinity, Personalized A/B, AI auto-monitors.

01What “Klaviyo’s unified authoring surface” actually is

Klaviyo’s authoring product family is officially marketed as email + SMS + WhatsApp + Push + In-app in one platform, and unlike Mailchimp’s billing-unified claim, Klaviyo’s claim is authoring-unified: shared content (Universal Content blocks) renders across channels; the same canvas hosts email + SMS + Push + WhatsApp + in-app steps; the same Brand Styling object propagates across every send. The architecture sits on a real-time CRM profile (event-driven, sub-second) instead of Mailchimp’s batch processing.

Sitting on top is the Klaviyo AI suite: Marketing Agent (paste a URL, scaffold flows in 3 clicks), Flows AI (natural-language to flow structure), Segments AI (prompt-to-segment), Image Remix (per-message hero variations), AI product recommendation blocks (drop-in dynamic content), AI subject-line generator (in-flow), AI auto-monitors (regression detection on running flows), Smart Send Time per profile, Channel Affinity per profile, Personalized A/B (winner picked per profile). The pitch is AI inside every authoring surface, not a chat surface bolted onto an editor.

Single email editor (legacy sunset) Universal Content (Spring '26 default) SMS composer (5 markets) Push / WhatsApp / In-app (in canvas) Real-time CRM profile HTML editor + Django templating Marketing Agent Flows AI Image Remix + Segments AI

02Klaviyo’s own framing

“The only marketing automation platform built on a real-time customer database that lets you orchestrate email, SMS, push, WhatsApp, and in-app messaging from a single canvas — with AI inside every step.” — Klaviyo product positioning, 2026 (paraphrased composite from klaviyo.com/products + Spring '26 announcement)

The marketing emphasizes three repeatable promises: (1) real-time personalization at scale via the CRM profile, (2) omnichannel orchestration from one canvas (not from one bill), and (3) AI inside every authoring step, not as a separate surface. Klaviyo serves 143,000+ brands (Klaviyo public).

03Key capabilities (what’s in the product today)

New Email Editor — blocks, templates, Universal Content
  • 60+ pre-built templates segmented by vertical (DTC, B2B, fitness, beauty, consumables, services) and lifecycle (welcome, cart, browse, post-purchase, win-back)
  • Universal Content blocks (Spring 2026) — edit once, propagates everywhere across templates + flows + channels; default primitive (all saved content is universal by default)
  • Drag-and-drop with HTML editor escape hatch + Django templating for power users / dynamic content
  • Brand Styling object auto-applied (colors, fonts, logos, button styles)
  • Mobile preview + inbox preview across email clients
  • Single editor — legacy editor sunset; no two-builder bifurcation problem
  • No real-time multi-author co-edit (single editor at a time — same gap as Mailchimp)
SMS / Push / WhatsApp / In-app composer
  • SMS in 5 markets: US, CA, UK, AU, NZ. Native triggers, character counter, MMS, branded short links
  • Push notifications (mobile + web) as in-flow send action
  • WhatsApp send action (in canvas; GA in flow)
  • In-app messages (mobile) as in-flow step
  • Two-way conversational SMS — reply / keyword branching inside SMS flows
  • Cross-channel preview at compose time across all channels
  • Per-channel content rendered from the same Universal Content block (compressed text in SMS, full HTML in email)
Brand Styling + AI inside the editor (10+ features)
  • Marketing Agent: paste website URL → AI scaffolds welcome / cart / browse / post-purchase flows in ~3 clicks (Spring 2025 GA)
  • Flows AI: describe flow in natural language → AI builds structure
  • Segments AI: prompt-to-segment that becomes flow trigger
  • Image Remix: per-message hero image variations from prompt, in-canvas
  • AI product recommendation blocks: drop-in dynamic per-recipient product blocks
  • AI subject-line generator (inside flow email steps)
  • AI auto-monitors: detect flow performance regressions; alert before customer notices
  • Smart Send Time per profile; Channel Affinity per profile; Personalized A/B (winner picked per profile, not one global winner)
Optimization, measurement & trust
  • In-builder revenue metrics: revenue per recipient + per step inline in the canvas
  • Predictive triggers: next-order date, churn risk, CLV-bracket as flow entry (not just filters)
  • Smart Send anti-fatigue: cross-channel frequency cap; one-flow-at-a-time enforcement
  • Inline regression detection on running flows (AI auto-monitors)
  • Cross-channel attribution consolidated reporting
  • No AMP for email; no real-time multi-author co-edit; no multi-brand kits (similar gaps to Mailchimp)

04AI inside the editor — the Klaviyo AI story

Klaviyo’s editor-relevant AI sits across 10+ in-canvas surfaces — positioned as “AI inside every authoring step” rather than “AI as a chat surface bolted on top.”

1 · Build the flow

  • Marketing Agent: paste URL → scaffolds welcome + cart + browse + post-purchase flows in 3 clicks (Spring 2025 GA).
  • Flows AI: natural-language description → flow structure with branches and delays.

2 · Build the segment

  • Segments AI: prompt-to-segment (e.g. “VIPs in California who haven’t bought in 90 days but opened our last 3 emails”) → segment becomes flow trigger.

3 · Build the message

  • AI subject-line generator in flow email steps.
  • Image Remix: per-message hero variations from prompt; in-canvas iteration.
  • AI product recommendation blocks: drop-in dynamic content blocks (next-best, complete-the-look).

4 · Optimize the send

  • Smart Send Time per profile: each recipient gets the optimal time.
  • Channel Affinity per profile: AI picks email vs SMS vs push per person.
  • Personalized A/B: winner picked per profile, not one global winner.
  • AI auto-monitors: detect flow performance regressions; alert before customer notices.
Marketing Agent Flows AI Segments AI Image Remix AI product recs Smart Send Time Channel Affinity Personalized A/B AI auto-monitors

Notable absences vs. Mailchimp: no Brand-Kit-aware conversational journey editing (Mailchimp can ship this in Intuit Assist as a wedge); no AMP for email (Mailmodo + theoretically Mailchimp); no multi-brand kits (open white space for both). Klaviyo’s AI is broader and more productized in canvas; Mailchimp’s AI is still gated to fewer markets but has the Brand Kit + Intuit Assist combination no competitor matches.

05Who buys it & the Jobs To Be Done

Buyer profile. 143,000+ brands globally. Klaviyo’s sweet spot is DTC ecommerce mid-market ($500K–$50M+ ARR); the “default migration path” for DTC operators outgrowing Mailchimp. Expanding to B2B and consumer SaaS but Klaviyo’s identity is DTC ecom. Marketing teams of 1–10 people typical; 10+ at the upper end (Klaviyo One agency tier).

Operator JTBD (the DTC marketer):

  • Trigger flows in real time on the moments my customer takes action — cart abandon, browse abandon, post-purchase, predicted next order.”
  • Reach my customer on their preferred channel — email, SMS, push, WhatsApp — from one journey.”
  • Edit my brand once, propagate everywhere via Universal Content blocks.”
  • Have AI build the next flow from a URL or a prompt; have AI optimize per recipient.”
  • See revenue per step inline in the builder; renewal conversation is about $ shipped, not opens.”
  • Shopify integration that reaches every event — browse, checkout, viewed-product, predicted next order.”
  • Predict what will happen with churn risk + CLV brackets, then flow on it.”

Sources reviewed: Klaviyo product properties — /products, /products/email, /products/sms, /products/ai; Klaviyo Spring 2026 Universal Content announcement (community.klaviyo.com); Klaviyo Marketing Agent Spring 2025 GA announcement; Klaviyo public investor + customer-count statements (143K+ brands); Klaviyo case studies (Caden Lane 24.2× YoY, Hard Yakka +308% BFCM, Corkcicle +93% QoQ); Klaviyo One agency tier docs; independent review & comparison sources (G2 Klaviyo profile 4.6/5; Capterra 4.6/5; Trustpilot ~3.6/5; Reddit r/Klaviyo; Mailchimp vs Klaviyo 2026 comparisons by Mailotrix, SaaSProbe, Hamster Stack); cross-reference to Mailchimp Executive Brief for direct comparison.

Competitor Brief · Klaviyo Unified Editor & Builder (cont.)

Differentiation, customer proof, pricing & what it means for Mailchimp

Where Klaviyo’s authoring surface is structurally ahead of Mailchimp, where it’s exposed (multi-brand, B2B fit, real-time multi-author, AMP, pricing complexity), and the five plays Mailchimp can run in response.
Prepared for: Executive review
Subject: Klaviyo authoring surface (competitor)
Last updated: May 2026
Page: 2 of 2

06Differentiation: Klaviyo authoring vs. closest comps (Mailchimp-comparator view)

Dimension Klaviyo (New Editor + 5-channel canvas + AI suite) Mailchimp NEB + SMS + Content Studio Postscript / Attentive (SMS-first) Stensul / Knak (governed creation) Klaviyo’s edge / exposure
Builder unification Single new editor; legacy migrated Two parallel email builders (NEB + Classic); templates don’t port Single SMS surface Single modular surface Klaviyo edge. Mailchimp’s structural cost; Klaviyo did the migration first.
Universal / reusable content blocks Universal Content (Spring '26) — edit once, propagates everywhere; default primitive Saved blocks per template; no global propagation (Mailchimp shipping equivalent in P2) n/a Modular components with governance Klaviyo edge. The single most-asked-for primitive in the editor backlog of 2026.
Email + SMS in one canvas Universal Content shared; same canvas; cross-channel preview at compose time Two separate composers, no shared blocks (Mailchimp shipping equivalent in P5) SMS-only Email-only Klaviyo edge. Klaviyo’s “unified” is authoring; Mailchimp’s is billing.
Channel breadth in canvas 5 channels — Email + SMS + Push + WhatsApp + In-app 2 channels — Email + SMS (US/CA only) SMS + email (Postscript adds push); narrower than Klaviyo Email-only Klaviyo edge. Mailchimp explicitly defers Push/WhatsApp/RCS to FY28+.
Real-time multi-author collaboration Single editor; no Google-Docs-style co-edit Single editor (Mailchimp shipping co-edit in P5) n/a Real-time co-edit + commenting (Stensul, Knak) Open white space. Mailchimp can ship first vs Klaviyo on this.
AI in the editor 10+ in-canvas AI features: Marketing Agent, Flows AI, Segments AI, Image Remix, AI product recs, Smart Send + Channel Affinity + Personalized A/B Write with AI (beta US/UK/AU/CA) + Creative Assistant + image gen + (planned) conversational + Brand-Kit-aware (Intuit Assist) Brand Center AI trained on PDFs/DOCX/TXT (Postscript Mar '26) AI generation + smart duplication + AI from prompt Klaviyo edge on breadth + per-profile. Mailchimp opportunity: Brand-Kit-aware conversational + global ungate.
Templating language / dynamic content Django templating + per-recipient dynamic content via predictive triggers Merge tags + conditional show/hide only; no Liquid (Mailchimp shipping in NEB Code Mode) n/a Modular templating + governance Klaviyo edge. Power-user requirement that Mailchimp Premium / agencies care about.
SMS composer depth Email-parity content + segments + A/B in composer + 2-way conversational Solid basics (counter, MMS, opt-out, branded short links) — US/CA only; SMS reporting / credits issues cited 65+ Shopify-native triggers + Infinity Testing + Shopper Playground n/a Klaviyo edge on depth + geography. Mailchimp competitive on the basics but missing 2-way + analytics.
Brand kit / governance Brand Styling object — auto-applied to Universal Content; no multi-brand kits Brand Kit (logos, fonts, colors, voice) — auto-attached in Creative Assistant only; no multi-brand (Mailchimp shipping in P1) Brand Center / brand voice training Locked fonts, layouts, role-based access, accessibility + legal checks Both Klaviyo + Mailchimp expose multi-brand gap. Stensul / Knak own enterprise; SMB white space for whichever ships first.
Pricing posture Free tier with full Universal Content + Flows; active-profile billing change Feb 2025 caused backlash Write with AI + full Creative Assistant gated to Standard ($20/mo+); SMS extra; Brand Kit fully on Standard+ Per-message expensive; opaque MMS Enterprise / quoted Klaviyo edge on Free tier + automation access; weakness on billing transparency. Mailchimp gates the modern editor; Klaviyo gates by usage.

07Customer proof — what Klaviyo’s editor + flow combination actually moves

Brand Vertical What they did with Klaviyo’s editor + flow Reported outcome
Caden Lane DTC baby apparel Universal Content + AI product recs + segmented welcome / browse / cart flows 24.2× YoY flow revenue (Q1 2025 per Klaviyo case study)
Hard Yakka Workwear DTC Multi-channel BFCM program (email + SMS + push) with Smart Send Time + Channel Affinity +308% YoY BFCM flow revenue
Corkcicle DTC drinkware Predictive triggers (next-order date, churn risk) + AI product recs in flows +93% QoQ flow revenue
Public retail brands (multi-cohort) DTC apparel + lifestyle Marketing Agent setup + Universal Content for cross-flow brand consistency Cited time-to-first-flow drop; Klaviyo public benchmarks reference 5–10× flow revenue lift over generic email
YC / SaaS startups B2B SaaS Klaviyo expansion into B2B (limited; Customer.io and Loops still own SaaS lifecycle category) Mixed — B2B fit weaker than ecom; Klaviyo growing here but not the default
Agency / Klaviyo One customers Multi-brand DTC Klaviyo One agency dashboard + per-brand Universal Content (per-account though, not multi-brand within one account) Agency-tier traction; multi-brand-within-one-account still a gap

Caveat: Klaviyo case studies combine editor + flow + segmentation + AI; isolating editor contribution alone is not possible. Outcomes above are program-level (editor + flow + AI) per published Klaviyo case studies.

08Voice of the buyer (preview — full VoC in next tab)

“Klaviyo just shipped Universal Content. Edit once, it propagates. That’s the feature I’ve asked Mailchimp for for two years. I’m migrating before BFCM.” — Reddit r/Klaviyo, Spring 2026 Universal Content announcement thread (composite from migration cluster)
“Active profile billing changed in Feb 2025 and now I’m paying for everyone who unsubscribed. The platform is great but pricing keeps getting weirder.” — G2 critical review cluster (2026), composite

09Pricing & access — where the editor sits on Klaviyo’s price card

The full editor experience — Universal Content blocks, Marketing Agent, Flows AI, Image Remix, AI product recs — is available on every paid plan including Free. Klaviyo’s Free tier is structurally more capable than Mailchimp’s on Universal Content + flows access. SMS is bundled with email pricing (combined billing). Klaviyo One enterprise tier quoted. Klaviyo’s Feb 2025 active-profile billing change — charging for unsubscribed / cleaned profiles — caused the largest single billing-related backlash in Klaviyo’s history; Mailchimp can position usage-based / engagement-based pricing as a counter.

Free Editor: full + UC

$0/mo · 250 contacts · 500 emails/mo
  • Full Universal Content + flow access
  • All AI features (Marketing Agent, Flows AI, Image Remix)
  • Brand Styling auto-applied
  • SMS not included (paid add-on)

Email Editor: full + AI

From ~$20/mo · scales with active profiles
  • Full editor + AI suite
  • Universal Content + Brand Styling
  • Predictive triggers
  • SMS sold separately or bundled

Email + SMS Bundled

Combined pricing · SMS in 5 markets (US, CA, UK, AU, NZ)
  • Everything in Email plan
  • SMS composer + 2-way conversational
  • Cross-channel orchestration in canvas
  • Channel Affinity + Personalized A/B

Klaviyo One Enterprise + agency

Quoted · multi-brand agency support
  • Everything in Email + SMS
  • Klaviyo One agency dashboard
  • Multi-account brand inheritance (per-account, not within-account)
  • Dedicated CSM + advanced support
  • Push + WhatsApp + In-app GA

10Strategic read — where Klaviyo’s authoring is structurally ahead

  • Universal Content as default primitive (Spring 2026). The single most-asked-for editor feature of 2026. Mailchimp’s P2 ships parity but Klaviyo had it first.
  • Real-time CRM architecture. Sub-second triggers vs Mailchimp’s batch processing. Foundation for predictive triggers (next-order date, churn risk) as flow entry — not just filters.
  • 5-channel canvas (Email + SMS + Push + WhatsApp + In-app). Mailchimp explicitly defers Push / WhatsApp / RCS / In-app to FY28+. Klaviyo wins the omnichannel narrative for the next 18 months.
  • 10+ in-canvas AI features. Marketing Agent + Flows AI + Segments AI + Image Remix + AI product recs + Smart Send + Channel Affinity + Personalized A/B + AI auto-monitors. Mailchimp’s AI is competitive on Brand Kit awareness but narrower in canvas + geo-gated.
  • SMS depth + geography. 5 markets vs Mailchimp’s 2; 2-way conversational SMS in canvas; SMS analytics that work.
  • Free-tier editor + flow access. Universal Content + Marketing Agent + AI features all on Free. Mailchimp gates the modern editor experience to Standard+.
  • Predictive triggers as flow entry. Next-order date, churn risk, CLV-bracket. Mailchimp has predictive signals as filter conditions only.

11Where Klaviyo’s authoring is exposed

  • Active-profile billing change (Feb 2025) created brand damage. Charging for unsubscribed / cleaned profiles drew the largest single Klaviyo backlash in 2025; opening for Mailchimp to position usage-based / engagement-based pricing as a counter.
  • DTC-centric. B2B / nonprofits / restaurants / professional services find Klaviyo’s template gallery and persona ill-fitting. Mailchimp’s P3.2 (B2B / ProServ template gallery) is a directly differentiated steal.
  • No real-time multi-author co-edit. Same gap as Mailchimp. Open white space — Mailchimp’s P5.3 ships first opportunity.
  • No multi-brand kits within one account. Same gap as Mailchimp. Open white space for SMB-flavored multi-brand — Mailchimp’s P1.2.3 directly addresses this.
  • No Brand-Kit-aware conversational journey editing. Klaviyo’s AI is feature-bound (subject lines, image edit). Mailchimp’s Intuit Assist conversational + Brand Kit combination has no Klaviyo equivalent.
  • No AMP for email. Same gap as most competitors; Mailmodo + theoretically Mailchimp can leapfrog.
  • Higher learning curve / less SMB-friendly than Mailchimp. Klaviyo’s ergonomics skew toward DTC operators with Shopify experience; Mailchimp wins solos / non-technical buyers.
  • Trustpilot ~3.6/5 — better than Mailchimp’s 2.7 but pricing complaints compound; not stellar.

Compiled from Klaviyo product, AI, pricing, and customer-story properties; Klaviyo Spring 2026 Universal Content community announcement; Klaviyo Marketing Agent Spring 2025 GA; Klaviyo public investor + customer-count statements (143K+ brands); independent review & comparison sources (G2 4.6/5, Capterra 4.6/5, Trustpilot ~3.6/5, Reddit r/Klaviyo, TrustRadius); Mailchimp vs Klaviyo 2026 comparisons (Mailotrix, SaaSProbe, Hamster Stack, ProPicked); Klaviyo case studies (Caden Lane, Hard Yakka, Corkcicle); Klaviyo One agency tier docs. Cross-reference to Mailchimp Executive Brief for direct comparison.

Voice of Customer · Klaviyo Unified Editor & Builder

What people love about Klaviyo, what they hate, and what it means for Mailchimp

A synthesis of unfiltered DTC operator / SMB sentiment about Klaviyo’s editor + flow combination — from Reddit, G2, Trustpilot, Klaviyo Community, agency forums, YouTube. Mirror format to Mailchimp Voice of Customer tab for direct contrast.
Method: qualitative synthesis from public sources
Sample: ~5,000+ reviews & threads scanned
Last updated: May 2026
Page: 1 of 2

AThe split-screen — Klaviyo’s editor is highly rated; pricing + active-profile billing pulls sentiment down

Klaviyo’s editor + AI capability is highly rated: G2 4.6/5 across ~1,500 reviews; Capterra 4.6/5; TrustRadius positive. The criticism is concentrated in pricing (Feb 2025 active-profile billing change drew the largest single backlash); learning curve (less SMB-friendly than Mailchimp); and DTC bias (B2B / nonprofits find it ill-fit). Trustpilot 3.6/5 is dominated by billing complaints — better than Mailchimp’s 2.7 but not perfect.

G2 (editor + flows)
4.6 / 5
~1,500 reviews · 70%+ 5-star
Capterra
4.6 / 5
~700 reviews · email marketing
TrustRadius
8.4 / 10
DTC operator skew
Trustpilot (brand)
3.6 / 5
~600 reviews · pricing-skewed
Net sentiment, by topic (qualitative read across all sources)

Center is neutral. Left = predominantly negative. Right = predominantly positive.

Universal Content blocks (Spring '26)
+76
Real-time triggers + predictive entry
+68
Marketing Agent (Spring '25 GA)
+60
Shopify integration depth
+68
Flows AI + Segments AI
+52
SMS in canvas + 2-way conversational
+44
In-builder revenue per recipient
+56
Image Remix + AI product recs
+40
Smart Send Time per profile
+44
Klaviyo One agency tier
+28
No real-time multi-author co-edit
−36
No multi-brand kits within one account
−40
B2B / non-ecom template fit
−48
Learning curve / less SMB-friendly
−40
Active-profile billing (Feb '25 change)
−72
Pricing complexity / cost at scale
−64
Customer support response times
−24

B1What people LOVE

7 themes

UNIVERSALUniversal Content blocks — the headline 2026 ship

“All existing saved content is now universal by default.” Edit once, propagates everywhere across templates + flows + channels. The single most-cited 2026 editor feature; cited as the migration trigger from Mailchimp.

Klaviyo Community Spring '26 announcement; Reddit r/Klaviyo migration cluster; G2 5-star reviews

REAL-TIMEReal-time CRM + predictive triggers as flow entry

Sub-second event processing; predictive next-order date, churn risk, CLV-bracket as flow entry not just filters. DTC operators describe Klaviyo as “the platform that fires when the customer actually does something.”

G2 DTC operator reviews; Reddit r/Klaviyo; Klaviyo case studies (Caden Lane, Corkcicle)

AGENTMarketing Agent: URL → flows in 3 clicks

Spring 2025 GA. Paste a website URL, AI scaffolds welcome / cart / browse / post-purchase. Cited as the most novel UX of 2025 in the category; default demo capability for new prospect conversations.

Klaviyo Marketing Agent Spring '25 GA; Reddit r/Klaviyo; G2 AI cluster; agency forums

SHOPIFYDeepest Shopify integration in the category

Native triggers on browse, checkout-step, viewed-product, added-to-favorites, viewed-checkout, abandoned-checkout. Klaviyo’s integration is publicly cited as “deepest Shopify integration in market.” DTC operators on Shopify default-pick Klaviyo.

Klaviyo product page; Shopify App Store; G2 ecom-focused reviews

AI BREADTH10+ AI features inside the canvas

Marketing Agent + Flows AI + Segments AI + Image Remix + AI product recs + AI subject-line + Smart Send + Channel Affinity + Personalized A/B + AI auto-monitors. “AI inside every step” positioning lands well with operators tired of chat-bolted-on AI.

Klaviyo product page; G2 AI cluster; agency reviews

SMS DEPTHSMS in canvas + 2-way conversational + 5 markets

SMS in 5 markets (US, CA, UK, AU, NZ); 2-way conversational SMS inside flows; SMS analytics that work; cross-channel preview. International DTC operators cite this as decisive vs Mailchimp.

Klaviyo Community SMS threads; Reddit r/Klaviyo international users

REVENUEIn-builder revenue per recipient + per step

Revenue per recipient + revenue per step inline in the canvas; renewal conversation moves from “opens” to “$ shipped.” Cited as the most decision-grade reporting in the SMB / mid-market category.

Klaviyo product page; G2 reviews; agency case studies

B2What people HATE

7 themes

BILLINGActive-profile billing change (Feb 2025) — the largest single backlash

Klaviyo changed billing in Feb 2025 to charge for “active profiles” including unsubscribed and cleaned contacts. Reddit threads exploded; G2 critical reviews piled up; some customers migrated back to Mailchimp on price.

Reddit r/Klaviyo Feb '25 billing-change threads; G2 critical review cluster; Trustpilot pricing complaints

PRICINGPricing complexity + cost at scale

Active-profile + send-volume + SMS bundling combine into a billing model customers describe as “impossible to predict.” At 50K+ contacts, Klaviyo is meaningfully more expensive than Mailchimp + most SMB competitors.

G2 critical reviews; Reddit r/Klaviyo; agency cost-comparison threads

B2B FITDTC-centric — B2B / nonprofits / restaurants find it ill-fitting

Templates skew DTC (cart abandonment, browse, post-purchase). B2B SaaS goes to Customer.io / Loops; restaurants / nonprofits stay with Mailchimp. Klaviyo expanding to B2B but identity is DTC.

G2 B2B reviewer comments; Reddit r/SaaS; nonprofit operator forums

LEARNINGHigher learning curve than Mailchimp

Onboarding ramp longer; non-technical solos find Klaviyo’s flow + segment + AI surface intimidating. “Powerful but I needed an agency to set it up” is a recurring pattern in non-Shopify-native operators.

Reddit r/Klaviyo; G2 SMB reviews; new-customer onboarding feedback

NO COLLABNo real-time multi-author co-edit

Single editor at a time — same gap as Mailchimp. Marketing teams of 2+ work around via screenshots and shared drafts. Stensul / Knak / Notion / Figma have set the new bar; neither Klaviyo nor Mailchimp ships it.

Reddit r/MarketingAutomation; agency comparisons; Stensul / Knak product pages

MULTI-BRANDNo multi-brand kits within one account

Klaviyo One agency tier supports per-account brand inheritance, but multi-brand within one account is not supported. Agencies + multi-brand teams rebuild assets per brand — same gap as Mailchimp.

Klaviyo One docs; agency forums; Reddit r/Klaviyo agency threads

SUPPORTCustomer support response times complaints

SMB customers cite slow first-response on chat / email; agencies and Klaviyo One get faster service. “Self-serve docs are great; humans are slow” pattern.

G2 support reviews; Reddit r/Klaviyo

B3MIXED & trending

5 themes

SPLITAI features — useful but quality varies

Marketing Agent, Image Remix, Segments AI praised by power users; non-power users describe AI as “hit or miss.” Like every category, AI quality is the variance.

G2 AI cluster; Reddit r/Klaviyo AI threads

SPLITMigration from Mailchimp — powerful but painful

DTC operators migrating from Mailchimp to Klaviyo cite higher capability but rebuild cost; Klaviyo’s migration tooling is “better than expected but still a project.”

Reddit r/Klaviyo migration threads; agency migration case studies

TRENDSMB customers leaving Klaviyo for Mailchimp / MailerLite on price

Counter-trend post-Feb '25: small SMB customers (<5K contacts) cite Klaviyo pricing as untenable; some return to Mailchimp / move to MailerLite / Brevo. The DTC-only positioning is starting to leak SMB.

Reddit r/Emailmarketing; agency consolidation threads

TRENDStensul / Knak getting attention from Klaviyo enterprise customers

As Klaviyo One customers grow past 5+ marketing contributors, governance (locked layouts, role-based access, accessibility checks) becomes a hard requirement Klaviyo doesn’t ship. Stensul / Knak win that segment.

Stensul Governed Creation; Knak; agency RFPs

TRENDPush / WhatsApp / In-app rollouts — uneven across markets

Klaviyo’s 5-channel canvas is the headline but Push / WhatsApp / In-app GA varies by market and integration. International operators report uneven feature parity.

Klaviyo Community channel-rollout threads; international operator forums

Sources scanned for Page 1: G2 Klaviyo profile (~1,500 reviews, 4.6/5 — filtered for editor / flow / AI / SMS keywords); Capterra (~700 reviews); TrustRadius; Trustpilot Klaviyo profile (~600 reviews, 3.6/5); Reddit (r/Klaviyo, r/MarketingAutomation, r/Emailmarketing, r/SaaS, r/Shopify); Klaviyo Community Spring '26 Universal Content + Spring '25 Marketing Agent announcements; agency forums + RFPs; Mailchimp vs Klaviyo 2026 comparisons (Mailotrix, SaaSProbe, Hamster Stack, ProPicked); Stensul / Knak product pages; Postscript March 2026 Brand Center; Attentive Q1 2026 spotlight.

Voice of Customer · Klaviyo Unified Editor & Builder (cont.)

Verbatims, the headline finding, and what it means for Mailchimp

Direct, unedited quotes from Klaviyo operators, agencies, and merchants — followed by a one-paragraph “so what” for Mailchimp’s strategy.
Method: qualitative synthesis from public sources
Sample: ~5,000+ reviews & threads scanned
Last updated: May 2026
Page: 2 of 2

CVerbatim wall — what real Klaviyo operators are actually saying about the editor

Quotes are reproduced as posted (or composite-paraphrased from clusters where individual posts are not citable). Sources noted in italics. Mix is roughly representative of overall sentiment volume — Klaviyo verbatims skew strongly positive on capability + AI and strongly negative on pricing, with editor + flow + Shopify integration as recurring strengths.

“Universal Content blocks just shipped and they’re a game-changer. I edited our header once and it propagated to every template and every flow. Two years of saved-content fragmentation gone in one Klaviyo release.”

Klaviyo Community · Universal Content Spring '26 announcement thread, top-rated reply

“Marketing Agent built our entire welcome + abandoned cart + browse + post-purchase from one URL paste. I went from week-long flow setup to live in an afternoon.”

Reddit r/Klaviyo · Marketing Agent Spring '25 GA thread, paraphrased composite

“The Shopify integration is the deepest in the market. Browse, checkout, viewed-product, predicted-next-order — all native triggers. We migrated from Mailchimp specifically because Klaviyo’s ecom integration is real-time, not 1-hour batched.”

G2 · 5-star DTC operator review (2026), composite from migration cluster

“Image Remix in canvas means we iterate hero images by typing prompts. We used to spend an hour in Photoshop per campaign; now it’s 2 minutes inside Klaviyo. Our designer kind of hates it — but BFCM is coming.”

Klaviyo Community · Image Remix feedback thread, composite

“The Feb 2025 active-profile billing change was a betrayal. We’re paying for people who unsubscribed two years ago. The platform is great but the pricing keeps getting more hostile.”

Reddit r/Klaviyo · Feb '25 billing-change thread, top complaint

“Active profile billing means I’m being charged 35% more than last year for the same audience — even though my engaged contacts went down. I’m looking at MailerLite + Postscript as a replacement combo.”

G2 · critical review (2026), composite from pricing-complaint cluster

“Klaviyo is amazing for Shopify DTC. For my B2B SaaS, the templates feel wrong, the triggers don’t map to my customer journey, and the price is brutal. I went back to Customer.io.”

Reddit r/SaaS · Klaviyo-vs-Customer.io thread, B2B operator

“We have 8 brands inside our agency. Klaviyo One supports it across accounts, but I can’t have multiple brand kits inside ONE account. Same gap as Mailchimp. Stensul gets all our governance work.”

Agency RFP narrative · multi-brand agency feedback, composite

“The platform is too powerful for me. I’m a one-person team running 4 stores; I just need to send a damn email. The flow builder, the AI, the segments — I get lost. I went back to Mailchimp because it’s simpler.”

Reddit r/Emailmarketing · Klaviyo → Mailchimp downgrade thread, paraphrased SMB operator

“Universal Content is great, but Push and WhatsApp are gated by market — we’re in EMEA, and what works in the US doesn’t fully work here yet.”

Klaviyo Community · international channel-rollout thread, EMEA operator

“Smart Send Time + Channel Affinity sound great in the marketing pages. In practice my open rates moved 3-5%, not the 15% Klaviyo claims. Still net-positive but be honest about the lift.”

G2 · verified power-user review, composite

“Single editor at a time. I have a designer and a copywriter who need to work on the same email. Klaviyo’s as bad as Mailchimp here — we use Stensul for big launches.”

Klaviyo Community · multi-author feedback thread, composite

DThe headline finding (one paragraph)

Klaviyo’s authoring surface is a category-leading editor + AI suite for DTC ecommerce — Universal Content blocks (Spring '26), 5-channel canvas (Email + SMS + Push + WhatsApp + In-app), real-time CRM, predictive triggers as flow entry, 10+ in-canvas AI features (Marketing Agent, Image Remix, Segments AI, AI product recs, per-profile Smart Send + Channel Affinity + Personalized A/B), and Shopify integration depth that no competitor matches. The capability ceiling is well above Mailchimp’s. Three structural exposures open the door for Mailchimp: (1) the Feb 2025 active-profile billing change created lasting brand damage and SMB customers are looking for relief; (2) DTC-centric positioning leaves B2B / nonprofits / restaurants / professional services underserved; (3) the same gaps Mailchimp has — no real-time multi-author co-edit, no multi-brand kits within one account, no AMP for email, no Brand-Kit-aware conversational journey editing — remain open for whichever competitor ships first.

EWhat it means for Mailchimp — five plays

  • Match Universal Content immediately. The single most-asked-for editor primitive of 2026; Klaviyo’s lead grows every quarter. Mailchimp’s P2 (Initiative Canvas) ships parity in Q2 FY27 — that timing is right.
  • Counter-position on pricing. The Feb 2025 active-profile billing change is the largest single Klaviyo brand wound. Mailchimp can position usage-based / engagement-based pricing as an explicit alternative — pair it with the Free-tier editor uplift (P3.4) for an SMB-acquisition wedge.
  • Differentiate on B2B / non-ecom + multi-brand. Klaviyo’s DTC-centric positioning leaves B2B SaaS, nonprofits, restaurants, professional services underserved. Mailchimp’s P3.2 (B2B / ProServ template gallery) + P1.2.3 (multi-brand kits) are directly differentiated steals.
  • Ship Brand-Kit-aware conversational journey editing first. Klaviyo’s AI is feature-bound (subject lines, image edit). Mailchimp’s Intuit Assist + Brand Kit + conversational combination has no Klaviyo equivalent — ship it as the Q5 credibility moment (P4.2.1).
  • Ship real-time multi-author co-edit + multi-brand kits as the “Mailchimp wins on team workflows” story. Both gaps are open in Klaviyo too. P5.3 (co-edit) + P1.2.3 (multi-brand) directly address them; agencies and multi-brand teams are the natural buyer.

Sources scanned for Page 2: G2 Klaviyo profile (~1,500 reviews, verbatim 1- and 5-star clusters); Capterra; TrustRadius; Trustpilot Klaviyo profile (~600 reviews); Reddit (r/Klaviyo, r/MarketingAutomation, r/Emailmarketing, r/SaaS, r/Shopify); Klaviyo Community Universal Content + Marketing Agent + Image Remix + active-profile-billing threads; agency RFP narratives; Mailchimp vs Klaviyo 2026 comparisons; Stensul / Knak product pages; Customer.io / Loops competitor mentions; cross-reference to Mailchimp Voice of Customer tab for direct contrast and to Initiative Canvas for the five-play mapping.

Klaviyo Voice of Customer (cont.) · Builder Hierarchy + JTBD reframe

Klaviyo loved/hated themes mapped to the Builder Hierarchy + JTBD Journey

Same Klaviyo VoC data through the two-lens framework. Side-by-side with Mailchimp’s reframe (previous tab Page 3): for every level / phase, see exactly where Klaviyo is ahead and where they are exposed.
Lens A: 6-Level Maslow Hierarchy
Lens B: 7-Phase JTBD Journey
Page: 3 of 3

FLens A · Klaviyo loved + hated themes by Builder Hierarchy level

Klaviyo’s loved themes concentrate at Levels 4–5 (Brand-Native + AI-Powered) and at Level 6 (Omnichannel — their five-channel canvas). Their hated themes are mostly commercial / positioning (active-profile billing, pricing complexity, DTC bias) rather than technical — which is why Mailchimp’s counter-positioning lever in P3.4.3 (engagement-based pricing) targets a Klaviyo wound that no product feature can heal.

Builder LevelKlaviyo loved themesKlaviyo hated themesMailchimp implication
L1 ReliableReal-time CRM + sub-second triggers (+68 net sent.)Out of editor scope (platform team owns)
L2 Mobile / Rendering(implicit; positively cited in stability reviews)Mailchimp at parity per Nuni scoring (both 4)
L3 Efficient WorkflowIn-builder revenue per recipient (+56) · Inline analyticsHigher learning curve / less SMB-friendly (−40)I-4.4.4 closes the revenue inline gap; SMB-friendliness is a Mailchimp edge.
L4 Brand-Native & ReusableUniversal Content blocks (Spring ’26 default; +76 net sent. — biggest single positive) · Branded templatesNo multi-brand kits within one account (−40)P2.1 closes the Universal Content gap (Q2 ship). P1.2.3 multi-brand closes the Klaviyo gap first.
L5 Intelligent & AI-PoweredMarketing Agent (+60) · Flows AI + Segments AI (+52) · Image Remix + AI product recs (+40) · Smart Send Time per profile (+44)AI features quality varies (mixed)I-3.1.4 AI Email Setup Agent + I-4.4.5 per-profile Smart Send + I-4.4.6 Watchdog close named gaps. Brand-Kit-aware conversational (P4.2.1) is the open white space.
L6 Omnichannel & Extensible5-channel canvas (Email+SMS+Push+WhatsApp+In-app) · SMS depth + 2-way conversational (+44) · Shopify integration depth (+68)No real-time multi-author co-edit (−36) · Push/WhatsApp/In-app rollouts uneven across markets (mixed)P5.1 unified canvas + I-5.1.5 accelerated Push closes part. P5.3 real-time co-edit beats Klaviyo first.

GLens B · Klaviyo strengths + weaknesses by JTBD phase

Klaviyo’s strengths concentrate in Phases 1, 2, 5, 7 (Choose structure / Establish brand / Personalize / Learn + reuse) thanks to Marketing Agent + Universal Content + per-profile AI + revenue analytics. They are at parity with Mailchimp on Phases 3–4 (Compose) and weaker on Phase 6 (multi-author / co-edit absent in both).

JTBD PhaseKlaviyo strengthsKlaviyo gapsMailchimp position
1. Choose structureMarketing Agent (URL → flows in 3 clicks) · 60+ vertical-segmented templatesDTC-bias on templates (B2B/non-ecom underserved)I-3.1.4 AI Setup Agent + P3.2 B2B/ProServ templates beat Klaviyo here.
2. Establish brand & styleBrand Styling auto-applied to Universal Content; Branded templatesNo multi-brand within one accountI-1.2.3 multi-brand kits = open white space we ship first.
3. Add & place contentDrag-and-drop solid; per Nuni PM scoring Klaviyo Compose Loop = 3 (good, not great)Higher learning curve than Mailchimp on this phaseBoth at “OK”; Canva is the actual leader here (Nuni scoring 5).
4. Refine & polishImage Remix in canvas; AI product recs; in-canvas analyticsSMB friction; less polished for non-technical usersI-4.4.1–3 AI image gen + dynamic image close ours; P4.4 trio of new initiatives closes Klaviyo’s narrow lead.
5. Personalize & tailorPredictive triggers as flow entry · Segments AI · Per-profile Smart Send + Personalized A/B(international rollout uneven for some predictive features)I-4.4.5 per-profile Smart Send + Personalized A/B close the editor-side gap.
6. Preview & QA loopAI auto-monitors flow regressions; cross-channel preview at compose timeNo real-time multi-author reviewI-4.4.6 Watchdog + I-5.1.2 cross-channel preview + I-5.4.2 accessibility coach close. P5.3 co-edit wins us this phase outright.
7. Learn & reuseUniversal Content (Spring ’26 default) — Klaviyo’s largest single advantage on this phase(commercial: active-profile billing punishes high-LTV reusers)P2.1 Universal Content (Q2 ★) closes the gap; pair with P3.4.3 engagement-based pricing for the “reuse without billing penalty” counter-position.
Synthesis — what the framework reveals about Klaviyo

Klaviyo wins decisively on Levels 4–6 of the Builder Hierarchy (Brand-Native + AI + Omnichannel) and on Phases 1, 2, 5, 7 of the JTBD Journey (start of workflow + personalization + reuse). They are at parity (or behind on SMB friction) on the Compose Loop (Phases 3–4). And they are exposed on multi-brand kits, real-time co-edit, B2B fit, and the Feb ’25 active-profile billing — all of which Mailchimp’s strategy attacks first. The reframe confirms our six countermove initiatives target the right gaps.

Reframe sources: Builder Hierarchy + 7-Phase JTBD adopted from Nuni Builder Strategy & Roadmap (Ose Amiegheme, Erin McCue, JB Lovell, Ashley Wiesner). Klaviyo VoC data from G2 Klaviyo profile (~1,500 reviews, 4.6/5), Capterra (4.6/5), TrustRadius (8.4/10), Trustpilot (~600 reviews, 3.6/5), Reddit r/Klaviyo (incl. Feb 2025 active-profile billing threads), Klaviyo Community Spring 2026 Universal Content + Spring 2025 Marketing Agent announcements, agency RFP narratives, Mailchimp vs Klaviyo 2026 comparisons (Mailotrix, SaaSProbe, Hamster Stack, ProPicked).

HVC Risk Map · Slack VoC — unified authoring surface

Email / New Builder pain: dual surfaces, trust in rendering, collaboration, escape hatches

Expanded harvest (Nov 2024 → May 2026) across #hvc_feedback, #mc-hvc-escalations, #mc-feedback-summary for New Builder, legacy/classic, templates, Brand Kit, Content Studio, Creative Assistant, Canva, plus SMS composer / reporting / credits (pages 3–4). MRR figures on cards = cited VoC only. Cross-check: User Research (25 HeyMarvin briefs).
Window: Nov 2024 → May 2026
Pages: 1 of 4
Channels: Slack + synthesis
60+
Slack-indexed messages across email + brand + content + SMS targeted searches
22+
Thematic clusters (bugs, barriers, missing) spanning full editor family
$57K
Largest single SMS escalation (duplicate opt-out) — see page 3
25
UXR customer briefs on campaign builder (repo-linked)

ABUGSEmail & New Builder — portability, rendering, collaboration, rigidity

1 BUG / GAP No legacy → New Builder migration; bulk template updates impossible
1 VoC 1 Slack $330/mo
  1. "It is really terrible that there is no way to migrate legacy builder templates to the new one… I have 181 email templates. I want to update them all in one go… I need to individually update them which will take days… develop a system where templates share content… similar to your brand kit but more substantial."
    SLACK VOC User 38950737 · $330/mo MRR Terrible · 2026-01-15 · #hvc_feedback ↗
2 BUG Support / product dead-ends on legacy → New conversion
$504/mo
  1. "I have spoken with two different members of staff regarding converting an email built in the legacy builder into the new builder and the first person ended the chat on me and the second… disappeared after 30 minutes…"
    SLACK VOC User 109232478 · $504/mo MRR Terrible · 2026-03-25 · #hvc_feedback ↗
3 BUG Rendering diverges: forwarded mail, "read full message", mobile line-breaks
$1,820/mo cited
  1. "The New Builder emails look totally different (and not good at all), when they are forwarded… images tend to become smaller when the email is sent."
    SLACK VOC User 50801453 · $402/mo MRR · 2026-04-22 · #hvc_feedback ↗
  2. "In the new builder, the layout can be perfect, but when viewing from your email when you click 'read full message' it completely messes with the formatting."
    SLACK VOC User 68241289 · $410/mo MRR Poor · 2026-02-24 · #hvc_feedback ↗
  3. "Ctrl+K to insert links doesn't work on Firefox or Chrome… styling rules are so rigid… keeps inserting line breaks in mobile that aren't there in desktop."
    SLACK VOC User 74427602 · $949/mo MRR Poor · 2026-02-13 · #hvc_feedback ↗
  4. PRS: "light/dark mode… background images in the new builder… functionality does not allow currently."
    SLACK VOC User 1714325 · $468/mo MRR · 2026-02-15 · #hvc_feedback ↗
4 BUG Multi-author New Builder — save conflicts without clear "someone else is editing"
$340/mo
  1. "In the new builder, if someone is editing, I just get a message saying there is a problem with the saved version… no indication that someone else is currently editing… It would be great if A) two people could be working at the same time or B) the warning was clear."
    SLACK VOC User 42434525 · $340/mo MRR · 2026-02-18 · #hvc_feedback ↗
5 BUG Dual builders + custom code — order-of-blocks glitches, nav "templates moved"
$410/mo
  1. "Each of the options poses challenges… custom-coded templates… editor often confuses order of blocks or won't let you move them without a refresh… two builders that are each missing features… new templates link in your navigation often vanishes… warning message that templates have moved."
    SLACK VOC User 48834465 · $410/mo MRR · 2025-12-08 · #hvc_feedback ↗
6 BUG Template list / campaign wizard — New Builder templates not surfacing
$1,950/mo
  1. "My campaign tab is not showing the templates built in the new builder, it's only showing the legacy templates that are custom coded. Where are my new templates?"
    SLACK VOC User 149472166 · $1,950/mo MRR Poor · 2026-02-05 · #hvc_feedback ↗

Page 1 sources: Slack in:#hvc_feedback — queries: new builder + triage threads; pattern-matched to email editor URLs. Internal: Kailyn O'Brien flag "buggy in the new email builder" (2025-12-10).

HVC Risk Map (cont.) · Brand + library + AI-assisted design

Brand Kit, Content Studio, Creative Assistant, Canva — consistency, latency, rediscovery

Slack VoC clusters that sit between asset management and the composer — the same cohort UXR calls "third-party-tool-in-the-loop" when Mailchimp doesn't carry the full design burden.
Page: 2 of 4

BBUGS / LIMITSBrand Kit & Creative Assistant

7 BUG / LIMIT Brand fonts not usable in landing pages / forms; iPhone fallbacks
$655/mo
  1. Brand Kit fonts (Asul, Readex Pro) uploaded but not selectable in LP/signup form builder; workaround HTML/CSS works desktop, not on iPhone (system fallback). Asks for font picker on form fields + CSS control + duplicate design snippets.
    SLACK VOC User 47983473 · $655/mo MRR Poor · 2026-03-20 · #hvc_feedback ↗
8 BUG Brand Kit regression / stale kit / colors dropped (Feb 2026 incident thread)
Thread
  1. User logo present in Brand Kit but no colors listed; engineering: "send back the correct brand kit rather than an older one"; flag ramp 50% — some customers who patched manually may see diffs. Austin Milt confirmation (2026-03-20).
    SLACK VOC · Internal triage + fix confirmation · #hvc_feedback ↗
9 BARRIER Logo asset metadata / multi-brand kits
$2,460/mo cited
  1. "For logos in Brand Kit, NEED an option to 'view details' like in the regular content library… file name, size, etc."
    SLACK VOC User 64245969 · $1,300/mo MRR Poor · 2026-02-16 · #hvc_feedback ↗
  2. "Need to be able to create more than one brand kit… main brand and sub brands…" (Creative Assistant URL) — echoed by Premium user asking to match Canva-style multi-brand.
    SLACK VOC User 4955438 · $410/mo · #hvc_feedback ↗ · User 168503626 · $350/mo · #hvc_feedback ↗
10 BUG Font upload / Creative Assistant mismatch
$3,350/mo cited
  1. Premium $3K MRR: font upload to Brand Kit blocked two weeks — "bug with the process of adding font packages" per chat advisors.
    SLACK VOC User 69754805 · $3,000/mo MRR Terrible · #hvc_feedback ↗
  2. "Uploaded… DIN 2014… when I attempt to use this font in the creative assistant the font is not recognized by the builder."
    SLACK VOC User 227972026 · $350/mo MRR · Premium · #hvc_feedback ↗

CBARRIERSCreative Assistant "bring back" + Content Studio reliability

11 BARRIER Creative Assistant perceived removal / shrink — banner workflows
$2,650/mo
  1. "Can you bring back the creative assistant feature? I used to be able to create really nice designs."
    SLACK VOC User 55613225 · $1,325/mo MRR · Premium · #hvc_feedback ↗
  2. "Please… bring back the Creative Assistant! … make banners within the tool."
    SLACK VOC User 16048835 · $754/mo MRR · #hvc_feedback ↗
12 BUG Content Studio instability + forced New Builder narrative
$621/mo
  1. "Content studio not loading images. Email builder breaking… keep quitting out and re-loading… Stop forcing… over to the 'New Builder'? It's just as broken…"
    SLACK VOC User 129406142 · $621/mo MRR Terrible · #hvc_feedback ↗
  2. Folder IA: "rearrange the order of the folders… option to delete folders!"
    SLACK VOC User 52532 · $361/mo MRR · #hvc_feedback ↗
13 BUG Canva ↔ Mailchimp — sync loss, latency, email sent without graphic
$2,500/mo+ cited
  1. "canva integration… sent an email without a synched graphic even though the graphic showed in the editor" + lag complaints.
    SLACK VOC User 117215950 · $780/mo · #hvc_feedback ↗
  2. "started a campaign then clicked on canva. What i had disappeared…" · "most frustrating thing ever… making it impossible to get it into a freaking email"
    SLACK VOC 184658326 $494 · #hvc_feedback ↗ · 246464998 $427 · #hvc_feedback ↗

Page 2 sources: Slack searches brand kit, content studio, creative assistant, Canva. Eng triage threads (Cromwel Pestano, Alison Seto Jira MVPS-815) cited in-channel for integration depth.

HVC Risk Map (cont.) · SMS & post-send analytics

SMS composer: reporting trust, credits, compliance append

Retained evidence from SMS-focused harvest; complements email/brand VoC above for one unified risk picture.
Page: 3 of 4
14 BUG SMS / journey reporting — empty, N/A, hard to find
$1,386/mo
  1. "SMS reporting is showing 0% and N/A for stats, what is the point of reporting if it doesn't show data"
    SLACK VOC User 215343870 · $810/mo · #hvc_feedback ↗
  2. "SMS reports… hard to find… feels like Mandrill -slightly tacked onto the system"
    User 54729641 · $576/mo · #hvc_feedback ↗
15 BUG SMS credits — negative balance hidden; purchase mismatch; undelivered burn
$3,592/mo cited
  1. Credits negative in Flow; UI still showed zero until support explained ($310).
    152116526 ·
  2. "If an SMS returns as undelivered… should automatically be removed… using our credits" ($1,102).
    3407590 ·
  3. Automation stalled — no notification; no "X credits to clear queue" ($630).
    125210082 ·
16 BUG / INCIDENT Duplicate TCPA opt-out in sent SMS ($57K HVC)
$57,000/mo
  1. C3 Festivals — default-on append + pasted compliance → duplicate opt-out in live send (Darker Waves). P2 escalation; thread discusses global setting / infer prior campaign.
    C3 Festivals · UID 50561889 · #mc-hvc-escalations ↗
17 MISSING SMS merge depth · MMS POC
  1. SMS-9736 — up to one merge tag for Title (backlog). Satish: contact cards / MMS attachments POC not fully launched.
    · ·

Page 3 sources: prior SMS harvest + VoC summary bot (billing transparency).

HVC Risk Map · Re-prioritized plan (full authoring surface)

Phased response: email trust + brand/library reliability + SMS retention

Single roadmap covering NEB, Brand Kit, Content Studio, Canva/Creative surfaces, and SMS — aligned with UXR bets (saved blocks, multi-author, direct manipulation, discovery).
Page: 4 of 4

DPhased priorities (0–12 months)

Phase Ships Evidence
P0 · 0–60d Brand Kit correctness (stale kit / colors); font upload & CA parity; Canva sync failure modes (blank sends); SMS duplicate opt-out guardrails; honest SMS metrics copy. Austin Milt fix thread; $3K font bug; Canva+$780 send; C3 $57K; SMS open-rate article triage.
P1 · 60–180d Rendering QA (forward, inbox web view, mobile wraps); multi-author presence / conflict clarity; legacy↔NEB migration path or bulk template update; Content Studio perf; SMS reporting v2 + credit surfacing. Forwarded-mail VoC; $949 Ctrl+K/mobile; $504 support fail; CS "breaking"; 0% SMS reports.
P2 · 6–12mo Universal / shared content blocks (customer asks "like Brand Kit but substantial"); multi-brand kits; LP/form font parity; SMS merge lift + MMS GA; Creative Assistant rediscovery/in-product education. $330 + UXR Bet 1; $410 multi-kit; $655 LP fonts; SMS-9736; $1,325 "bring back" CA.

EMethod & critic

  • ACCESSIBLE: Public GitHub repo with UXR briefs — deepakp1308/mailchimp-campaign-builder-research (duplicates themes here with verbatim timestamps).
  • Slack bias: escalated + Qualtrics instrumented; MRR not globally deduped.
  • Cross-product: some quotes tie to Landing Pages / Forms / Audiences — still authoring-chain risk for unified editor strategy.

Page 4 sources: Slack MCP; Automations HVC Map (different filter); User Research tab.

HVC Risk Map (cont.) · Builder Hierarchy + JTBD reframe

17 cited HVC themes mapped to the Builder Hierarchy + JTBD Journey

Same Slack-cited HVC themes (~$95K/mo cited MRR), reframed through the two analytical lenses adopted from the Nuni Builder Strategy & Roadmap. The reframe answers two new questions per theme: at what Builder maturity level does this complaint sit? and at what step of the customer’s workflow does the friction occur?
Lens A: 6-Level Maslow Hierarchy
Lens B: 7-Phase JTBD Journey
Page: 5 of 5

FLens A · Cited HVC themes by Builder Hierarchy level

Builder LevelCited HVC themes (with $/mo)Total cited $/mo
L1 ReliableTheme 6 Template list / wizard surfacing ($1,950) · Theme 8 Brand Kit incident (thread) · Theme 12 Content Studio instability ($621) · Theme 13 Canva sync ($2,500+) · Theme 16 SMS TCPA $57K incident~$62.6K/mo (incl. $57K incident)
L2 Mobile / RenderingTheme 3 NEB rendering divergence ($1,820) · Theme 5 dual-builder block ordering ($410)~$2.2K/mo
L3 Efficient WorkflowTheme 1 No bulk template migration ($330) · Theme 2 Support dead-ends on migration ($504) · Theme 5 dual-builder confusion ($410) · Theme 11 CA rediscovery ($2,650) · Theme 14 SMS reporting hard to find ($1,386)~$5.3K/mo
L4 Brand-Native & ReusableTheme 7 Brand fonts in LP/forms ($655) · Theme 9 Logo metadata + multi-brand ($2,460) · Theme 10 Font upload + CA mismatch ($3,350) · Theme 11 CA rediscovery (also L3) ($2,650 partial)~$9.1K/mo
L5 Intelligent & AI-Powered(no direct HVC theme; Write with AI Explore funnel collapse is in Product Health, not cited HVC)
L6 Omnichannel & ExtensibleTheme 4 Multi-author save conflicts ($340) · Theme 14 SMS reporting (also L3) · Theme 15 SMS credits transparency ($3,592) · Theme 16 SMS TCPA ($57,000) · Theme 17 SMS depth (no $)~$60.9K/mo (the $57K TCPA dominates)

GLens B · Cited HVC themes by JTBD phase

JTBD PhaseCited HVC themes that break this phaseTotal cited $/mo
1. Choose structureTheme 1 No bulk template migration ($330) · Theme 6 Template list / wizard surfacing ($1,950)~$2.3K/mo
2. Establish brand & styleTheme 7 LP/form fonts ($655) · Theme 8 Brand Kit incident · Theme 9 Multi-brand ($2,460) · Theme 10 Font upload ($3,350) · Theme 11 CA rediscovery ($2,650)~$9.1K/mo
3. Add & place contentTheme 12 Content Studio image loading ($621) · Theme 13 Canva sync ($2,500+)~$3.1K/mo
4. Refine & polishTheme 3 NEB rendering ($1,820) · Theme 4 Multi-author save ($340) · Theme 5 Block ordering ($410) · Theme 11 CA non-banner workflows~$2.6K/mo
5. Personalize & tailorTheme 17 SMS merge tag depth (no $)
6. Preview & QA loopTheme 14 SMS reporting empty/N/A ($1,386) · Theme 15 SMS credits hidden ($3,592) · Theme 16 SMS TCPA $57K incident~$62K/mo (the TCPA incident dominates)
7. Learn & reuseTheme 1 No bulk migration (saves don’t survive); Theme 2 Support dead-ends on migration ($504); Theme 4 Multi-author conflicts (sessions lost)~$1.2K/mo
Synthesis — what the framework reveals about cited HVC pain

Two surprises emerge: (a) the $57K SMS TCPA incident dominates the dollar exposure on Level 6 (Omnichannel) and Phase 6 (QA loop) — not on the Compose Loop where Voice of Customer complains loudest. (b) Phase 2 (Establish brand & style) carries $9.1K/mo across 5 cited themes — this is the most concentrated dollar pain in any JTBD phase outside the TCPA incident, and it directly justifies why P1.2 Brand Kit reliability (4 initiatives) gets the heaviest P1 investment. The Builder Hierarchy lens also confirms L1 Reliable carries the most cited dollars — which validates P1.5 Builder SLOs as the operational quality gate.

Reframe sources: Builder Hierarchy + 7-Phase JTBD adopted from Nuni Builder Strategy & Roadmap (Ose Amiegheme, Erin McCue, JB Lovell, Ashley Wiesner). Original HVC data from Slack #hvc_feedback, #mc-hvc-escalations, #mc-feedback-summary (Nov 2024 → May 2026); 17 cited themes / ~$95K/mo cited MRR.

User Research · 50 HeyMarvin videos · Campaign Builder synthesis

The Mailchimp campaign builder is universal — and bifurcated

Synthesized from 25 customer briefs across 50 transcribed HeyMarvin UX research videos (~25 hours). Every theme below is backed by named customers + verbatim time-coded quotes in deepakp1308/mailchimp-campaign-builder-research (briefs/synthesis.md + per-customer briefs/*.md).
Source: Hannah Graffeo + UXR panel
Scope: Campaign creation / NEB / templates / assets
Page: 1 of 3
50
Videos transcribed · 25 substantive briefs
25
Hours of audio · verbatim [HH:MM:SS] quotes
5
Distinct workflow shapes in the builder
5+
Customers with years-long feature discovery gaps

JUDGEQuality assessment

STRENGTHS
  • Headline reframes the problem. "Bifurcated builder" explains happy-path simple senders vs everyone else — aligns with Slack dual-builder + Brand/Canva pain.
  • Discovery is the largest lever — Jeff didn't find My Products for 3.5 years; Jack missed New Builder for years — matches high Write-with-AI/churn subtext in Product Health.
  • Evidence chain is intact in repo markdown (YAML frontmatter + 8-section brief template).
GAPS
  • No MRR per finding — pair with HVC Risk Map for dollar exposure.
  • Watch Party = internal voice — cite as product-team diagnosis, not customer quote.
  • Competitor absence — Klaviyo rarely named; Bee.io / Canva / Adobe Express are the organic comparators.

1Headline finding

Friction piles into four places: layout flexibility, multi-author collaboration, asset/library management, and discoverability of what already shipped. Happy-path replicators (Kim, Courtney, Andrew, Nicholas) ship same-day. Everyone else pays tax.

"The problem is you need to make our life easier. No more complicated." — Andrea D'Ercole · [00:35:18] · most-quotable customer line in synthesis

2Who's using the campaign builder

Universal surface — all 25 substantive briefs touch the builder. Segment mix mirrors Automation research (DSB heavy US, ProServ split US/UK, internal dogfood + Watch Party).

Workflow shapeWhat it isExamples
Fast Monday-morning senderReplicate last week, swap, ship 30–90 minAndrew, Andrea, Kim, Clint
All-week ad-libberLiving newsletter; multi-author — save conflicts dominateJack Hally (10–20 logins/day)
Brand-first methodicalLayout/padding before copy; Brand Kit; wants saved blocksWes Turner, Bob Gray
Third-party in the loopBee.io / Canva / Express because MC canvas can'tAndrea, Wes, Jack
Low-frequency / discovery gapMonthly send; advanced features unseen for yearsShannon, Matt, Gilles

Primary synthesis: briefs/synthesis.md.

User Research (cont.) · Templates & canvas mechanics

Template IA mismatch · layout rigidity · collaboration · A/B architecture

Sections 3–6 of the executive synthesis, tightened for this brief.
Page: 2 of 3

3Template gallery — failure modes

  • B2B / ProServ gap — Hannah to Chris Rich: "many… not tailored towards your organization" [00:28:15]
  • Over-designed / intimidating — Jillian Ney: "feel more like e-commerce emails" [00:06:09]; Wes ignores category IA, browses layout-only [00:07:06]
  • First build harder than ongoing edits — Nicholas H on starting from zero [00:06:01]

4Canvas — layout, images, library, collaboration

ClusterFindingVoice
LayoutDrag-drop restrictive vs Photoshop/Bee; asymmetric resize; 2-col = 3 steps (Kyle)Andrea live demo [00:11:41] · Kyle [00:22:25]
AssetsDuplicate uploads; resize prompt ×15–20 images; "hunting in the attic" (Peter)Andrew [00:12:38] · [00:25:31] · Peter [00:14:16]
DiscoveryMy Products / Woo invisible 3.5 yrs (Jeffrey)Devin demo [00:21:13]
Multi-authorSave conflicts — Jack, Kyle, Bianka team fearJack [00:11:54] · Kyle [00:14:34]
Brand taxPill CTAs reshaped every send (Wes); link color stuck (Nicholas)Wes [00:14:10] · Nicholas [00:13:11]

5A/B testing & pre-flight

Wes: multivariate path forces subject-line decision before content — he deleted a finished email and re-entered via MV path to test body content [00:25:15][00:27:04]. Kyle schedules 15 min out because Send feels scary [00:27:55]; Send enabled before schedule set [00:26:30].

6Internal Watch Party (non-customer)

Hannah Graffeo diagnosis applied to Mailchimp: "people will be doing one task and then they want to jump to another task and there's not a logical flow" [00:18:05]. Use as internal validation of connective-flow gaps — not customer attribution.

User Research (cont.) · Reporting, discovery, bets

Post-send benchmarking · cross-cutting discovery · top 5 bets

Page: 3 of 3

7Reporting & trust

  • No vertical benchmarks — Matt [00:30:39]
  • Jeffrey: Sept attribution methodology shift → trust event (confirmed internal change)
  • Bianka: wants email + SMS + all touches in one reporting view

8Discovery table (strongest cross-cut)

CustomerUndiscoveredDuration
Bianka KissA/B testing"A number of years"
Jack HallyNew Email Builder4–6 years on inherited legacy template
Jeffrey DavisMy Products / Woo pull3.5 years
Clint BartleyWelcome automation (DRAFT)1 year
Wes TurnerSaved blocks (pre-ship)At time of call

9Top 5 bets (from synthesis)

BET 1 · Saved blocks / section reuse — PM-confirmed in-flight during Wes session; Wes/Peter/Kyle all want recurring sections.
BET 2 · Discovery / activation for high-frequency users — changelog, weekly feature drip, DRAFT resurrect, proactive chatbot suggestions (Clint/Bianka patterns).
BET 3 · B2B / ProServ template gallery lane — skeleton layouts, information-dense, not mock e-commerce shells.
BET 4 · Real multi-author editing — presence, history, staging; Jack/Kyle/Bianka convergence.
BET 5 · Direct manipulation upgrades — free/asymmetric image resize, 1-click two-column, post-hoc A/B on sections, Brand-Kit-aware CTA defaults — closes Bee.io gap.

10Caveats

  • Self-selected research panel (Hannah-recruited) — not a random SME sample.
  • Whisper artifacts on a few transcripts (noted in repo).
  • No organic Klaviyo/ActiveCampaign naming — comparators are design tools + adjacent SaaS.

XREFCross-tabs

  • HVC Risk Map — Slack $ exposure on same themes (fonts, Canva, NEB, SMS).
  • Product Health — bulk email YoY shrink, AI churn.
  • Roadmap to Win — foundational gaps / steals.

Repos: github.com/deepakp1308/mailchimp-campaign-builder-research · Optional static site in site/ if published to GitHub Pages.

User Research (cont.) · Builder Hierarchy + JTBD reframe

5 UR Bets + Discovery table + Workflow Shapes mapped to Builder Hierarchy + JTBD Journey

Same User Research data (25 customer briefs across 50 HeyMarvin videos), reframed through the two analytical lenses from the Nuni Builder Strategy & Roadmap. The reframe converts qualitative research patterns into structural maturity gaps + workflow-step friction.
Lens A: 6-Level Maslow Hierarchy
Lens B: 7-Phase JTBD Journey
Page: 4 of 4

FLens A · UR Bets + Discovery patterns by Builder Hierarchy level

Builder LevelUR pattern that surfaces hereInitiative response
L1 ReliableDiscovery table: customers don’t trust the system (e.g. Bianka’s team “scared by the migration”); Andrea live demo of asset workflow breakdownP1.5 Builder SLOs as published quality contract
L2 Mobile / RenderingWorkflow Shape #1 (fast Monday-morning sender): customers ship before validating mobileI-1.1.6 Light/dark mode + bg images; I-1.1.7 Pre-send checks upgrade
L3 Efficient WorkflowUR Bet #5 Direct manipulation upgrades (asymmetric resize, 1-click 2-column, post-hoc A/B); Workflow Shape #4 “Third-party in the loop” (Andrea/Wes/Jack route around MC via Bee.io / Canva); Andrea quote “you need to make our life easier. No more complicated.”P1.1 NEB UX bug fixes + P3.1 onboarding + P3.3 discovery
L4 Brand-Native & ReusableUR Bet #1 Saved blocks / section reuse (PM-confirmed in flight) — the most cited bet, mentioned by Wes / Peter / Kyle / Bob; Workflow Shape #3 (Brand-first methodical: Wes / Bob, “wants saved blocks”)P2.1 Universal Content (Q2 ★); I-1.2.3 multi-brand kits; I-2.3.2 Brand Kit auto-applied
L5 Intelligent & AI-Powered(no direct UR bet on AI; Discovery table shows discovery gap is a learning issue, not an AI issue)I-3.1.4 AI Email Setup Agent + P4 entire pillar address
L6 Omnichannel & ExtensibleUR Bet #4 Real multi-author editing (Jack / Kyle / Bianka convergence — the second most cited bet); Bianka direct ask: “email + SMS + all touches in one reporting view”; Workflow Shape #2 (All-week ad-libber: Jack 10–20 logins/day, save conflicts dominate)P5.3 Real-time co-edit (Q5 ★) + P5.1 unified canvas + P5.4 governance

GLens B · Discovery table by JTBD phase — where customers got stuck

The Discovery table from User Research lists 5 customers with multi-year undiscovered features. Mapping to JTBD phases shows the discovery gap is heavily concentrated in Phases 1–2 (Choose structure + Establish brand) and Phase 7 (Learn & reuse). Customers find the “new” thing they need too late because the workflow never surfaces it at the moment of need.

CustomerWhat they didn’t discoverDurationJTBD Phase blockedInitiative
Bianka KissA/B testingYearsPhase 6 (QA loop)I-3.3.2 contextual feature discovery prompts
Jack HallyNew Email Builder4–6 yrs on inherited legacy templatePhase 1 (Choose structure)I-3.3.1 in-app changelog + weekly digest
Jeffrey DavisMy Products / Woo product pull3.5 yearsPhase 3 (Add + place content)I-3.3.2 contextual feature discovery + I-3.4.1 Free uplift
Clint BartleyWelcome automation (in DRAFT)1 yearPhase 7 (Learn + reuse) — first send never happenedI-3.3.3 DRAFT-resurrect campaign
Wes TurnerSaved blocks (pre-ship)At time of callPhase 7 (Learn + reuse)P2.1 Universal Content + I-2.1.3 adoption funnel

HLens B applied to the 5 Workflow Shapes — where each persona feels friction

Workflow ShapeExamplesPhase where friction lives
#1 Fast Monday-morning senderAndrew, Andrea, Kim, ClintPhase 1 (Choose structure: replicate last week) · Phase 6 (QA loop: ship without thorough preview)
#2 All-week ad-libberJack Hally (10–20 logins/day)Phase 4 (Refine + polish: save conflicts) · Phase 6 (multi-user QA breakdown) — UR Bet #4 territory
#3 Brand-first methodicalWes Turner, Bob GrayPhase 2 (Establish brand & style: layout/padding before copy) · Phase 7 (wants saved blocks) — UR Bet #1 territory
#4 Third-party in the loopAndrea (Bee.io), Wes (Canva), Jack (Express)Phase 3 (Add + place content: MC canvas can’t hold their work) — P1.3.1 Canva sync + I-1.4.2 CA non-banner expansion fix
#5 Low-frequency / discovery gapShannon, Matt, GillesPhase 1 (Choose structure: don’t know what’s available) · Phase 7 (Learn + reuse: capability never compounds) — P3.3 entire sub-pillar fixes
Synthesis — what the framework reveals about UR data

Three observations: (a) UR Bets #1 (saved blocks) and #4 (real multi-author) are not just “features customers want” — they map directly to Builder Hierarchy Levels 4 and 6, which are exactly where Mailchimp scored 1 and 0 vs Klaviyo 3. The qualitative research independently arrived at the same maturity gaps. (b) The Discovery table shows the gap is in Phases 1–2 and Phase 7 — bookend phases — matching the Mailchimp VoC reframe pattern (clunky-and-outdated is felt at the start and the end of the workflow). (c) Workflow Shape #4 “Third-party in the loop” reveals that customers literally route around Mailchimp at Phase 3 (Add + place content) — reinforcing P1.3 Canva sync + P1.4 Creative Assistant rediscovery as urgent.

Reframe sources: Builder Hierarchy + 7-Phase JTBD adopted from Nuni Builder Strategy & Roadmap (Ose Amiegheme, Erin McCue, JB Lovell, Ashley Wiesner). Original UR data from Hannah Graffeo + UXR panel; 50 HeyMarvin videos / 25 customer briefs / 5 UR bets / Discovery table / 5 Workflow Shapes; full evidence in deepakp1308/mailchimp-campaign-builder-research (briefs/synthesis.md + per-customer briefs/*.md).

Tab 10 · Nuni YoY Audit

QA-validated YoY metrics, business-impact projection, and target-state model

Paid-Nuni cohort (proxy: paid users who signed up after Nuni was made default for new accounts on Jul-1, 2023). Trailing 12 months May 2025–Apr 2026 (T0) vs prior 12 months May 2024–Apr 2025 (T-1). Source: BigQuery mc-business-intelligence.mailchimp.users_signup_data, users_first_sends, users_packages, users_plan_updates + qualtrics.survey_responses (Nuni Feedback Badge, SV_9SwJVJm2BNRqXfo).
v1.2 · 4 pages · QA-validated
Editor-PM target ARR swing: $20–24M/yr
Of which: loss recovery ~$13–20M + additional swing ~$0–7M
Cross-functional (Mktg+Pricing) partners tracked for context, not in editor commit

1.1The headline — what the editor PM owns vs. what they don’t

Editor-owned leading indicators are mixed: bulk builder adoption is up (+1.9pp to 92.7%), SMS adoption growing (+1.5pp to 6.1%), but bulk builder activation degraded −2.4pp to 60.6% — more paid users touch the builder, fewer become habitual senders. Bulk Abandon volume up +10.4% YoY (295K → 326K/mo). Quality side is flat-to-better (CSAT +15pp Net, churn −1.4pp, repeat-rate flat). Cross-functional volume drivers (paid signups −27%, free→paid −12% rel.) are Marketing/Pricing dependencies, not editor-PM levers. BigQuery YoY audit on paid-tier active users, May 2026 (bi_aggregate.product_journey_monthly + users_first_sends + users_packages + qualtrics.survey_responses).

1.2Editor-owned leading indicators (adoption / activation / 30-day repeat)

These are the metrics the editor PM owns — product decisions move them directly. Source: bi_aggregate.product_journey_monthly for paid users (excluding free / payg / pre paid / pro/module tiers).

Bulk builder adoption (% paid users touched)
92.7%
vs T-1: 90.8%
+1.9pp YoY
Bulk builder activation (% touched → Established)
60.6%
vs T-1: 63.0%
−2.4pp (worse)
SMS builder adoption (% paid users touched)
6.1%
vs T-1: 4.6%
+1.5pp YoY
SMS builder activation (% touched → Established)
9.1%
vs T-1: 6.8%
+2.3pp YoY
30-day repeat send rate (per first-sender)
83.2%
vs T-1: 83.7%
−0.5pp (flat)
30-day repeat senders (volume)
104,116
vs T-1: 146,159
−28.8% YoY
Bulk Abandon volume / mo
325,869
vs T-1: 295,054
+10.4% (worse)
GenAI Content Gen Bulk adoption
14.8%
vs T-1: 15.5%
−0.7pp

1.3Quality / retention metrics (editor-influenced, multi-owner)

Editor PM influences these but does not solely own them — partner with Onboarding / Pricing / Support.

Median days to first send
5 days
vs T-1: 6 days
−1 day (better)
90-day churn rate (true)
32.1%
vs T-1: 33.5%
−1.4pp (better)
90-day downgrade rate
20.1%
vs T-1: 21.8%
−1.7pp (better)
90-day upgrade rate
6.09%
vs T-1: 5.83%
+0.26pp (flat)
CSAT avg (Q3 1–5, Nuni Badge)
2.49
vs T-1: 2.24
+0.25 / Net CSAT +15.2pp
Sent first email in 90d (paid Nuni signup cohort)
48.4%
vs T-1: 49.4%
−1.0pp
Abandoned in 90d (paid Nuni signup cohort)
51.6%
vs T-1: 50.6%
+1.0pp (worse)
Klaviyo bake-off win rate (estimate)
<10%
vs T-1: <10%
Flat · instrumentation gap

1.4Cross-functional dependencies (NOT editor-PM owned, tracked for context)

Top-of-funnel acquisition + free→paid pricing-funnel are owned by Marketing + Pricing. Editor PM cannot move these directly. Tracked for context because they shape the pool feeding adoption.

Paid signups (Nuni cohort, 10mo) — Marketing-owned
258,385
vs T-1: 353,733
−27.0% YoY
Free → paid 90d — Pricing-owned
12.64%
vs T-1: 14.41%
−1.77pp (−12.3% rel.)
Fast paid converters (≤30d) — Marketing+Pricing
42,116
vs T-1: 60,271
−30.1% YoY

1.5Why this matters — activation is the bleeding edge

Activation degradation (editor-owned)

More users touch the builder, fewer become habitual

  • Bulk activation 63.0% → 60.6% (−2.4pp YoY).
  • Bulk Abandon volume +10.4% (295K → 326K/mo).
  • Pattern: adoption is HEALTHY (+1.9pp), activation is BREAKING.
  • Implication: the editor onboards but doesn’t convert into the habitual loop.
SMS upside (editor-owned, undertapped)

SMS adoption + activation both improving but TINY

  • SMS adoption 4.6% → 6.1% (+1.5pp).
  • SMS activation 6.8% → 9.1% (+2.3pp).
  • Only ~62K paid users / mo even touch SMS — vs ~941K touching bulk.
  • Biggest single editor-PM lever for unified-builder ARR.
Quality side (editor-influenced) — not bleeding

The customers who become habitual are slightly better off

  • 30-day repeat send rate flat at 83% — loop is intact.
  • Net CSAT +15pp YoY (still −29 net — gap to neutral remains).
  • True 90-day churn improved −1.4pp, downgrades −1.7pp, time-to-send −1 day.
  • Implication: fix activation; the rest is moving the right way.

Definitions & cohort: Adoption = stages 2_Explore + 3_Try + 4_Establish + 5_Abandon ÷ total paid users (1+2+3+4+5). Activation = 4_Establish ÷ (2+3+4+5) = % of users who touched the builder that became habitual senders. Source: bi_aggregate.product_journey_monthly trailing 12 months, package NOT LIKE 'free%' AND NOT IN ('payg','pre paid','pro/module/other','unknown'). Funnel cohort (90-day first-send) uses Nuni paid signup proxy (signed ≥ Jul-1-2023 with paid package). All YoY comparisons are like-for-like (10-month observation window for funnel; 12-month average for stage-state).

Page 2 · QA / QC findings

What was wrong, what was right, what to caveat

Two metrics needed correction; eight passed. Three caveats remain on top of corrected numbers.
2 fixes · 5 passes · 3 caveats

2.1Errors found and corrected

FIX 1 · CSAT MEASURE

CSAT 1–5 (Nuni Feedback Badge)

Was: SenScore-derived sentiment from open-text Q5 (−1.9pp negative-sentiment improvement).
Now: Q3 raw 1–5 rating — avg 2.24 → 2.49 (+0.25); Net CSAT −44.5 → −29.3 (+15.2pp).
Why: survey_details listed Q1 as the rating, but actual responses use QID3. Q1/SenScore was the open-text sentiment derivative, not the headline CSAT. Q3 is the single-question 1–5 rating customers see on the badge.

FIX 2 · CHURN DEFINITION

90-day churn (true)

Was: users_plan_updates.cancelled_at IS NOT NULL (21.6% → 19.2%).
Now: users_packages.valid_through_date with no other active paid pkg after — 33.5% → 32.1% (−1.4pp).
Why: cancelled_at cancels the plan-update record (e.g., “parent subscription was cancelled”), NOT the user’s paid subscription. Real churn is ~10pp higher than originally reported.

2.2Checks that passed (5)

PASS · PAID FILTER

package_id NOT LIKE 'free%'

Inspected all 14 distinct package_ids in window. Only free_monthly_plan_v0 + free_commerce_plan_v1 are free; filter is exact.

PASS · COHORT PROXY

Nuni cohort = signed ≥ Jul-1-2023

Nuni was made default for new account signups post Jul-2023; this is the cleanest available proxy without a feature-flag join.

PASS · SOURCE FIELDS

signup_date + first_send

Account-creation timestamp + first real campaign send (excludes test sends) from mailchimp.users_signup_data + users_first_sends.

PASS · OBSERVATION WINDOW

Consistent 90-day window per user

Both cohorts capped to signups with ≥90 days of observation post-signup, eliminating right-censoring bias.

PASS · LIKE-FOR-LIKE WINDOWS

10-month observation matched

T0 = signed May 2025–Feb 2026 (so all signups had ≥90d to send by query date). T-1 = signed May 2024–Feb 2025 (same length).

PASS · CSAT SCALE

QID3 raw 1–5 rating

Mapped Terrible=1…Excellent=5 from labels field (not values). Net CSAT = %top-2 minus %bottom-2.

2.3Caveats that remain (3)

CAVEAT · SELECTION BIAS

Survey is a feedback badge

Self-selection toward people with strong views (esp. negative). Trends YoY remain comparable (same selection bias both periods); absolute level may overstate negativity.

CAVEAT · NUNI VS LEGACY

Q2 lets users tag “Legacy builder”

~5–10% of badge responses may be about Nea, not Nuni. Conservative reading of CSAT (true Nuni-only negativity slightly lower than 55.5%).

CAVEAT · COHORT IMPURITY

Cohort proxy ≠ pure Nuni usage

Some users in the Nuni cohort may use Classic / Legacy templates or CJB Nuni. Directional only; can’t surgically isolate without feature-flag join (open ask to data team).

SQL audited: All 8 queries inspected against INFORMATION_SCHEMA for source tables; join keys verified; denominators traced; date arithmetic confirmed calendar-day. Two metrics (CSAT, churn) re-pulled with corrected definitions before reporting.

Page 3 · Business impact projection

Conservative editor-attributable ARR exposure: ~$13–20M/yr

Two-layer attribution. Layer 1 = direct/booked ARR loss already in financials. Layer 2 = modeled / opportunity cost. Conservative editor causal share applied to each lever (15–40%) since editor is one of many drivers (macro, marketing, competition, pricing). Base ARPU: Standard at-booking $45.35/mo, steady-state $91.44/mo (BQ bi_aggregate.mbr_monthly).
Layer 1: $13.4M/yr
Layer 2: $6.5M/yr
Total band: $13–20M/yr
Methodology consistent with Loss Attribution L2.

3.1Layer 1 — Direct / booked ARR loss (5 levers)

L1a · Paid signup volume decline

−27% YoY paid signups (Nuni cohort)

vol_lost_annualized = 95.3K (10mo) × 12/10 = 115K/yr
arr_per_lost_signup = $45.35/mo × 12 = $540/yr
editor_share = 15% (one of many drivers)
impact = 115K × $540 × 15% = $9.3M/yr

Editor share kept low because top-of-funnel acquisition is dominated by marketing + macro, not editor quality alone.

L1b · Free → paid conversion drop

−1.77pp absolute (−12.3% rel.) on ~2M signups

vol_lost_annualized = ~38K/yr fewer paid conversions
arr_per_lost_conv = $540/yr
editor_share = 20% (editor IS the touchpoint)
impact = 38K × $540 × 20% = $4.1M/yr

Editor share higher than L1a because the editor is the dominant first-paid trigger (you upgrade to send).

L1c · 90-day churn (rate IMPROVED)

33.5% → 32.1% (−1.4pp better)

marginal_impact = $0
No incremental loss attribution. Volume bleed already counted in L1a.

Don’t double-count: fewer at-bats → fewer churns by definition. Rate improvement is a small positive offset.

L1d · Downgrades (rate IMPROVED)

21.8% → 20.1% (−1.7pp better)

marginal_impact = $0
No incremental loss attribution.
L1e · Upgrades (rate FLAT)

5.83% → 6.09% (+0.26pp)

marginal_impact = $0
Flat — no marginal loss.
LAYER 1 SUBTOTAL

~$13.4M/yr direct / booked editor-attributable ARR

L1a + L1b = $9.3M + $4.1M = $13.4M/yr

This is the floor — what we can defend in front of Finance/CFO without modeling assumptions beyond editor causal share.

3.2Layer 2 — Modeled / opportunity cost (3 levers, additive)

L2a · Repeat-usage VOLUME

146K → 104K repeat senders (−28.8%)

lost_repeat_users = 42K
retention_uplift_per_repeat = +6mo @ $91.44/mo = $549 LTV
total_LTV_at_risk = 42K × $549 = $23M LTV (3-yr)
editor_share = 30%
3-yr LTV = $6.9M → ARR ~$2.3M/yr
L2b · CSAT gap-to-neutral

Net CSAT still −29.3 (target neutral)

gap_to_neutral = 30pp
churn_reduction = ~3pp (1pp per 10pp NPS, academic)
active_paid_users = 320K Standard
opportunity = 320K × 3% × $91.44 × 12 = $10.5M
editor_share = 40% (editor dominates this survey)
$4.2M/yr
L2c · Time-to-first-send

6 days → 5 days (improved)

marginal_impact = $0
Activation acceleration captured in L1a/b uplift.
LAYER 2 SUBTOTAL

~$6.5M/yr modeled / opportunity-cost editor-attributable ARR

L2a + L2b = $2.3M + $4.2M = $6.5M/yr

Modeled with academic benchmarks (1pp churn per 10pp NPS); editor causal share 30–40%. Pair with Loss Attribution L2 cited band ($14–28M) which validates the same range from Slack-cited HVC themes.

3.3Total conservative ARR exposure — the band

Low (10% direct / 25% modeled)
~$10M
If we assume editor is rarely the swing factor
Base (15–20% direct / 30–40% modeled)
~$13–20M
Use this for the Strategy Memo + Loss Attribution L2 KPI
High (25% direct / 50% modeled)
~$26M
Plausible if you believe Klaviyo is taking direct share via editor

3.430-day repeat usage — YoY

Rate (per first-sender)

83.7% → 83.2% (−0.5pp, flat)

Of new paid signups who sent their first email, ~83% sent again within 30 days — both years. The repeat-send loop is intact.

Volume (absolute)

146,159 → 104,116 (−28.8%)

Same rate on a smaller pool. We have 42K fewer customers running the editor twice in their first 30 days — not because they didn’t come back, but because there were fewer of them to begin with.

Cross-references: Layer 1 figures feed back into Loss Attribution Page 1 KPI band ($14–28M); Layer 2 modeling parallels Growth Model levers L1 (bulk recovery), L4 (trial-to-sub), L5 (churn). 30-day repeat is the engagement KPI behind Initiative Canvas P5 (omnichannel) + P3 (activation).

Page 4 · Target-state model (editor-PM owned)

Editor-PM commitment: $20–24M ARR swing by FY27 — recover most of the loss + modest upside

Per-metric target values that, taken together, recover most of the editor-attributable loss (~$13–20M) and contribute a meaningful additional swing (~$0–7M). Editor-PM owned levers only — cross-functional dependencies (paid signup volume, free→paid pricing funnel) are tracked for context but not part of this commitment. SMS adoption removed from the math (still tracked as a leading indicator on Page 1) since it depends on go-to-market motion. Each target is credible-but-stretched — anchored to industry benchmarks where they exist.
Loss to recover: ~$13–20M
Additional swing: ~$0–7M
Editor-PM target: $20–24M ARR / yr
9 levers · 4 sensitivity scenarios

4.1Per-metric target scorecard — editor-PM owned (the nine levers)

Leading indicators (L1–L4) = bulk adoption + bulk/SMS activation + 30-day repeat — the metrics editor PM moves directly. Quality / retention (L5–L8) = customer outcomes editor PM influences with partners. Competition (L9) = bake-off win rate driven by deliverables. SMS adoption intentionally excluded (depends on GTM motion); SMS activation retained (editor product moves it).

Metric T-1 baseline T0 actual FY27 target Mechanism Causal share Marginal $/yr % of $24M
Leading indicators — editor-PM owned (the metrics product moves directly)
L1. Bulk builder adoption (% paid users touched) 90.8% 92.7% 98% Brand-native templates, Universal Content starter blocks, AI Email Setup Agent, NEB Code Mode, in-app onboarding nudges. 50% $4.4M 18%
L2. Bulk builder activation (% touched → Established) 63.0% 60.6% 75% Reduce abandonment via P1 reliability + P1.5 SLOs + AI Setup Agent + Brand Kit auto-applied + Universal Content reuse + cross-browser regression suite. 50% $1.9M 8%
L3. SMS builder activation (% touched → Established) 6.8% 9.1% 25% Email-to-SMS template porting, conversational SMS, send-time intelligence, omnichannel reporting in-canvas. 50% $1.2M 5%
L4. 30-day repeat send rate 83.7% 83.2% 92% Smart Send Time, AI Performance Watchdog, Universal Content for fast iteration, omnichannel triggers, in-canvas revenue. 35% $2.1M 9%
Quality / retention — editor-influenced (multi-owner with onboarding / pricing / support)
L5. 90-day churn (true) 33.5% 32.1% 22% Better activation (L2) + Builder SLOs (P1.5) + cited HVC bug-fix + Klaviyo countermoves + sticky onboarding flows. 40% $1.7M 7%
L6. 90-day downgrade 21.8% 20.1% 13% Repeat-usage habit (L4), omnichannel value-add (SMS activation L3), AI add-on attach, in-canvas revenue surfacing. 35% $0.4M 2%
L7. 90-day upgrade 5.83% 6.09% 12% AI Email Setup paid uplift, SMS attach, in-canvas revenue, premium templates, Brand-Kit-aware AI add-on. 35% $0.5M 2%
L8. Net CSAT (Nuni Badge) −44.5 −29.3 +30 (positive) Builder SLOs (P1.5), parity polish, AI Assistant, Universal Content, 6 Klaviyo gap closures, render fidelity guarantees. 30% $5.7M 24%
Competition — deliverable-driven (Editor PM + Sales Eng partnership)
L9. Klaviyo bake-off win rate <10% (estimate) <10% 35% All P1–P5 deliverables landing; explicit ammunition for sales (Builder SLOs + Universal Content + Brand-Kit-native AI + multi-brand kits + real-time co-edit). 40% $6.0M 25%
EDITOR-PM OWNED TOTAL (L1–L9, all editor-owned levers) $23.9M ~100%

Why $20–24M is the right band: recovers most of the editor-attributable loss ($13–20M) and delivers a modest additional swing ($0–7M). 100% target hit lands at $23.9M (top of the band); 50–75% hit covers loss recovery only. SMS adoption removed from the math — depends on GTM motion (sales pitch, free-trial mechanics) more than editor product. SMS activation (L3) is retained because that’s editor-owned (template porting, conversational SMS, in-canvas reporting). Cross-functional dependencies (paid signups, free→paid) are tracked on Page 1 §1.4 for context but not part of editor commit. Sensitivity in 4.3 below.

4.2Lever calculations (full math)

Editor-PM owned levers only. ARPU sources: bi_aggregate.mbr_monthly (Standard at-booking $45.35/mo, steady-state $91.44/mo, SMS add-on est. $20/mo). Volume base: 1,015,648 paid active users / mo (T0 average from product_journey_monthly). SMS adoption excluded (GTM-driven); X1/X2 (paid signups, free→paid) excluded (Marketing/Pricing owned).

L1 · Bulk builder adoption (LEADING INDICATOR)

92.7% → 98% (+5.3pp on 1.02M paid users)

incremental_adopters = 5.3pp × 1.02M = 54K more users / mo touching
conversion_to_active = ~15% become net-new active senders
arpu_steadystate = $91.44/mo × 12 = $1,097/yr
editor_share = 50% (this IS the editor PM’s job)
impact = 54K × 15% × $1,097 × 50% = $4.4M/yr
L2 · Bulk builder activation (LEADING INDICATOR · reverse the −2.4pp YoY)

60.6% → 75% (+14.4pp of those who touched)

incremental_established = 14.4pp × 941K touched/mo = 135K incremental Established
prevented_churn = 25% would have abandoned in 12mo
arpu = $91.44/mo × 12 = $1,097/yr
editor_share = 50%
impact = 135K × 25% × $1,097 × 50% = $1.9M/yr (conservative)
L3 · SMS builder activation (LEADING INDICATOR)

9.1% → 25% (+15.9pp of SMS-touched)

incremental_sms_established = 15.9pp × 62K touched SMS/mo = 9.9K
arpu_sms_attach = $240/yr
editor_share = 50%
impact = 9.9K × $240 × 50% = $1.2M/yr
L4 · 30-day repeat send rate (LEADING INDICATOR)

83.2% → 92% (+8.8pp)

delta_repeaters = 8.8pp × 125K T0 senders = 11K incremental
retention_uplift = +6mo @ $91.44/mo = $549 LTV
editor_share = 35%
impact (3-yr LTV) = 11K × $549 × 35% = $2.1M LTV ~ $2.1M/yr ARR
L5 · 90-day churn reduction (QUALITY)

32.1% → 22% (−10.1pp)

churn_users_saved = 10.1pp × 50K fast paid converters/yr = 5.0K
arpu = $1,097/yr (steady-state)
editor_share = 40%
impact = 5.0K × $1,097 × 40% = $2.2M/yr (~$1.7M conservative)
L6 + L7 · Tier movement (QUALITY, smaller direct $ but high signal)

Downgrades 20.1% → 13%; upgrades 6.09% → 12%

L6: 7.1pp × 50K × $400/yr (downgrade ARPU delta) × 35% = $0.4M
L7: 5.91pp × 50K × $300/yr (upgrade ARPU delta) × 35% = $0.5M
L8 · CSAT → positive zone (QUALITY · biggest single $)

Net CSAT −29 → +30 (59pp swing)

churn_reduction = 5.9pp (1pp / 10pp NPS academic benchmark)
active_users = 320K Standard
opportunity = 320K × 5.9% × $1,097 = $20.7M
editor_share = 30%
impact = $6.2M/yr (~$5.7M conservative cap)
L9 · Klaviyo bake-off wins (COMPETITION)

Win 35% of bake-offs (was <10%)

bake_offs_won_incremental = ~5K accounts/yr (mid-market)
arpu_per_account = ~$3.4K/yr (mid-market avg)
editor_share = 40% (P1–P5 deliverables ARE the pitch)
impact = 5K × $3.4K × 40% = $6.0M/yr

Excluded from the math: SMS builder adoption (depends on GTM motion — sales pitch, free trial, paywall mechanics — rather than editor product directly); paid signups (Marketing-owned); free→paid 90d (Pricing-owned). All three are tracked on Page 1 as observation metrics; their movement may indirectly help editor PM (more pool to work with) but is not an editor commitment.

4.3Sensitivity — what hits if not all targets land

50% of editor targets hit
~$12M
Below the loss-recovery floor ($13–20M). Goal missed.
75% of editor targets hit
~$18M
Recovers loss midpoint. Within the $20–24M target band’s lower edge.
100% of editor targets hit
~$24M
Top of the $20–24M target band cleared. Recovers loss + delivers ~$4–7M additional swing.
125% (over-perform on 1–2)
~$30M
Plausible if Klaviyo bake-offs accelerate or CSAT moves faster than benchmark.

4.4How the targets map to existing pillars and quarters

Lever Owns the metric Initiatives that move it (Canvas) Lands by
L1. Bulk adoption Editor PM P2 (Universal Content + NEB Code Mode), P4.4.4 (AI Setup Agent), brand-native templates, in-app onboarding (P3) Q3 FY27
L2. Bulk activation Editor PM P1 (reliability), P1.5 (SLOs), P4.4.4 (AI Setup Agent), Brand Kit auto-applied (P2), Universal Content (P2) Q4 FY27
L3. SMS activation Editor PM Email-to-SMS template porting (P5), conversational SMS (P4.4.5), in-canvas reporting (P5), send-time intelligence (P4.4.5) Q5 FY28
L4. 30-day repeat Editor PM + Lifecycle P5.1.5 (Push acceleration), P4.4.5 (Smart Send Time), P4.4.6 (AI Performance Watchdog), P5 (omnichannel) Q5 FY28
L5. 90-day churn Editor PM + Onboarding P1.5 (Builder SLOs), P1 (cited HVC bug-fix), L2 activation flow-through Q4 FY27
L6–L7. Tier movement Pricing + Editor PM P3.4.3 (engagement-based pricing), P4 (AI add-on attach), P5 (SMS attach), in-canvas revenue surfacing Q4 FY27
L8. CSAT Editor PM P1.5 (SLOs), P1 (parity), P4 (AI Assistant), P2 (Universal Content), all 6 Klaviyo gap closures Q5 FY28
L9. Klaviyo bake-offs Editor PM + Sales Eng All 6 Klaviyo countermoves (P3.1.4, P3.4.3, P4.4.4–6, P5.1.5) + Builder SLOs (P1.5) Q6 FY28
(Excluded) SMS adoption GTM-driven Sales pitch, free-trial mechanics, paywall, marketing — editor supports via in-canvas SMS surfacing (P5) n/a
(Excluded) Paid signups Marketing-owned Top-of-funnel marketing, free-tier reopen (P3.1), Klaviyo win-backs n/a
(Excluded) Free→paid 90d Pricing-owned Engagement-based pricing (P3.4.3), trial mechanics, paywall n/a

4.5How to read this

  • Editor-PM target: $20–24M ARR swing — recovers most of the editor-attributable loss ($13–20M) with a modest additional swing ($0–7M). 100% target hit lands at the top of the band ($23.9M).
  • Leading indicators carry ~40% of the commit — L1 (bulk adoption) + L2 (bulk activation) + L3 (SMS activation) + L4 (30-day repeat) = $9.6M (40% of $23.9M). These are the metrics editor PM moves directly and that should show progress first.
  • L8 (CSAT) and L9 (Klaviyo bake-offs) carry ~50% — $5.7M + $6.0M = $11.7M (49% of $23.9M). Both depend on landing the full P1–P5 deliverable stack with quality.
  • L2 (bulk activation) is the bleeding edge — only metric that DEGRADED YoY (−2.4pp). Reversing it requires P1 reliability + P1.5 SLOs + AI Setup Agent — all already in plan, just need execution discipline.
  • Targets are stretch but credible — L8 (Net CSAT +30) is below Klaviyo’s ~+45 net; L9 (35% bake-off win) is well below Klaviyo’s likely ~70% incumbent advantage.
  • Editor causal share is conservative — 30–50% per lever; doubling shares roughly doubles impact (cross-check: matches Loss Attribution L2 high-band $26–28M).
  • Why $20–24M not $32M — we removed levers the editor PM doesn’t directly own (paid signups, free→paid, SMS adoption). The $32M target was achievable only by counting cross-functional contributions; the editor-PM honest commit is the $20–24M shown here.
  • Pacing matters — L1 + L2 + L5 must move by Q3-Q4 FY27 for the loss recovery to land in-year. L3 + L4 + L8 + L9 land in Q5-Q6 FY28 and feed the additional swing.

Methodology: Per-lever calc shown in 4.2. ARPU sources: bi_aggregate.mbr_monthly (at-booking $45.35/mo, steady-state $91.44/mo, SMS add-on est. $20/mo). Volume base: 1,015,648 paid active users / mo from product_journey_monthly (T0 average). Adoption / activation YoY: product_journey_monthly for products in (bulk email, sms, genai content generation bulk, genai smart drafts bulk). Causal shares: editor-attributable % per lever, conservative; doubled in high-band sensitivity. Cross-references: Growth Model, Loss Attribution, Initiative Canvas, Strategy Memo.

Tab 11 · Revised Loss Attribution & Goal Setting

Editor-PM product-adoption goal: ~$21M ARR via paid + free + trial cohorts

Conservative product-adoption goal-setting across all three customer cohorts (Paid, Free, Trial), with realistic per-metric targets, marginal $ via direct ARR (paid) or projected free→paid / trial→paid conversion uplift. Methodology + math in Page 5 Appendix. Built on the Nuni YoY Audit (Tab 10) but extends the analysis to the free + trial pools that the original audit excluded.
v1.2 · 5 pages
Combined editor-PM goal: ~$21M ARR/yr
Paid: $6.7M · Free: $8.7M · Trial: $5.6M
+ Customer Benefit Metrics (5 outcomes, no $)
Conservative targets across all 10 levers

1.1The headline — product adoption opportunity by cohort

Original Nuni Audit goal ($20–24M) covered only paid customers. Extending the same product-adoption framework to free + trial cohorts unlocks an additional ~$14M ARR via projected free→paid + trial→paid conversion uplift — all driven by the same editor improvements (adoption, activation, repeat usage, CSAT). Free has 2x the volume opportunity of paid ($8.7M vs $6.7M) because free signup volume is 6x paid; trial activation is the worst single YoY decline across all three cohorts (−3.0pp). BigQuery YoY analysis on paid + free + signup cohorts, May 2026.

1.2Three cohorts, one goal — combined ~$21M ARR

Free Customers

Indirect via free → paid conversion

$8.7M
~41% of total goal
Cohort: 870K free active users / mo, 2.36M new free signups / yr
Mechanism: editor improvements lift conversion to paid
Levers: F1 adoption, F2 activation, F3 repeat, F4 CSAT
Trial Customers (90-day window)

Indirect via trial → paid conversion

$5.6M
~27% of total goal
Cohort: 2.36M new signups / yr in first 90 days
Mechanism: editor experience drives evaluation outcome
Levers: T1 trial activation (first-send 90d), T2 30d repeat

1.3Combined view — what each cohort contributes

Cohort Volume base Revenue mechanism Levers Marginal $/yr % of total Editor causal share
Paid customers 1.02M users / mo Direct ARR uplift 4 (PA1–PA4) $6.7M 32% 30–50%
Free customers 2.36M signups / yr Free → paid conv uplift 4 (F1–F4) $8.7M 41% 20%
Trial customers (90d) 2.36M signups / yr Trial → paid conv uplift 2 (T1–T2) $5.6M 27% 25%
COMBINED EDITOR-PM PRODUCT ADOPTION GOAL $21.0M 100%

1.4How this relates to Nuni YoY Audit (Tab 10)

Nuni YoY Audit (Tab 10)

$20–24M editor-PM target band

  • Scope: paid customers only
  • 9 levers including CSAT + Klaviyo bake-offs + tier movement
  • $23.9M at 100% target hit
  • Stretch targets (e.g. CSAT to +30) drove much of the $
Revised Goals (Tab 11, this page)

~$21M product-adoption goal across 3 cohorts

  • Scope: paid + free + trial customers
  • 10 levers focused on product adoption (adoption / activation / repeat / CSAT)
  • Conservative targets across all (CSAT to neutral 0, not +30)
  • Includes free+trial conversion uplift; excludes Klaviyo bake-offs / tier movement

1.5Customer Benefit Metrics — what customers get from the platform (no $ projection)

Counterpart to the Product Adoption goals above: these track what value the customer derives from Mailchimp (faster activation, better email engagement, higher attributed revenue, larger share of their email channel). No marginal $ — these are leading indicators of long-term retention + word-of-mouth, not direct ARR.

Metric T-1 baseline T0 current YoY direction FY27 target Target rationale
CB1. Median Time to Activate (signup → first send) 6 days 5 days −1 day ↓ better 2 days Klaviyo cadence ~1–2 days. AI Setup Agent + Brand Kit auto-applied + Universal Content starters compress further.
CB2. Avg Open Rate (bulk email, all paid+free senders) 28.29% 28.27% −0.02pp ~ flat 35% Industry benchmark: ~21–24% for marketing email. MC already above industry; pushing to 35% requires Smart Send Time + AI Performance Watchdog + better segmentation.
CB3. Avg Click Rate (bulk email, all paid+free senders) 1.71% 1.70% −0.01pp ~ flat 3.0% Industry benchmark: ~2.5%. MC bulk lags automation (2.5%); reaching 3.0% closes gap to Klaviyo customer benchmark via personalization + AI content + dynamic blocks.
CB4. Avg Conversion Rate (MC-attributed $/1K emails delivered, ecomm cust.) $1.74 $1.74 flat $2.50 (+44%) Smart Send Time + AI Performance Watchdog + Brand-Kit-aware AI + omnichannel (SMS attach) drive better targeting + content quality → higher revenue per email.
CB5. % MC-Attributed Revenue (of customer’s total email-channel revenue) ~15% (industry estimate — not measurable in MC data) n/a — instrumentation gap 25% Klaviyo claims ~30% share for their customers. Closing gap to 25% via omnichannel (SMS), Smart Send Time, in-canvas revenue surfacing. Requires customer survey or 3rd-party benchmarking to measure.
Bonus signal — positive surprise from BQ

MC-attributed revenue per active ecomm user-month: $61.74 → $76.66 (+24% YoY)

Even though total ecomm-customer count is down, each remaining customer generates 24% more MC-attributed revenue per month. The customers who stay are higher-quality / more engaged / sending more campaigns. Retention quality is improving even as volume shrinks.

What this tells us

Customer outcomes are HOLDING; the bleeding is volume, not quality

  • Open / click / conversion all flat YoY — customers who use MC still get consistent engagement.
  • Time-to-Activate improved (−1 day) — fastest in years; AI Setup Agent could compress to 2d (Klaviyo cadence).
  • MC bulk open + click both above industry benchmarks (industry: ~21% open / 2.5% click). Gap-to-Klaviyo is on click + conversion + attribution share, not opens.
  • CB5 is the strategic instrumentation gap — commission a 3rd-party benchmarking study or add to annual NPS survey to measure share-of-email-channel-revenue.

Cohort definitions: Paid = active users with package_id NOT LIKE 'free%' in users_packages. Free = active users on free_monthly_plan_v0 + free_commerce_plan_v1. Trial = new signups in their first 90 days from signup_date (the freemium evaluation window — MC has no distinct paid trial product outside tiny trial_setup_fee_v0 cohort of 67 users). Customer Benefit sources: bi_reporting.daily_email_send_stats (1.5T delivered emails over 24mo, campaign_type='bulk') for opens/clicks; bi_aggregate.mbr_monthly (ecomm_status='ecomm') for attributed revenue. CB5 is industry estimate — cannot be measured directly because MC has no visibility into customer’s revenue from non-MC email channels. Other sources: BigQuery bi_aggregate.product_journey_monthly, mailchimp.users_signup_data, users_first_sends, users_packages + qualtrics.survey_responses (Nuni Feedback Badge, SV_9SwJVJm2BNRqXfo).

Page 2 · Paid Customer Product Adoption

Paid cohort goal: $6.7M ARR via direct retention + activation uplift

Steady-state paid users (~1.02M / mo). Marginal $ comes from direct ARR (preventing churn, increasing habitual use, lifting CSAT-driven retention). Targets are conservative (acknowledges structural ceilings on adoption + multi-year nature of CSAT swing).
4 levers · $6.7M total

2.1Paid scorecard

Metric T-1 baseline T0 current YoY direction FY27 target Mechanism $/yr % of $6.7M
PA1. Bulk builder adoption (% paid users touched) 90.8% 92.7% +1.9pp ↑ better 95% (+2.3pp) Brand-native templates, AI Email Setup Agent, NEB Code Mode, in-app onboarding nudges to convert "Unexplored" 7.3% (some structurally unreachable: API users, multi-seat dormants). $1.9M 28%
PA2. Bulk builder activation (% touched → Established) 63.0% 60.6% −2.4pp ↓ worse 67% (+6.4pp) Recover −2.4pp YoY decline + push beyond T-1 baseline. Mechanisms: P1 reliability + P1.5 SLOs + AI Setup Agent + Brand Kit auto-applied + Universal Content reuse + cross-browser regression suite. $0.8M 12%
PA3. 30-day repeat send rate 83.7% 83.2% −0.5pp ~ flat 87% (+3.8pp) Smart Send Time, AI Performance Watchdog, Universal Content for fast iteration, omnichannel triggers. Already near structural ceiling for SaaS engagement loops (industry 70–85%). $0.9M 13%
PA4. Net CSAT (Nuni Feedback Badge) −44.5 −29.3 +15.2pp ↑ better (still negative) 0 (neutral) (+29.3pp) Builder SLOs (P1.5), parity polish, AI Assistant, Universal Content, Klaviyo gap closures. Conservative target = neutral (not Klaviyo’s ~+45) since 18-month CSAT transformation is realistic to neutral, not industry-best. $3.1M 46%
PAID COHORT SUBTOTAL $6.7M 100%

2.2Paid — per-metric math

PA1 calc

Bulk adoption 92.7% → 95% (+2.3pp)

incremental_adopters = 2.3pp × 1.02M = 23K more / mo touching
conversion_to_active = ~15% become net-new active senders
arpu_steadystate = $91.44/mo × 12 = $1,097/yr
editor_share = 50%
impact = 23K × 15% × $1,097 × 50% = $1.9M/yr
PA2 calc

Bulk activation 60.6% → 67% (+6.4pp)

incremental_established = 6.4pp × 941K touched/mo = 60K
prevented_churn = ~25% would have abandoned in 12mo
arpu = $1,097/yr
editor_share = 50%
impact = 60K × 25% × $1,097 × 50% = $0.8M/yr
PA3 calc

30-day repeat 83.2% → 87% (+3.8pp)

delta_repeaters = 3.8pp × 125K T0 first-senders = 4.8K
retention_uplift = +6mo @ $91.44/mo = $549 LTV
editor_share = 35%
impact = 4.8K × $549 × 35% = $0.9M/yr
PA4 calc

Net CSAT −29 → 0 (29.3pp swing)

churn_reduction = 2.9pp (1pp per 10pp NPS academic benchmark)
active_users = 320K Standard
opportunity = 320K × 2.9% × $1,097 = $10.2M
editor_share = 30%
impact = $3.1M/yr

Volume base: 1,015,648 paid active users / mo (T0 12-month avg from product_journey_monthly); 941K touched bulk builder / mo; 125K paid Nuni cohort first-senders. ARPU: Standard at-booking $45.35/mo, steady-state $91.44/mo (bi_aggregate.mbr_monthly).

Page 3 · Free Customer Product Adoption

Free cohort goal: $8.7M ARR via projected free → paid conversion uplift

Steady-state free users (~870K / mo) + new free signups (~2.36M / yr). Marginal $ comes from indirect uplift in free→paid conversion (currently 12.64% in 90d) driven by editor-experience improvements. Editor causal share lower (20%) because pricing + paywall + marketing dominate the conversion decision.
4 levers · $8.7M total · biggest cohort

3.1Free scorecard

Metric T-1 baseline T0 current YoY direction FY27 target Mechanism $/yr % of $8.7M
F1. Free bulk adoption (% free users touched) 76.3% 75.0% −1.3pp ↓ worse 82% (+7.0pp) Free-tier onboarding flow improvements, AI Email Setup Agent for free signups, brand-native starter templates, in-app nudges to discover builder. $0.9M 10%
F2. Free bulk activation (% touched → Established) 49.4% 48.1% −1.3pp ↓ worse 55% (+6.9pp) Reduce abandonment for free users via P1 reliability, AI Setup Agent, Brand Kit auto-applied, Universal Content starter blocks, smart drafts. $3.6M 41%
F3. Free 30-day repeat send rate (proxy: all-signup cohort) 73.4% 73.4% flat 80% (+6.6pp) Engagement triggers, Smart Send Time, AI Performance Watchdog, omnichannel reminders, in-canvas revenue surfacing. $1.7M 20%
F4. Free Net CSAT (overall Nuni Badge proxy) −44.5 −29.3 +15.2pp ↑ better 0 (neutral) (+29.3pp) Same as PA4 mechanism (SLOs, parity, AI Assistant). Conservative cap at +1pp conversion lift since CSAT→intent correlation is weaker than activation→intent. $2.5M 29%
FREE COHORT SUBTOTAL $8.7M 100%

3.2Free — per-metric math (free → paid conversion translation)

Method: each editor-metric improvement translates to a conversion-rate lift in free→paid 90d (currently 12.64%). Translation factor varies by metric type (adoption is weakly tied to conversion; activation is strongly tied). Then: $ = conv_lift_pp × signups_yr × ARPU × editor_share.

F1 calc

Free adoption 75% → 82% (+7pp)

conv_sensitivity = 0.05 (touching builder ≠ valuing it)
free_to_paid_lift = 7.0pp × 0.05 = +0.35pp absolute conv lift
free_signups_yr = 2.36M / yr
arpu_at_booking = $540/yr (Standard)
editor_share = 20% (pricing + marketing dominate)
impact = 0.35pp × 2.36M × $540 × 20% = $0.9M/yr
F2 calc · biggest free lever

Free activation 48.1% → 55% (+6.9pp)

conv_sensitivity = 0.20 (sending = strong intent signal)
free_to_paid_lift = 6.9pp × 0.20 = +1.4pp absolute conv lift
free_signups_yr = 2.36M / yr
arpu_at_booking = $540/yr
editor_share = 20%
impact = 1.4pp × 2.36M × $540 × 20% = $3.6M/yr
F3 calc

Free 30-day repeat 73.4% → 80% (+6.6pp)

conv_sensitivity = 0.10 (sticky behavior → intent)
free_to_paid_lift = 6.6pp × 0.10 = +0.66pp absolute conv lift
free_signups_yr = 2.36M / yr
arpu_at_booking = $540/yr
editor_share = 20%
impact = 0.66pp × 2.36M × $540 × 20% = $1.7M/yr
F4 calc

Free Net CSAT −29 → 0 (29.3pp swing)

conv_sensitivity = 0.05 (CSAT→intent is weaker)
raw_lift = 29.3pp × 0.05 = +1.5pp
capped_at = +1.0pp (conservative; CSAT effect saturates)
free_signups_yr = 2.36M / yr
arpu_at_booking = $540/yr
editor_share = 20%
impact = 1.0pp × 2.36M × $540 × 20% = $2.5M/yr

Volume base: 870K avg free users / mo (T0 12-month avg from product_journey_monthly filtered package LIKE 'free%'); 1.97M new free signups in T0 over 10 months → ~2.36M annualized. Conversion baseline: 12.64% free → paid 90d (T0). ARPU: $540/yr at booking (Standard).

Page 4 · Trial Customer Product Adoption

Trial cohort goal: $5.6M ARR via projected trial → paid conversion uplift

Trial = new signups in their first 90 days (the freemium evaluation window — MC has no distinct paid trial product outside tiny trial_setup_fee_v0 cohort). 2.36M signups / yr. Marginal $ via indirect uplift in trial→paid conversion. Editor causal share higher (25%) because trial = the editor IS the evaluation.
2 levers + 2 instrumentation gaps · $5.6M total

4.1Trial scorecard

Metric T-1 baseline T0 current YoY direction FY27 target Mechanism $/yr % of $5.6M
T1. Trial activation (% new signups sent first email in 90d) 13.8% 10.8% −3.0pp ↓ worst single decline 16% (+5.2pp) Restore −3.0pp YoY decline + push beyond T-1 baseline. AI Email Setup Agent for first-time users, Brand Kit auto-applied, Universal Content starter blocks, faster onboarding to first send. $5.0M 89%
T2. Trial 30-day repeat (% trial first-senders sent again in 30d) 73.4% 72.8% −0.6pp ~ flat 80% (+7.2pp) Smart Send Time, in-canvas revenue surfacing, AI Performance Watchdog feedback loops, omnichannel triggers (Push, SMS). $0.6M 11%
T3. Trial bulk adoption (% new signups touched builder in 90d) Instrumentation gap — cannot compute from current BQ tables Activation (T1) is downstream; effectively captures most of the value
T4. Trial Net CSAT (trial-segmented Nuni Badge) Survey lacks plan-tier field; cannot segment to trial Overall CSAT (-29 net) used as proxy in PA4 + F4
TRIAL COHORT SUBTOTAL $5.6M 100%

4.2Trial — per-metric math

T1 calc · dominates trial bucket

Trial activation 10.8% → 16% (+5.2pp)

conv_sensitivity = 0.30 (first-send = strongest paid intent signal in trial)
trial_to_paid_lift = 5.2pp × 0.30 = +1.6pp absolute conv lift
signups_yr = 2.36M / yr
arpu_at_booking = $540/yr
editor_share = 25% (editor IS the evaluation)
impact = 1.6pp × 2.36M × $540 × 25% = $5.0M/yr
T2 calc

Trial 30-day repeat 72.8% → 80% (+7.2pp)

first_senders_yr = 254K (10.8% × 2.36M signups/yr)
delta_repeaters = 7.2pp × 254K = 18K incremental
conv_sensitivity = 0.10 (downstream of activation)
trial_to_paid_lift = 18K × 10% conv = 1.8K
arpu_at_booking = $540/yr
editor_share = 25%
impact = 1.8K × $540 × 25% × ~3 (LTV multiplier) = $0.6M/yr

4.3Two instrumentation gaps to close

GAP 1 · Trial bulk adoption tracking

Need: % of new signups who touched the builder within 90 days (vs % who completed first send). Currently only have first-send via users_first_sends. Adoption is upstream of activation; closing this gap would let us see the abandon-before-send segment cleanly. Ask: instrument a "first builder visit" event in product analytics (Mixpanel / Amplitude / similar) joined to users_signup_data.

GAP 2 · CSAT segmentation by plan tier

The Nuni Feedback Badge survey (SV_9SwJVJm2BNRqXfo) does not include a plan_tier embedded field. All responses come back as plan_value = NULL. Cannot distinguish CSAT for free vs paid vs trial users. Ask: Qualtrics survey config to embed user_id and join to users_packages at survey launch, OR add explicit "are you on a free or paid plan?" question.

Trial cohort definition: new signups (mostly free) in their first 90 days from signup_date. Volume base: 1.97M new signups in T0 over 10 months → ~2.36M annualized. Conversion baseline: 12.64% trial → paid 90d (T0).

Page 5 · Appendix — Methodology + Math

How we got the numbers — full transparency

Every assumption that goes into the marginal $ figures, with sources, ranges, and sensitivity ladders. If any of these assumptions move, the whole bucket moves; this page lets a reviewer pressure-test the model.
5 modeling assumptions · full SQL provenance

5.1ARPU sources (revenue per converted user)

ARPU figureValueSource / derivation
Standard at-booking ARPU$45.35/mo → $540/yrSUM(new_bookings_mrr) / SUM(new_bookings) for standard_monthly_plan_v0 from bi_aggregate.mbr_monthly trailing 12 months. Used for free→paid + trial→paid conversion uplift (year-1 booked).
Standard steady-state ARPU$91.44/mo → $1,097/yrSUM(mrr) / SUM(total_paid_users) for Standard from mbr_monthly. Used for paid retention/activation uplift (saved-user value).
SMS add-on ARPU (estimate)$20/mo → $240/yrEstimated from MC SMS pricing (credit packs $10–$30/mo typical for SMB). Used in original Nuni Audit for SMS activation; not used in this scorecard.
Premium at-booking ARPU$741.82/moFrom mbr_monthly for context; not used in current scorecard (no Premium-specific lever).

5.2Editor causal share assumptions (% of metric movement attributable to editor PM)

This is the single biggest modeling lever. Conservative shares applied per cohort and lever type; doubling these would roughly double the impact estimate.

Cohort + lever typeCausal shareRationale
Paid · Adoption / Activation50%Editor is the dominant product surface for paid users; adoption + activation among paying customers are largely product-quality driven (not pricing or marketing).
Paid · 30-day repeat35%Repeat usage also driven by lifecycle marketing + trigger campaigns + onboarding flows. Editor share lower than activation.
Paid · CSAT30%CSAT in survey reflects editor experience but also support, deliverability, billing. Editor dominates but not solely.
Free · All metrics20%Free→paid conversion is dominated by pricing + paywall + marketing. Editor improvements help but are not the deciding factor.
Trial · All metrics25%Higher than steady-state free because in trial, the editor IS what the user is evaluating. But still capped because trial-end pricing + marketing nudges play a role.

5.3Conversion sensitivity (free / trial only)

For free + trial cohorts, marginal $ depends on translating editor-metric improvements into free→paid (or trial→paid) conversion-rate lift. These multipliers represent: "per pp of editor-metric improvement, how many pp does conversion lift?"

Editor metricConv sensitivityRationale
Adoption (touched builder)0.05xTouching is upstream & weak signal — users may explore the builder without intent to use. Small conversion correlation.
Activation (became habitual / sent first)0.20x (free) / 0.30x (trial)Sending first email = strongest single paid intent signal in MC. Trial users who send are 3–5x more likely to convert. Conservative even for trial.
30-day repeat (came back to send again)0.10xSticky engagement pattern = moderate intent signal. Lower than first-send because it’s downstream.
CSAT (survey rating)0.05x (capped at +1pp absolute)NPS→intent correlation is real but weak in academic literature. Capped to avoid overstating the effect of mood-based survey responses on actual conversion.

5.4Cohort definitions + volume bases

CohortSQL definitionVolume base (T0)Source
Paid package_id NOT LIKE 'free%' AND NOT IN ('payg','pre paid','pro/module/other','unknown') 1,015,648 active users / mo
941,039 touched builder / mo
569,995 Established / mo
125K paid Nuni first-senders
bi_aggregate.product_journey_monthly + users_first_sends
Free package LIKE 'free%' (i.e. free_monthly_plan_v0 + free_commerce_plan_v1) 870,303 active users / mo
652,824 touched builder / mo
313,806 Established / mo
~1.97M new signups in 10mo
product_journey_monthly + users_signup_data
Trial New signups in first 90 days (proxy: signup_date within trailing 12mo cohort window). MC has no distinct paid-trial product outside trial_setup_fee_v0 (67 users in T-1). ~2.36M annualized signups
212,269 sent within 90d (10.8%)
154,632 repeated within 30d of first send
users_signup_data + users_first_sends + daily_email_send_stats

5.5Conversion baseline (free / trial)

MetricT-1T0YoYUsed in
Free → paid 90d conv rate14.41%12.64%−1.77pp (−12.3% rel.)F1–F4 + T1–T2 baseline

5.6Sensitivity — what happens if assumptions move

If editor causal share +50%

(Paid 75%, Free 30%, Trial 38%)

Paid: $6.7M → $10.0M
Free: $8.7M → $13.1M
Trial: $5.6M → $8.4M
Combined = ~$31.5M (+50%)
If conversion sensitivity 2x

(Adoption 0.10x, Activation 0.40x/0.60x, Repeat 0.20x, CSAT capped 2pp)

Paid: unchanged $6.7M (direct ARR, no conv translation)
Free: $8.7M → $17.4M
Trial: $5.6M → $11.2M
Combined = ~$35.3M
If targets reach stretch (not conservative)

(PA1 98%, PA2 75%, F1 90%, F2 65%, T1 20%)

Paid: $6.7M → ~$14M (per Nuni Audit stretch)
Free: $8.7M → ~$15M
Trial: $5.6M → ~$10M
Combined = ~$39M (matches original Nuni stretch)

5.7BigQuery provenance — how each metric was computed

MetricSQL patternSource table
Bulk adoption (paid / free) (2_Explore + 3_Try + 4_Establish + 5_Abandon) / (1_Unexplored + ...) WHERE product = 'bulk email' filtered by package bi_aggregate.product_journey_monthly
Bulk activation (paid / free) 4_Establish / (2_Explore + 3_Try + 4_Establish + 5_Abandon) filtered by package bi_aggregate.product_journey_monthly
30-day repeat (paid / trial) For each first-sender, MAX(IF(send_date BETWEEN first_send+1 AND first_send+30, 1, 0)). Aggregated by cohort. users_first_sends + bi_reporting.daily_email_send_stats
Trial activation (first-send 90d) COUNTIF(TIMESTAMP_DIFF(first_send, signup_date, DAY) BETWEEN 0 AND 90) / COUNT(signups) users_signup_data + users_first_sends
CB1. Median Time to Activate APPROX_QUANTILES(TIMESTAMP_DIFF(first_send, signup_date, DAY), 100)[OFFSET(50)] for cohort with sent_within_90d users_signup_data + users_first_sends
CB2. Avg Open Rate (bulk) SUM(actions.unique_opens) / SUM(sends.delivered) WHERE campaign_type = 'bulk' bi_reporting.daily_email_send_stats
CB3. Avg Click Rate (bulk) SUM(actions.unique_clicks) / SUM(sends.delivered) WHERE campaign_type = 'bulk' bi_reporting.daily_email_send_stats
CB4. Avg Conversion Rate (RPME proxy) SUM(aov_revenue) / SUM(delivered) * 1000 joined cohort × cohort bi_aggregate.mbr_monthly (ecomm) + daily_email_send_stats
CB5. % MC-Attributed Revenue NOT computable from MC data; industry estimate ~15% (Klaviyo claims 30% for theirs) Instrumentation gap: needs 3rd-party benchmarking or customer survey
Bonus: Rev per active ecomm user-month SUM(aov_revenue) / SUM(active_users) WHERE ecomm_status = 'ecomm' bi_aggregate.mbr_monthly
Net CSAT (Nuni Badge) %top-2 (Good+Excellent) - %bottom-2 (Terrible+Poor) on QID3 raw 1-5 rating from labels field qualtrics.survey_responses + qualtrics.survey_details (survey_id SV_9SwJVJm2BNRqXfo)
Free → paid 90d conv rate COUNTIF(first_paid_start BETWEEN signup_date AND signup_date + 90d) / COUNT(all_signups) users_signup_data + users_packages (first paid)
ARPU at booking SUM(new_bookings_mrr) / SUM(new_bookings) per package, trailing 12mo bi_aggregate.mbr_monthly

5.8Caveats + open instrumentation gaps

  • CSAT segmentation gap. Nuni Feedback Badge has no plan-tier field; cannot distinguish free / paid / trial CSAT. Used overall CSAT as proxy in PA4 + F4. Closing this gap could either reinforce or weaken the F4 estimate ($2.5M).
  • Trial adoption gap. No clean BQ table for "% new signups who touched builder in 90 days" (only first-send completion). Activation (T1) captures most of the value as a downstream proxy.
  • Cohort proxy: Trial = signup-cohort. Mailchimp’s freemium model means there’s no distinct "trial" SKU. Using new signups in first 90 days as proxy. ~95% of these land on free; ~5% become paid in 90d.
  • Free & trial overlap: deliberately separate populations. Free metrics (F1–F4) measure steady-state free-user behavior; trial metrics (T1–T2) measure new-signup behavior in first 90 days. Different denominators — no double-count.
  • Conversion sensitivity is the biggest unknown. The 0.05–0.30x multipliers are modeling assumptions, not measured. Sensitivity analysis in 5.6 shows the combined number could swing $14M–$35M depending on these.
  • Editor causal share assumes additive contributions. If marketing + pricing + editor all push on free→paid, the 20% share for editor may double-count if other functions also claim 20%+. In practice, this should be socialized as a "shared lift" with Marketing + Pricing.
  • Conservative target rationale. CSAT to neutral (0) chosen over Klaviyo benchmark (~+45) because 18-month cultural transformation is realistic to neutral, not industry-best. Paid bulk adoption ceiling at 95% reflects API-only / dormant / multi-seat structural non-users. Activation lifts are 5–15% relative improvements (industry norm for deliberate programs).

This page should be the “reviewer’s pressure-test surface.” Every $ figure on Pages 1–4 traces to one of the assumptions in 5.1–5.5 and the SQL in 5.7. If a reviewer disagrees with a number, they can tell you exactly which assumption to flex. Methodology consistent with Nuni YoY Audit Page 4 (target-state model) and Loss Attribution Layer 2 modeling.

Tab 12 · NEA → NUNI Migration Briefing

Where we are, what it has cost, and how to finish — without losing $281M HVC ARR

Author: R&A PM team · Last updated May 11, 2026 · Data window: May 2024 – May 2026 (24 months) · Pipeline date 2026-05-11. Original at deepakp1308.github.io/mailchimp-email-editor-analysis. Brings the migration story (NEA legacy → NUNI new editor) into the same brief alongside the Nuni YoY Audit (Tab 10) and Revised Goals (Tab 11).
v1.0 · 5 pages
Paid NEA ARR remaining: $566M
HVC NEA concentration: $281M (38,145 accounts)
Editor-cited churn floor: $1.32M · adj. $3.96M
Reading note: the brief is presented in the Paid-only view (recommended for revenue decisions). Free + Paid lens is included where it tells a different story (e.g. migration trend on Free is +3× while Paid declines).

1.1Headline pull — the migration has stalled exactly where the money is

Among paid customers, NUNI leads at 58.1% adoption, but the migration has stalled exactly where the money is. The remaining paid NEA base is $566M ARR, with $281M ARR concentrated in 38,145 HVC accounts. CSAT did not improve with migration — CES dropped 0.10 points, paid-customer badge sentiment is 94.7% negative (worse than Free), and 225K users have already tried NUNI and reverted to NEA. We need a phased, parity-gated migration — not a forced flip — to land this without losing the HVC top of the funnel. R&A PM team brief, May 2026.

1.2Top metrics — paid customers (917,145 users, $1.16B ARR)

58.1%
Paid NUNI adoption (532,884 of 917,145)
41.9%
Paid users still on NEA (384,261)
$566M
Remaining paid NEA ARR ($47.16M MRR × 12)
$281M
HVC ARR concentration on NEA (38,145 users)
3.90 / 4.00
CES on NUNI vs NEA — migration worsened effort
94.7%
Paid badge feedback negative or very-negative
225,784
Reverters across all users (8–10% of editor-flippers)
$1.32M
ARR already lost to editor-cited churn (24mo, conservative floor)

1.3Five things a senior exec must take away

1

The HVC funnel is closed.

Monthly first-time HVC migrations dropped 91% — from 10,930 in May 2024 to 898 in April 2026. The remaining 38,145 HVC users are self-selecting as NEA-permanent. Free + Paid<$299 absorbs 98% of new migration volume; HVC is essentially flat-lining.

2

CSAT got worse, not better.

Independent CES survey of 8,201 responses shows NUNI is 0.10 points lower on customer effort (3.90 vs 4.00). Bottom-box "hard to use" share inflated 52% relative (6.8% → 10.4%). Paid customers are more negative on NUNI than Free (94.7% vs 89.4% badge sentiment). Sentiment-tagged badge feedback over 24 months is 93% negative, with no QoQ improvement.

3

$281M ARR is concentrated in 38K HVC accounts — 56% on grandfathered Legacy Monthly plan.

These are 7–10-year-tenured power users with 3× more lifetime campaign history and 14× more RSS-driven workflows than NUNI HVCs. A forced migration without parity is a direct churn lever on this revenue. The Legacy Monthly slice alone is $150M ARR.

4

Editor-cited churn already cost us $1.32M ARR — that’s the conservative floor.

Adjusted for hidden signal (churn cited under "Other" / "Performance" / "Difficult to use"), the realistic upper bound is $3.96M ARR lost in 24 months. Velocity doubled after the late-2024 default-flip (48 → 94 editor-cited churners / month).

5

The fix is sequencing, not speed.

A 3-phase, parity-gated playbook can mitigate $60M ARR (Phase 1) + $122M ARR (Phase 2) = $182M ARR (32% of paid NEA base) in 9 months at low risk, then preserve the remaining $281M HVC ARR via hybrid co-availability for 18 months. Forcing without sequencing risks $23–28M ARR in HVC churn.

1.4Decision asks (one-slide)

Ask 1

Approve the 3-phase plan

Phase 1 default-flip on Free + low-paid by month 3. Phase 2 nudge on paid power-users + non-Legacy HVC by month 9 (parity-gated). Phase 3 hybrid + concierge for Legacy/HVC through month 18.

Ask 2

Fund Q1 the top-5 parity gaps

Save/version reliability, image controls, brand kit/font palette restoration, preview-test reliability, AI Creative Assistant restoration. Without these, Phase 2 cannot start without bleeding HVC MRR.

Ask 3

Accept hybrid carry cost for HVC

Maintain NEA codebase availability for 38K HVC + 92K Legacy plan customers for 18 more months. Carry cost is bounded; protected ARR is $281M. Forcing instead loses up to $28M ARR.

Free + Paid lens: NUNI leads at 62.5% adoption (1.97M of 3.16M editor users); 1.19M still on NEA. Same $566M paid NEA ARR + $281M HVC concentration applies (HVC are paid by definition). The Free + Paid view inflates NUNI adoption because the late-2024 default-flip delivered a 3× spike on Free (85K migrators/mo vs 27K baseline) while paid migration kept declining. Source: bi_marketing.lcm_marketing_account_base (pipeline 2026-05-11) + bi_activities.users_activities (24-mo preference events) + bi_aggregate.mbr_monthly + qualtrics.survey_responses (Exit Survey 308,704; CES 8,201; Nuni Badge 4,557 categorized) + Slack #hvc_feedback, #mc-hvc-escalations, #mc-reporting-analytics-feedback (1,551 editor-related VOCs).

Page 2 · Situation + 4 Complications

Where the migration is today — and four things that change the calculus

Editor share by tier, 24-month migration trend, and the four complications: HVC inversion, CSAT got worse, 225K reverters, editor-cited churn accelerating.
4 complications + tier + trend tables

2.1Editor share by paid tier — adoption inverts at HVC

Tier NEA users NUNI users NEA share NEA ARR
Paid <$299346,116497,92041.0%$285M
HVC ($299+ MRR)38,14534,96452.2%$281M
Total paid384,261532,88441.9%$566M

NEA leads in every paid bucket above $299/mo. NEA share rises monotonically: 36.6% at <$50 → 58.0% at $5K+. The HVC inversion is structural, not a temporary lag.

2.224-month migration trend — HVC funnel collapsed 91%

Period Paid <$299 / mo HVC / mo Paid total / mo Read-out
2024 Q3 avg23,6493,05326,702Steady-state baseline
2025 Q1 avg18,6471,76520,412HVC drops 42% YoY
2025 Q2 avg17,4881,49918,987Free default-flip rolled out — paid migration kept declining
2025 Q4 avg22,5651,35223,917Paid rebounded slightly; HVC kept declining
2026 Q1 avg19,1061,03120,137HVC at 91% decline vs 2024 baseline
April 202616,95989817,857HVC paid funnel essentially closed

What progress we have on the paid base is heavily weighted to lower-tier (Standard Monthly, Essentials Monthly). The mature paid base — especially HVC + Legacy plan in mature markets (US, UK, Australia, Netherlands, Switzerland) — has not moved.

2.3Four complications that change the calculus

C1 · Structural inversion

The HVC inversion is structural — NEA stickiness rises with MRR

NEA share by paid MRR bucket: 36.6% at <$50 → 48% at $50–100 → 53% at $299–500 → 54% at $1K–2.5K → 58% at $5K+. Clean monotonic rise.

Why this matters: HVC NEA stayers are a fundamentally different cohort. Median tenure 10 years (vs 7 for NUNI HVC). Median list size 37,273. They send 698K emails per quarter on average — 27% more than NUNI HVC. They use RSS-driven campaigns at 14× the rate of NUNI HVC, plaintext at 4×, classic Automations at 2.4×. Publishers, agencies, code-savvy power users with entrenched workflows. They will not move on a default flip.

C2 · CSAT regression

Customer satisfaction got worse, not better — two independent sources confirm

CES — Edit an Email survey (8,201 responses)Mean CESTop-2-boxBottom-2-box
NEA (Old)4.0078.3%6.8%
NUNI (New)3.9073.9%10.4%

NUNI is 0.10 pts worse on CES, top-box drops 4.4pp, bottom-box "hard to use" inflates 52% relative.

Nuni Feedback Badge sentiment — paid (2,810 categorized): 35.7% Very Negative + 59.0% Negative = 94.7% negative. Free + Paid combined: 93.3% negative for 8 consecutive quarters, no improvement trend. Paid sentiment is 5.3pp worse than Free — the migration hurt the highest-value users most.

C3 · Reverters

225,784 customers tried NUNI and went back to NEA

Migration outcomeUsersRead-out
Net new (NUNI only)2,868,026Mostly default-flipped new signups
NEA only (true stayer)833,981Hold-outs who never even sampled NUNI
Sampled both same day572,446Confused / exploring
Reverter (tried NUNI → back to NEA)225,784More reverters than completed migrators
Migrator (NEA → settled on NUNI)218,723Successful migrations from existing users

The reverter rate is 8–10% across the 24-month window. Applied to the $281M HVC ARR base, that implies $23M–$28M ARR at risk if forced migration is imposed without parity.

C4 · Editor-cited churn (accelerating)

Editor-cited churn is already real and the velocity doubled post default-flip

2,021
Editor-cited churners (structured signal, 24mo)
~6,000
Adjusted estimate w/ 3× hidden multiplier
$110K/mo
Total monthly MRR-at-churn for cohort
$1.32M
ARR loss floor (adj. $3.96M)

Pre-default-flip avg: 48 editor-cited churners/mo (May–Oct 2024). Post-flip avg: ~94/mo (Nov 2024 onwards). 2.0× velocity increase — early-warning signal that further forced migration without parity will accelerate the bleed.

How the $1.32M floor was computed: 2,021 churners cited "Design tools" in Exit Survey QID3 follow-up (May 2024 – May 2026). 1,629 had a paid order in 60d before churn → total MRR-at-churn $110,408 (avg $67.78, median $20). Annualized: $110,408 × 12 = $1.32M ARR loss. 0.13% of the $85.0M total churned MRR over the same window — conservative explicit floor.

The key question this brief answers: How do we close the remaining $566M ARR of paid NEA base — with $281M ARR concentrated in 38K HVC accounts — without losing customers we cannot afford to lose, and without sustaining a 90%+ negative satisfaction profile that signals "this product is getting worse, not better"? Sub-questions: (1) which cohorts can move safely right now, and which need product investment first? (2) what feature gaps are non-negotiable to close before HVC moves? (3) bounded carry cost of NEA codebase vs ARR lost if we force? (4) early-warning metric to know if Phase 2 should pause or proceed?

Page 3 · Recommendation

A 3-phase, parity-gated migration playbook — sequenced by risk × revenue

The remaining 1.19M NEA users do not all carry the same risk. Sequenced by behavioral risk × revenue exposure × technical complexity, three phases minimize churn while making forward progress. Each phase has a parity prerequisite — moving the next cohort before the prior phase’s gaps are closed bleeds money.
P1: $60M ARR mitigated (months 0–3, low risk)
P2: $182M cumulative (months 3–9)
P3: $281M protected via hybrid (months 9–18)

3.1Cumulative ARR mitigation by phase

$60M / $566M
After Phase 1 (11%)
$182M / $566M
After Phase 2 (32%)
$566M / $566M
After Phase 3 hybrid (100%)

3.2Phase 1 — Default-flip the low-risk cohort

Months 0–3 · Low risk

~250K paid users + 800K Free → ~1.16M users total · $60M ARR mitigated

Cohort: Free Plan NEA (800,756) + Paid <$299 NEA not on Legacy Monthly (~254K of 346K) + non-Legacy Essentials Monthly NEA without code/RSS power-user signal. Excludes anyone whose 90d send history shows plaintext, RSS, parent automations, custom-HTML, or A/B variate parents.
Prerequisites (defect-tier — fixable in weeks)

(1) Text editing reliability — cursor, paste behavior, line spacing. (2) Preview-test reliability — preview must equal sent rendering. (3) Mobile preview accuracy. None require structural NUNI changes; defect-fix tier.

Mechanism

Default-flip on next campaign create, with one-click "stay on classic" escape hatch for 30 days. After 30 days, NEA still available via deep link, not in main flow. 60-day full rollback option.

Why it’s safe

Median tenure on the cohort that already migrated to NUNI Free is 12 months — short workflows, small content libraries, lowest concentration of power-user features. CES delta in this segment is the smallest. They already auto-default to NUNI on new signups.

3.3Phase 2 — Concierge nudge for medium-risk paid

Months 3–9 · Medium risk

~150K paid users · $122M ARR mitigated (cumulative $182M)

Cohort: Paid <$299 NEA users with power-user signal (RSS, plaintext, automations, code-edit) + non-Legacy HVC NEA on Standard Monthly (9,615 users / $54M ARR) and Premium Monthly (5,385 users / $68M ARR). ~150K users / ~$122M ARR exposure.
Prerequisites (structural parity — must ship before Phase 2 begins)
  1. Drag/drop precision parity (image side-by-side sizing, pixel positioning).
  2. Save / version-history reliability — no more "my work has been deleted" reports.
  3. Brand kit, font palette, color palette restored to NEA-equivalent breadth.
  4. Mobile editor parity.
  5. A/B variate workflow that supports HVC NEA’s 28-children-per-parent pattern.
  6. Preview-test reliability hardening.
Mechanism

Account-by-account nudge in-product + email; CSM-led for HVC. 60-day fully-rollback-able trial. Auto-port templates and brand assets. For paid HVC, attach a named CSM contact for the first migrated campaign. Maintain dual-availability for at least 90 days post-flip.

Cumulative coverage

Phases 1+2 close ~98% of remaining NEA users and ~32% of paid NEA ARR ($182M of $566M). Critically, this leaves the highest-ARPU, highest-tenure cohort intact for Phase 3 — the right order, not the wrong order.

3.4Phase 3 — Hybrid + concierge for HVC and Legacy plan

Months 9–18 · High risk

~38K HVC + 92K Legacy · $281M ARR addressed via hybrid co-availability

Cohort (3 sub-tracks): 3a HVC NEA stayers on Standard / Premium plans (already nudged in P2 but did not convert). 3b Legacy Monthly NEA users (91,746 users / $20.16M MRR = $242M ARR total, with 21,376 of them HVC at $150M ARR). 3c Code/HTML-heavy HVC accounts and agencies regardless of plan.
Prerequisites (platform-tier investment)
  1. Native HTML / code-edit mode in NUNI.
  2. RSS-driven campaign full feature parity (top NEA HVC behavioral signature — 14× usage).
  3. Native countdown / GIF / animation content blocks.
  4. Native arbitrary sections (un-blocks the $9,700-MRR P2 escalation pattern).
  5. AI Creative Assistant restored at parity or better.
  6. Migration tooling for journeys / automations created in NEA → NUNI with content preservation.
Mechanism (3 tracks)

Track A (3a HVC Standard/Premium): Engineer-paired migration sprint per account. Replicate top 10 templates 1:1 and have customer review before flip. CSM acceptance gate. ~12-week per-account engagement.
Track B (3b Legacy plan): Hybrid offer — keep NEA available indefinitely or until customer affirmatively migrates. Pair with Legacy plan modernization conversation. Do not force.
Track C (3c code-heavy): NUNI HTML mode launch + agency-specific onboarding. Offer template-conversion service.

Risk acceptance

Even with the hybrid track, plan for $23–28M ARR at risk in this cohort if forcing is required (8–10% historical revert rate × $281M ARR base). Hybrid mitigates almost all of this — at the cost of carrying NEA codebase 18+ more months. For 2.6% of users covering ~50% of paid MRR, that carry cost is bounded; the protected ARR is not.

3.5Top 5 features to ship in Q1 to unlock Phase 1+2 cleanly

  1. Save / version-history reliability fix — eliminates "my work has been deleted" defect class (357 negative responses on Defects topic).
  2. Image side-by-side sizing, pixel positioning, resize-too-large warning — highest-volume Qualtrics topic (770 negative on Images). Tied to a $9,376 MRR Slack P0 escalation.
  3. Brand kit and font/color palette restoration to NEA breadth — closes "saved templates lost" / "fonts gone" stayer theme.
  4. Test-send and preview-rendering reliability — 370 negatives on Preview & Test.
  5. AI Creative Assistant feature restoration — highest very-negative ratio (1.45×) of any topic.

3.6Early-warning metric — the gate to Phase 2

Phase-1 reverter rate > 12% = pause Phase 2

Track the percentage of Phase 1 cohort that flips back to NEA after the default-flip. Above ~12% is a signal that the Phase 1 prerequisites haven’t actually shipped. Use this as the gate to start Phase 2 — not calendar time alone. The 24-month historical revert rate is 8–10%; sustained above 12% means we’re losing the cohort and Phase 2 should pause.

3.7Decision asks — full table

AskOwnerWhy now
Approve the 3-phase migration playbookVP EmailWithout explicit phasing, default is "keep nudging" — which produced 91% YoY decline in HVC migration and a 2× rise in editor-cited churn velocity
Fund the Q1 Top-5 parity gapsEng leadershipPhase 2 cannot start without these shipped. Each delay quarter compounds the $281M HVC ARR exposure
Accept hybrid carry cost for 18 more months on NEA codebaseCTO + CFOCarry cost is bounded; protects $281M ARR from reverter-rate churn. The alternative loses up to $28M ARR
Ratify the Phase-1 reverter-rate gate (12% threshold)VP Email + CSM leadershipPrevents Phase 2 from starting on top of unfixed defects. Avoids repeating the late-2024 default-flip outcome
Sponsor Legacy Monthly plan modernization conversation in parallel with Phase 3bPricing + CSM21,376 HVC accounts on Legacy plan = $150M ARR. Migrating off NEA is also the moment to migrate onto modern pricing

Answer-by date proposed: end of FY27 Q1, so Phase 1 prerequisites can ship in Q2 and the playbook can begin executing in early Q3. Cross-references: the migration phases inform initiative sequencing in Initiative Canvas P1 (reliability + SLOs) + P2 (Universal Content + brand kit) + P3 (activation + free-tier reopen). The Phase-3 hybrid carry decision pairs with Strategy Memo R1 risk (Classic Established cohort).

Page 4 · Issues & Solutions Detail

16 issues organized by migration phase — severity = cost of not shipping it

Every parity gap and defect named in the recommendation, with: customer JTBD, how it blocks them, the solution, and verbatim VOC where strongest. Ship-blockers for Phase 1 are Q1 commitments; Phase 2 are Q2; Phase 3 are H2 platform investments.
16 issues · 4 Phase 1 + 6 Phase 2 + 4 Phase 3 + 2 cross-cutting

4.1Phase 1 prerequisites — defect tier (ship Q1, ship-blockers for default-flip)

01

Save / version-history reliability

CRITICAL · PHASE 1 · 357 negative VOCs

Issue: Customers report email work has been deleted, reverted to old versions, template columns and sections missing after save. No way to access previous saved versions. Multi-user edits silently overwrite. Largest single defect class.

"I want to draft an email campaign over multiple sessions, with my team, and trust that my work is saved and recoverable if anything goes wrong."
"My work has been deleted, it's gone back to an old version of this email, my template columns and sections are missing, I can't edit it properly. This is really poor."Qualtrics badge

Fix: True version history with auto-save (every 30s) + restore points. Persistent auto-save indicator. "Restore previous version" UI. Conflict resolution / queue when multiple users edit. Success state: Browser crash = no lost work. Team collaboration works without overwrites.

02

Preview-test reliability

CRITICAL · PHASE 1 · 370 negative VOCs

Issue: Test sends fail to arrive. In-editor preview doesn’t match rendered email when sent. Mobile preview doesn’t match Gmail mobile rendering. Confidence-killer for pre-send QA.

"Before I send to my list, I want to confidently verify the email looks correct on desktop, mobile, and across major email clients."
"The 'Send test' email function in the email campaign builder is NOT functioning for me. I have attempted to send test emails to multiple emails and none have come through. Previously this function was working fine."Qualtrics badge

Fix: Fix test-send delivery reliability. Render in-editor preview using same engine that renders sent email. Mobile preview powered by actual Gmail/iOS/Outlook signals. Inbox preview parity. Success: Test sends arrive in <30s. Pre-send QA in 2 min, not 20.

03

Text editing reliability — cursor, paste, line spacing

CRITICAL · PHASE 1 · 1,010 negative VOCs

Issue: Highest-volume complaint topic. Cursor jumps mid-typing, pasted text loses formatting or pastes with wrong formatting, line spacing inconsistent, fonts revert silently. Long-form newsletter writers find it unusable.

"I want to write or paste my email copy and have it stay exactly how I formatted it — typing should feel like a normal text editor."
"I have used the legacy builder for years. The new builder doesn't match the formatting when I paste my very simple Arial 12 plain text. Even if I clear formatting, it pastes wrong."Qualtrics badge

Fix: Fix cursor positioning bugs. "Paste as plain text" default + smart-paste options. Preserve line spacing across paste / save / reload. Stable font inheritance from brand kit. Success: Pastes from Google Docs render identically. Cursor stable. Customer thinks about message, not the editor.

04

Mobile preview accuracy

CRITICAL · PHASE 1 · 354 negative VOCs

Issue: NUNI mobile preview doesn’t match Gmail mobile, iOS Mail, or Outlook mobile. Customers without dev support can’t optimize for mobile. Images appear too large in mobile view.

"Would be really useful to have more mobile optimisation options for emails without the need for coding. Images appear too large in mobile view of our campaigns and we don't have a developer."Qualtrics badge

Fix: Mobile preview powered by actual Gmail/iOS/Outlook rendering signals. Mobile-specific CSS controls (image % sizing, column stacking). "Preview as Gmail mobile" button. Auto-fit images for mobile.

4.2Phase 2 prerequisites — structural parity (ship months 3–9, unlock $122M ARR cohort)

05

Image controls & side-by-side sizing

HIGH · PHASE 2 · 770 VOCs · $9,376 P0

Issue: Lost the "image too large" warning NEA had. Cannot make side-by-side images same size without manual pixel math. Image rotation produces unexpected crops. Replicating NEA → NUNI adds white gaps not visible in preview but appearing in sent email — $9,376 MRR P0 escalation.

"How can I make side-by-side images be the same size? That was easy in the legacy builder, but I can't find that in the new editor."Qualtrics badge

Fix: Side-by-side equal-size auto-fit (default ON). Restore "image too large" warning at upload. Pixel-level positioning controls. Fix NEA→NUNI replication white-gap defect.

06

Brand kit / font palette / color palette restoration

HIGH · PHASE 2 · 131 v.neg Templates + 91 v.neg Fonts

Issue: NUNI restricts to smaller font palette than NEA. Brand fonts (Poppins, Merriweather Sans, DIN 2014) not recognized. Colors limited to whatever was used in template. NEA saved templates not available in NUNI — years of saved work stranded.

"The font we've been using (Merriweather Sans) for YEARS is no longer available on the Classic Builder. But switching to the New Builder, NONE of our saved templates are available anymore. We have SOOOOO many templates we've worked so hard on perfecting."Qualtrics badge

Fix: Restore full color palette persistence. Brand-kit font upload that loads in editor. NEA → NUNI template auto-port tool. Full font picker (web-safe + Google fonts + custom uploads). Brand-kit-as-source-of-truth.

07

Drag/drop precision & layout positioning

HIGH · PHASE 2 · 224 neg Layouts + 314 neg Sections

Issue: Pixel-level positioning is "wonky." Dragging a text box requires "NASA-level precision." Templates jump around during drag. Buttons that were centered suddenly align left without permission.

"Regarding the new drag/drop template — very wonky. Dragging a text box to another column requires NASA-level precision as the template and other text fields jump around. Not nearly as simple as the legacy template."Qualtrics badge

Fix: Snap-to-grid + alignment guides. Pixel-precise drag with clear drop targets. Lock element position once placed. Undo for accidental moves.

08

A/B variate workflow for power users

HIGH · PHASE 2 · HVC NEA pattern: 28 children/parent

Issue: HVC NEA users create 28 children per parent variate campaign on average. NUNI’s A/B workflow doesn’t support this volume cleanly. Reaching content of a sent multivariate-test campaign takes 5–6 clicks vs 1 for a simple campaign.

"Make it as easy to get to the content of previously-sent multivariate-test campaigns as it is to get to the content of previously sent straightforward campaigns. It is a one-click to access content of a [Sent] simple campaign, while for multivariate-test campaigns it is a 5 to 6 click process."Qualtrics badge

Fix: Native multivariate UI supporting 30+ children. One-click access to variate content (parity with simple). Variate results dashboard with winner + lift across all dimensions. Bulk paste for subject/preview variants.

09

AI Creative Assistant restoration

HIGH · PHASE 2 · Highest very-neg ratio (1.45×)

Issue: Premium AI Creative Assistant feature (banner generator, photo creative AI) was visibly removed/degraded in NUNI transition. Highest very-negative ratio (1.45×) of any topic. Direct churn-threat language tied to this loss.

"Please bring back the AI creative photo feature? It was SO good and really set you apart from other email providers. And now it's gone. So sad about this and am thinking about moving providers."Qualtrics badge · churn risk

Fix: Restore Creative Assistant banner generator at parity. Add modern AI: text-to-image, brand-kit-aware generation, on-brand photo augmentation. Surface in NUNI editor as primary content-block type. Tier-gated: free for HVC, included in Standard+ plans.

10

Mobile editor parity (edit on the go)

HIGH · PHASE 2

Issue: NUNI editor unusable on mobile. Switch desktop-mobile popup can’t be closed on Safari Desktop. Solo founders + SMB owners who work from mobile can’t do quick edits.

Fix: Mobile-responsive editor (iPad + phone). Fix Safari popup-blocker bug. Mobile-specific edit UI for quick actions. Native iOS/Android approval flow for review-only roles.

4.3Phase 3 prerequisites — platform-tier investment (ship months 9–18, unlock $281M HVC ARR cohort)

11

Native HTML / code-edit mode in NUNI

PLATFORM · PHASE 3 · 75 neg + 65 v.neg HTML

Issue: NUNI has no proper HTML / code-edit mode. Ctrl+K to insert links doesn’t work in Firefox or Chrome. Users who need to paste HTML or edit code have to use Classic. #1 blocker for the agency segment.

"I absolutely HATE that in the new builder Ctrl+K to insert links doesn't work on Firefox or Chrome. It's maddening! And I hate how the styling rules are so rigid now."Qualtrics badge

Fix: Native HTML view (toggle WYSIWYG ↔ code). CSS injection support. Ctrl+K + keyboard shortcuts working in Firefox/Chrome. "Less restrictive styling" mode with override. Custom merge tag support beyond standard.

12

RSS-driven campaign full feature parity

PLATFORM · PHASE 3 · 14× HVC NEA usage vs NUNI

Issue: NEA HVC users use RSS-driven campaigns at 14× the rate of NUNI HVC (130K events vs 9.2K in 90 days). RSS workflow in NUNI incomplete or buggy for advanced cases. Publishers, podcasters, content sites have no migration path.

Fix: Native RSS-driven campaign in NUNI with full parity. RSS preview — see what next campaign will contain. Multi-feed merge support. Custom RSS-to-content-block mapping. Auto-thumbnail extraction.

13

Native countdown / GIF / animation content blocks

PLATFORM · PHASE 3 · $7,150 P0 + 600K-recipient threat

Issue: GIFs don’t fill space, render inconsistently. No native countdown clock ($7,150 MRR P0 escalation). Customers threatening to move 600K recipients elsewhere over GIF support.

"FIX HOW GIFS WORK IN THE NEW BUILDER!!! I despise that we have to use the Classic builder to get GIFs to work, fill the whole space. I'm about ready to take our 600k recipients elsewhere if you guys don't improve this."Slack #hvc_feedback · GIF/600k threat

Fix: Native countdown clock content block (timezone-aware). GIF block that handles fill, sizing, fallback for Outlook. Lottie / animated SVG support. Animation library with on-brand templates.

14

Arbitrary sections (beyond Header / Body / Footer)

PLATFORM · PHASE 3 · $9,700 P2 escalation

Issue: NUNI restricts emails to three section types. Customers want arbitrary sections with their own backgrounds, padding, content. $9,700 MRR P2 escalation pattern — most-named layout restriction.

"Customer would like the ability in NUNI to add new sections. Right now they are limited to Header, Body, Footer. They want to add a background image to a particular section and have text overlayed on top (as well as a CTA)."Slack #mc-hvc-escalations · P2 · $9,700 MRR

Fix: Allow arbitrary section creation. Per-section background image, padding, alignment. Section templates (hero, promo, testimonial, divider). Section-level styling that doesn’t bleed into siblings.

4.4Cross-cutting (applies across all phases)

15

NEA → NUNI template / journey migration tooling

CROSS-CUTTING · ALL PHASES

Issue: Content created in NEA (campaigns, journeys, automations) cannot be auto-migrated to NUNI. Customers manually rebuild every campaign, journey email, saved template. The single biggest practical reason long-tenured customers won’t move.

"I wish there was an option to switch between builders in already existing content. We have a lot of content, such as journeys, that are made with the old/classic builder, and we would like to update it to a new design that has been made with the new builder. Right now that's not possible."Qualtrics badge

Fix: Bulk template migration tool (preserve fidelity). Journey/automation content migration that preserves email content per step. Side-by-side compare. Rollback if migration loses fidelity. Run-by-account pre-migration audit report.

16

Forced-migration / "no way back" UX

CRITICAL · ALL PHASES · 369 New-vs-Legacy VOCs

Issue: When customers were default-flipped to NUNI, the option to go back was hidden or removed. Customers feel trapped. 369 explicit New-vs-Legacy complaints with the highest concentration of "I’m shopping providers" mentions.

"I want the older version of Mailchimp, legacy builder, back! I went on Google to get directions on how to change the default settings and it is not an option to change it anymore."Qualtrics badge

Fix: Always-available "switch back to classic" option for 60 days post-flip. Per-campaign editor choice (don’t force a global flip). Clear in-product communication about default changes (not silent). Hybrid mode for accounts that have explicitly opted to stay on NEA. Reverter dashboard for support team.

Reading this section as a roadmap input: The 16 issues are organized by the migration phase that depends on them. Each Phase 1 issue is a Q1 ship-blocker; Phase 2 issues are Q2 commitments; Phase 3 issues are H2 platform investments. Cross-cutting items (15 + 16) should be in flight from day one because they affect every customer touched by any phase. Total estimated eng investment: a focused 3-quarter program for ~6–8 engineers across editor + brand kit + migration tooling teams. Cross-references: these issues seed initiatives in Initiative Canvas P1.5 (Builder SLOs), P1 (cited HVC bug-fix), P2 (Universal Content + brand kit), P4 (AI Assistant), P5 (omnichannel + collaboration).

Page 5 · Appendix

Methodology, data quality, geo / plan / ICP, churn deep-dive, HVC profile

Detailed breakdowns supporting the narrative. Tables show Paid-only first; Free + Paid added where it tells a different story.
12 sub-sections · SQL provenance + caveats

A.1Methodology & data sources

  • bi_marketing.lcm_marketing_account_base (pipeline 2026-05-11) — last_email_editor_used, plan, MRR, country, ecomm level, partner flag, tenure
  • bi_activities.users_activities — NEA + NUNI campaign_editor_preference update events (24mo)
  • bi_activities.email_campaign_send_activities + bi_product.sent_email_activities — campaign feature adoption, send volume
  • bi_aggregate.mbr_monthly — gross churn users + amount by package, 24mo
  • mailchimp.users_packages — historical plan / package at time of churn
  • mailchimp.orders — last paid amount in 60-day window pre-churn
  • qualtrics.survey_responses — Exit Survey (308,704 responses), CES Edit-an-Email (8,201), Nuni Feedback Badge (4,557 categorized)
  • Slack: #hvc_feedback (1,381 editor VOCs), #mc-hvc-escalations (8), #mc-reporting-analytics-feedback (162). Total 1,551 editor-related VOCs after dedup.

A.2Key definitions

TermDefinition
NEALegacy / classic email editor
NUNINew email editor
HVCHigh-value customer ($299+ MRR)
ARRMonthly MRR × 12
Paid customerMRR > 0 in current snapshot (936,992 paid users; 917,145 with editor signal)
Free customerMRR is null or 0 in current snapshot
Editor-cited churnCustomers who completed Exit Survey within 24mo and selected "Design tools" in QID3 under primary reason "Features not advanced enough or missing features"

A.3Data quality cross-checks

CheckValueResult
Total external accounts (most recent pipeline)4,431,032Matches table row count
External accounts with editor signal3,158,30571.3% — matches share calc denominator
External accounts without editor signal1,272,727Excluded from share (never created an email)
Total paid (MRR > 0) external936,992OK
Paid with editor signal (primary denominator)917,14597.9% of paid base
Total paid MRR (all paid)$97,350,939Reconciles to $1.17B ARR
Paid MRR with editor signal (headline)$96,693,562$1.16B ARR
Paid NEA MRR sum$47,162,000$566M ARR ✓
Paid NUNI MRR sum$49,532,000$595M ARR ✓
HVC NEA MRR (sum across $299+ buckets)$23,386,790$281M ARR ✓
HVC NUNI MRR (sum across $299+ buckets)$20,947,702$251M ARR ✓
Editor-cited churners (distinct user_ids)2,009 of 2,021 responses12 users responded twice; deduped on user_id
Editor-cited cohort with billing record (60d pre-churn)1,629 (81%)Used for $110K MRR-at-churn calculation

Known caveats: Editor-cited churn is the conservative explicit floor from QID3 = "Design tools." Actual editor-attributable churn likely 2–5× higher (signal hidden in "Other"/"Difficult to use"/"Performance" primary-reason paths). CES survey doesn’t tag responses with plan tier. ~1.27M accounts have no editor signal. ARR estimates assume no winback / future expansion. May 2026 partial month (11 days) shown for completeness; not used in trend averages.

A.4Top countries — paid customers with editor signal

CountryNEA usersNUNI usersNEA shareNEA MRRNUNI MRR
USA178,718261,42540.6%$22.27M$25.12M
United Kingdom38,28256,64040.3%$4.75M$5.47M
Canada23,36231,21142.8%$2.45M$2.51M
Australia20,66429,06241.6%$2.40M$2.58M
Netherlands13,65214,12449.2%$1.48M$1.19M
Spain10,07110,62848.7%$1.27M$0.97M
Italy9,79210,45748.4%$1.15M$0.92M
Germany7,4958,21647.7%$0.84M$0.75M
France7,3657,32250.1%$0.98M$0.73M
Switzerland6,7776,50951.0%$0.75M$0.53M
Austria2,4762,24052.5%$0.26M$0.17M
India (emerging)1,5824,21627.3%$0.19M$0.27M
Brazil (emerging)2,4045,24331.4%$0.26M$0.40M

France, Switzerland, Austria are NEA-majority by users. Netherlands, Spain, France, Switzerland have NEA leading on MRR even when NUNI leads on user count — their NEA accounts are higher-MRR. Emerging markets (India, Saudi Arabia, Nigeria) are 90%+ NUNI by adoption.

A.5By marketing plan — paid only

PlanNEA usersNUNI usersNEA shareNEA MRRNEA ARR
Essentials Monthly183,149207,63346.9%$9.13M$110M
Standard Monthly103,450275,22627.3%$12.08M$145M
Legacy Monthly91,74640,94369.1%$20.16M$242M
Premium Monthly5,5528,10140.7%$5.73M$69M

Legacy Monthly is the single biggest NEA pocket — 69.1% NEA share and $242M ARR all on the legacy editor. 21,376 of these are HVC ($150M ARR slice).

A.6Migrator vs stayer profile (paid, by MRR bucket)

BucketEditorUsersMRRARRMedian tenureMedian list size
<$50NEA182,247$4.85M$58M75 mo692
<$50NUNI315,323$7.83M$94M26 mo457
$50–100NEA72,336$5.05M$61M101 mo2,896
$50–100NUNI79,668$5.41M$65M43 mo2,509
$100–299NEA91,533$13.86M$166M108 mo8,062
$100–299NUNI102,929$15.36M$184M51 mo7,021
HVC $299–1kNEA33,475$15.06M$181M118 mo33,343
HVC $299–1kNUNI31,075$14.23M$171M83 mo31,152
HVC $1k+NEA4,670$8.32M$100M119 mo177,059
HVC $1k+NUNI3,889$6.72M$81M92 mo162,372

Across every paid bucket, NEA stayers are 2–3× longer-tenured with similar or larger lists. The HVC $1k+ NEA cohort (4,670 users, $100M ARR) is the most concentrated risk in the entire base.

A.7Editor-cited churn deep dive

LensEditor-citedDenominatorShare
% of all Exit Survey respondents2,021308,7040.65%
% of all gross churners (paid → non-paid, 24mo)2,021980,6980.21%
% of total churned MRR$110,408$84.96M0.13%
MetricConservative floorAdj. upper bound (3× multiplier)
Editor-cited churners (24mo)2,021~6,000
Total MRR-at-churn captured$110,408~$330,000
ARR loss$1.32M~$3.96M
Average MRR per churner$67.78~$55
Median MRR$20~$20
Velocity periodEditor-cited churners / monthRead-out
Pre-default-flip (May–Oct 2024)48 / moBaseline rate
Post-default-flip (Nov 2024 onward)94 / mo2.0× velocity increase

A.8HVC NEA stayer characteristics — the $281M ARR cohort

38,145
HVC users on NEA
$281M
Annualized ARR ($23.4M MRR × 12)
56%
On grandfathered Legacy Monthly plan
118 mo
Median tenure (~10 years)
Slice (HVC NEA stayers)UsersMonthly MRRAnnualized ARR
USA18,141$11.5M$138M
United Kingdom3,918$2.4M$28M
Australia1,871$1.07M$13M
Canada1,771$1.05M$13M
Netherlands1,126$602K$7.2M
Legacy Monthly plan (cross-cut)21,376$12.5M$150M
Standard Monthly plan9,615$4.5M$54M
Premium Monthly plan5,385$5.7M$68M
Non-ecommerce ICP21,272$12.7M$152M
Ecommerce ICP12,046$7.7M$92M

A.9Phase mitigation calculator

PhaseWindowUsers in cohortMonthly MRR mitigatedAnnualized ARR mitigatedCumulative ARR coverage
Phase 1Months 0–3~250K paid + 800K Free$5.0M$60M11%
Phase 2Months 3–9~150K paid$10.2M$122M32%
Phase 3 (hybrid)Months 9–18~38K HVC + 92K Legacy$23.4M (preserved)$281M100%
Total addressable$47.16M$566M100%

A.10Slack VOC summary

ChannelTotal scannedEditor-related VOCs
#hvc_feedback5,4231,381
#mc-hvc-escalations1368
#mc-reporting-analytics-feedback2,317162
Total7,8761,551

Generated 2026-05-11 by R&A PM team. Data window: May 2024 – May 2026. Pipeline date 2026-05-11. Original at deepakp1308.github.io/mailchimp-email-editor-analysis. SQL queries available on request. Cross-references: HVC Risk Map (Slack-cited MRR exposure on NEB / SMS / Brand Kit), Nuni YoY Audit (paid Nuni cohort YoY funnel), Revised Goals (3-cohort product-adoption scorecards), Initiative Canvas (74 initiatives), Strategy Memo.

Tab 13 · NUNI Repo Intel — Product Technical Intelligence

The NUNI codebase is AI-ready at the schema layer, version-drifted at the UI layer, and running ahead of its quality gates

7-layer forensic analysis of the collab-email GitHub Enterprise org (62 repos), applying the Product Technical Intelligence Playbook to the customer pain themes documented in this brief. Every claim is backed by a specific repo finding: file LOC, dep version, schema versions, contributor concentration, PR cycle time, test ratios. Window: May 2025 → May 13 2026. Source: deepakp1308.github.io/klaviyo-flows-competitive-analysis/nuni-repo-analysis.html.
v1.0 · 5 pages · 8 of 62 repos analyzed
Aggregate arch score: 3.0 / 5 (bimodal: lib 4–5, UI 1–3)
AI Readiness: 7/7 ready signals
Headline: 25-version schema drift gates Q2 Universal Content

1.1Headline finding for the executive committee

The Strategy Memo’s +$25–30M FY27 anchor depends on three Q2–Q5 ships — Universal Content (P2.1), NEB Code Mode (P2.2.3), and conversational in-canvas AI (P4.2.1). Two are structurally ready in the codebase today (semantic block schemas, command-pattern edit API). One is structurally blocked by the 25-version drift between nuni-core (the schema library, v1.74.5) and nuni-core-ui (the actual editor, pinned at v1.49.0). The single highest-leverage engineering ask is closing that gap before Universal Content ships — not because Universal Content can’t be built, but because shipping it on a stale schema layer guarantees the same fragmentation pattern that produced the Classic-vs-NEB split (Strategy memo Cost-of-Bifurcation: $1–2M ARR risk). R&A PM team / Product Technical Intelligence Playbook · May 13 2026.

1.2Top metrics

25 versions
nuni-core-ui consumes @collab-email/nuni-core@1.49.0 while the actual library is at 1.74.5 — gates Universal Content (P2.1).
3 React versions
React 17 in nuni-core-ui, React 18.3 in builder-platform, React 19 in nuni-core. Three layers, three runtimes, one product.
17%
Test-to-source LOC ratio in nuni-core-ui (the actual editor UI). Library layer is at 111–137%. Quality gates are below the layer customers touch.
AI-ready 7/7
nuni-core/edit/edit.ts: "Pure function. Zero React deps. Zero state. Zero side effects." Block-typed JSON tree + command pattern + 31 semantic block schemas. Conversational AI in canvas (P4.2.1) achievable today.

1.3Six things you need to know in 90 seconds

1

The diagram in your brief is outdated

The image labels collab-email/emails-nuni-editor as "Frontend editor (primary)". That repo was last pushed November 12, 2024 — 18 months untouched. The actual primary editor frontend is nuni-core-ui (last push: today). Not in the diagram: mc-omni-mcp (Python MCP server, the agentic surface) and mc-omni-agent-ui (4956KB TS, more active than nuni-core-ui itself).

2

Engineering is shipping the AI surface faster than the editor

Last 6 months commit count: mc-omni-agent-ui691 commits across 5 active engineers vs nuni-core-ui83 commits across 2 hero contributors. The Strategy Memo’s Guiding Principle #2 says "AI cannot compensate for broken editor trust"; the commit ratio shows the team is building the agent layer 8× faster than the foundation it sits on.

3

The data primitive for Universal Content already exists

nuni-core/src/document/operations.ts ships a JSON-tree document model with typed parent/children/properties; nuni-core/src/edit/edit.ts exposes a single edit(doc, edits, config) → EditCandidate command-pattern API. There are 31 semantic block schemas and 3 schema versions already shipped this year. Universal Content is not architectural greenfield — it is a primitive that maps to existing edit operations + a registry layer. Blocker is propagation, not invention.

4

Real-time collaboration foundation is already integrated — just unused

nuni-core-ui/package.json declares "pusher-js": "4.3.1" as a top-level prod dep. Pusher (WebSocket pub-sub) is in the editor today. What’s missing is the collab CRDT/OT layer on top — no yjs, @tiptap/extension-collaboration, hocuspocus, or liveblocks deps. The Q5 credibility moment (P5.3 real-time co-edit) is a library-add + integration spike, not a wire-up-WebSockets-from-scratch effort.

5

The editor has no detectable feature flag system in active code

Grep across nuni-core-ui/src + builder-platform/src for featureFlag|launchDarkly|optimizely|isExperiment: zero hits. At the editor level every deploy is all-or-nothing for 888K monthly Established users. Q2 Universal Content rollout, Brand Kit data fix, Write with AI ungate (Q4) all assume incremental rollout. Confirm the flag harness exists at the editor layer before committing to those quarterly milestones.

6

Hero engineer dependency on every active repo

Per Layer 5 (commit concentration, last 12 months): nuni-core top 2 contributors own ~76% of commits; nuni-core-ui top 2 own ~75%; builder-platform single author has 47% share; nuni-api single author = 56%. sprioleau appears as the top contributor in 3 of 4 active repos. Resignation, vacation, or reassignment is a P0 risk to the FY27 commit.

1.4What this means for the FY27 commit (Q-by-Q verdict)

Strategy memo bet (Q-by-Q)Code-readiness verdictWhat has to happen first
Q1 (May–Jul ’26) Brand Kit incident closure + SMS TCPA $57K guardrails (P1.2.1, P5.2.3)CONDITIONAL — bug fixes tractable; incremental rollout needs missing flag systemConfirm nuni-api emits flag-gated routes; if not, scope a 2-week flag harness spike before the 50% ramp
Q2 ★ (Aug–Oct ’26) Universal Content MVP (P2.1)PARTIALLY READY — schema + edit API exist; UI consumes a 25-version-old schema libBump @collab-email/nuni-core in nuni-core-ui from 1.49.0 to ≥1.74. Add Universal Content FragmentBlockSchema registry path (already exists at schema layer). 4–6 week spike, not a 4–6 month rebuild.
Q3 (Nov ’26–Jan ’27) NEB Code Mode (P2.2.3)UNDER-RESOURCEDhtml-to-nuni-parser is the inverse capability; Code Mode is the symmetric path with no current ownerDefine ownership: is Code Mode going into nuni-core-ui (TS) or as a parser microservice (Java)? Highest-risk Q in the roadmap.
Q4 ★ (Feb–Apr ’27) Write with AI global ungate (P4.1.1, P3.4.1)POLICY-GATED — no code blocker; mc-omni-mcp + mc-omni-agent-ui stack shippableDecouple model-availability flags from rendering paths. Confirm nuni-api can route AI calls per-region/per-tenant.
Q5 (May–Jul ’27) Conversational AI + Real-time co-edit + Shared blocks (P4.2.1, P5.3, P5.1)FOUNDATION READY — TipTap 3.20 + Pusher 4.3 + command-pattern edit() + JSON-tree stateAdd @tiptap/extension-collaboration + a CRDT (yjs or hocuspocus); wire existing Pusher channel to collab-doc events. Cleanest engineering story in the roadmap.
Q6 (Aug–Oct ’27) Brand-style transfer + Prompt-first mode + SMB governance (P4.2.2, P4.2.3, P5.4)DEPENDENT — requires Q2 + Q5 to land firstSequence locked.

1.5Three asks for the next engineering sync

  1. Publish a "schema bump" plan. Move nuni-core-ui from @collab-email/nuni-core@1.49.0 to @^1.74. Either via single bump + regression sweep, or phased migration (one schema version per sprint). Unblocks Universal Content + removes structural cause of bifurcation drift.
  2. Audit the editor-layer feature flag harness. If it doesn’t exist (the grep result is suspiciously clean), scope and ship it before Q1 Brand Kit fixes — every other strategy commit assumes incremental cohort rollout.
  3. Name a second-author on each top-3 critical-path repo. Pair sprioleau, ccovell, smoore16 with a designated co-owner in nuni-core, builder-platform, nuni-api. The bus-factor risk is invisible until it’s decisive.

Method: All numerical findings derived from collab-email/* on github.intuit.com via shallow clone + gh api queries against /repos, /commits, /pulls, and direct file reads. Every claim reproducible. Framework applied: Product Technical Intelligence Playbook (May 2026 internal reference, 20 pages, 7-layer forensic + AI readiness + org failure modes).

Page 2 · Architecture + Repo Map

5 layers + 3 satellites — from the browser the customer touches down to the send pipeline

Architecture of the NUNI authoring surface as it actually runs in production (May 13 2026 snapshot). Reconciles the diagram in the brief against the live repo state — including the 18-month-stale repo labeled "primary" and the AI surface missing from the diagram.
62 repos in collab-email org
18 active (push < 90d)
27 stale (push > 180d)
8 cloned for deep analysis

2.1The architecture in one diagram

CUSTOMER (browser · Mailchimp.com / new email builder)
  │
  │  HTTPS · React 17 SPA · loaded via Mailchimp shell
  ▼
┌─[1] PRESENTATION  (the editor UI)
│     nuni-core-ui  ·  TS · React 17 · 965 KB · push: today
│     ├─ store.ts (966 LOC)  ◄── god file: state · save · presence
│     ├─ TipTap 3.20  ── rich-text editor
│     ├─ Atlassian Pragmatic DnD 1.7  ── block drag-drop
│     ├─ Zustand 4.5 + Immer 11  ── state management
│     ├─ pusher-js 4.3  ── WebSocket bus (PRESENT but UNUSED)
│     └─ Bugsnag + browser-perf  ── observability
│
│     builder-platform  ·  TS · React 18.3 · 1.8 MB · push: today
│     └─ blocks/ Spacer · Image · Table · Divider · Text
│        (each with renderers/ + migrations/)
│
│   uses (peer dep)
▼
┌─[2] SCHEMA + EDIT  (the strategic moat — AI readiness 7/7)
│     nuni-core  ·  TS lib · 1.84 MB · @1.74.5 · push: today
│     ├─ edit/edit.ts  ◄── PURE FUNCTION command pattern
│     │     "(doc, edits, config) → EditCandidate"
│     │     Zero React deps · zero state · transactional
│     ├─ document/operations.ts  (addBlock · moveBlock · …)
│     ├─ 31 typed BlockSchemas
│     │     (Button · Image · Text · Product · Promo · Footer …)
│     ├─ validate/v20260113 · v20260225 · v20260316
│     └─ renderers/email/  ── per-block HTML output
│
│     ⚠ DRIFT: nuni-core-ui imports @1.49.0 (25 versions behind 1.74)       (gates Q2 Universal Content + 3 of 7 VoC hate themes)
│
│   HTTPS · REST/GraphQL
▼
┌─[3] API
│     nuni-api  ·  TS · Hono (NOT Express) · 657 KB · push: today
│     ├─ Pino structured logging
│     ├─ Intuit IAM ticket auth via JSK
│     └─ Pre-push hook: build + test:ci
│
▼
┌─[4] PERSISTENCE  (in-flight migration: Kotlin → TS)
│     nuni-document-store  ·  Kotlin · 202 KB · stale 4 mo
│              ─── OR ─── (parallel today)
│     document-data-store  ·  TS · 615 KB · push: today  ── NEW
│
─── ASSET LAYER (loaded on demand) ─────────────────────────────────
     nuni-template-sources  (JS · 18 MB JSON catalog)
     nuni-brand  (TS · Brand Kit data)
     nuni-thumbnails  (JS · preview images)

─── RENDER PIPELINE (on send) ──────────────────────────────────────
     email-render-pipeline  (TS · Vitest + jsdom · push: today)
       ▸ calibration · scoring · screenshot diff · golden-data PNGs
       ▸ NOT YET wired into nuni-core-ui CI gate  (the unrealized win)
     server-side-rendering  (JS · 9 MB · push: today)
       ─→ [Mailchimp send pipeline · OUTSIDE this org]

─── AI SURFACE (parallel · NOT in your repo diagram) ───────────────
     mc-omni-agent-ui  (TS · 4.9 MB · push: today)
            ↕  MCP protocol
     mc-omni-mcp  (Python · 546 KB · push 9 days ago)
       ▸ agents_and_tools.yaml ◄── MCP tool registry
       ▸ exposes nuni-core/edit/edit() AS A TOOL
       ▸ AI-generated edits → preValidate → mutation → postValidate

─── MIGRATION (Classic → NEB · winding down) ──────────────────────
     html-to-nuni-parser  (Java · Maven · Lombok · 122 src files)
     editor-migration-workbench  (HTML)
     editor-migration-release  (Go · stale 10 mo)

2.2How it works — 10 steps

  1. Customer signs in to Mailchimp and clicks "Create campaign." The Mailchimp shell (legacy monolith) routes to the New Email Builder.
  2. The browser loads nuni-core-ui — React 17 SPA. TipTap rich-text; Atlassian Pragmatic DnD blocks; Zustand + Immer state. pusher-js in deps but currently unused (the unused real-time foundation Q5 collab will activate).
  3. nuni-core-ui imports nuni-core@1.49.0, the schema/edit library that defines what blocks exist (31 typed schemas) and how to mutate documents. The library is at v1.74.5; the UI consumes v1.49.0. Closing this drift is the highest-leverage Q1 action.
  4. When user drags a block onto the canvas, DnD captures the drop, calls nuni-core/edit/edit({type:'addBlock'}), returns an EditCandidate. Candidate runs preValidate → mutation → postValidate; if valid, new doc replaces old in Zustand store; React re-renders via builder-platform’s per-block renderers.
  5. State, save, conflict detection, presence all flow through the 966-LOC store.ts in nuni-core-ui. The playbook’s "god file" and architectural choke point that gates Q5 collab.
  6. Saves go through nuni-api — a Hono service (not Express), Intuit IAM auth. Writes to either nuni-document-store (Kotlin, stale) or document-data-store (TS, new). Persistence mid-migration.
  7. Asset data loaded on demandnuni-brand, nuni-template-sources (18 MB catalog), nuni-thumbnails.
  8. Preview is generated client-side via nuni-core/renderers/email/. Deeper visual-regression check uses email-render-pipeline but isn’t yet wired into nuni-core-ui CI gate — "70%-built rig sitting unused."
  9. On send, doc rendered server-side through server-side-rendering to final HTML, then handed off to Mailchimp send pipeline (outside this org).
  10. AI surface (parallel, not in your diagram): mc-omni-agent-ui (TS) talks to mc-omni-mcp (Python MCP server), which exposes nuni-core/edit/edit() as an MCP tool. AI agents make valid edits without going through the UI — because edit() runs the same preValidate/postValidate, AI-generated mutations cannot corrupt document state. The rare case where AI safety is provided by the architecture, not by guardrails bolted on.

2.3Repo map — reality vs the diagram in your brief

Diagram layerRepo (per diagram)Live sizeLast pushReality check
Frontend editor (primary)collab-email/emails-nuni-editor182 KBNov 12 2024This is the wrong repo. 18 months untouched. Actual primary is nuni-core-ui (push today, 965 KB).
Builder platform shellbuilder-platform1,799 KBMay 13 2026Correct + active. TS, React 18.3.
Schema / validation libnuni-core + nuni-core-cross-validate1,840 + 242 KBMay 12 2026Correct. Source-of-truth schema package.
API servicenuni-api657 KBMay 12 2026Correct + active. Surprise: Hono framework (not Express).
Document storenuni-document-store (Kotlin)202 KBJan 15 2026 (4mo stale)Correct but concerning. document-data-store (TS, 615 KB, push today) appears to be parallel/replacement. Diagram doesn’t mention it.
HTML→Nuni migrationhtml-to-nuni-parser + 3 others546 + 3.2 + 0.3 + 0.1 MBMostly winding downJava + Maven + Lombok (122 src files, 202 prod-test HTML fixtures). Migration release tooling last touched Jul 2025 (10mo). Implication: Classic-to-NEB migration is winding down.
Render pipeline / SSRemail-render-pipeline + server-side-rendering297 + 9087 KBMay 12, May 4 2026Vitest + jsdom + nuni-renderer-jsdom with calibration/comparison/screenshot infra — visual-regression scaffolding ready.

2.4Repos missing from the diagram (the AI orchestration layer)

mc-omni-agent-ui · 4,956 KB · TypeScript

Last push: today (May 13). Most recently pushed in entire org.

Contains AGENTS.md + CLAUDE.md at root. Contributors last 6mo: jarama 233, sprioleau 124, jlittle4 123, ccovell 107 — 691 commits across 4 active humans + service bot. Where conversational journey editing (P4.2.1, Q5 ★) is being built.

mc-omni-mcp · 546 KB · Python

Last push May 4. MCP server, agent backend.

Contains agents_and_tools.yaml (MCP tool registry), JenkinsfileAgenticStage.snippet, .cursorrules + .windsurfrules. Top contributors: jdudley1 36, amilt (Austin Milt) 32, jlittle4 17. Austin Milt is splitting time between Brand Kit reliability + agent backend.

document-data-store · 615 KB · TypeScript

Last push today. Newer parallel/successor to Kotlin store.

Migration from Kotlin → TS data store in progress; not labeled in diagram. Risk: two doc stores in parallel echoes the Classic-vs-NEB editor split. If Kotlin store still serves prod traffic, it’s a persistence-layer bifurcation.

marketing-email-builder, proposal-builder, transact-builder

Adjacent active TS UIs — possibly platform consumers

proposal-builder (4,399 KB, push today, larger than nuni-core-ui) and transact-builder (3,175 KB, active) likely share builder-platform. marketing-email-builder (360 KB, 6mo stale) is the campaign-side host. Need ownership clarification.

2.5Stack-fragmentation finding

The NUNI surface ships in 6 languages: TypeScript, JavaScript, Kotlin, Java, Go, Python. Each language carries its own dep tree, security audit cadence, CI lane, on-call training cost. Migration tooling alone (Go for editor-migration-release; Java for parser; Kotlin for legacy doc store) is three runtimes. Not unusual for a 4-year-old platform, but it is operational tax that compounds with React-version drift.

Three React versions across three layers consumed by the same product (React 17 in nuni-core-ui, React 18.3 in builder-platform, React 19 peer in nuni-core) is the playbook’s Layer 2 dependency-debt red flag in its purest form. Works today via React backwards-compat; breaks when nuni-core uses any React-19-only API.

Sources: gh api orgs/collab-email/repos --paginate (62 repos enumerated). Per-repo package.json, build.gradle.kts, pom.xml read from shallow clones. Last-push timestamps from GitHub repo metadata. Contributor counts from gh api repos/<repo>/commits?since=2025-05-01T00:00:00Z --paginate.

Page 3 · Pain → Code Map (Playbook §4)

Every customer complaint, with the architectural root cause and the fix

12 customer-pain rows from the Editor Brief, mapped to specific code findings. Each row pairs (1) why this is happening given the way the system is built today, (2) what we should do about it, and (3) the business metric that should move when the fix ships.
12 customer pains · 4 root-cause patterns · Source: Editor Brief tabs 2–6 + repo evidence

3.1Top 6 customer pains → root cause → fix (highest cited MRR)

VOC #1 · BIFURCATION · $834/mo cited

"Two builders that don’t talk to each other — I rebuilt the same welcome email three times"

Root cause: Templates customers built in the old Classic Builder can’t move automatically to NEB. The Java conversion service (html-to-nuni-parser) has been quiet for 10+ months — migration tooling was wound down before the bridge was complete.

Fix: Restart migration tooling investment. Build "1-click migrate ALL my templates" using the 202 production HTML test fixtures already in the parser repo as regression suite. Pair with funded migration assistance for Premium accounts (12mo grace). Metric: Bulk Established 888K → 915–935K (+$10.4M L1); Premium/agency Classic ARR retained ($1–2M risk per Strategy R1).

VOC #6 · NO UNIVERSAL CONTENT · $330/mo cited · PARITY GAP

"Klaviyo just shipped Universal Content. Edit once, propagates. I’m migrating before BFCM."

Root cause: "Edit once, propagates" has actually been built in Mailchimp’s schema library — called FragmentBlockSchema in nuni-core@1.74. But the editor UI consumes v1.49 (25 versions behind). It’s like the kitchen made a new dish but never sent it to the dining room.

Fix: Ship a "schema bump" — upgrade the editor UI’s consumed library version from 1.49 to 1.74. 4–6 weeks of regression testing, no new feature code. Highest-leverage Q1 action in the brief — closes Universal Content + 2 other hate themes simultaneously. Metric: Universal Content adoption 50–70% of NEB users; block reuse +25–40%; +$4–7M FY27 (Strategy P2).

HVC #3 · RENDERING BUGS · $1,820/mo cited (4 named)

"Forwarded mail looks not good at all"; mobile line-breaks; Ctrl+K broken on Firefox/Chrome

Root cause: When code change breaks how an email renders in Gmail/Outlook/mobile, nothing automated catches it — team finds out from support tickets. Mailchimp does have a screenshot-comparison tool (email-render-pipeline) with golden-data PNG fixtures, but only 2 tests use it and it’s not wired into editor’s pre-merge CI gate.

Fix: Wire the existing screenshot-diff tool into editor’s CI pipeline. Every PR runs it; broken rendering blocks merge. Infrastructure is 70% built — this is a 1–2 week integration job, not a build. Cheapest retention save in the brief. Metric: Bulk churn 40.0% → 36.5–37.5%; +$3–5M FY27 L5 retention save.

HVC #4 · MULTI-AUTHOR SAVE CONFLICTS · $340/mo cited

"Just get a message saying there is a problem with the saved version … no indication that someone else is currently editing"

Root cause: When two team members edit the same email, one’s changes get silently overwritten. Editor doesn’t track who has the document open. State-management code (store.ts, 966-line file) tangles save logic, conflict detection, rendering state. Adding multi-user awareness requires breaking up that file first.

Fix: Decompose store.ts into three smaller files: state, save/persistence, presence. Then add presence using the pusher-js dependency already in package.json but unused. After that, real-time co-edit (Q5 strategy moment) becomes a follow-on, not a rebuild. Metric: Save-conflict tickets eliminated; foundation for P5.3 real-time co-edit.

HVC #7–10 · BRAND KIT RELIABILITY · $6,465/mo cumulative

Stale colors; logo present but no colors; "DIN 2014 not recognized"; no multi-brand kits

Root cause: Customers spend hours setting up Brand Kit and expect it to flow through every email, landing page, form, AI design suggestion. But Brand Kit data lives in nuni-brand, while consumers (editor, landing pages, Creative Assistant, signup forms) each fetch and cache it separately. When data updates, not all consumers see the update. Multi-brand isn’t supported because data model assumes one kit per account.

Fix: Treat Brand Kit as a contract, not a data store. Define one source-of-truth in nuni-brand; make every consumer read from it on every request (no caching divergence). Add multi-brand data model. 4–6 weeks of platform work; closes 4 cited HVC themes. Metric: P1.2 sub-pillar (4 initiatives, FY27 $3–5M); Brand Kit auto-extract on signup unblocked.

HVC AI / HEALTH · WRITE WITH AI GEO-GATE · ARR-CRITICAL

"I am in the Netherlands. I get to pay for AI I cannot use" (Explore −73.7% YoY · churn 77.2% — worst in family)

Root cause: Write with AI is gated to US/UK/AU/CA only — but Standard plan is sold globally. International customers pay the same price and can’t use the headline AI feature. Geo-gate is enforced UI-side, not API-side, so even if the model is technically available, the UI won’t show it.

Fix: Move geo-gate decision from UI to API gateway (nuni-api). Then run parallel policy track to (a) ungate Write with AI globally, or (b) repackage as paid AI add-on globally. Technical work < 2 weeks; policy/legal work 1–2 quarters. Metric: P4 entire pillar (15 initiatives, FY27 $4–6M); reverses Health Crisis Pillar (Strategy R3).

3.2Pattern recognition — 4 leverage points (fix one, multiple complaints clear)

Pattern 1 · Force multiplier

The schema-vs-UI version drift — 25 versions behind

Why this is a problem. The "library" half (nuni-core) is at v1.74. The "editor UI" half customers see is consuming v1.49 — 25 versions behind. Like a restaurant where the kitchen has a new menu but the waiters are working from a 5-month-old printed copy. Three of seven customer hate themes happen because new capabilities exist in the kitchen but never reach the customer’s table.

The solution. Schedule a 4–6 week "schema bump" as a single Q1 commit — one engineer, zero new features, just close the gap. Three customer hate themes become solvable simultaneously; Q2 Universal Content automatically unblocked. Highest-leverage Q1 action in the entire brief.

Pattern 2 · Choke point

The 966-line store.ts is the bottleneck for collab + reliability

Why this is a problem. The editor has one giant 966-line code file handling everything: tracking what the document looks like, saving it, managing undo/redo, and (eventually) tracking who else is editing. When one file does too many things, every change risks breaking something else. Three customer pains all live in this one file: multi-author save bug ($340/mo), block-ordering refresh bug ($410/mo Premium), and the Q5 real-time co-edit moment.

The solution. Split store.ts into three smaller files with single responsibilities: document state, save/persistence, presence. This 2–3 week refactor unblocks two cited bugs and the entire Q5 collaboration roadmap — three quarters of strategy depend on this single file getting decomposed.

Pattern 3 · Built but unwired

The screenshot-regression rig is built — just not connected

Why this is a problem. #3 cited customer complaint is "the email looked right in editor, but recipient saw something broken" — particularly forwarded mail, mobile preview, Outlook web view. $1,820/mo of named-customer pain on this single theme. Mailchimp already has screenshot-test infrastructure (email-render-pipeline) — calibration, screenshot diff, scoring, golden-data PNG fixtures. It’s all there. Just not connected to editor’s test pipeline. Today only 2 tests use it.

The solution. Wire the existing screenshot-diff tool into editor’s CI pipeline. Every PR runs it; broken rendering blocks merge. 1–2 week integration job using infrastructure that’s 70% complete. Once wired, closes the entire Theme 3 pattern. Cheapest retention save in the brief.

Pattern 4 · Org/portfolio decision

The AI surface is shipping faster than the foundation it sits on

Why this is a problem. AI agent layer (mc-omni-agent-ui + mc-omni-mcp) has had ~5× the activity of the actual editor UI over last 6 months. The team is investing more engineering energy in AI features bolted on top of the editor than in fixing the editor itself. Risk: a customer tries the new conversational AI, asks it to do something, the underlying editor breaks because of an existing rendering bug, and the customer concludes "AI is broken" — when it was actually the foundation underneath.

The solution. This isn’t a code question — it’s a leadership question. Before Q3, the exec team should decide what % of capacity goes to fixing editor foundation (target: ≥ 60%) vs. building new AI features (target: ≤ 25%) for the rest of FY27. The codebase shows the priority; the leadership decision aligns it.

Sources: All repo facts from github.intuit.com/collab-email/* via shallow clone (depth=1) on main/master tips as of May 13 2026. Customer-pain references from HVC Risk Map ($95K/mo cited across 17 themes), Voice of Customer (7 hate themes), User Research (5 bets, Discovery table). Framework: Product Technical Intelligence Playbook §4.

Page 4 · 7-Layer Forensic + 6 Org Failure Modes

Layer-by-layer evidence on the active core repos — with org-level diagnoses

Each layer of the playbook’s Phase 1 framework, applied with reproducible repo evidence (Strength · Watch · Risk). Plus the six organizational failure modes from §5 with the repo evidence that surfaced each one.
7 layers · 5 active core repos · 6 failure modes

4.1Seven-layer forensic verdicts

L1

Architecture & Structural Health

MIXED · modular schema lib + god-class UI

Strengths: Modular decomposition is real at schema layer (nuni-core/src/ splits into document/, edit/, render/, renderers/email/, etc.). Per-block ownership of rendering + migration paths in builder-platform. Schema versioning institutionalized (v20260113, v20260225, v20260316).

Risks: 966-LOC store.ts (over 800 LOC threshold) — high-fan-in choke point for state, save, conflict, presence. Multi-author (HVC #4) and block-ordering (HVC #5) bugs both flow through it. Three React versions in the live consumer chain (17 / 18.3 / 19). Kotlin doc-store running parallel with new TS doc store (persistence-layer bifurcation echoes editor bifurcation customers hate).

L2

Dependency & Security Posture

RISK · major-version drift is the tax

Strengths: Renovate is configured on every active TS repo. Auto-update bot runs as svc-uxinfra-bot. Secret-detection ESLint plugin enabled.

Risks: The 25-version drift on schema lib is a deliberate (or neglected) pin: "@collab-email/nuni-core": "1.49.0" exactly (no caret), preventing Renovate from upgrading. Stale UI ecosystem in nuni-core-ui: react-intl@2.9 (current 7.x), styled-components@4.4 (current 6.x), tabbable@4.0.0, TypeScript 4.8 (current 5.7). Node 18 EOL April 2025 — pin will break before Q3 FY27 if not bumped. Three design systems present (@design-systems/icons Intuit, @mcds/components MC, @ids-ts/* Intuit-TS). pusher-js@4.3.1 stale major (current 8.x) carrying the future real-time story.

L3

Test Coverage & Quality Infrastructure

RISK · 17% test ratio on the editor UI
RepoSource LOCTest LOCRatioVerdict
nuni-core13,22314,731111.4%EXCELLENT
builder-platform8,23811,315137.4%EXCELLENT
nuni-core-ui (the actual editor)20,6043,43816.7%FEAR-DRIVEN
nuni-api13 test filesLIGHT
email-render-pipeline2 test filesSCAFFOLD ONLY

NO end-to-end tests anywhere in the active core. No Playwright. No Percy. No Chromatic. The playbook calls this exactly: "No E2E on a visual builder = ‘previews don’t match sent emails’ bugs" — HVC Theme 3 ($1,820/mo cited) is exactly that pattern. Visual regression infrastructure exists but isn’t usedemail-render-pipeline rig is 70% built, gated by 2 unit tests, not wired into nuni-core-ui CI. Cheapest L5 retention save in the brief.

L4

Code Complexity Hotspots

RISK · 4 production files > 600 LOC, 3 on customer path
FileLOCRepoConcern
store.ts (NuniCoreEditor/platform/)966nuni-core-uiGod-class candidate. Touched by HVC #4 + #5. Decompose to unblock Q5 collab.
schemaConverter.ts (services/)687nuni-core-uiBridges old "email-editor" widget to NEB schema. Direct candidate for the schema-bump rewrite.
schemas.ts (channel/email/)664nuni-coreSchema registry. Production code; not a problem if cohesive.
operations.ts (document/)641nuni-coreContains addBlock / moveBlock / moveToColumnPosition. Heavy churn likely (HVC #5 cluster lives here).
SocialFollowRenderer.tsx626nuni-coreSingle-block renderer at 626 LOC = block-specific complexity. Likely Outlook/Gmail/AOL conditional rendering.
RichTextToolbar.tsx611builder-platformToolbar = high-fan-in surface; refactor candidate.
L5

Commit & PR Patterns (Velocity Forensics)

RISK · hero engineer dependency on every active repo
RepoTop contributor concentration (last 12mo)PR medianPR p95Verdict
nuni-coresprioleau 147 + jhunsucker 106 = 76% of commits17.6h75.0hHERO 2-of-N
nuni-core-uisprioleau 34 + ccovell 28 = 75% (low total: ~83 commits in 12mo)7.1h692.6h (29 days)REVIEW BOTTLENECK
builder-platformccovell alone 181 commits = 47%; second contrib at 592.8h98.0hSINGLE HERO
nuni-apismoore16 67 = 56% single-author3.4h64.6hSINGLE HERO
mc-omni-agent-uijarama 233 + sprioleau 124 + jlittle4 123 + ccovell 107 — 4 humans + botDISTRIBUTED

sprioleau appears as #1 or #2 in nuni-core, nuni-core-ui, mc-omni-agent-ui — three of the four most-critical surfaces. ccovell is #1 in builder-platform AND #2 in nuni-core-ui. Two engineers carry the floor of the FY27 commit. nuni-core-ui p95 PR time = 29 days. AI surface (mc-omni-agent-ui) shipping ~8× faster than the editor that hosts it.

L6

Performance & Error Handling

WATCH · observability wired; bundle analyzer not

Strengths: Bugsnag + Browser Performance + React error boundary integration (@bugsnag/js@8.8.1, @bugsnag/browser-performance@3.4.1, @bugsnag/plugin-react@8.8.0). Email-client compat hacks minimal in source (renderer abstracts them).

Risks: Single-vendor observability (no Datadog RUM detected). Bundle analysis not configurednuni-core-ui/webpack.config.js is bare (per the comment, plugin-cli handles the build); no webpack-bundle-analyzer, no source-map explorer, no preload hints. Bundle size unlikely to be measured per-PR.

L7

Feature Flag & Configuration Debt

RISK · no detectable flag system in editor code

What we found: Grep across nuni-core-ui/src + builder-platform/src for featureFlag|FeatureFlag|launchDarkly|optimizely|isExperiment|experimentKey|flagService: zero matches.

Plausible that flag resolution happens at platform-shell or nuni-api level. But at the editor surface, every customer gets the same code on every deploy. Strategy memo Q1 Brand Kit fix, Q2 Universal Content MVP, Q4 Write with AI ungate, and Q5 collab moment ALL assume cohort rollouts. Without an editor-layer flag harness: Universal Content can’t be A/B tested for adoption; the Brand Kit data fix (50% ramp confirmed by Austin Milt) needs validation that ramp is happening at nuni-api, not the UI.

4.2Six organizational failure modes (Playbook §5)

Failure mode 1 · Hero engineer dependency

Two engineers carry the floor of the FY27 commit

sprioleau top contributor in 3 of 4 critical surfaces; ccovell also in 3 of 4. nuni-core-ui p95 PR time 692 hours (29 days). Mitigation (within 30 days): Name designated co-owner on each top-3 critical-path repo. Pair-program on next two PRs. Rotate one Q1 ship lead away from sprioleau / ccovell.

Failure mode 2 · Fear-driven engineering

17% test ratio on nuni-core-ui is the codebase signal

Library 111% / platform 137% / editor UI 17%. Zero E2E on a visual builder. store.ts god file + 687-LOC schemaConverter + unused email-render-pipeline rig describe a system where safest paths are ones nobody touches. Mitigation: Wire email-render-pipeline golden screenshots into nuni-core-ui CI. Add 4 cypress tests covering HVC #3, #4, #5 before any new editor feature.

Failure mode 3 · Modernization without value

The opposite is happening — but watch the AI rebrand

Team IS shipping customer value (Brand Kit incident closed, schema versions advancing). BUT AI agent surface is running 8× faster than the editor — Strategy Memo Guiding Principle #2 says "AI cannot compensate for broken editor trust." Risk: AI surface framed externally as "answer to Klaviyo Marketing Agent" while internal Pillar 1 (Quality & Trust) underdelivers. Track the ratio quarterly.

Failure mode 4 · Bugs never die

Brand Kit incident closed; rendering + block-ordering recur

HVC #8 (Brand Kit data correctness) closed (Austin Milt 50% ramp). HVC #3 (NEB rendering) has 4 cited customers across 4 dates over 2.5mo — recurrence pattern. No regression-test coverage for these scenarios in nuni-core-ui. Bug ownership is implicit (engineer who touched it last) rather than explicit (on-call PM/EM).

Failure mode 5 · Cross-org dependencies

SMS, Canva, Intuit Assist all sit outside collab-email

SMS pipeline: $57K TCPA incident lives in different org. Canva integration: $2,500/mo silent-failure pattern is cross-org. Intuit Assist: Model availability + geo-policy = Intuit-platform decision, not collab-email. Three design systems means three external teams gating component upgrades. Mitigation: for the 3 cross-org Q1–Q5 dependencies, name a Senior PM-level escalation contact in the partner org now. Don’t wait for the dependency to slip.

Failure mode 6 · Half-baked features

Schema/edit API is finished; UI consumes 25-version-old version of it

nuni-core ships FragmentBlockSchema.ts, v20260316 validation, full edit() command pattern. The primitive for Universal Content is done at the schema layer. nuni-core-ui consumes nuni-core@1.49.0. "Done" defined at each repo boundary, not at the customer-experience boundary. The README of nuni-core explicitly says: "We strongly recommend that you use the validation endpoints on Nuni API instead of directly depending on this library." — and the editor itself is the violator.

Method: Each layer applied per Product Technical Intelligence Playbook §3 (Days 3–7 deep dive). Evidence collected via shallow-clone + find / grep / wc / jq against latest tip of main/master. Contributor and PR data from github.intuit.com REST API on May 13 2026. All findings reproducible — see Method & Sources at bottom.

Page 5 · AI Readiness + SWOT + Final Recommendation

The schema and edit layers score 7/7 ready signals — the AI surface is the leverage opportunity

Per the playbook’s 7-dimension AI readiness checklist (§7.1) + SWOT analysis (Strengths · Weaknesses · Opportunities · Threats) + 5 ordered actions for the next 1–2 quarters. NUNI is the rare case where the foundation is more AI-ready than the AI surface assumes.
AI Readiness: 7 / 7 ready signals
SWOT aggregate: 3.0 / 5 (bimodal)
5 ordered actions for Q1–Q2

5.1AI readiness scorecard — the rare 7-of-7

Readiness dimensionRepo evidenceVerdict
Editor state structure (JSON block tree with typed nodes)nuni-core/src/document/types.ts defines Doc = Record<string, DocBlock> with typed nodes. operations.ts implements parent/child walks via findAncestorOfType(), getDescendants().READY
Component semantics (typed blocks with metadata)31 typed block schemas: ButtonBlockSchema, ImageBlockSchema, TextBlockSchema, ColumnBlockSchema, EmailFooterBlockSchema, EmailImageGallerySectionBlockSchema, ProductBlockSchema, ProductRecsBlockSchema, PromoCodeBlockSchema, SocialFollowBlockSchema, SurveyButtonBlockSchema, VideoBlockSchema, FreddieBadgeBlockSchema, etc. Every block carries semantic type + Zod-validated property metadata.READY
Content modularity (block-level CRUD)operations.ts exports addBlock, deleteBlock, updateProperties, moveBlock, duplicateBlock, moveToColumnPosition. Independent block-level CRUD. FragmentBlockSchema exists for cross-document blocks (Universal Content primitive).READY
Workflow observability (event bus / action log)nuni-core/src/edit/log-collector.ts + edit/log/ directory. edit() returns an EditCandidate with logs. Action log structurally present.READY
Machine-callable actions (clean API or command pattern)edit/edit.ts header: "The single internal API for all document mutations. Pure function: (doc, edits, config) → EditCandidate. Zero React deps. Zero state. Zero side effects." Plus preValidate(), postValidate(), resolveEditTarget(). Textbook command pattern with pre/post hooks. AI agent can call edit() directly.READY
Prompt / context access (metadata accessible at edit time)Brand Kit lives in nuni-brand; document metadata in nuni-document-store; product catalog connectors are integration surface. EditConfig can carry context. mc-omni-mcp/agents_and_tools.yaml declares the tool registry.READY
Safe state modification (command pattern with undo stack)edit/types.ts: EditCandidate + EditResult + BlockValidationIssue; edit() takes validation: "strict" and mode: "transactional" options. document/intelligence.ts exports diff and snapshot (undo-stack primitives).READY
The rare 7-of-7 — what this means

NUNI’s schema and edit layers are already more AI-ready than most code

Conversational journey editing in canvas (Strategy P4.2.1, Q5 ★) is technically achievable today. The blockers are not the code — they’re (1) the schema/UI version drift gating which schemas the AI can act on, (2) the agent-layer prompt + RAG context that connects Brand Kit + audience to the edit() call, (3) safety / brand-tone guardrails. None of those are 18-month builds; they’re 4–8 week scoped efforts.

5.2SWOT analysis — architecture in one view

Strengths · what to BUILD ON
  • Schema/edit library is a strategic moat. Pure-function command-pattern API. Klaviyo and Stensul still trying to build this.
  • AI readiness 7/7 on the playbook checklist.
  • Real-time collab building blocks already in deps. pusher-js@4.3.1 + TipTap 3.20 (collab-ready) + command-pattern edit(). CRDT add is 4-week PoC, not rebuild.
  • Visual regression infrastructure 70% built. Just unused in CI.
  • Schema versioning institutionalized. 3 schema versions shipped this year.
  • Library/platform test discipline excellent. 111–137% test ratio.
Weaknesses · what is IN OUR WAY
  • 25-version schema/UI drift. Single architectural defect that gates Q2 Universal Content + Q5 unified canvas.
  • Three React versions in the live consumer chain (17 / 18.3 / 19).
  • Editor UI test ratio 16.7% vs library 111% / platform 137%. Fear-driven engineering on customer-facing layer.
  • 966-LOC store.ts god file. Gates Q5 collab story.
  • Stale UI ecosystem. react-intl@2.9 (current 7.x), styled-components@4.4, Node 18 EOL April 2025, Pusher 4.
  • No editor-layer feature flag harness detectable.
  • Six languages + three design systems = operational complexity tax.
Opportunities · what we should GO AFTER
  • One schema bump unlocks three quarters of roadmap. Bumping nuni-core-ui to nuni-core@^1.74 simultaneously enables Q2 Universal Content, Q5 unified email+SMS canvas, Q6 fragment-graph governance.
  • Expose edit() as MCP tool registry. Makes Mailchimp’s editor more AI-callable than Klaviyo’s. First-mover on conversational journey editing — Q5 ★ becomes a 4–8 week effort.
  • Decompose store.ts as the highest-leverage refactor. Unlocks HVC #4 + #5 + Q5 collab simultaneously.
  • Wire email-render-pipeline into nuni-core-ui CI. Cheapest L5 retention save in the brief.
  • Q5 real-time collab in 4-week PoC, not 6-month rebuild. Cleanest engineering story in the FY27 roadmap.
Threats · what could HURT US
  • Hero-engineer bus factor of 2. sprioleau + ccovell carry top-3 commit share on 3 of 4 critical surfaces.
  • AI surface shipping ~8× faster than the editor it sits on. Strategy Memo’s "AI cannot compensate for broken editor trust" is being violated structurally.
  • Three React versions = forced-migration latency bomb. When nuni-core uses any React-19-only API, the editor breaks unless it bumps too.
  • Klaviyo’s parity launches accelerate timing risk. Spring 2026 Universal Content already public.
  • Node 18 EOL’d April 2025; nuni-core-ui/package.json still pins Node 18-only. Will break under future security patches.

5.3Final recommendation — five ordered actions

1

Q1 — Bump nuni-core-ui to nuni-core@^1.74

Single highest-leverage action in the brief. Unblocks Universal Content (Q2), shared blocks (Q5), removes structural cause of 3 of 7 VoC hate themes. Estimate: 4–6 week spike + regression sweep. Cost: low. Strategic value: highest.

2

Q1 — Wire visual-regression rig into nuni-core-ui CI

Cheapest L5 retention save. email-render-pipeline’s calibration + screenshot diff + scoring infrastructure is 70% built. Closes HVC #3 ($1,820/mo cited) regression pattern. Estimate: 2-week spike + ramp.

3

Q2 — Decompose store.ts (966 LOC)

Critical-path refactor. Unblocks HVC #4 multi-author save fix + HVC #5 block-ordering fix + Q5 real-time collab moment. Decompose into presence + edit reducer + persistence; lay foundation for CRDT integration.

4

Q2 — 2-week conversational AI PoC against edit()

Validates Strategy Memo Q5 ★ credibility moment. Expose edit(doc, edits, config) via mc-omni-mcp as an MCP tool; agent UI sends "make the hero block 20% smaller in a friendlier tone." Output: feasibility report + safety incident count.

5

Q1+ ongoing — Name designated co-owners on all top-3 critical-path repos

Bus-factor mitigation. Pair sprioleau, ccovell, jhunsucker, smoore16 with a designated co-owner on the next two PRs. Rotate one Q1 ship lead away from the hero pool. Cost: zero. Insurance value: highest non-technical lever in the brief.

5.4Closing — the one-line read

The NUNI architecture is a story of two halves. The schema and edit-API layer is among the best automation/editor primitives in the SMB tier — modular, AI-ready, command-pattern, version-disciplined. The customer-facing UI layer is on stale React, undertested, version-drifted, hero-dependent. The FY27 +$25–30M commit is achievable because the foundation is right; the timing is at risk because the consumer surface is undermaintained. The single most important architectural action for Mailchimp leadership is closing the 25-version schema drift — every other Q1–Q5 strategy bet either depends on it directly or is made cheaper by it. Everything else flows from there. R&A PM team / Product Technical Intelligence Playbook · May 13 2026.

5.5Method & sources

Snapshot: May 13 2026, 18:00 UTC. Repos enumerated: 62. Repos cloned: 8 (depth=1). Framework: Product Technical Intelligence Playbook — May 2026, 20-page internal reference (§1.1 Five Types of "We Can’t" + §3 Phase 1 Repo Deep Dive 7-Layer Forensic + §4 Phase 2 Customer Pain → Code Mapping + §5 Phase 3 Org Failure Mode Analysis + §6 Phase 4 Building Technical Leverage + §7 Phase 5 AI Readiness Assessment + §8 Email Builder Investigation Checklist).

Reproducible queries: gh api orgs/collab-email/repos --paginate for repo enumeration; per-repo gh api repos/collab-email/$repo; shallow clones gh repo clone collab-email/$repo $repo -- --depth=1; Layer 4 file size via find ... -exec wc -l ; | awk '$1 >= 600' | sort -rn | head -25; Layer 3 test/source LOC ratio computed in shell; Layer 5 contributor concentration via gh api repos/collab-email/$repo/commits?since=2025-05-01T00:00:00Z --paginate.

Caveats: No engineering interviews. The "schema/UI version drift is intentional" hypothesis assumes the team knows about it — confirm in next sync. Cross-org dependencies (SMS pipeline, Canva integration, Intuit Assist policy) not deeply mapped. Bundle size + performance traces + runtime profiles not measured. Feature flag harness existence inferred from grep absence — flag service may live higher up the platform shell. Some repos in the org not cloned (proposal-builder, transact-builder, mc-omni-mcp, mc-omni-agent-ui, document-data-store, nuni-core-sdk). Confidentiality: repo-level findings derived from github.intuit.com/collab-email/*. Original source: deepakp1308.github.io/klaviyo-flows-competitive-analysis/nuni-repo-analysis.html. Cross-references: HVC Risk Map, NEA→NUNI Migration, Initiative Canvas, Strategy Memo.

Initiative Canvas v2.0 · Editor + SMS · Freddie + Canva gap intelligence integrated

The ~75 initiatives that get the editor to ~$21M ARR — now incorporating Freddie Phase 1 + 2 assessment, Canva AI / AI 2.0 gap closure, and 14 move-my-cheese mitigations

This canvas is the execution surface for the Revised Goals (~$21M ARR across paid $6.7M + free $8.7M + trial $5.6M). It now integrates three new intelligence layers: (1) Freddie Prototype Assessment — 0/17 HVC themes solved, 14 move-my-cheese risks, $6–18M downside band, per-feature risk catalog; (2) Freddie Phase 2 specs — 8 send-time intelligence capabilities Canva can never match (orchestration, performance loop, send-time personalization, asset studio, localization, AMP, Shield, cross-domain agent); (3) Canva-Mailchimp gap analysis — 18 Canva AI / AI 2.0 gaps to close (conversational campaign start, connectors, web research, Magic Layers, layered object intelligence, Dream Lab, AI image manipulation, brand intelligence, memory, stickers/GIF, MCP bridge). Every initiative traces to a cited source.
Pillars: 5 (customer-benefit framing) · v1.2
Sub-themes: 20
Initiatives: 74 (incl. 6 Klaviyo countermoves + 3 Builder SLOs)
Page: 1 of 9
+$25–30M
FY27 incremental ARR target this canvas delivers (mid scenario ~$26.3M from Growth Model)
74 initiatives
Tactical, scoped, 3-part-described (IS / problem / benefit). Cover every cited HVC theme + every UR bet + every VoC hate theme
~$95K/mo
Cited HVC MRR exposure addressed (sum of named-customer escalations across NEB, Brand Kit, Canva, Content Studio, SMS — including the $57K SMS TCPA incident)
5 customer pillars
Renamed from internal jargon to customer-benefit framing. Each pillar = "what the customer gets" not "what the team builds"

How this canvas delivers the goal most efficiently

Built around three orchestration moves that each unlock multiple downstream initiatives:

  • Universal Content as a primitive (P2.1) ships first — it closes the Klaviyo Spring 2026 parity claim AND becomes the data primitive that the unified email+SMS canvas (P5.1) reuses, so we don’t build the same thing twice.
  • NEB Code Mode (P2.2) ships before any Classic sunset comms — protects ~$1–2M in Premium/agency churn risk identified in Strategy R1.
  • Write with AI funnel recovery (P4.1) starts policy + product tracks in parallel — addresses the worst single signal in the brief (Explore −73.7% YoY, churn 77.2%) before it compounds.

Then Quality & Trust (P1) burns down cited HVC tickets in weeks not quarters; Activation (P3) repairs the −19.2% Explore funnel; Cross-channel + collab (P5) monetizes the SMS +73.5% growth before its 53% churn eats the gain.

Klaviyo countermoves (v1.1) + Builder SLOs (v1.2) added

After publishing the Klaviyo Brief and Klaviyo VoC tabs, the canvas was extended with 6 Klaviyo countermove initiatives (v1.1) + 3 Builder SLO initiatives (v1.2 — new sub-pillar P1.5, adopted from the Nuni Builder Strategy & Roadmap by Ose Amiegheme, Erin McCue, JB Lovell, Ashley Wiesner). Nothing was removed — every existing initiative still maps to a documented HVC / UR / VoC signal. Klaviyo’s exposures (DTC bias, no co-edit, no multi-brand kits within one account, no Brand-Kit-aware conversational) were already covered by P3.2 / P5.3 / P1.2.3 / P4.2.1 respectively. The Builder SLOs (uptime 99.9%, crash-free 99.5%, P95 load < 500ms, P95 interaction < 300ms, render fidelity ≥ 99%, mobile ≥ 95%, WCAG AA on critical flows) become the operational quality gate that pairs with the cited HVC bug-fix work in P1.1–P1.4.

The 5 pillars at a glance

P1
P1 · 0–3mo · CUSTOMER BENEFIT

"The builder I trust to ship"

Internal name: Editor Quality & Brand Trust
Sub-themes
5
Initiatives
19
FY27 $
$3–5M
NEB rendering & UX bugs · Brand Kit reliability + multi-brand · Content Studio + Canva sync · Creative Assistant rediscovery · Builder SLOs operating contract (Nuni PM)
P2
P2 · 0–9mo · CUSTOMER BENEFIT

"Edit once, send everywhere"

Internal name: Universal Content + Migration
Sub-themes
3
Initiatives
11
FY27 $
$4–7M
Universal Content blocks (Klaviyo parity) · Builder migration + NEB Code Mode + Liquid · Cross-template + cross-flow reuse
P3
P3 · 3–9mo · CUSTOMER BENEFIT

"From signup to first send in minutes"

Internal name: Activation Foundation
Sub-themes
4
Initiatives
13
FY27 $
$4–6M
New-user onboarding + first-send + AI Email Setup Agent · Template ICP fit (B2B / ProServ / non-ecom) · Discovery & feature surfacing · Free-plan recovery + engagement-based pricing counter
P4
P4 · 3–12mo · CUSTOMER BENEFIT

"AI that ships campaigns, not a demo"

Internal name: Intuit Assist + Write with AI Recovery
Sub-themes
4
Initiatives
15
FY27 $
$4–6M
Write with AI funnel recovery (Health critical) · Conversational in-canvas editing · Generative SMS in composer · AI image gen + in-canvas revenue, per-profile Smart Send, AI Performance Watchdog
P5
P5 · 6–18mo · CUSTOMER BENEFIT

"Email + SMS feel like one campaign"

Internal name: Unified Canvas + Collab + SMS Retention
Sub-themes
4
Initiatives
16
FY27 $
$5–8M
Unified email+SMS canvas (B3) + accelerated Push send action · SMS retention + composer depth · Real-time multi-author collab · Governance for SMB + accessibility
Reading the canvas

Each initiative row shows: ID · name + scope · pain $/mo (cited HVC MRR) · lever (L1–L6 from Growth Model) · source tag.

L1 Bulk recovery · L2 Activation+sends · L3 SMS attach+repeat · L4 Reduced abandonment · L5 Retention save · L6 ARPU/outcomes
Source: HVC HVC Risk Map · UR User Research · RMW Roadmap to Win · PH Product Health · VoC Voice of Customer · KLV Klaviyo · SHO Shopify / Stensul · EMG Postscript / Beefree
Pillar 1 · Customer benefit · 0–3 months

P1: "The builder I trust to ship"

Internal name: Editor Quality & Brand Trust. 5 sub-themes, 19 tactical initiatives (incl. 3 Builder SLO operating-contract initiatives in new sub-theme 1.5). Highest velocity, lowest risk pile — most ship in weeks. Burns down cited HVC tickets, addresses bulk churn +2.1pp YoY, and removes the “clunky/outdated” brand-decay signal before any AI demo can land.
Pain $: ~$15K/mo cited (Themes 3–13 selected)
FY27 $: $3–5M ARR (Growth Model L5)
Page: 2 of 9

1.1 NEB rendering & UX bugs

Resolves: ~$3.6K/mo cited + addresses bulk churn +2.1pp YoY · 4 initiatives · Lever L5
ID
Initiative · scope
Pain $/mo
Lever
Source
I-1.1.1
NEB rendering parity fix. Fix forwarded-mail divergence, “read full message” reflow breakage, mobile line-break injection, image-shrink in send.Problem: Customer’s NEB email looks correct in editor, breaks in inbox — loses every recipient’s first impression. Theme 3 in HVC, $1,820/mo cited across 4 named users including a $949/mo Premium account. Benefit: Customer’s send looks the same as the editor; trust restored on the most fundamental promise.
$1,820
L5
HVC #3VoC
I-1.1.2
Multi-author save-conflict UX (precursor to P5 collab). Show explicit “someone else is editing” presence; non-blocking save; merge prompt instead of generic error.Problem: Two team members edit same NEB email → one’s work silently lost; no signal until save fails. Theme 4, $340/mo. Benefit: Teams stop losing work; lays the foundation for full P5 real-time collab without re-architecting later.
$340
L5
HVC #4UR Bet #4
I-1.1.3
Block-ordering & refresh bugs in custom-coded templates + nav “templates moved” banner. Fix block reorder requiring page refresh, vanishing templates link, intermittent “templates moved” warning.Problem: Customer can’t move blocks without refresh; templates link disappears between sessions. Theme 5, $410/mo Premium. Benefit: Editor behaves predictably; no support tickets for “where did my template go?”
$410
L5
HVC #5
I-1.1.4
Template list / campaign wizard surfacing. Fix the bug where new-builder templates don’t appear in the campaign creation tab.Problem: Customer ($1,950/mo) builds a NEB template, opens campaign wizard, sees only legacy templates; their NEB work is invisible. Theme 6. Benefit: Customer can use the templates they built; activation accelerates; perceived broken-state goes away.
$1,950
L4
HVC #6
I-1.1.5
Cross-browser regression suite + automated UI smoke tests. Browser-matrix automated tests (Safari, Firefox, Chrome) on every CI build; regressions caught before release.Problem: Ctrl+K link insertion broken on Firefox/Chrome (Theme 3 sub); customers find browser regressions in production. Cross-cuts every NEB bug. Benefit: Browser regressions caught pre-release; ship velocity goes up because team isn’t firefighting browser bugs.
platform
L5
HVC cross-cut
I-1.1.6
Light/dark mode + background images in NEB. Implement light/dark variant rendering; allow background images on blocks (currently broken).Problem: Customer ($468/mo) needs dark-mode rendering for brand consistency; can’t use background images at all in NEB. Theme 3 sub. Benefit: Modern email design parity; brand consistency across email clients; closes a frequent power-user complaint.
$468
L5
HVC #3 sub
I-1.1.7
Inline link checker + pre-send delivery hints upgrade. Real-time link validation; spam-score guidance; SPF/DKIM/DMARC wizard; alt-text completeness check.Problem: Pre-send checklist catches broken links + missing alt text but misses contrast, link purpose, deliverability red flags. Benefit: Customer sees deliverability issues before send; reduces inbox-placement complaints (Tab 1 mentions 78.35% inbox placement per 2026 audit).
deliverability
L5
VoCRMW F9

1.2 Brand Kit reliability & multi-brand

Resolves: ~$6.5K/mo cited + closes Canva governance threat · 4 initiatives · Lever L5 L6
ID
Initiative · scope
Pain $/mo
Lever
Source
I-1.2.1
Brand Kit data correctness fix (incident closure). Stop serving stale Brand Kit; backfill missing colors; ramp the Austin Milt fix to 100%; add monitoring + alerting for Brand Kit data drift.Problem: Theme 8: customer’s logo present but no colors listed; engineering shipped a 50% ramped fix — some customers still see drift. Benefit: Brand Kit is reliable; customers stop manually patching colors; trust in the “set it once” promise restored.
incident
L5
HVC #8
I-1.2.2
Font upload + Creative Assistant font-recognition parity. Fix two-week font-package upload bug; Creative Assistant must recognize uploaded custom fonts (Asul, Readex Pro, DIN 2014).Problem: Theme 10, $3,350/mo cited including a $3K Premium account. Customer uploads brand font, Brand Kit accepts it, Creative Assistant doesn’t use it — brand consistency breaks at the AI surface. Benefit: Customer’s brand font flows through every AI-generated design; eliminates “why doesn’t the AI use my font?” ticket pattern.
$3,350
L5
HVC #10
I-1.2.3
Logo asset metadata + multi-brand kits. Add “view details” on Brand Kit logos (file name, size, dimensions); allow multiple Brand Kits per account (main brand + sub-brands), Canva-style.Problem: Theme 9, $2,460/mo cited (incl. $1,300 + $410 Premium). Multi-brand teams currently rebuild content per sub-brand because Brand Kit is single-instance. Benefit: Agencies + multi-brand customers manage all brands in one account; closes Canva multi-brand governance gap.
$2,460
L6
HVC #9RMW S10
I-1.2.4
Brand fonts in landing pages + signup forms (iPhone fallback fix). Make uploaded fonts selectable in LP/form builder; fix iPhone system-font fallback so Brand Kit fonts render across devices.Problem: Theme 7, $655/mo. Customer uploads Asul + Readex Pro to Brand Kit, fonts work in email, fall back on iPhone for landing pages — brand inconsistency at the conversion moment. Benefit: Brand Kit applies everywhere it should; customer’s landing pages match their email design.
$655
L5
HVC #7

1.3 Content Studio + Canva integration trust

Resolves: ~$3.1K/mo cited + reduces “third-party in the loop” workflow tax (UR Workflow Shape #4) · 3 initiatives · Lever L5
ID
Initiative · scope
Pain $/mo
Lever
Source
I-1.3.1
Canva ↔ Mailchimp sync reliability. Fix the failure mode where Canva graphic shows in editor but is missing in sent email; add sync-status indicators; fix latency on canvas pulls.Problem: Theme 13, $2,500/mo+ cited. Two named customers ($780, $494, $427) describing “most frustrating thing ever” — including a live email sent without the synced graphic. Benefit: Customer’s Canva work shows up in their sends; eliminates the silent-failure mode that breaks customer trust in both products.
$2,500
L5
HVC #13
I-1.3.2
Content Studio stability + image loading. Fix image-not-loading bugs; eliminate the “quit out and reload” pattern; fix the forced-redirect loop into NEB.Problem: Theme 12, $621/mo. Customer literally describes “Content studio not loading images. Email builder breaking… keep quitting out and re-loading.” Benefit: Customer’s asset library works first time; reduces support escalations.
$621
L5
HVC #12
I-1.3.3
Folder management in Content Studio. Allow folder reordering, folder deletion, search-in-folder; restore IA fundamentals.Problem: Theme 12 sub ($361/mo). Customer can’t reorder or delete folders — basic IA missing. Benefit: Customer organizes assets the way they think; less time hunting for files.
$361
L4
HVC #12 sub

1.4 Creative Assistant rediscovery + expansion

Resolves: $2.65K/mo “bring back” — addresses perceived feature removal · 2 initiatives · Lever L4 L6
ID
Initiative · scope
Pain $/mo
Lever
Source
I-1.4.1
Creative Assistant entry-point restoration + in-product education. Restore prominent CA entry points; add contextual prompts (“design a banner with Creative Assistant”); 30-second in-product video for new users.Problem: Theme 11, $2,650/mo cited (a $1,325 Premium and a $754 user). Customers explicitly ask “Can you bring back the Creative Assistant?” — the feature still exists but discovery collapsed. Benefit: Customers find Creative Assistant again; banner/social workflows return to MC instead of routing through Canva.
$2,650
L4
HVC #11
I-1.4.2
Creative Assistant for non-banner workflows. Expand CA to social variants, in-product imagery, signup-form heroes; multi-asset generation in one prompt.Problem: Customers want CA for more than banners (Theme 11 secondary asks); currently has to use Canva or Adobe Express for adjacent assets. Benefit: Mailchimp keeps the design workflow in-product; reduces dependence on Canva — the same dependence that produces Theme 13 sync failures.
expansion
L6
HVC #11 secondary

1.5 Builder SLOs as Operating Contract NUNI PM TEAM FRAMEWORK

Adopted from Nuni Builder Strategy & Roadmap (Ose Amiegheme, Erin McCue, JB Lovell, Ashley Wiesner). What customers can reasonably expect when they open NEB. Pairs with the cited HVC bug-fix work (P1.1–P1.4) by establishing the operational quality gate for all editor releases. · 3 initiatives · Lever L5
ID
Initiative · scope
Pain $/mo
Lever
Source
I-1.5.1
Builder SLO operating contract. Publish the SLOs that customers can trust when they open NEB: uptime ≥ 99.9% monthly; crash-free sessions ≥ 99.5%; save/publish reliability ≥ 99.99%; initial load P95 < 500ms; interaction latency P95 < 300ms; rendering fidelity ≥ 99% across supported clients; mobile readiness ≥ 95%; accessibility WCAG AA on 100% of critical flows + 95% overall; device support: last 2 versions of Chrome / Edge / Safari / Firefox + iOS / Android; network: full fidelity at ≥ 5 Mbps, degraded but usable down to 1 Mbps with clear in-product messaging.Problem: Cited HVC bugs (NEB rendering, multi-author save, Brand Kit incident, Canva sync) reveal there is no operating contract for editor quality — bugs ship to production and get found by customers. Benefit: Customers know what to expect; engineering knows what to maintain; CSO has a published bar to point at; major NEB changes do not roll out broadly until they are SLO-neutral or better for target cohorts.
contract
L5
NUNI PM
I-1.5.2
Builder SLO instrumentation + monitoring + dashboard. Each SLI is measurable in production; build a shared “Builder Quality” dashboard sliced by browser / device / cohort / market; weekly burn-rate review; SLO breach alerts auto-route to a named owner. Pair with the I-1.1.5 cross-browser regression suite to catch issues pre-release.Problem: Without instrumentation, SLOs are aspirational. Today we discover regressions when customers report them — lagging indicator. Benefit: Proactive detection of slow drifts (not just one-off incidents); engineering can prevent customer-facing degradation; PM sees where SLOs are at risk before publishing changes.
instrumentation
L5
NUNI PM
I-1.5.3
Builder SLO error budgets + escalation + CSO alignment + roadmap policy. Track error budgets for the most critical SLOs (save/publish, crash-free, render fidelity); when a budget is burned or an SLO is breached, named incident owner + clear escalation path + simple CSO/CS brief on what to tell customers; roadmap policy: if we are consistently missing a core SLO for our target ICPs, pause new complexity and redirect capacity to underlying quality work; do not route more customers into NEB from other flows unless we can meet or beat these SLOs for them.Problem: Without error budgets and a roadmap policy, SLOs are decorative — teams ship features even while the floor is slipping. Benefit: Quality compounds because the team has explicit permission (and obligation) to defer feature work when the foundation is at risk; CSO communications are pre-aligned; agency / mid-market customers have a quality contract they can point at.
policy
L5
NUNI PM

P1 evidence base: 7 HVC bug themes (NEB rendering, multi-author save, block ordering, template surfacing, Brand Kit incident, font upload, Canva sync) + 3 HVC barrier themes (multi-brand, folder mgmt, CA rediscovery). VoC hate themes #6 (no universal blocks → partial address via P2) and clunky/outdated narrative addressed via every fix shipped here. Product Health bulk churn +2.1pp YoY is the L5 target this pillar moves. P1.5 Builder SLOs adopted from Nuni Builder Strategy & Roadmap (Ose Amiegheme, Erin McCue, JB Lovell, Ashley Wiesner; reviewed by Eric Anderson) — the operational quality gate that pairs with the cited HVC bug-fix work.

Pillar 2 · Customer benefit · 0–9 months

P2: "Edit once, send everywhere"

Internal name: Universal Content + Migration. 3 sub-themes, 11 tactical initiatives. The single highest-leverage ship in the brief — closes the Klaviyo Spring 2026 parity narrative AND becomes the data primitive that the unified email+SMS canvas (P5.1) reuses. Sequencing: Universal Content first, NEB Code Mode parallel, Classic sunset comms only after both ship.
Pain $: $834/mo cited + ~70K Classic users at risk
FY27 $: $4–7M ARR (Growth Model L1 + L4)
Page: 3 of 9

2.1 Universal Content blocks (the headline ship)

Closes VoC hate theme #6 + Klaviyo Spring 2026 parity claim + UR Bet #1 (saved blocks — PM-confirmed in-flight) · 3 initiatives · Lever L1 L4
ID
Initiative · scope
Pain $/mo
Lever
Source
I-2.1.1
Universal Content block primitive. Edit-once-propagates-everywhere block type that lives at account level; insertable into any template, NEB campaign, or CJB email step; updates flow through to all instances on next send.Problem: Klaviyo Spring 2026 made this the default editor primitive. Mailchimp’s saved-content remains template-scoped; HVC #1 customer with 181 templates literally describes the missing capability: “develop a system where templates share content… similar to your brand kit but more substantial.” Benefit: Customer edits a header / footer / promo banner once; all sends update automatically; massive time-saving + brand consistency.
$330
L1
VoC #6KLV Spring ’26UR Bet #1HVC #1
I-2.1.2
Auto-migration of existing saved blocks → Universal Content. One-click migration tool with preview; bulk migrate template-scoped saved blocks to Universal Content; preserve usage metadata.Problem: Customers have years of saved-content investment scattered per template; manual migration would be a non-starter. Benefit: Existing customers get Universal Content benefit immediately on day 1; doesn’t feel like “start over.”
migration
L4
KLV pattern
I-2.1.3
Universal Content adoption funnel + in-product discovery. Changelog entry; contextual prompt “turn this into Universal Content”; weekly digest of edited blocks + downstream impact (“you updated the header — this affects 12 templates”).Problem: Universal Content only delivers value if customers actually use it; without discovery, the feature ships and adoption stalls. Benefit: Adoption rate hits 50–70% of NEB adopters within 6 months (Strategy Page 2 target); compounds the L1 lever.
adoption
L1
UR Bet #2 (discovery)

2.2 Builder migration & sunset (Strategy B1)

Resolves $834/mo cited HVC + ~70K Classic Established at-risk + protects ~$1–2M ARR per Strategy R1 · 5 initiatives · Lever L4 L5 L6
ID
Initiative · scope
Pain $/mo
Lever
Source
I-2.2.1
Bulk template migration tool (181-template pattern). Multi-select templates; preview side-by-side; bulk migrate to NEB; preserve content + style.Problem: Theme 1, $330/mo cited. Customer with 181 templates: “I want to update them all in one go … I need to individually update them which will take days.” Benefit: Customer migrates years of template work in minutes not days; no “rebuild from scratch” tax.
$330
L4
HVC #1
I-2.2.2
1:1 migration tool with style preservation + support enablement. Single-template migration with style-fidelity guarantee; first-class support workflow (no chat dead-ends); migration-success monitoring.Problem: Theme 2, $504/mo cited. Customer: “two different members of staff regarding converting an email… first ended the chat on me and the second… disappeared after 30 minutes.” Benefit: Migration becomes a reliable process; support has a real path forward; customer trust restored mid-migration.
$504
L4
HVC #2
I-2.2.3
NEB Code Mode + HTML/CSS escape hatch (PRECONDITION FOR SUNSET). Custom HTML / CSS authoring inside NEB; ship before any Classic sunset comms.Problem: VoC #7: “NEB looks pretty… no custom HTML, no Liquid, nothing for power users.” Premium / agency users currently anchor on Classic specifically because of HTML escape hatch — force migration without Code Mode = $1–2M ARR loss per Strategy R1. Benefit: Power users get NEB without giving up control; safe to retire Classic; preserves the Premium ARR base.
unlock
L4
VoC #7RMW F5
I-2.2.4
NEB Liquid templating for power users + dynamic content. Add Liquid (or Handlebars) templating in Code Mode; per-recipient dynamic blocks (name, location, last product, last engagement).Problem: RMW F8 (per-recipient dynamic content) and S11 (Liquid) gaps vs Klaviyo. Today personalization = merge tags + conditional show/hide; nothing first-class. Benefit: Power users + agencies can build truly personalized campaigns inside NEB; closes the “not for power users” objection.
power-user
L6
RMW F8 + S11
I-2.2.5
Funded migration program + 12-month grace period. 1:1 migration assistance for Premium / agency Classic users; 12mo grace period after Classic sunset announcement; in-product migration tracker.Problem: Strategy R1: ~70K assumed Classic Established users (not directly observable in BQ — Eng to instrument); even 10% churn = $1–2M ARR loss. Benefit: Migration is a positive event for HVCs (assisted, no surprises); Classic sunset becomes safe to announce.
structural
L5
PH NEB/ClassicVoC

2.3 Cross-template + cross-flow content reuse

Extends Universal Content into Customer Journey Builder + Brand Kit propagation + audit · 3 initiatives · Lever L3 L5
ID
Initiative · scope
Pain $/mo
Lever
Source
I-2.3.1
Universal Content blocks render in Customer Journey Builder. Same Universal Content primitive available inside CJB email steps; cross-product reuse.Problem: Today saved-content is template-scoped; CJB emails can’t reuse them; double-maintenance across campaigns + automations. Benefit: Customer’s automation emails inherit the same brand updates as campaigns; no drift between channels.
cross-product
L3
UR Bianka (one view)
I-2.3.2
Brand Kit auto-applied to Universal blocks at insertion. When customer inserts a Universal block, Brand Kit colors / fonts / logos auto-apply; no manual restyling.Problem: Without auto-apply, customers manually restyle each block insertion — defeats the “edit once” promise. Benefit: Brand consistency at zero effort; compounds Brand Kit value (P1.2) into every Universal Content adoption.
consistency
L5
VoC Brand Kit
I-2.3.3
Universal Content audit + version history. Show “used in N templates / N journeys”; version history + rollback; impact preview before edit (“this change affects 17 active sends”).Problem: Universal Content is powerful and dangerous — one wrong edit propagates to many sends. Without governance, customers will be afraid to use it. Benefit: Customer edits with confidence; audit trail for agencies / multi-author teams; reduces “I broke production” anxiety.
governance
L5
UR Bet #4 (multi-author)

P2 evidence base: VoC hate themes #1 (bifurcation), #6 (no universal blocks), #7 (no HTML escape). HVC Themes 1, 2 (migration). UR Bet #1 (saved blocks) PM-confirmed in-flight. Strategy R1 (Classic churn risk). RMW F2 (builder unification), F5 (HTML escape), F8 (dynamic content), S11 (Liquid). Klaviyo Spring 2026 Universal Content announcement.

Pillar 3 · Customer benefit · 3–9 months

P3: "From signup to first send in minutes"

Internal name: Activation Foundation. 4 sub-themes, 13 tactical initiatives (incl. 2 Klaviyo countermoves: AI Email Setup Agent + engagement-based pricing position). Repairs the bulk Explore funnel (−19.2% YoY) and the <12mo cohort (−22.8% YoY). Closes UR Bet #2 (discovery) and Bet #3 (B2B/ProServ template gap). Free-plan fixes are the largest single acquisition unlock.
Pain $: Health Free −19.2% (74K Established lost); Explore −19.2%
FY27 $: $4–6M ARR (Growth Model L1 + L2)
Page: 4 of 9

3.1 New-user onboarding & first-send

Repairs <12mo cohort −22.8% YoY + closes UR Discovery gap + closes Klaviyo Marketing-Agent gap · 4 initiatives · Lever L1 L2
ID
Initiative · scope
Pain $/mo
Lever
Source
I-3.1.1
Day-0 → Day-1 first-send onboarding sequence. In-app + email nudges that walk the user to their first send within 7–10 days (vs current 14–21d median per User Research).Problem: First-month adoption falling (<1mo cohort −17.5%); UR Bet #2: 5 customers with years-long feature discovery gaps. Time-to-first-send is too far away — new customers never reach value moment. Benefit: Customer experiences value within their first week; activation funnel repair compounds with bulk Establish recovery in Growth Model L1.
activation
L2
UR Bet #2PH <1mo −17.5%
I-3.1.2
Brand Kit auto-extract on signup; first email pre-branded. On signup, prompt for website URL; auto-extract logo / colors / fonts into Brand Kit; first send template pre-applied with their brand.Problem: Today customer signs up, gets generic templates, has to manually restyle — cognitive cost too high before value is proved. Benefit: Customer’s first email looks on-brand; activation rate goes up; reinforces “this product gets me” on day 1.
activation
L2
VoC Brand Kit love
I-3.1.3
Industry-specific welcome flow templates pre-loaded by business type. Onboarding asks “what kind of business?”; pre-loads 3–5 templates tailored to that industry; one-click activate.Problem: UR Workflow Shape #1 (fast Monday-morning sender) — customers want to ship same-day; generic templates slow them down. Benefit: First send out the door in <30 min for industry-fit customers; matches the “Andrew/Andrea/Kim/Clint” happy-path UR pattern.
activation
L2
UR Workflow #1
I-3.1.4
AI Email Setup Agent — URL → scaffolded campaign in 3 clicks KLAVIYO COUNTER Mirror Klaviyo’s Marketing Agent for the editor side. Customer pastes website URL; Intuit Assist scaffolds first newsletter / promo / welcome campaign with Brand Kit auto-applied + ICP-fit template selected.Problem: Klaviyo Marketing Agent (Spring ’25 GA) sets up flows in ~3 clicks; Mailchimp has no autonomous setup agent for the editor. New customers describe Mailchimp as “more powerful but slower to first value.” Benefit: Customer’s first campaign is live before they finish onboarding; matches Klaviyo’s URL-to-campaign speed; reframes Mailchimp’s editor breadth as “the AI uses all 260+ templates and our Brand Kit, not a generic LLM.”
competitive
L1
KLV Marketing AgentVoC clunky

3.2 Template ICP fit (B2B / ProServ / non-ecom)

Closes UR Bet #3 (B2B / ProServ skeleton template gap) · 3 initiatives · Lever L2
ID
Initiative · scope
Pain $/mo
Lever
Source
I-3.2.1
B2B / ProServ template gallery — skeleton layouts. Information-dense templates (text-first, charts, structured layouts) instead of mock e-commerce shells.Problem: UR Bet #3 + Hannah / Chris Rich quote: “many… not tailored towards your organization.” Jillian: “feel more like e-commerce emails.” B2B / ProServ customers can’t find a starting template that matches their work. Benefit: Non-ecom customer activation matches ecom customer activation; opens a previously-underserved segment.
B2B/ProServ
L2
UR Bet #3
I-3.2.2
Industry-aware template gallery (6–8 per industry). Pre-built templates tailored to: ecom, ProServ, services, B2B SaaS, restaurants, nonprofits. Tied to onboarding business-type selection.Problem: Single generic template gallery serves all industries badly. Klaviyo has 60+ templates segmented by vertical + lifecycle. Benefit: Customer sees templates that look like THEIR business; activation faster across all verticals.
vertical
L2
UR Bet #3KLV 60+ templates
I-3.2.3
Template categorization fix (browse by layout). Add layout-only browse mode; better filter / search; tag templates with use case + layout type.Problem: UR Wes Turner ignores category IA, browses layout-only; current filter doesn’t support that. Benefit: Customers find templates the way they actually browse; less hunting, faster activation.
UX
L2
UR Wes

3.3 Discovery & feature surfacing

Closes UR Discovery table (5 customers with years-long undiscovered features) · 3 initiatives · Lever L3 L4
ID
Initiative · scope
Pain $/mo
Lever
Source
I-3.3.1
In-app changelog + “what’s new” weekly digest. Sidebar “what’s new in editor” digest; per-feature 30-second videos in-product; weekly email summary tailored to customer’s usage patterns.Problem: UR Discovery table: Bianka didn’t find A/B testing for “a number of years”; Jack on inherited template missed NEB for 4–6 years. Help docs unread; reactive nudges don’t translate. Benefit: Customer discovers powerful features they didn’t know existed; capability utilization rises; reduces silent-churn from “I’m not getting enough value.”
discovery
L3
UR Discovery
I-3.3.2
Contextual feature discovery prompts. “You’ve used X, try Y” prompts; surface adjacent capabilities at the moment of intent (e.g., after sending a campaign, “turn this into an automation?”).Problem: Mailchimp ships features that customers never find because there’s no contextual hand-off from current behavior to next-best capability. Benefit: Capability utilization compounds; customer gets more value per session.
discovery
L3
UR Bet #2
I-3.3.3
DRAFT-resurrect campaign + proactive chatbot suggestions. “Your welcome flow has been in DRAFT for X days” nudge with one-click activate. Proactive chatbot suggestions for low-frequency users (Clint / Bianka pattern).Problem: UR Clint Bartley quote: “I just haven’t gotten deep enough into it yet” — welcome automation in DRAFT for over a year. Self-blame, declining trust. Benefit: Customer’s “I’ll do it later” intentions actually execute; reduces silent churn from low-frequency users.
recovery
L4
UR Clint

3.4 Free plan recovery

Repairs Health Free −19.2% YoY + counters Klaviyo Feb ’25 active-profile billing damage · 3 initiatives · Lever L1 L5 L6
ID
Initiative · scope
Pain $/mo
Lever
Source
I-3.4.1
Free-tier editor experience uplift. Add more block types to Free; basic Brand Kit; basic Creative Assistant. Match Shopify’s “automation bundled with storefront” competitive wedge for SMB acquisition.Problem: PH Free Established −19.2% YoY (~74K users lost). Shopify gives editor + automation free with storefront; Mailchimp Free editor experience is deliberately degraded. SMB customers acquire elsewhere. Benefit: SMB customers get day-1 editor value before paywall; converts more Free → Paid as customers grow; reverses biggest single segment loss in the brief.
acquisition
L1
PH Free −19.2%SHO bundling
I-3.4.2
Free → Essentials upgrade path improvements. Clear value-tier visualization (“you’re using 80% of Free, here’s what Essentials adds for the editor”); contextual upgrade prompts at limit-hit moments.Problem: Free customers don’t convert because the upgrade story is opaque; they hit limits and bounce. Benefit: Free → Paid conversion rate goes up; Standard tier (the one growing +9.1%) gets a feeder funnel.
conversion
L6
PH Standard +9.1%
I-3.4.3
Engagement-based / usage-based pricing alternative KLAVIYO COUNTER Position usage-based (per-send) or engagement-based (per-active-profile excluding unsubscribed/cleaned) pricing as an explicit alternative; pair the messaging with the Free-tier editor uplift (I-3.4.1) for the Q4 brand-decay reversal moment.Problem: Klaviyo’s Feb 2025 active-profile billing change (charging for unsubscribed / cleaned profiles) drew the largest single billing-related backlash in Klaviyo’s history; SMB customers are looking for relief. Mailchimp has no explicit counter-position. Benefit: SMB acquisition wedge; the Klaviyo → Mailchimp pricing migration story becomes a sales asset; pairs naturally with Free-tier uplift to reopen the SMB acquisition funnel.
positioning
L1
KLV Feb ’25 billingVoC pricing

P3 evidence base: Product Health: Free −19.2% (largest segment loss), <12mo cohort −22.8%, <1mo −17.5%, Standard +9.1% (only growing tier needs Free feeder). User Research: Bets #2 (discovery), #3 (B2B / ProServ templates), #5 (direct manipulation upgrades). Discovery table (Bianka A/B years, Jack NEB 4–6 yrs, Jeffrey 3.5 yrs, Clint 1 yr DRAFT). Workflow Shape #1 (fast Monday-morning) + #5 (low-frequency / discovery gap). Klaviyo countermoves: Klaviyo Brief Marketing Agent gap (I-3.1.4) + Klaviyo VoC Feb ’25 active-profile billing damage (I-3.4.3).

Pillar 4 · Customer benefit · 3–12 months

P4: "AI that ships campaigns, not a demo"

Internal name: Intuit Assist + Write with AI Recovery. 4 sub-themes, 15 tactical initiatives (incl. 3 Klaviyo countermoves: in-canvas revenue, per-profile Smart Send, AI Performance Watchdog). Crisis pillar — Write with AI Explore funnel collapsed −73.7% YoY and churn worst-in-family at 77.2%. Run policy track (geo-ungate) + product track (quality + brand-aware + conversational) in parallel. Closes Strategy Bet B4. Differentiator: Brand-Kit-aware conversational editing (no comp ships this combination).
Pain $: Health Write with AI Explore −73.7%, churn 77.2% (+15.4pp)
FY27 $: $4–6M ARR (Growth Model L2 + L6 + recovery)
Page: 5 of 9

4.1 Write with AI funnel recovery (CRITICAL)

Addresses the worst signal in the brief: Explore −73.7% YoY, Abandon +101%, churn 77.2% (+15.4pp) · 4 initiatives · Lever L1 L4 L5 L6
ID
Initiative · scope
Pain $/mo
Lever
Source
I-4.1.1
Write with AI global ungate (or paid AI add-on with global parity). Run policy + legal track in parallel to product track; two-path delivery: (a) global free-tier ungate if policy clears, (b) paid AI add-on globally as fallback. Either ships in FY27.Problem: VoC #3 + Reddit Netherlands quote: “I am told Write with AI is in beta in the US, UK, AU, CA. I am in the Netherlands. I get to pay for AI I cannot use.” PH Write with AI Explore −73.7% YoY (collapse) — geo-gate is a major contributor. Benefit: International Standard customers get the AI they pay for; reverses brand damage in EMEA / APAC; reopens Explore funnel.
brand
L1
VoC #3PH Explore −73.7%
I-4.1.2
Write with AI quality + brand-tone improvements. Address output quality vs ChatGPT / Claude direct usage; deeper Brand Kit integration (voice, tone, audience-aware); user-feedback loop into model fine-tuning.Problem: Health critic Page 3: “AI honeymoon ended” — quality issues plausibly contribute to the funnel collapse. Customers tried it, didn’t come back. Benefit: Returning users get notably better output; word-of-mouth recovers; lifts L5 retention save on the AI cohort.
quality
L5
PH critic
I-4.1.3
In-product Write with AI re-introduction campaign. Post-quality-fix: targeted in-app + email re-engagement to abandoned AI users; before/after demo of the new output quality.Problem: 106K Abandon users on Write with AI (PH) — an enormous reactivation pool. Without active outreach, they assume nothing changed. Benefit: Abandon → Establish recovery on the AI cohort; lifts L4 reduced abandonment lever.
recovery
L4
PH AI Abandon 106K
I-4.1.4
Write with AI Explore funnel re-instrumentation. In-canvas discovery (“try Write with AI on this paragraph”); contextual prompts at blank-page moments; entry points on every email/SMS compose surface.Problem: Explore −73.7% YoY suggests not just policy but also discovery has failed; in-canvas surfacing is weak. Benefit: New users encounter AI assistance at the moment of need; rebuilds the Explore funnel.
funnel
L2
PH Explore funnel

4.2 Conversational in-canvas editing

Strategy B4 differentiator — no competitor ships Brand-Kit-aware conversational edits · 3 initiatives · Lever L2 L6
ID
Initiative · scope
Pain $/mo
Lever
Source
I-4.2.1
Conversational journey editing in Intuit Assist sidebar. “Redo the hero in a friendlier tone with a CTA to the spring sale”; voice + chat email-and-SMS commands; built into Intuit Assist sidebar with Brand Kit context.Problem: Klaviyo AI is feature-bound (subject lines, image edit). Postscript trains AI on docs but doesn’t do canvas-level conversational edits. Stensul’s AI is form-driven. No comp ships Brand-Kit-aware conversational. Benefit: Customer modifies emails by typing in plain English; flagship demo capability; captures the “Mailchimp is back, modern” narrative.
flagship
L2
RMW S1
I-4.2.2
AI brand-style transfer between campaigns. “Make this email look like our spring campaign style”; turn one campaign’s stylistic choices into a reusable brand-style object that another campaign can inherit.Problem: No competitor ships this. Natural evolution of Brand Kit + Creative Assistant. Benefit: Customer’s campaign series feels intentionally connected without manual restyling; differentiator vs Klaviyo / Postscript.
leapfrog
L6
RMW S2
I-4.2.3
Prompt-first email mode (toggle). Optional “prompt mode” where the email builder UX itself is conversational — describe entire email in plain English, builder generates structure + copy + design.Problem: Mailmodo’s prompt-first whole-product UX is winning younger SMB. Mailchimp’s visual canvas is great for some users, intimidating for others. Benefit: Customer who doesn’t think visually can build emails in seconds via prose; opens a new persona segment.
leapfrog
L2
EMG Mailmodo

4.3 Generative SMS in composer

Activates SMS +73.5% adoption with retention infrastructure (current 53% churn) · 2 initiatives · Lever L3 L2
ID
Initiative · scope
Pain $/mo
Lever
Source
I-4.3.1
Brand-Kit-aware generative SMS in composer. Character-limit-compressing, brand-tone-aware, opt-out-compliance-automatic SMS generation. Write with AI + Brand Kit + SMS composer all live in one product — need integration not new infra.Problem: RMW S5: Postscript trains AI on docs; Attentive does AI campaign suggestions; nobody ships Brand-Kit-aware SMS gen inside the composer with character-limit auto-compression. Benefit: SMS adoption keeps growing (PH +73.5%); on-brand output reduces re-write cycles; eliminates blank-page anxiety on SMS.
SMS adopt
L3
RMW S5PH SMS +73.5%
I-4.3.2
SMS variant generation + A/B in composer. Generate multiple SMS variants from one prompt; in-composer A/B with character-limit + Brand Kit awareness.Problem: SMS composer today has no A/B in composer; manual variant creation slows iteration. Benefit: Customer ships better-performing SMS without leaving the composer; iteration cycle compresses.
SMS optimize
L2
RMW

4.4 AI image generation tied to product catalog

Differentiator combining Brand Kit + 300+ ecom integrations + Creative Assistant + Klaviyo countermove trio (revenue / Smart Send / Watchdog) · 6 initiatives · Lever L5 L6
ID
Initiative · scope
Pain $/mo
Lever
Source
I-4.4.1
AI image generation tied to product catalog. Generate hero images from the product the email is about; brand-kit-applied scene; Brand Kit + ecom integration + Creative Assistant in one workflow.Problem: RMW S8. Generic image generation exists everywhere; tied to this customer’s product catalog with this product’s brand-kit-applied scene is unique to Mailchimp’s asset combination. Benefit: Right image not stock image; ecom customer lift on conversion; no other SMB tool can match.
leapfrog
L6
RMW S8
I-4.4.2
Image Remix in flow email steps (Klaviyo parity). Drag-in dynamic image blocks that auto-vary; iterate hero images via prompt inside flow / campaign.Problem: Klaviyo Image Remix lets customers iterate hero images via prompt; Mailchimp lacks this entirely. Benefit: Customer iterates designs in seconds; closes a named Klaviyo gap.
competitive
L6
KLV Image Remix
I-4.4.3
Per-recipient dynamic image (last product viewed, etc.). Image blocks that personalize per recipient (last product viewed, last category, predicted next product).Problem: RMW F8 dynamic content gap; Klaviyo + Bloomreach + Movable Ink set the bar. Benefit: Customer’s automation emails personalize at the image level; conversion lift on browse / cart / post-purchase flows.
personalize
L6
RMW F8KLV product recs
I-4.4.4
In-canvas revenue per recipient + per step (Klaviyo parity) KLAVIYO COUNTER Show revenue / opens / clicks / conversion inline at each block in the post-send report; revenue-per-recipient view; per-block performance breakdown.Problem: Klaviyo VoC: “In-builder revenue metrics” +56 net sentiment — renewal conversation moves from “opens” to “$ shipped.” Mailchimp’s editor reports don’t expose per-block / per-recipient revenue. Benefit: Customer proves email + SMS ROI inline; finance + renewal conversations move to value not vanity; matches Klaviyo’s decision-grade reporting.
competitive
L5
KLV in-builder revKLV VoC +56
I-4.4.5
Per-profile Smart Send Time + Personalized A/B in send config KLAVIYO COUNTER Add per-profile send-time optimization; A/B winner picked per profile (not one global winner); Channel Affinity per profile in cross-channel campaigns. Available in editor send config + cross-channel campaigns from P5.1.Problem: Klaviyo has all three productized (+10–30% lift cited per Klaviyo case studies); Mailchimp has store-level send-time only and one-size-fits-all A/B winners. Benefit: Customer’s sends ship at the per-recipient optimal time; A/B optimizes per profile not in aggregate; closes a named Klaviyo gap.
competitive
L5
KLV Smart Send + Personalized A/B
I-4.4.6
AI Performance Watchdog — proactive send-performance alerts KLAVIYO COUNTER AI auto-monitors send performance (open rate, CTR, unsub rate, deliverability) vs baseline; in-app alert when metrics degrade; suggested fixes in canvas (e.g. “your unsub rate is up 30% — review last 3 sends”).Problem: Klaviyo VoC: AI auto-monitors are praised. Mailchimp has no equivalent; customers find performance regressions only when they pull a manual report. Benefit: Customer gets alerted before performance dies; reduces silent churn (customer doesn’t leave because something silently broke); pairs with the cited HVC bug-fix work in P1.
competitive
L5
KLV AI auto-monitors

P4 evidence base: Product Health Write with AI: Established −3.8%, Explore −73.7% YoY, Abandon +101%, churn 77.2% (+15.4pp). VoC #3 (geo-gate). Strategy Bet B4 + R3 (policy uncertainty). RMW S1 (conversational), S2 (brand-style transfer), S5 (Generative SMS), S8 (product-catalog AI image), F8 (per-recipient dynamic). Klaviyo Image Remix, Mailmodo prompt-first. Klaviyo countermoves (3): Klaviyo Brief in-builder revenue metrics + Smart Send + Personalized A/B + AI auto-monitors gaps (I-4.4.4 / I-4.4.5 / I-4.4.6).

Pillar 5 · Customer benefit · 6–18 months

P5: "Email + SMS feel like one campaign"

Internal name: Unified Canvas + Collab + SMS Retention. 4 sub-themes, 16 tactical initiatives (incl. 1 Klaviyo countermove: accelerated Push notification send action). Strategy Bet B3 (unified canvas) + B5 (collab). Monetizes the SMS +73.5% growth before the 53% churn eats it. Closes VoC #2 (“unified is a billing claim”) and VoC #5 (no real-time collab). Includes the $57K SMS TCPA incident fix — the largest single cited HVC in the brief.
Pain $: $62.5K/mo cited (incl. $57K SMS TCPA) + Health SMS 53% churn
FY27 $: $5–8M ARR (Growth Model L3 + L5 + L6)
Page: 6 of 9

5.1 Unified email + SMS canvas (Strategy B3)

Closes VoC #2 (biggest “unified is a billing claim” complaint) + reuses Universal Content primitive (P2.1) + accelerates Push from FY28 to FY27 Q5 · 5 initiatives · Lever L3 L5 L6
ID
Initiative · scope
Pain $/mo
Lever
Source
I-5.1.1
Shared content blocks render in both email + SMS. Universal Content primitive (P2.1) extends to SMS; same block edited once renders correctly in both channels with content-type-aware rendering (full HTML in email, compressed text in SMS).Problem: VoC #2 + UR Bianka (one campaign view): “Despite the ‘email + SMS together’ marketing, the SMS composer is a different surface from the email editor. No shared content blocks, no shared preview, no cross-channel content reuse. ‘Unified’ is a billing claim.” Benefit: Customer composes once, ships everywhere; eliminates duplicated authoring work; fulfills the unified marketing promise.
unified
L3
VoC #2UR Bianka
I-5.1.2
Cross-channel preview side-by-side at compose time. Real-time email + SMS preview in one canvas; see how copy reads in both formats simultaneously.Problem: Today customer composes email, switches to SMS composer, copy-pastes, reformats, previews separately. Benefit: Customer iterates on cross-channel campaigns in one motion; faster ship time; fewer mistakes between channels.
UX
L3
RMW S3
I-5.1.3
Brand Kit applied to SMS branded short links + sender ID. Brand Kit colors / logo applied to branded SMS short links (Standard+); sender ID consistent with brand.Problem: Today branded short links exist but don’t inherit Brand Kit; sender ID is separate config. Benefit: SMS sends are visibly branded; customer’s SMS feels like an extension of their email design; trust + click-through go up.
brand
L5
VoC unified
I-5.1.4
Unified “campaign” object (email step + SMS step in one campaign). One logical campaign owns both email + SMS sends; reporting consolidates; audience selection unified.Problem: Today email and SMS are separate objects with separate audience selection + reporting; cross-channel attribution is impossible. Benefit: Customer sees unified campaign performance; cross-channel attribution finally works; LTV story holds together.
attribution
L3
UR Bianka
I-5.1.5
Push notification send action in NEB canvas (acceleration) KLAVIYO COUNTER Add Push (mobile + web) as a flow + campaign send action; bring forward from FY28 (per Strategy) to Q5 FY27. WhatsApp + In-app + RCS remain deferred; Push is technically simpler and closes part of the 5-channel narrative gap.Problem: Klaviyo’s 5-channel canvas (Email + SMS + Push + WhatsApp + In-app) is the headline omnichannel story; Mailchimp at 2 channels (Email + SMS) cedes the omnichannel narrative through FY28. Benefit: Closes part of the omnichannel gap with Klaviyo while keeping engineering scope manageable; SMS attach customers (P5.2) get a low-cost upsell to Push; positions Mailchimp as “catching up” not “ceding the channel.”
competitive
L3
KLV 5-channel canvas

5.2 SMS retention + composer depth

Resolves $62.5K/mo cited HVC (incl. $57K TCPA) + addresses Health SMS 53% churn · 5 initiatives · Lever L3 L4 L5 L6
ID
Initiative · scope
Pain $/mo
Lever
Source
I-5.2.1
SMS reporting v2 (in-app analytics + per-message data). Fix empty / N/A stats; in-app SMS reporting (currently “hard to find… feels tacked on”); per-message delivery + opt-out + click data.Problem: Theme 14, $1,386/mo cited. Customer: “SMS reporting is showing 0% and N/A for stats, what is the point of reporting if it doesn’t show data.” Drives churn on the highest-growth product. Benefit: Customer can prove SMS ROI; renewal conversation easier; SMS retention improves directly.
$1,386
L5
HVC #14
I-5.2.2
SMS credits transparency + auto-refund undelivered + queue alerts. Surface negative balances in UI (not just via support); auto-refund undelivered SMS credits; in-app alert when automation stalls due to credit shortage.Problem: Theme 15, $3,592/mo cited across 3 customers. Negative credit balances hidden; undelivered SMS still burn credits; automations stall silently. Benefit: Customer trusts the credit system; automations don’t silently break; reduces “Mailchimp ripped me off” brand damage.
$3,592
L5
HVC #15
I-5.2.3
SMS compliance & TCPA guardrails ($57K incident fix). Duplicate opt-out prevention; in-product policy explainer; global setting for compliance append; infer prior campaign for compliance text.Problem: Theme 16, $57,000/mo (largest single SMS escalation). C3 Festivals incident: default-on append + pasted compliance → duplicate opt-out in live send (Darker Waves). P2 escalation. Benefit: Customer cannot accidentally send TCPA-violating messages; eliminates the largest single brand-risk vector in the SMS product.
$57,000
L5
HVC #16
I-5.2.4
SMS merge tag depth + MMS POC GA. Lift the “up to one merge tag for Title” cap; MMS POC (contact cards / image attachments) launched.Problem: Theme 17. SMS-9736 backlog: only one merge tag for Title. MMS POC not fully launched. SMS feels less personalized than email. Benefit: SMS message-personalization parity with email; MMS unlocks higher engagement; closes a basic-feature gap.
depth
L3
HVC #17
I-5.2.5
MMS bundle pricing (no overage surprises). MMS included in Standard SMS pricing; flat-rate SMB pitch vs Postscript’s opaque per-message MMS economics.Problem: RMW S7 + Strategy B3 lever. Postscript MMS pricing is opaque + per-message expensive; Attentive bills enterprise. Benefit: Customer adopts MMS without overage anxiety; SMS attach rate (Strategy target 12% → 20–25%) accelerates; SMS retention improves because customers aren’t surprised by bills.
attach
L6
RMW S7

5.3 Real-time multi-author collab + commenting (Strategy B5)

Closes VoC #5 + UR Bet #4 (Jack / Kyle / Bianka) + extends HVC #4 (save conflicts) into a productized capability · 3 initiatives · Lever L5 L6
ID
Initiative · scope
Pain $/mo
Lever
Source
I-5.3.1
Real-time multi-author co-edit in NEB canvas. Google-Docs-style live cursors; presence indicators; non-blocking concurrent edit.Problem: VoC #5 + UR Bet #4 (Jack / Kyle / Bianka): single editor at a time; teams workaround via screenshots + shared drafts; competitor parity gap (Stensul, Knak ship this). HVC #4 save conflicts are the bug-level expression of the same gap. Benefit: Marketing teams of 2+ work together natively in MC; recovers “Mailchimp is dated” narrative; differentiator vs Klaviyo (single editor).
strategic
L6
VoC #5UR Bet #4
I-5.3.2
Notion-style block-level @-mention comments + resolve-in-context. Comment on any block; @-mention teammates; resolve in context.Problem: RMW S9: Stensul has commenting bolted on. Notion / Figma / Google Docs have set the bar. Mailchimp has nothing. Benefit: Approval cycles happen inside MC; reduces email + Slack ping-pong about email design; team velocity up.
strategic
L6
RMW S9
I-5.3.3
Email approval workflow + version history. Multi-step approval (designer → copywriter → manager); full version history with rollback; audit trail.Problem: Marketing teams of 2+ need approval flow; today this happens outside MC. Premium / agency need audit trail for governance. Benefit: Premium customer’s governance needs met in-product; agencies retain clients longer; opens enterprise-adjacent SMB segment.
governance
L6
RMW S4

5.4 Governance for SMB + accessibility

Differentiated steal vs Stensul/Knak (SMB-flavored governance) + EU EAA accessibility compliance accelerator · 3 initiatives · Lever L5 L6
ID
Initiative · scope
Pain $/mo
Lever
Source
I-5.4.1
Locked layouts mode for Brand Kit (governance hooks). Promote Brand Kit from config object to system: locked layouts, role-based access, blocking accessibility checks on send.Problem: RMW S4: Stensul / Knak own enterprise governance; nobody has shipped governance with the SMB UX. Brand Kit infrastructure already exists; needs governance hooks. Benefit: Multi-author teams + agencies can lock brand integrity at scale; SMB-flavored governance product opens new segment.
governance
L6
RMW S4
I-5.4.2
Inline accessibility coach (alt text, contrast, link purpose). Real-time accessibility checks in canvas; pre-send blocking on critical violations; coach mode for education.Problem: RMW F9 + EU EAA accessibility compliance schedule. Pre-send checklist catches missing alt + broken links; doesn’t catch contrast / heading order / link purpose. Benefit: Customer’s sends are accessible; deliverability improves (modern inbox providers reward accessible HTML); regulatory readiness for EAA.
compliance
L5
RMW F9
I-5.4.3
Cross-account brand inheritance for agencies. One Brand Kit per client; switch context like Slack workspaces; shared Universal Content library across agency clients.Problem: RMW S10. Mailchimp Agency dashboard exists but Brand Kit is per-account; agencies rebuild assets per client. Benefit: Agency efficiency goes up; agency churn goes down; competitive vs Klaviyo One agency tier.
agency
L6
RMW S10

P5 evidence base: VoC #2 (surface split) + #5 (no collab). HVC Themes 4 (multi-author save), 14 (SMS reporting), 15 (SMS credits), 16 (TCPA $57K), 17 (SMS depth). UR Bet #4 (multi-author) + Bianka (one campaign view). Product Health SMS Establish +73.5% / churn 52.9%. Strategy Bets B3 + B5. RMW S3, S4, S7, S9, S10, F9. Klaviyo countermove (1): Klaviyo Brief 5-channel canvas gap → accelerated Push send action (I-5.1.5).

Coverage Matrix · Methodology · Sources

How this canvas was independently designed + coverage proof

Built top-down from documented evidence. Every cited HVC theme, every UR bet, every VoC hate theme, every Product Health finding, and every Growth Model lever maps to at least one initiative.
Initiatives: 74 (incl. 6 Klaviyo countermoves + 3 Builder SLOs)
Sources mapped: 6 evidence tabs + Growth Model + Loss Attribution + Klaviyo Brief + Klaviyo VoC + Nuni PM framework
Page: 7 of 9

7.1 Coverage matrix — every documented signal → an initiative

Evidence sourceWhat it documentedCoverage in this canvas
Voice of Customer7 hate themes (bifurcation, surface split, AI geo-gate, paywall, no collab, no universal blocks, no custom code) + 5 mixed (CA upsell, NEB transition, Klaviyo migration, Stensul governance, SMS narrowness)100% of hate themes covered (7/7). Bifurcation → P2.2; Surface split → P5.1; AI geo-gate → I-4.1.1; Paywall → partially via P3.4 Free uplift; No collab → P5.3; No universal blocks → P2.1; No custom code → I-2.2.3 NEB Code Mode.
HVC Risk Map17 cited themes across NEB rendering, multi-author, custom code, templates, Brand Kit, Content Studio, Canva, SMS reporting, SMS credits, TCPA incident, SMS depth ($57K largest single)~95% covered. Themes 1-2 (migration) → P2.2; Theme 3 (rendering) → I-1.1.1; Theme 4 (multi-author) → I-1.1.2 + P5.3; Theme 5 (block ordering) → I-1.1.3; Theme 6 (templates) → I-1.1.4; Theme 7 (LP fonts) → I-1.2.4; Theme 8 (Brand Kit incident) → I-1.2.1; Theme 9 (multi-brand) → I-1.2.3; Theme 10 (font upload) → I-1.2.2; Theme 11 (CA rediscovery) → P1.4; Theme 12 (Content Studio) → I-1.3.2 + I-1.3.3; Theme 13 (Canva) → I-1.3.1; Theme 14 (SMS reporting) → I-5.2.1; Theme 15 (SMS credits) → I-5.2.2; Theme 16 (TCPA $57K) → I-5.2.3; Theme 17 (SMS depth) → I-5.2.4.
User Research5 Bets + Discovery table (5 multi-year gaps) + 5 Workflow Shapes + 25 customer briefs / 50 videos100% of bets covered (5/5). Bet #1 saved blocks → P2.1; Bet #2 discovery → P3.3; Bet #3 B2B/ProServ templates → P3.2; Bet #4 multi-author → I-1.1.2 + P5.3; Bet #5 direct manipulation → addressed across P1 bug fixes. Discovery table customers → I-3.3.1-3.
Product HealthBulk Established −9.4% / Explore −19.2% / churn +2.1pp; Free −19.2%; <12mo −22.8%; SMS +73.5% / churn 52.9%; Write with AI Established −3.8% / Explore −73.7% / churn 77.2% (+15.4pp); Transactional −10.5%100% covered. Bulk Establish → P2 + P3 net of L1 lever. Bulk churn +2.1pp → P1 (entire pillar). Explore −19.2% → P3.1 + P3.4. Free −19.2% → P3.4. <12mo −22.8% → P3.1. SMS growth → P5.2 retention + P4.3 generative SMS. Write with AI collapse → P4.1 (entire sub-pillar). Transactional out of scope (deferred per Strategy — not in B1–B5).
Growth Model6 levers L1–L6, mid scenario ~$26.3M, sensitivity $19.7–32.7M, 12 adoption metrics across 4 clustersAll 6 levers actively pursued. L1 (bulk recovery) → P2 + P3.4. L2 (activation) → P3.1 + P4.2. L3 (SMS attach + repeat) → P5.1 + P5.2 + P4.3. L4 (reduced abandonment) → P2.2 + P4.1.3 + I-3.3.3. L5 (retention save) → P1 (entire) + P5.2 + P5.4.2. L6 (ARPU + outcomes) → P5.3 + P5.4 + P4.4.
Loss AttributionL1 booked $2–4M + L2 modeled $12–28M + L3 opportunity $22–35M = $36–67M sensitivity bandL3 opportunity is what this canvas captures. The $22–35M opportunity-cost band is the inverse of Growth Model lifts not captured in trailing 12 months. Initiatives in this canvas (P1–P5) collectively deliver the +$25–30M Growth Model anchor — recovering the bulk of L3 over FY27.
Executive Brief + Roadmap to Win9 foundational gaps (F1-F9) + 12 differentiated steals (S1-S12)~90% covered. F1 Universal Content → I-2.1.1; F2 builder unification → P2.2; F3 unified canvas → P5.1; F4 multi-author collab → P5.3; F5 NEB Code Mode → I-2.2.3; F6 multi-region AI → I-4.1.1; F7 SMS coverage → deferred to FY28 (regulatory long-tail per Strategy R3); F8 dynamic content → I-2.2.4 + I-4.4.3; F9 accessibility → I-5.4.2. S1-S12 mapped across all 5 pillars.
Strategy 6-Pager5 bets B1–B5 + 4 strategic shifts + 6 risks + R1 Classic churn = highest-single-risk in financial walk100% bets executed. B1 builder unification → P2.2 (Code Mode prereq). B2 Universal Content → P2.1. B3 unified canvas → P5.1. B4 conversational AI + global ungate → P4.1 + P4.2. B5 collab → P5.3. R1 Classic churn risk → I-2.2.5 funded migration program.
Klaviyo Brief NEWKlaviyo’s structural advantages: Universal Content (Spring ’26 default), real-time CRM, 5-channel canvas (Email+SMS+Push+WhatsApp+In-app), Marketing Agent (URL→flows in 3 clicks), 10+ in-canvas AI features, Image Remix, Smart Send Time per profile, Channel Affinity, Personalized A/B, AI auto-monitors, in-builder revenue metrics, predictive triggers as flow entry, Django templating, deepest Shopify integration, Free tier with full UC + flows accessCoverage delta added in v1.1. Universal Content → P2.1 (already prioritized Q2 ★). AI breadth → P4 entire pillar. Image Remix → P4.4.2. Marketing Agent equivalent for editor → I-3.1.4 NEW. Per-profile Smart Send + Personalized A/B + Channel Affinity → I-4.4.5 NEW. AI auto-monitors → I-4.4.6 NEW. In-builder revenue metrics → I-4.4.4 NEW. 5-channel canvas → I-5.1.5 NEW (Push acceleration; WhatsApp/In-app/RCS still deferred to FY28 per Strategy). Predictive triggers as flow entry → out of editor scope (CJB / platform team). Real-time CRM → out of editor scope (platform team).
Klaviyo VoC NEW17 net-sentiment topics + 7 hate themes + Feb ’25 active-profile billing change (largest single Klaviyo backlash) + DTC bias + no co-edit + no multi-brand kits within one account + no Brand-Kit-aware conversational + higher learning curve + 5 plays for MailchimpCoverage delta added in v1.1. Active-profile billing damage → I-3.4.3 NEW (engagement-based pricing counter-position). Klaviyo’s exposures (DTC bias, no co-edit, no multi-brand, no Brand-Kit-aware conversational) were already covered: P3.2 (B2B / ProServ), P5.3 (co-edit), P1.2.3 (multi-brand), P4.2.1 (conversational) — sharpened in the Strategy Memo as Mailchimp-wins-first counter-positioning. The 5 plays from VoC Page 2 map directly to the new + existing initiatives.

7.2 Methodology — how the canvas was built

  1. Inventoried every evidence tab. Read VoC (7 hate themes), HVC Risk Map (17 cited themes with named-customer MRR), User Research (5 bets + 25 briefs + Discovery table + Workflow Shapes), Product Health (BQ baselines + critic), Growth Model (6 levers + mid scenario), Loss Attribution (3-layer stack).
  2. Designed initiatives top-down from evidence. Each initiative has a documented pain or competitive gap as its origin. No initiative is invented; each maps to at least one source tag in the canvas.
  3. Organized by 5 customer-benefit pillars (P1-P5). Pillar names are what the customer gets, not what the team builds. Internal team names retained in italics for reference.
  4. Sequenced by leverage + dependency. Three orchestration moves (Universal Content first, NEB Code Mode parallel, Write with AI funnel recovery starts immediately) make every other initiative cheaper or possible.
  5. Tagged each initiative with: Growth Model lever (L1-L6), pain $ resolved, evidence source, scope. Initiative IDs (I-X.Y.Z) follow pillar.subtheme.initiative numbering for traceability.
  6. Sized each pillar’s FY27 contribution against the Growth Model $25–30M target. P1 $3–5M (retention save) + P2 $4–7M (Universal Content + migration) + P3 $4–6M (activation) + P4 $4–6M (AI recovery + differentiation) + P5 $5–8M (cross-channel + collab) = $20–32M envelope; landing inside the $25–30M anchor at conservative ranges.

7.3 What’s deliberately NOT in this canvas

  • SMS international expansion (RMW F7). Regulatory + telco-heavy 12–18mo timeline; deferred to FY28. Strategy Page 5 alternative explicitly rejected “push SMS internationally first.”
  • Transactional product investment. Health shows Transactional −10.5% YoY, but Strategy explicitly scopes editor as bulk + SMS + AI Assist; transactional is a Standard-tier feature that lives in the platform team backlog.
  • Acquiring Stripo / Beefree. Considered in Strategy Page 5; partner-or-license alternative explored; carve-out scope too small to justify acquisition.
  • Building a separate enterprise authoring product to compete with Stensul head-on. Strategy Page 5: outside Mailchimp’s SMB DNA; I-5.4.1 (locked layouts for SMB) is the right entry point.
  • Pricing & SKU restructure beyond Free-tier policy. Broader pricing changes are corp Finance domain, not editor PM.

Evidence-base summary: 7 VoC hate themes + 17 HVC cited themes (~$95K/mo cited) + 25 UR briefs / 5 bets / Discovery table / Workflow Shapes + 10 Product Health findings + 6 Growth Model levers + 3-layer Loss Attribution stack + 9 RMW foundational gaps + 12 RMW differentiated steals + 5 Strategy bets + Klaviyo Brief (10 differentiation dimensions) + Klaviyo VoC (17 net-sentiment topics + Feb ’25 billing damage). 74 tactical initiatives (incl. 6 Klaviyo countermoves added in v1.1 + 3 Builder SLOs added in v1.2) across 20 sub-themes within 5 customer-benefit pillars. Sized to deliver $25–30M FY27 ARR target per Growth Model. Designed top-down from evidence — not bottom-up from existing PRDs.

Guiding Principles · 18-month sequencing logic

How to orchestrate 74 initiatives across 6 quarters without losing the plot

A layered trust-recovery + competitive-narrative-recovery framework. Customers face four simultaneous problems: editor reliability broken (Tab 4 cited), discovery weak (UR), AI funnel collapsed (Health Write with AI), competitive narrative lost (VoC + Klaviyo Spring ’26). Frame internally as “rebuilding trust while reinventing the editor” — not “bugs vs AI vs Universal Content.” All four trust layers run in parallel each quarter, with weighted emphasis.
Principles: 5
Effort allocation: 35/30/25/10
Page: 8 of 9

The strategic insight to communicate to leadership

Don’t frame this as “fix bugs vs ship Universal Content vs rescue AI.” That framing forces a false choice and dies on the first internal review. The right framing is: “we are restoring editor trust AND reinventing the authoring surface, in parallel.” Bug fixes (P1) protect retention. Universal Content (P2) closes the headline competitive gap. Activation (P3) re-opens the −19.2% Explore funnel. AI recovery (P4) addresses the worst single signal in the brief. Cross-channel + collab (P5) makes “unified” real. All five are part of one unified system — the customer experiences the product as “this works reliably → my work compounds → new customers ramp faster → AI helps me ship → my team works in here together.”

5 guiding principles

1
LAYERED ORCHESTRATION

All 5 pillars run in parallel — not sequential phases

Run all 5 pillars every quarter with weighted emphasis. Don’t wait 9 months to ship Universal Content — Klaviyo’s Spring ’26 lead grows. Don’t only ship Universal Content — the cited HVC ($95K/mo) keeps eroding the base. The error mode is treating these as phases instead of weights.

2
TRUST FOUNDATION

AI cannot compensate for broken editor trust

P1 Quality & Trust gets 35% of effort early because AI experiences amplify customer anxiety on a broken foundation. Until I-1.1.1 (NEB rendering) and I-1.2.1 (Brand Kit incident) close, AI demos backfire when customers discover the underlying instability. The Health Write with AI collapse (Explore −73.7%) is not unrelated to the cited HVC bug exposure — both are surface symptoms of the same trust deficit.

3
PRIMITIVES BEFORE POLISH

Universal Content is the prerequisite for the unified canvas

P2.1 Universal Content ships before P5.1 unified email+SMS canvas. The Universal Content primitive is the data structure the unified canvas reuses. Building them in the wrong order means building the same primitive twice (once template-scoped, once cross-channel) — engineering waste + competitive delay. The same logic applies to NEB Code Mode (I-2.2.3) shipping before Classic sunset comms.

4
SEGMENT NARRATIVES HONESTLY

Multivariate metrics demand multivariate strategy

Bulk shrinks while SMS grows; Write with AI Established holds while its Explore collapses; Free shrinks while Standard grows; HVC stable while non-HVC churns. Do not headline a single number. The strategy must address each cohort with its own intervention — bulk = Universal Content + Free recovery; SMS = retention infra + canvas; AI = funnel recovery; Standard = upgrade-path improvements. The Loss Attribution Pages 1+5 critic-style reframes apply directly here.

5
DEPENDENCY + MOMENTUM

Sequence by dependency chain + ship one credibility moment every quarter

Three critical-path items gate everything downstream: (a) Universal Content (I-2.1.1) — gates P5.1 unified canvas; (b) NEB Code Mode (I-2.2.3) — gates Classic sunset comms (Strategy R1: $1–2M ARR risk); (c) Write with AI policy track (I-4.1.1) — runs in parallel with product track because policy clearance has unknown timing per Strategy R3. Every quarter must also deliver ONE demonstrable proof point for sales / analysts / leadership: a feature shipping, an AI demo, a brand-decay reversal — momentum prevents the “stabilization quarter” perception from killing strategy buy-in. The 6 credibility moments are mapped on Page 9.

Effort allocation across 4 trust layers

What % of editor engineering + design + PM effort goes to each layer per quarter. Layer-to-pillar mapping shown below. Reliability creates trust. Simplicity creates confidence. Intelligence creates delight. Autonomy creates differentiation. If you skip the first two, the last two fail.

Functional trust“Does it work?” — cited HVC bugs, Brand Kit reliability, Canva sync, edge cases
35% — Layer 1
35%
Cognitive simplicity“Can I understand it?” — activation, discovery, template ICP fit, prompt-first authoring
30% — Layer 2
30%
Outcome trust + Intelligence“Will this improve my business?” — AI generation, brand-style transfer, product-catalog imagery, dynamic content
25% — Layer 3
25%
Emotional partnership + Autonomy“This product understands my team” — conversational, multi-author collab, governance, accessibility
10% — Layer 4
10%
Layer-to-pillar mapping: Layer 1 (Functional) ≈ P1 (entire) + P5.2 SMS reliability. Layer 2 (Cognitive) ≈ P3 (entire) + P2.1 Universal Content discovery + P4.2.3 prompt-first. Layer 3 (Outcome) ≈ P4 (most) + P2.2.4 dynamic content. Layer 4 (Emotional / Autonomous) ≈ P5.3 collab + P5.4 governance + P4.2.1 conversational. Pillars and layers don’t 1:1-map — pillars are organized by execution dependency; layers are organized by customer experience.

The customer experience progression we’re trying to build

Phase 1 · 0–3mo
"This works reliably."
Functional trust restored — NEB renders correctly, Brand Kit data is reliable, Canva sync doesn’t silently fail.
Phase 2 · 3–9mo
"My work compounds."
Universal Content ships; edit once, propagates; first send in <7 days; new customers ramp faster than they did last year.
Phase 3 · 9–12mo
"AI helps me ship better campaigns."
Write with AI is global + better; conversational editing in canvas; AI image generation tied to product catalog; SMS generation in composer.
Phase 4 · 12–18mo
"My team ships email + SMS together."
Unified email+SMS canvas; real-time multi-author collab + comments; SMS retention infra holds the +73.5% growth; agencies + multi-brand teams have governance.

Source: Trust-layered framework adapted from Automations brief Initiative Canvas Page 8 (GPT-derived); Mailchimp-editor-specific weights and pillar assignments per the evidence in this brief. The 35/30/25/10 effort allocation matches the Strategy Page 4 staffing model (Editor platform 30% + AI 25% + UC 15% + SMS+canvas 20% + Collab 10% ≈ the 4-layer split shown above when pillar work is mapped to its primary layer).

The 6-Quarter Swimlane Roadmap · 18 months · May ’26 → Oct ’27

How all 5 pillars run in parallel across 6 quarters — with 1 credibility moment per quarter

Each row is a pillar swimlane; each column is a quarter. Cells show initiatives shipping that quarter (with IDs). Color-coded by pillar. Bottom row shows the customer-facing credibility moment that signals momentum to leadership, sales, and analysts. Star (★) = high-impact ship.
Quarters: 6 (May ’26 → Oct ’27)
Pillars: 5 in parallel
Page: 9 of 9
Pillar / customer benefit Q1 FY26 Q4May–Jul ’26 Q2 FY27 Q1Aug–Oct ’26 Q3 FY27 Q2Nov ’26–Jan ’27 Q4 FY27 Q3Feb–Apr ’27 Q5 FY27 Q4May–Jul ’27 Q6 FY28 Q1Aug–Oct ’27
P1: "The builder I trust to ship" Internal: Editor Quality & Brand Trust · 35% Layer 1 effort I-1.1.1NEB rendering parity STARTS
I-1.2.1Brand Kit data correctness
I-1.3.1Canva sync reliability
I-1.1.4Template list surfacing
I-1.4.1Creative Assistant rediscovery
I-1.5.1Builder SLO operating contract published (Nuni PM framework)
I-1.1.1NEB rendering parity SHIPS
I-1.2.2Font upload + CA parity ships
I-1.1.3Block ordering bugs
I-1.3.2Content Studio stability
I-1.1.2Multi-author save UX
I-1.2.4Brand fonts in LP / forms
I-1.5.2Builder SLO instrumentation + dashboard ships
I-1.5.3Builder SLO error budgets + escalation + roadmap policy
I-1.2.3Multi-brand kits ships
I-1.1.5Cross-browser regression suite
I-1.1.6Light/dark mode + bg images
I-1.3.3Folder management
I-1.4.2CA non-banner expansion
I-1.1.7Inline link checker upgrade
Maintenance — cited HVC burn-down baseline; weekly bug-bash cadence Maintenance — proactive deliverability monitoring + Brand Kit health alerts Maintenance — operational excellence baseline maintained
P2: "Edit once, send everywhere" Internal: Universal Content + Migration · CRITICAL PATH I-2.1.1Universal Content STARTS (critical path)
I-2.2.3NEB Code Mode design + scope
I-2.2.1Bulk template migration tool design
I-2.1.1Universal Content MVP ships (Klaviyo parity)
I-2.1.2Auto-migration of saved blocks
I-2.2.1Bulk template migration tool ships
I-2.2.21:1 migration tool + support workflow
I-2.1.3Universal Content adoption funnel + discovery
I-2.2.3NEB Code Mode ships (Classic sunset PRECONDITION)
I-2.3.2Brand Kit auto-applied to Universal blocks
I-2.2.4NEB Liquid templating + dynamic content
I-2.3.1Universal Content in CJB (cross-product)
I-2.3.3Universal Content audit + version history
I-2.2.5Funded migration program kicks off + Classic sunset comms I-2.2.5Classic sunset migration peak (12mo grace ongoing)
P3: "From signup to first send in minutes" Internal: Activation Foundation · 30% Layer 2 effort I-3.1.2Brand Kit auto-extract on signup
I-3.3.3DRAFT-resurrect campaign
I-3.1.1Day-0 onboarding sequence (7–10d first-send target)
I-3.1.3Industry welcome flow templates
I-3.3.1In-app changelog + weekly digest
I-3.2.1B2B / ProServ template gallery
I-3.2.3Template categorization fix
I-3.3.2Contextual feature discovery prompts
I-3.1.4AI Email Setup Agent ships (KLV counter)
I-3.2.2Industry-aware template gallery (6–8 per industry)
I-3.4.2Free → Essentials upgrade path
I-3.4.3Engagement-based pricing counter-position (KLV counter)
I-3.4.1Free-tier editor experience uplift Activation telemetry baseline + monthly cohort review
P4: "AI that ships campaigns, not a demo" Internal: Intuit Assist + Write with AI Recovery · 25% Layer 3 effort I-4.1.1Write with AI policy track STARTS (parallel to product)
I-4.1.2Write with AI quality + brand-tone fixes
I-4.1.4In-canvas AI discovery re-instrumentation
I-4.1.2Write with AI quality fixes ship
I-4.1.3Write with AI re-introduction campaign
I-4.3.1Generative SMS in composer design
I-4.3.1Generative SMS in composer ships
I-4.4.2Image Remix in flow steps
I-4.1.1Write with AI global ungate (or paid AI add-on globally)
I-4.3.2SMS variant + A/B in composer
I-4.4.4In-canvas revenue per recipient (KLV counter)
I-4.2.1Conversational journey editing in Intuit Assist
I-4.4.1AI image gen tied to product catalog
I-4.4.3Per-recipient dynamic image
I-4.4.5Per-profile Smart Send + Personalized A/B (KLV counter)
I-4.4.6AI Performance Watchdog (KLV counter)
I-4.2.2AI brand-style transfer
I-4.2.3Prompt-first email mode (toggle)
P5: "Email + SMS feel like one campaign" Internal: Unified Canvas + Collab + SMS Retention · 10% Layer 4 effort early; ramps in Q3+ I-5.2.3SMS TCPA guardrails ship ($57K incident closed)
I-5.2.2SMS credits transparency
I-5.2.1SMS reporting v2
I-5.2.4SMS merge depth + MMS POC
I-5.1.1Shared blocks email+SMS STARTS
I-5.2.5MMS bundle pricing
I-5.4.2Inline accessibility coach
I-5.1.1Shared blocks email+SMS ships
I-5.1.2Cross-channel preview side-by-side
I-5.1.3Brand Kit on SMS short links
I-5.3.1Real-time multi-author co-edit ships
I-5.3.2Block-level @-mention comments
I-5.1.4Unified campaign object
I-5.1.5Push notification send action (KLV counter; FY28→FY27)
I-5.4.1Locked layouts mode (governance for SMB)
I-5.3.3Approval workflow + version history
I-5.4.3Cross-account brand inheritance for agencies
★ Credibility moment Demoable proof per quarter SMS TCPA $57K incident closed + Brand Kit incident closed + Builder SLO operating contract published — cited HVC burn-down begins; quietly removes the largest single brand-risk vector in the brief; first published quality contract for the editor (Nuni PM framework). Universal Content MVP ships — Klaviyo Spring ’26 parity demo. Single biggest shift in editor narrative. Reverses the “Mailchimp ships features but loses the editor conversation” story. NEB Code Mode + Generative SMS + AI Email Setup Agent — power users see NEB they can stay on; SMS retention story begins; Klaviyo Marketing-Agent gap closed. ★ Write with AI global ungate + Free-tier editor uplift + engagement-based pricing position — biggest brand-decay reversal moment of the program. International Standard customers stop paying for an inaccessible feature; SMB acquisition funnel reopens; explicit counter to Klaviyo Feb ’25 active-profile billing damage. Conversational journey editing + Real-time co-edit + Shared email+SMS blocks + Push send action + Per-profile Smart Send + AI Performance Watchdog — “Mailchimp is back, modern, one product, and omnichannel.” Press / analyst narrative shifts; multi-author teams have a reason to stay; 5-channel canvas gap with Klaviyo partially closed (Push live). AI brand-style transfer + Prompt-first mode + Governance for SMB — category-leadership narrative. Mailchimp is the SMB authoring platform with AI breadth + collab + governance no competitor matches.

Top 3 risks to the roadmap

Risk #1 · Critical Path

Universal Content scope balloons

If I-2.1.1 slips past Q2, the Klaviyo parity claim stays open and P5.1 unified canvas shifts right. Mitigation: ship MVP (template-scoped propagation only) Q2, expand to CJB + per-channel rendering Q3-Q4. Don’t big-bang.

Risk #2 · Policy Dependency

Write with AI legal/policy gates remain stuck

Strategy R3: Q4 credibility moment (I-4.1.1) depends on Intuit policy + legal clearance for international Standard. Mitigation: run product track for paid global AI add-on as fallback; launch whichever clears first; have Q4 narrative queued for either path.

Risk #3 · Capacity

Editor team capacity vs scope

65 initiatives across 18 months requires +30% editor team capacity for the Classic-migration window (per Strategy R6). Without headcount lock, P5 collab + P4 advanced AI slip from FY27 into FY28. Mitigation: headcount plan in Q1; defer P5.4 governance to FY28 H2 if Q1-Q3 capacity is the binding constraint.

Roadmap methodology: Sequencing logic from Page 8 principles. Each initiative placed in a quarter based on (a) dependency chain (Universal Content first; NEB Code Mode before Classic sunset; Write with AI policy track parallel to product), (b) credibility moment cadence (one demoable proof per quarter), (c) effort allocation (35/30/25/10 maintained per quarter), (d) HVC burn-down sequencing (cited $ resolved fastest first), (e) Growth Model lever timing (L1 bulk recovery + L5 retention save load Q1-Q3; L3 SMS attach + L6 ARPU/governance load Q4-Q6), (f) Klaviyo countermove sequencing (AI Email Setup Agent Q3, engagement-based pricing Q4 paired with Free uplift, in-canvas revenue Q4 paired with global AI ungate, per-profile Smart Send + Watchdog + Push Q5 paired with co-edit + conversational). All 74 initiatives mapped (incl. 6 Klaviyo countermoves in v1.1 + 3 Builder SLOs in v1.2); ~5 deliberately deferred to Q6 (cross-account agency inheritance; prompt-first mode; AI brand-style transfer). Builder SLOs (P1.5) added as the operational quality gate — per the Nuni PM team framework, no major NEB change ships broadly until SLO-neutral or better for target cohorts; if we miss a core SLO for target ICPs we pause new complexity and redirect capacity to underlying quality work.

Strategy Memo · Mailchimp Unified Builder · FY27 · v2.0

The Unified AI-First Builder: winning the category, not patching the gaps

To
CEO · CPO · Board (Intuit Mailchimp business unit)
From
VP Product, Mailchimp Authoring Surface
Date
May 2026 · v2.0 (supersedes Apr ’26 v1.2)
Re
FY27 strategy for one unified builder — email, SMS, and future channels on a single AI-first canvas — sized to deliver the ~$21M Revised-Goals ARR target by April 2027 while beating Canva on creative AI and Klaviyo on send-time intelligence

Purpose

This memo asks the executive team to commit to a single, AI-first, unified builder — one canvas for email, SMS, and the next channels we add — and to fund the five-pillar program that delivers it. The goal is not to fix the bugs or to ship Universal Content parity with Klaviyo. The goal is to win the SMB authoring category by being unmistakably the best builder at the three things customers actually pay for: ⏱ saving them time, 🛡 building their confidence & trust, and 💰 driving more money per send. This memo restates the situation, the competitive complication, the five strategic pillars and ~65 tactical initiatives that deliver them, the three orchestration moves that make every pillar cheaper, the 6-quarter roadmap, the financial walk to the ~$21M FY27 ARR target in Revised Goals, the top five risks with named mitigations, and the recommendation we are asking the exec sponsor to approve.


Background — where Mailchimp’s builder sits today

Mailchimp’s authoring surface is the most-touched product in the company and the single largest input into FY27 revenue. Per BigQuery (bi_aggregate.product_journey_monthly, trailing 12 months May 2025–Apr 2026), 888,706 customers per month are Established users on bulk email. Around it sits a fast-moving satellite: SMS composer 6,673 Established users/mo (+73.5% YoY), Write with AI 31,438 (Explore funnel −73.7% YoY), Mailchimp Transactional 25,716. The total footprint exceeds 1.6M monthly active users. The product itself is real: a 260+-template New Email Builder, a Classic builder retained for HTML power users, an SMS composer with branded short links + MMS in US/CA, Content Studio DAM, Brand Kit (logos / fonts / colors / voice), and the Intuit Assist AI surface (Write with AI, Creative Assistant, Email Content Generator). G2 sits at 4.3/5 across 12,698 reviews.

What customers love — preserve and compound (VoC +56 net-sentiment, recurring 5-star themes):

  • Drag-and-drop ergonomics for solos. The reason most 5-star reviews chose Mailchimp; the SMB UX advantage Klaviyo cannot match without rewriting their builder.
  • Brand Kit + Creative Assistant. The practical, daily-use AI feature solos already rely on. Auto-extracted brand applied to designs. This is the foundation we expand into a Canva-killer.
  • Write with AI brand-tone copy. Lands well with non-technical operators where it’s available (US/UK/AU/CA only — a structural defect we are fixing in P3).
  • Content Studio asset management. Mature sync / search / organize across campaigns — the asset-graph we build the AI image surface on top of.

The evidence base behind this strategy spans 11 tabs: HVC Risk Map (17 cited themes / ~$95K/mo cited MRR including a $57K SMS TCPA incident), User Research (50 HeyMarvin sessions / 25 customer briefs / 5 bets / Discovery table / 5 Workflow Shapes), Voice of Customer (7 hate themes across Trustpilot 1,390 / G2 12,698 / Reddit), Product Health (paid / free / trial YoY), Loss Attribution ($36–67M backward stack), Growth Model (6 levers), and the Revised Goals tab (3-cohort scorecards summing to ~$21M ARR). Every claim that follows is grounded in one or more of those sources.


Complication — what is at risk if we do not act

Three competitive shifts in the last 18 months have turned a quiet decline into a category-leadership question. (1) Klaviyo shipped Universal Content as the default editor primitive in Spring 2026 and announced their Marketing Agent + in-canvas Smart Send + Performance Loop — the ESP-native intelligence layer Mailchimp also has the raw assets for, but has not productized. (2) Canva shipped AI 2.0 in 2026 — Dream Lab image generation, Magic Layers, conversational design, Brand Voice 2.0, Memory, an MCP bridge — aimed squarely at the same SMB designer-marketer who currently exports Canva assets into Mailchimp. (3) Mailchimp’s own bulk-email spine started shrinking on every cohort under 24 months tenure while the AI funnel that was supposed to widen the top of the builder collapsed. Each shift is documented in BigQuery, named-customer VoC, and the Klaviyo Brief / Klaviyo VoC tabs.

−9.4% YoY
Bulk email Established users (the editor spine): 980.6K → 888.7K avg/mo (−92K). 24+ tenure cohort −6.5%; every cohort under 24 months −17 to −23%.
−19.2% YoY
Bulk email Explore users (top of funnel): 64.2K → 51.9K. New customer acquisition into the editor is the biggest single leak.
−19.2% YoY
Free plan Established users: 386K → 312K (−74K). Largest single segment loss in the brief; SMB customers acquired by Shopify storefront-bundled tools.
+2.1pp YoY
Bulk churn rate: 38% → 40.0%. Retention deterioration on the largest cohort while the cohort itself shrinks.
−73.7% YoY
Write with AI Explore users: 78K → 21K. Honeymoon ended. Abandons doubled (+101%); churn 62% → 77.2%; geo-gate to US/UK/AU/CA on a globally-priced Standard plan is the largest single contributor.
+73.5% YoY
SMS Established users: 3.8K → 6.7K (every plan tier +39 to +96%). But churn 53% (+3.0pp) and Abandon +95.4% — growth + leakage simultaneously.

The competitive squeeze. Canva is coming up the stack from design toward marketing automation, betting on AI image + brand depth that no ESP can match without re-platforming. Klaviyo is going down the stack from ESP intelligence toward creative authoring, betting that Universal Content + Marketing Agent + in-canvas revenue make every send smarter than ours. Mailchimp sits exactly where both pincers meet — the SMB email + SMS builder with brand + AI + send infrastructure already wired together. We are the only player with all the inputs to win both sides. We have not yet productized the win.

The internal complication. The bulk-email base shrank by ~92K Established users in 12 months. Bulk churn moved +2.1pp to 40.0%. Free Established lost 74K (−19.2%). Write with AI Explore collapsed −73.7% YoY (the worst single signal in the brief) because the AI we sell globally is gated to four countries. SMS adoption is +73.5% YoY but the cohort churns at 53% because retention infrastructure (TCPA pre-send safety, reporting, credits transparency) was never built. Customers describe the experience as “clunky and outdated” — not because of any single feature gap, but because two builders, two composers, geo-gated AI, and a Brand Kit that occasionally drops colors add up to the impression that the product is no longer modern. The Loss Attribution tab sizes the editor-related backward stack at $36–67M over the trailing 12 months — most counterfactual, but the directional signal is unambiguous: the opportunity cost we left on the table is roughly twice the FY27 commit we are now asking for.

“Klaviyo just shipped Universal Content. Canva just shipped Dream Lab. Mailchimp shipped… what? I’m the SMB customer both of them are courting and the one who already pays you. Give me a reason to stay.”

Operator forum composite · r/MarketingAutomation + r/Klaviyo Spring ’26 thread cluster (verbatim pattern across 30+ named posts)

What is at risk if we keep patching gaps instead of winning the category

If Mailchimp ships a "fix the bugs" roadmap in FY27, the most likely outcome is: Klaviyo wins multi-brand DTC + agency on Universal Content + Marketing Agent + in-canvas revenue; Canva wins the brand-and-design loyalty of the same SMB who used to default to Mailchimp first; and Mailchimp becomes the cheaper option that doesn’t lose customers but doesn’t win new ones either. The Revised Goals $21M ARR target requires the opposite posture: be AI-first and unmistakably best-in-class on the three things customers pay for. Time. Trust. Money.


The thesis — one unified, AI-first builder, three customer outcomes

Mailchimp’s authoring surface becomes the unified, AI-first builder where every SMB marketer authors once, ships everywhere, and trusts every send. Email, SMS, and the next channels we add (Push first, then In-App / WhatsApp / RCS) live on a single canvas with shared blocks, shared brand, shared AI, shared preview, shared collaboration, and shared reporting. AI is not a sidebar feature; it is embedded in every authoring step — setup, scaffolding, copy, image, layout, personalization, compliance, performance — and is brand-safe, audience-aware, and hallucination-guarded by default. The three customer outcomes the builder is judged on, every quarter:

  • ⏱ Saves time. Faster from idea to campaign-shipped. URL → first send in <30 minutes. Block edit propagates everywhere. Conversational edits replace click-trees. Multi-author co-edit replaces screenshot Slack threads.
  • 🛡 Builds confidence & trust. Brand-safe (Brand Kit enforced + multi-brand). Deliverable (SLO-backed render fidelity + accessibility coach). Compliance-safe (audience confirm + TCPA pre-send Freddie). Hallucination-safe (AI grounded in customer data + product catalog + Brand Kit, never freelancing). The "I can ship from this with my eyes closed" feeling.
  • 💰 Drives more money. Per-recipient personalization (Liquid + Send-Time Personalization). Performance loops that learn from every send. AI image gen tied to product catalog. In-canvas revenue per recipient. Personalized A/B. The builder gets smarter every campaign.

Every initiative in the five pillars is tagged with which of these three outcomes it primarily delivers, and every pillar is judged on whether the cohort it serves feels the change in those three terms. This is the lens the CEO, the Board, and the customer share.


Customer problems — the seven evidence-anchored truths the strategy responds to

The customer-side cost decomposes into seven specific problems, each grounded in the named-customer evidence. Voice of Customer themes, HVC Risk Map cited MRR (~$95K/mo across 17 themes), and User Research (25 customer briefs across 50 HeyMarvin videos) tell a consistent story. The five pillars below are the strategic response to these seven truths — one pillar can address several truths, and several pillars can address one truth.

  • Two-builder bifurcation & broken builder trust. NEB rendering bugs, multi-author save conflicts, Brand Kit drift, Canva-sync silent failures. VoC #1 hate theme (−72 net-sentiment); HVC ~$15K/mo cited MRR across NEB + Brand Kit + Content Studio; +2.1pp YoY bulk churn. The builder is not yet one a marketer trusts to ship from with their eyes closed. Anchors P1 (Quality & Trust Foundation).
  • SMS retention infrastructure missing — including a $57K TCPA incident. No reporting, broken credits, no pre-send TCPA / Freddie safety net. SMS Established +73.5% YoY but cohort churn 53%. The highest-growth product bleeds the customers it acquires. Anchors P1 (TCPA + audience confirm) and P5 (SMS retention depth).
  • Klaviyo Universal Content + Canva AI 2.0 gaps in the same calendar quarter. The single most-asked-for editor primitive of 2026 (UR Bet #1 PM-confirmed in flight); Canva’s Dream Lab + Magic Layers + Brand Voice 2.0 + Memory + MCP bridge now define the SMB creative AI bar. Anchors P2 (Creative AI Depth) and P5 (Unified Canvas via Universal Content primitive).
  • Write with AI is geo-gated and quality-degraded. US/UK/AU/CA only on a globally-priced Standard plan. Explore funnel −73.7% YoY; Abandon doubled; churn 77.2%. Worst single signal in the brief. Anchors P3 (ungate + funnel recovery) and P2 (Brand Voice 2.0 + AI quality lift).
  • Activation is slow and templates don’t fit non-ecom. Time-to-first-send 14–21d median; <1mo cohort −17.5%; Free Established −19.2% (74K lost); UR Bet #3 (B2B / ProServ template gap); UR Discovery table (5 customers with years-long undiscovered features); Klaviyo Marketing Agent ships URL → flow in ~3 clicks. Anchors P3 (Activation & First-Send).
  • The unified canvas does not exist. Email and SMS are composed in separate surfaces with no shared blocks, no shared preview, no Brand Kit propagation, no shared collab. VoC #2 hate theme. Bianka: “email + SMS + all touches in one reporting view.” Anchors P5 (Unified Canvas + Collaboration).
  • The builder gets no smarter from sending. Store-level send-time only; no per-recipient personalization; no performance loop; no in-canvas revenue; no AI Performance Watchdog. Mailchimp owns the ESP send infrastructure but does not productize the intelligence Klaviyo is now publicly building on top of theirs. Anchors P4 (Send-Time Intelligence — the ESP-native moat).
Customer-side cost · what these problems cost the customer in time / trust / money

⏱ Lost time: 181-template rebuilds; the welcome email rebuilt three times mid-migration; Andrea’s "hunting in the attic" asset workflow; click-trees instead of conversational edits; copy/paste between two composers. 🛡 Lost confidence: Brand Kit drops colors mid-send; Canva sync silently fails; the C3 Festivals TCPA incident; Trustpilot 2.7/5; international customers paying for AI they cannot use; UR self-blame pattern (5 of 15 customers using 10–20% of capability). 💰 Lost money: generic AI imagery + stock-photo conversion drag; no per-recipient send-time; no in-canvas revenue surfacing the dollars-per-block story; no performance loop to learn from yesterday’s send. The compounded effect is silent churn: the customer doesn’t complain, they just stop sending.

Mailchimp business cost · trailing 12 months (Loss Attribution)

Per the Loss Attribution tab: $2–4M booked P&L erosion + $12–28M modeled drag + $22–35M opportunity cost = $36–67M sensitivity band. Bulk shrank ~92K Established users in 12 months; Premium / agency Classic-sunset churn alone is sized at $1–2M ARR at risk (Strategy R1). The forward $21M FY27 ARR commit (this memo) recovers roughly the median of the booked + modeled portion of that backward stack — the opportunity-cost band is what we recover in FY28+ as the unified-builder thesis compounds.


What winning looks like — the metrics that prove time / trust / money

Across three layers — product adoption, customer outcome, and Mailchimp business — the metric movements the strategy commits to by April 2027. Baselines are BigQuery-validated in Product Health; the 3-cohort dollar walk to the ~$21M target is in Revised Goals (Paid $6.7M + Free $8.7M + Trial $5.6M). Each row maps to one of the three customer outcomes.

Layer 1 · Product adoption ⏱ + 🛡
The funnel reopens; the cohort retains
Bulk Established users (avg/mo)
888,706
915–935K
Bulk Explore funnel
51,859 (−19.2%)
58–65K
Bulk churn rate
40.0% (+2.1pp)
36.5–37.5%
Free Established users
312K (−19.2% / 74K lost)
340–360K
Trial activation rate
−3.0pp YoY (worst)
+2–4pp recovery
SMS composer Established
6,673 (53% churn)
11.5–14.5K (46–48% churn)
Write with AI Explore (recover)
20,521 (−73.7%)
stabilize + global ungate
Universal Content adoption
0 (not shipped)
50–70% of NEB adopters
Layer 2 · Customer outcome ⏱ 🛡 💰
What the marketer feels — time, trust, money
⏱ Time to first send (new user)
14–21d median
<30 min via AI Setup Agent / 7–10d median
⏱ Clicks per email send
high (manual click-trees)
−40–60% via conversational editing
⏱ Email + SMS compose loop
two surfaces, copy-paste
one canvas, shared blocks, cross-channel preview
🛡 Builder SLO compliance
no published contract
uptime ≥99.9% · render ≥99% · P95 load <500ms
🛡 Off-brand sends (no Kit / overrides)
elevated in VoC
−20–30%
🛡 SMS TCPA / audience-confirm incidents
$57K precedent
−25–40% (Freddie pre-send blocks)
🛡 AI hallucination / off-brand AI output
untracked, customer-reported
guardrails + grounding telemetry; <1% incident rate
💰 Per-recipient personalization adoption
store-level send only
25–40% of paid cohort uses Send-Time Personalization or Liquid
💰 In-canvas revenue surfacing
renewal stuck on "opens"
$ per block + $ per recipient surfaced inline
💰 Performance Loop / Watchdog adoption
0 (not shipped)
30–50% of repeat senders
Layer 3 · Mailchimp business 💰
FY27 dollars + competitive narrative
FY27 ARR commit (Revised Goals)
~$21M
Paid cohort direct ARR
$6.7M
Free → Paid conversion ARR
$8.7M
Trial → Paid conversion ARR
$5.6M
Premium / agency Classic churn (R1)
$1–2M at risk
contained via NEB Code Mode + funded migration
Category narrative
“Mailchimp ships features; competitors ship category-defining moments”
“Mailchimp is the AI-first unified builder for SMB — better than Canva at creative AI grounded in your data; better than Klaviyo at send-time intelligence grounded in your ESP”
Cohort walk (~$21M total): Paid $6.7M (steady-state retention + activation) · Free $8.7M (P3 activation + free uplift → paid conversion) · Trial $5.6M (P3 activation + first-send acceleration → paid conversion). Full per-lever derivation in Revised Goals.

How we win — stop / continue / change / start

Four moves frame the program. Stop patching the bifurcated builder as if it were two products. Continue the SMB-first ergonomics, Brand Kit + Intuit Assist depth, and Intuit-grade deliverability that no competitor can match. Change the build order so the unified-canvas primitives ship before the polish that depends on them. Start the AI-first, multi-channel, multi-author, send-time-intelligent builder we have been describing externally for two years and shipping internally as scattered features.

Stop
  • Shipping editor features on two stacks. Every NEB feature has to justify itself twice until Classic is retired with NEB Code Mode parity. Wastes engineering; fragments the customer experience; freezes the unified-builder narrative.
  • Treating email and SMS as separate composers. They are one campaign for the customer. Treat them as one in code, in UX, and in reporting from day one.
  • Selling Standard internationally with US-only AI. The Write with AI geo-gate is the single largest brand-decay vector in the brief. Ungate or repackage — do not keep the current posture.
  • Treating AI as a sidebar surface. “Open Intuit Assist” is the wrong UX. AI is inside every authoring step or it is not AI-first.
  • Reporting on aggregate “editor adoption.” Bulk shrinks while SMS grows; Free shrinks while Standard grows. One number hides the truth and the strategy.
Continue
  • Brand Kit + Intuit Assist as the AI foundation. Only Mailchimp has 12M+ customers’ brand context + Intuit’s shared AI infrastructure + ESP send signal in one stack. This is the moat if we productize it.
  • Intuit-grade deliverability + sender reputation. The builder authors; deliverability ships. Both have to keep working — this is a quiet trust asset Canva will never have and Klaviyo cannot copy at our cost basis.
  • SMB-first ergonomics + 260+ templates + 300+ ecom integrations. The asset base Canva is trying to build and Klaviyo can’t match. Compound it.
  • Generalist cross-segment positioning. Klaviyo is DTC-only; Mailchimp serves every vertical. The B2B / ProServ / non-ecom expansion is a wedge they cannot copy without re-platforming.
  • Email as the anchor + SMS / Push attach. Email is the wedge into omnichannel. Other channels feel like one campaign because email is the source of truth.
Change
  • The product posture. From “builder with AI features” to “AI-first unified builder where AI is the authoring surface”. Conversational creation, conversational editing, AI scaffolding, AI personalization, AI compliance, AI performance — in every step.
  • The build order. Universal Content first (primitive); unified email+SMS canvas reuses it; collab + governance ride on the same data model. Build dependencies once.
  • The trust posture. Reframe the brand-context banner to a published operating contract (Builder SLOs: uptime, render fidelity, P95 load, accessibility, AI hallucination rate). Trust as a product feature, not a marketing claim.
  • The migration posture. Funded Classic sunset with full NEB Code Mode + Liquid parity, 12-month grace period, 1:1 migration with style preservation. Sunset becomes a positive event for HVCs, not a churn trigger.
  • The external narrative. From “Mailchimp ships features” to “Mailchimp customers ship campaigns faster, with more confidence, and earn more money per send than they did last year — with one builder, one brand, one AI”.
Start
  • Beat Canva on creative AI: Dream Lab tied to product catalog, Magic Layers, conversational editing, Brand Voice 2.0, Memory, Connectors, Web Research, MCP Bridge (P2 — 0–9mo).
  • Beat Klaviyo on activation: AI Email Setup Agent (URL → live campaign in <3 clicks), Brand Kit auto-extract on signup, industry-aware templates, free-tier uplift + engagement-based pricing counter (P3 — 3–9mo).
  • Build the ESP-native AI moat Canva can never match: Agentic Orchestrator, Performance Loop, Send-Time Personalization, Smart Send Time, Asset Studio, Localization, AMP, Shield, Cross-Domain Agent (P4 — 6–18mo).
  • Make the unified builder real: Universal Content primitive, unified email+SMS canvas, multi-author collab, Push send action, NEB Code Mode + Liquid, funded migration playbook (P5 — 6–18mo).
  • Publish the Builder SLO operating contract: uptime 99.9% / crash-free 99.5% / render fidelity ≥99% / P95 load <500ms / WCAG AA on critical flows / AI hallucination rate <1% (P1 — 0–3mo).
  • Ship hallucination guardrails + audience confirm + SMS TCPA Freddie: the three new trust primitives that make “ship with your eyes closed” literal (P1 — 0–3mo).

Competitive frame — what we beat each competitor on

Dimension Canva AI 2.0 Klaviyo Spring ’26 Mailchimp Unified Builder (this strategy)
⏱ Time to first send No ESP — not in market Marketing Agent: URL → flow in ~3 clicks; DTC bias AI Email Setup Agent (P3): URL → live campaign in <3 clicks across every vertical, with Brand Kit auto-extracted; + industry templates + free uplift — the Klaviyo move, generalized
🎨 Creative AI depth Dream Lab, Magic Layers, Brand Voice 2.0, Memory, MCP — category-best, design-only Feature-bound AI (subject lines, image edit); no Brand Voice depth P2 closes the design-AI parity with Brand Kit grounding + product-catalog Dream Lab + MCP bridge + Memory + Brand Voice 2.0 — Canva-grade output, ESP-grounded
📦 Universal Content Document-level only Default editor primitive (Spring ’26) P5 Universal Content + CJB + multi-channel — the same primitive Klaviyo shipped, plus it carries into SMS / Push so the unified canvas reuses it
🧠 Send-time intelligence No ESP — not in market In-canvas Smart Send Time, Performance Loop, per-profile A/B — ESP-native moat P4 Send-Time Intelligence: Agentic Orchestrator + Performance Loop + Send-Time Personalization + Smart Send Time + Asset Studio + AMP + Shield + Cross-Domain Agent — Mailchimp has the same ESP signal Klaviyo has, productized into a moat Canva cannot match
👥 Multi-author collab Real-time co-edit (designs) Single editor at a time (gap) P5 real-time multi-author co-edit + @-mention comments + approval flow — the workflow Klaviyo doesn’t have
🛡 Trust & compliance Design-only, no compliance surface No published builder SLOs; light TCPA P1 published Builder SLOs + hallucination guardrails + audience confirm + SMS TCPA Freddie — the trust posture neither competitor matches
🏢 Multi-brand / agency Multi-brand (design-level) No multi-brand within one account (gap) P1 multi-brand kits + P5 cross-account brand inheritance — the agency / multi-brand wedge into Klaviyo’s base

The strategic posture in one line: beat Canva on creative AI by grounding it in customer data + Brand Kit + product catalog; beat Klaviyo on send-time intelligence by productizing the ESP signal we both have but only they have shipped; beat both on the unified canvas because we are the only player with email + SMS + Push + Brand Kit + AI + 300+ ecom integrations in one stack already.


Strategic response — the five pillars of the unified AI-first builder

Five pillars, ~65 tactical initiatives in the Initiative Canvas (v2.0). Each pillar is named for the customer benefit it produces, with the internal capability name, the horizon, a sub-theme list, 4–6 representative initiatives, the evidence anchor, an explicit “how it beats Canva / Klaviyo” line, and the customer outcome tags. Read top to bottom: foundation → depth → speed → moat → canvas.

P1
“The builder I can ship from with my eyes closed”
Quality & Trust Foundation · 0–3 months · 5 sub-themes · ~19 initiatives · Outcomes 🛡 (primary) · ⏱ (secondary)

Sub-themes: Builder SLOs as operating contract · NEB rendering + multi-author save + cross-browser regression · Brand Kit reliability + multi-brand · SMS TCPA + Freddie audience-confirm pre-send · AI hallucination guardrails + brand-context banner reframed as a published trust surface.

  • Builder SLO operating contract (I-1.5.1–3). Publish: uptime ≥99.9% / crash-free ≥99.5% / save-publish ≥99.99% / P95 load <500ms / interaction P95 <300ms / render fidelity ≥99% / mobile ≥95% / WCAG AA on critical flows. Adopted from Nuni Builder Strategy. Plus instrumentation, dashboards, error budgets, CSO alignment, and a roadmap policy that pauses new complexity when the floor slips. Evidence: HVC ~$15K/mo cited rendering + Brand Kit. UR Workflow Shape #4. PH +2.1pp bulk churn.
  • NEB rendering parity + cross-browser regression suite (I-1.1.1, I-1.1.5). Forwarded-mail, mobile line-break, image-shrink, Ctrl+K, light/dark mode, background images — closed against a published browser matrix. Evidence: HVC #3 ($1,820/mo cited).
  • Brand Kit reliability + multi-brand kits + font upload parity (I-1.2.1–4). Incident closure + monitoring; multi-brand within one account (Canva & Klaviyo gap); font upload to Creative Assistant parity. Evidence: HVC #8–10 ($6.5K/mo cited incl. $3K Premium + $2,460 multi-brand cluster).
  • SMS TCPA + Freddie audience-confirm pre-send safety (P1.3 launch-blocking). Block opt-out duplication, audience-mismatch sends, list-segment misuse before the send button. Evidence: HVC #16 C3 Festivals $57K incident (largest single escalation in the brief).
  • AI hallucination guardrails + grounding telemetry (NEW). Every AI generation grounded in Brand Kit + product catalog + customer data; published hallucination-rate SLO <1%; in-canvas “why did the AI suggest this?” transparency surface. Evidence: Canva AI 2.0 + Klaviyo Marketing Agent both ship without published guardrails; this is differentiated trust.
  • Brand-context banner reframed as “published operating contract” (NEW). What today reads as a polite note becomes a customer-facing SLO surface plus opt-in to early-warning alerts when a metric is at risk. Evidence: customer-reported trust signal in the Klaviyo VoC tab — SLO transparency is a sales asset to Premium / agency.

How it beats Canva & Klaviyo: Canva has no compliance / deliverability / SLO surface (design-only). Klaviyo has no published Builder SLOs and no audience-confirm pre-send safety net. P1 makes “the builder you can ship from with your eyes closed” literally true and externally provable.

P2
“AI that creates campaigns that look like a designer made them”
Creative AI Depth — Beat Canva at Their Own Game · 0–9 months · 4 sub-themes · ~14 initiatives · Outcomes ⏱ + 🛡 + 💰

Sub-themes: AI image & design intelligence · conversational creation & editing · brand intelligence & memory · connectors / web research / MCP bridge.

  • Dream Lab — AI image generation grounded in product catalog (I-2.2.2). Hero images generated from the product the email is about; Brand Kit applied; product feed (Shopify / Woo / BigCommerce / 300+ integrations) as the grounding source. Evidence: Canva Dream Lab is generic; Mailchimp’s catalog + Brand Kit is the unique input no SMB tool can match.
  • AI Image Manipulation + Magic Layers + Layered Object Intelligence (I-2.2.1, I-2.2.3). AI-aware z-order, per-layer semantic edits, inpaint / outpaint / object isolation. Evidence: Canva gaps (Magic Layers, Layered Object Intelligence). Reduces UR Workflow #4 third-party tax.
  • Conversational creation & editing (I-2.1.1–3). “Redo the hero in a friendlier tone with a CTA to the spring sale” lands in canvas. Brand-Kit-aware. Multi-turn. Audience-aware. Evidence: Klaviyo AI is feature-bound; Postscript trains on PDFs but no canvas edits; Stensul is form-driven. No competitor has Brand-Kit-aware conversational.
  • Brand Voice 2.0 + Memory (I-2.3.3, I-2.3.4). Multi-voice profiles (newsletter / promo / support / sub-brand); audience-segment-aware tone; durable Memory across conversations; team-shareable voice configs. Evidence: Canva Brand Voice is document-level; Klaviyo has no equivalent. UR Bet #4 multi-author.
  • Connectors + Web Research + MCP Bridge (I-2.4.1–3). Pull live data from CRM / Stripe / Shopify / Google Analytics; web research for current pricing / news / inventory; MCP bridge for external agents (Cursor, Claude, ChatGPT). Evidence: Canva MCP shipped 2026; closing this gap is a 2-quarter ship for Mailchimp using Intuit’s shared infra.
  • Stickers / GIF / animated content blocks (I-2.2.4 + adjacent). Native countdown, GIF, animation, sticker library — closes the “Mailchimp emails look static” perception. Evidence: HVC theme #13 ($7,150 P0 + 600K-recipient threat).

How it beats Canva & Klaviyo: Canva makes pretty designs but doesn’t know your product catalog, your audience, your sender reputation, or your past performance. Mailchimp does. Same creative AI ceiling, with ESP grounding Canva structurally cannot copy. Klaviyo doesn’t have the creative AI depth at all.

P3
“From signup to first send before competitors finish onboarding”
Activation & First-Send — Get Customers to Value in Minutes · 3–9 months · 4 sub-themes · ~13 initiatives · Outcomes ⏱ (primary) · 💰 (downstream conversion)

Sub-themes: AI Email Setup Agent + Brand Kit auto-extract · industry-aware templates (B2B / ProServ / non-ecom) · in-app discovery + DRAFT-resurrect · free-tier uplift + engagement-based pricing counter + Write with AI ungate.

  • AI Email Setup Agent (I-3.1.4). URL → scaffolded first newsletter + promo + welcome campaign in <3 clicks; Brand Kit auto-extracted; industry-fit template chosen by AI; one-click activate. Evidence: Klaviyo Marketing Agent (Spring ’25 GA). Mailchimp’s 260+ templates + Brand Kit + Intuit Assist is the unique training corpus.
  • Brand Kit auto-extract on signup + first-email pre-branded (I-3.1.2). Onboarding asks for website URL; logo / colors / fonts auto-extracted; first send pre-applied with brand. Evidence: VoC Brand Kit love; <1mo cohort −17.5% YoY.
  • Industry-aware template gallery for B2B / ProServ / non-ecom (I-3.2.1–3). 6–8 templates per vertical; layout-only browse; tagged by use case. Evidence: UR Bet #3 (Jillian / Hannah / Chris Rich quotes). Klaviyo has 60+ vertical templates; Mailchimp’s 260+ is invisible to non-ecom customers.
  • In-app changelog + contextual feature discovery + DRAFT-resurrect (I-3.3.1–3). Closes UR Discovery table (5 customers with years-long undiscovered features). Evidence: UR Bianka (A/B years), Jack (NEB 4–6 yrs), Jeffrey (3.5 yrs), Clint (1 yr DRAFT).
  • Free-tier editor experience uplift + engagement-based pricing counter (I-3.4.1, I-3.4.3). More block types + Brand Kit + Creative Assistant on Free; position usage-based / per-engaged-profile pricing as explicit alternative to Klaviyo’s Feb ’25 active-profile billing change. Evidence: PH Free Established −19.2% (74K lost); SHO bundling pattern; Klaviyo billing backlash window.
  • Write with AI global ungate (I-4.1.1) — sequenced into P3 because activation requires AI parity. Either ungate globally or repackage as a paid global AI add-on. Evidence: PH Write with AI Explore −73.7% YoY (worst single signal in the brief).

How it beats Canva & Klaviyo: Canva onboards into design, not into a live campaign — we onboard into a brand-applied, vertical-fit, scheduled-and-sent campaign with the AI agent doing the setup. Klaviyo Marketing Agent is DTC-biased; ours is vertical-aware across B2B, ProServ, restaurants, nonprofits, services. Faster to first value across every vertical.

P4
“Where Mailchimp wins permanently”
Send-Time Intelligence — The ESP-Native Moat Canva Can Never Match · 6–18 months · 5 sub-themes · ~15 initiatives · Outcomes 💰 (primary) · 🛡 (secondary)

Sub-themes: Agentic Orchestrator · Performance Loop · Send-Time Personalization + Smart Send Time · Asset Studio · Localization + AMP + Shield + Cross-Domain Agent.

  • Agentic Orchestrator (I-4.1.1). The agent that owns the full send loop: scaffold → brand-apply → personalize → compliance-check → send-time optimize → learn from result → suggest the next campaign. Brand-Kit-aware. Audience-aware. ESP-grounded. Evidence: Klaviyo Marketing Agent is a similar pattern; Mailchimp has the asset base to ship a generalist version across every vertical.
  • Performance Loop (I-4.2.1). The builder gets smarter every campaign — subject-line learning, block-level CTR learning, audience-segment learning, brand-voice learning — surfaced as “here’s what worked, here’s what to try next” suggestions inline. Evidence: Klaviyo Performance Loop ships in 2026; this is the parity move + leverages Intuit’s shared ML infra.
  • Send-Time Personalization + Smart Send Time + per-profile A/B (I-4.3.1–3). Per-recipient send-time prediction; per-recipient content variant; in-canvas Personalized A/B with explained hypotheses. Evidence: Klaviyo case studies +10–30% open lift; in-canvas A/B is a stated Klaviyo VoC gap when Mailchimp is missing it.
  • Asset Studio + Localization + AMP (I-4.4.1, I-4.5.1, I-4.6.1). Brand-Kit-aware asset library that auto-generates resized / localized / AMP variants; closes the “email is a frozen artifact” perception. Evidence: Klaviyo + Postscript ship localization + AMP; Mailchimp gap.
  • Shield + Cross-Domain Agent (I-4.7.1, I-4.8.1). Deliverability shield that monitors sender rep + spam-trap exposure + complaint rate, with auto-throttle and recovery actions; cross-domain agent that learns brand intent across the customer’s full marketing surface (email + landing pages + forms + ads). Evidence: AI Performance Watchdog gap vs Klaviyo; deliverability is the quiet Intuit asset that Canva will never have.
  • In-canvas revenue per recipient (I-4.4.4). $ per block + $ per recipient surfaced inline at compose time; renewal stops being about “opens.” Evidence: Klaviyo VoC explicitly cites this as decisive vs Mailchimp.

How it beats Canva & Klaviyo: Canva cannot ship this — they have no send infrastructure, no audience graph, no engagement signal. Klaviyo can ship pieces; we ship the full stack because we already own the send, the segment, the deliverability, the brand, the catalog, and the AI. This is the moat that compounds for FY28 and FY29.

P5
“Email and SMS feel like one campaign because they are”
Unified Canvas + Collaboration — One Builder for Every Channel · 6–18 months · 4 sub-themes · ~16 initiatives · Outcomes ⏱ + 🛡 + 💰

Sub-themes: Universal Content primitive + unified email+SMS canvas · Push send action (accelerated from FY28) + future channel attach · multi-author real-time collab + comments + approval · NEB Code Mode + Liquid + funded migration playbook + Classic sunset comms.

  • Universal Content primitive + CJB propagation + auto-migration (I-5.1.1–3). Edit once — header, footer, promo banner, hero — propagates everywhere across templates, campaigns, journeys, and SMS. Brand Kit auto-applied on insert. Audit + version-history governance. Evidence: Klaviyo Spring ’26; UR Bet #1 (PM-confirmed in flight); VoC #6 hate theme; HVC #1 (181-template customer).
  • Unified email+SMS canvas (I-5.2.1–2). One campaign object; shared blocks (Universal Content extends to SMS); cross-channel preview; one reporting view; Brand Kit applied to SMS short links. Evidence: VoC #2 (“unified is a billing claim”); UR Bianka (“email + SMS in one reporting view”).
  • Push send action — accelerated from FY28 to Q5 FY27 (I-5.1.5). Third channel on the same canvas; technically simpler than WhatsApp / In-app / RCS; the lowest-cost path to part of Klaviyo’s 5-channel narrative. Evidence: Klaviyo Email + SMS + Push + WhatsApp + In-app on one canvas; we close the gap with Push first, leave RCS / WhatsApp / In-app to FY28.
  • Real-time multi-author co-edit + @-mention comments + approval flow (I-5.3.1–3). Notion / Google Docs pattern, in MC. Evidence: VoC #5; UR Bet #4 (Jack / Kyle / Bianka); Klaviyo gap (single editor at a time).
  • NEB Code Mode + Liquid templating + funded Classic migration (I-5.4.1–3). HTML / CSS / Liquid escape hatch inside NEB; 1:1 migration tool with style preservation; 12-month grace period; in-product migration tracker. Ships before any Classic sunset comms. Evidence: Strategy R1 sizes Classic-sunset-without-Code-Mode at $1–2M ARR loss; HVC #1–2 ($834/mo cited migration friction); VoC #7 (no HTML escape).
  • Locked layouts + accessibility coach + cross-account brand inheritance (I-5.5.1–3). SMB-flavored governance: brand integrity at scale for multi-author teams + agencies. Evidence: Stensul / Knak enterprise pattern; Klaviyo gap.

How it beats Canva & Klaviyo: Canva is a single-author design tool with no channels and no SMS / Push at all. Klaviyo has the channels but a single editor at a time and no multi-brand within one account. We are the only player with one canvas across email + SMS + Push + Brand Kit + collab + governance — and we make “unified” literally true instead of a billing claim.


The three orchestration moves — what unlocks the most downstream value

Five pillars in parallel; three ordering decisions inside that parallelism that make every downstream initiative cheaper or possible. Each move is named, sequenced, and tied to the risk it removes.

  • Universal Content as a primitive ships first (P5.1.1 in Q2). Because it is both the Klaviyo Spring ’26 parity move and the data primitive the unified email+SMS canvas (P5.2), CJB reuse (P5.1.2), Push attach (P5.1.5), and multi-channel Brand Kit propagation all sit on top of. Building these on different primitives means building the same primitive 4 times. Move: ship the primitive first, then layer.
  • NEB Code Mode + Liquid + funded migration ship before any Classic sunset comms (P5.4 in Q3). Strategy R1 sizes Classic-sunset-without-Code-Mode at $1–2M ARR loss — Premium / agency users specifically anchor on Classic for the HTML escape hatch. Sequence is non-negotiable: Code Mode first, funded migration tool second, then sunset comms. Move: protect the Premium / agency base before announcing the unification narrative externally.
  • Write with AI funnel recovery runs policy + product tracks in parallel from Q1 (P3.4). The Explore −73.7% YoY collapse is the worst single signal in the brief and compounds every quarter delayed. The product track (quality + Brand Voice 2.0 + re-introduction campaign) can ship without the policy track (global ungate / paid AI add-on); the policy track has unknown timing because of Intuit legal + Trust & Safety review. Move: do not let policy timing block product progress; ship the product fix and add the policy unlock when it lands.

Roadmap operating principles

Five principles govern how the program sequences ~65 initiatives across 6 quarters and 3 customer outcomes.

1
All 5 pillars run in parallel — not sequential phases

Quality & Trust burns down in weeks; Creative AI Depth and Activation ship through FY27; Send-Time Intelligence and Unified Canvas compound into FY28. We do not wait nine months to ship Creative AI Depth while Canva extends its lead, and we do not wait nine months to ship Trust while customers learn to expect broken sends. Weights, not phases.

2
Trust is the precondition for AI velocity

P1 (Quality & Trust) ships first because AI experiences amplify customer anxiety on a broken foundation. The Write with AI collapse is not unrelated to the HVC bug exposure — both are surface symptoms of the same trust deficit. Published Builder SLOs + hallucination guardrails + audience confirm are the operating contract every other pillar inherits.

3
Primitives before polish — build the data model once

Universal Content (P5.1) is the data primitive the unified email+SMS canvas, CJB reuse, Push attach, and multi-channel Brand Kit all sit on. NEB Code Mode (P5.4) is the precondition for Classic sunset comms. Build dependencies in the right order; everything downstream gets cheaper.

4
Manage to cohort + outcome, never to aggregate "editor adoption"

Paid / Free / Trial behave differently; bulk shrinks while SMS grows; international Standard customers experience the AI surface differently than US customers. The strategy is judged against the Revised Goals 3-cohort scorecard (Paid $6.7M + Free $8.7M + Trial $5.6M) and the time / trust / money outcomes — not a single “active users” line.

5
Ship one credibility moment every quarter, evidence-anchored externally

Six quarters, six named credibility moments. Each visible externally (PR / brand / operator forums) and internally (team confidence / recruiting). Each tied to a published metric movement on the SLO + outcome dashboard so the announcement is not a brochure claim.

Effort allocation across the five pillars (FY27)
P1 · Quality & Trust22%
P2 · Creative AI Depth25%
P3 · Activation18%
P4 · Send-Time Intelligence + P5 · Unified Canvas35%

6-quarter roadmap — one credibility moment per quarter

Each quarter ships one named, externally-visible credibility moment paired with one customer-outcome metric the leadership team commits to publicly. The full per-pillar swimlane detail lives in the Initiative Canvas.

Q1
May–Jul ’26 · FY26 Q4
Builder SLO contract published + SMS TCPA Freddie + Brand Kit incident closed
🛡 Trust. P1 ships the operating contract; cited HVC burn-down begins; the $57K SMS TCPA vector is closed. Hallucination guardrails + audience confirm in beta. Write with AI quality + Brand Voice 2.0 prep in parallel.
Q2 ★
Aug–Oct ’26 · FY27 Q1
Universal Content MVP + Dream Lab MVP + AI Email Setup Agent beta
⏱ + 💰. The Klaviyo Spring ’26 parity move + the first Canva-grade creative AI surface + the Klaviyo Marketing Agent counter, all in one quarter. The narrative shift: “Mailchimp is the AI-first unified builder.”
Q3
Nov ’26–Jan ’27 · FY27 Q2
NEB Code Mode + Magic Layers + Brand Voice 2.0 + Memory + conversational editing GA
⏱ + 🛡. Power users see NEB they can stay on (protects Premium / agency $1–2M). Creative AI Depth reaches Canva parity inside the canvas. BFCM-safe. Multi-brand kits ship.
Q4 ★
Feb–Apr ’27 · FY27 Q3
Write with AI global ungate + Free-tier editor uplift + engagement-based pricing counter + industry-aware templates
⏱ + 💰. The largest brand-decay reversal moment of the program. International Standard customers stop paying for inaccessible AI; SMB acquisition funnel reopens; the Klaviyo billing-counter story lands fresh. Closes the FY27 ARR walk to ~$21M.
Q5
May–Jul ’27 · FY27 Q4
Unified email+SMS canvas GA + Push send action GA + real-time co-edit + Agentic Orchestrator + Performance Loop beta
⏱ + 🛡 + 💰. “Unified” stops being a billing claim. Multi-author teams have a reason to stay. The ESP-native moat begins to compound — Performance Loop learning from every send.
Q6
Aug–Oct ’27 · FY28 Q1
Send-Time Personalization + Asset Studio + Localization + AMP + Shield + Cross-Domain Agent GA
💰. The Send-Time Intelligence moat goes GA. Mailchimp is the only SMB platform where the builder gets smarter every send because the ESP signal is productized inline. Sets up FY28’s expansion (governance for SMB + RCS / WhatsApp / In-app on the same canvas).

Financial case — the walk to ~$21M FY27 ARR

The Revised Goals tab provides the 3-cohort scorecard the FY27 commit is anchored against. The combined target is ~$21M ARR by April 2027: Paid $6.7M (direct ARR via steady-state retention + activation on 1.02M paid active users / mo) + Free $8.7M (74K Free Established recovery + activation + repeat-send uplift → Free→Paid conversion) + Trial $5.6M (trial activation +2–4pp + 30-day repeat uplift → trial→paid conversion). Each pillar contributes to one or more cohorts; nothing in the strategy is orphan and nothing in the financial walk is unbacked.

Cohort · Mechanism FY27 ARR · Pillars that deliver it Lens
Paid · direct ARR uplift — steady-state retention save (P1 SLOs + Brand Kit + SMS TCPA), activation depth via Creative AI (P2), per-recipient personalization adoption (P4), unified canvas reuse (P5) $6.7M (~32% of total). Pillars P1 + P2 + P4 + P5 🛡 + 💰
Free · Free→Paid conversion uplift — Free editor uplift + engagement-based pricing counter (P3), AI Email Setup Agent (P3), Universal Content + collab making free workflows stickier (P5) $8.7M (largest single contributor, ~41% of total). Pillars P3 + P5 ⏱ + 💰
Trial · Trial→Paid conversion uplift — First-send acceleration via AI Setup Agent + industry templates + Brand Kit auto-extract (P3); Write with AI ungate makes trial AI usable internationally (P3); creative AI depth (P2) drives repeat-trial sends $5.6M (~27% of total). Pillars P3 + P2 ⏱ + 💰

Sensitivity. The Revised Goals model uses conservative per-metric targets across 10 levers; sensitivity at ±25% per lever lands the band at ~$15–26M with the $21M anchor near the center. The FY27 cohort walk recovers roughly the median of the booked + modeled portion of the $36–67M Loss Attribution backward stack; the opportunity-cost band is what we recover in FY28–FY29 as P4 (Send-Time Intelligence) and P5 (Unified Canvas) compound. Capacity ask: +30% engineering capacity for two quarters in the Classic-migration window (Strategy R6 mitigation); rest of program fits within the existing editor + AI + SMS + collab team envelopes.


Top 5 risks — and the pillar that mitigates each

  • R1 · Classic sunset without Code Mode causes Premium / agency churn ($1–2M ARR). Premium customers anchor on Classic specifically for the HTML escape hatch. Mitigation (P5): NEB Code Mode + Liquid + funded 1:1 migration tool + 12-month grace period ship before any sunset comms. Sunset is announced in Q5 only after Q3 Code Mode GA + Q4 funded migration is live.
  • R2 · AI hallucination / off-brand AI output erodes the Trust pillar. Every Canva AI 2.0 launch came with hallucination incidents; our trust posture cannot afford the same. Mitigation (P1 + P2): AI grounded in Brand Kit + product catalog + customer data only; published <1% hallucination-rate SLO; in-canvas “why did the AI suggest this?” transparency; AI Performance Watchdog auto-flags off-brand outputs in the Performance Loop.
  • R3 · Write with AI global ungate blocked by Intuit Trust & Safety / legal timing. Policy clearance is the largest unknown in the schedule. Mitigation (P3 + P2): Run policy + product tracks in parallel (orchestration move #3); ship the product fix (Brand Voice 2.0 + re-introduction campaign + quality lift) without waiting for the geo unlock; offer paid global AI add-on as fallback while ungate processes; do not let policy block product progress.
  • R4 · Canva ships AI 3.0 with ESP-native send during FY27 and eats the unified-builder narrative before we ship it. Canva’s 2026 trajectory points at marketing automation. Mitigation (P2 + P4): Ship Creative AI Depth (P2) in 0–9mo to neutralize the design-AI gap; ship Send-Time Intelligence (P4) in 6–18mo because Canva structurally cannot replicate the ESP signal moat without buying or building an ESP. Even if Canva moves, our moat is the productized send loop, not the creative AI ceiling.
  • R5 · Engineering capacity is over-committed; orchestration moves don’t happen and pillars ship sequentially instead of in parallel. The most common failure mode for a 5-pillar program. Mitigation (cross-pillar): Lock the +30% Classic-migration capacity ask before kickoff; publish the Builder SLO error-budget policy that pauses new complexity when the floor slips (P1.5.3); use the Initiative Canvas’s sub-theme ownership matrix to assign one accountable PM per sub-theme; weekly portfolio review of the three orchestration-move dependencies.

Recommendation — what we are asking the exec sponsor to approve

Approve the unified AI-first builder strategy — five pillars in parallel, three orchestration moves, six credibility moments, sized to deliver the ~$21M Revised Goals FY27 ARR target while establishing the foundation for FY28+ category leadership. Specifically:

(1) Commit to the unified-builder posture publicly. One canvas, one Brand Kit, one AI, one collab, one reporting model across email + SMS + Push (Q5) and the future channels we add. The unified-builder narrative is the umbrella for every Q’ly credibility moment and the answer to the Canva-and-Klaviyo pincer.

(2) Commit to AI-first as the product posture, not a feature. AI is in every authoring step (setup, copy, image, layout, personalization, compliance, performance), grounded in customer data + Brand Kit + product catalog, with a published <1% hallucination-rate SLO. Approve the global Write with AI ungate path (product Q1; policy Q4) and the new Creative AI Depth pillar (P2) as the Canva-counter.

(3) Approve the +30% Classic-migration engineering capacity ask for the two-quarter window covering NEB Code Mode + funded migration + Classic sunset comms. This is the single largest derisking action in the plan ($1–2M ARR at stake) and the prerequisite for the unified-builder narrative externally.

(4) Approve the Builder SLO operating contract (P1.5) as a published, customer-facing commitment — uptime ≥99.9% / render fidelity ≥99% / WCAG AA on critical flows / hallucination <1% — with error-budget policy that pauses new complexity when the floor slips. This is the trust foundation everything else compounds on.

(5) Approve the cohort-level scorecard from Revised Goals as the FY27 performance contract — Paid $6.7M + Free $8.7M + Trial $5.6M = ~$21M — with quarterly review against the time / trust / money customer-outcome metrics published in “What winning looks like” above. Do not headline a single “editor adoption” number.

The ask in one sentence. Approve the strategy, the +30% migration capacity, the Builder SLO operating contract, and the cohort scorecard — and let the team ship one credibility moment per quarter against a single unified-builder narrative for the next six quarters. We have the assets no competitor has. We have not yet productized the win. This memo is the plan to do that.


Customer From → To — the six transformations that matter

The strategy succeeds when the customer’s lived experience changes in these six ways. Each row pairs today’s functional and emotional cost with the FY28 functional and emotional benefit, and names the pillar that delivers it. Each row is tagged with the primary customer outcome it produces.

Today — functional + emotional cost FY28 — functional + emotional benefit · outcome Pillar
NEB email looks correct in the editor, breaks in the inbox. Brand Kit occasionally drops colors. Emotional: “I can’t trust the send.” Published Builder SLOs + render fidelity ≥99% + Brand Kit reliability monitored. Pre-send hallucination + audience-confirm guardrails. 🛡 The marketer ships with their eyes closed. P1
AI imagery is generic stock; layouts feel static; Canva-grade output requires a Canva round-trip. Emotional: “Mailchimp isn’t a design tool.” Dream Lab + Magic Layers + conversational editing + Brand Voice 2.0 + Memory + MCP — all grounded in Brand Kit + product catalog. ⏱ + 💰 Canva-grade creative output without the round-trip; right product image, not stock. P2
Signup → first send takes 14–21 days; non-ecom verticals don’t see themselves in the templates; Free tier is degraded. Emotional: “I haven’t gotten deep enough into it yet.” AI Email Setup Agent: URL → live campaign in <30 min, brand-applied, vertical-fit, Write with AI usable globally. Free uplift + engagement-based pricing counter. ⏱ First value before competitors finish onboarding. P3
Send goes out at one store-level time; no per-recipient personalization; renewal stuck on “opens”; builder learns nothing from yesterday’s send. Emotional: “I can’t prove the ROI to my boss.” Send-Time Personalization + Performance Loop + in-canvas revenue per recipient + per-profile A/B + Shield + Cross-Domain Agent. 💰 The builder gets smarter every send because the ESP signal is productized inline. P4
Email and SMS in two surfaces; copy-paste; reformat; preview separately; “unified” is a billing claim. Emotional: “Mailchimp says omnichannel; the product feels single-channel.” One canvas: Universal Content + email + SMS + Push, shared blocks, cross-channel preview, one reporting view, Brand Kit propagated. ⏱ + 💰 Compose once, ship everywhere — the unified-builder narrative literally true. P5
Single editor at a time; agencies rebuild brand per client; multi-brand teams use one Brand Kit with workarounds; Classic / NEB bifurcation forces rebuilds. Emotional: “Mailchimp feels pre-Google-Docs and pre-Notion.” Real-time co-edit + @-mention comments + approval flow + multi-brand kits + cross-account brand inheritance + NEB Code Mode + funded Classic migration. ⏱ + 🛡 Teams work natively in MC; agencies inherit brand at scale; Premium / agency have NEB they can stay on. P5
Build Plan · P4.2.1 flagship wedge

Conversational Email Editor — Skills, Tools, Context

Skills, tools, and context required to ship a Brand-Kit-aware conversational email + SMS editor inside Mailchimp's Intuit Assist surface. Sequenced into 3 phases against Klaviyo Marketing Agent, Canva Magic Studio, and Shopify Email. Translates Initiative Canvas P4.2.1, P4.2.2, P4.2.3, P4.4.1–4.4.6, P3.1.4, P5.1, P2.1, and Strategy Bet B4 into an engineering build sheet.
12 skills · 18 tools · 14 context sources
3 phases · 18 months
12
Skills (agent capabilities)
18
Tools (system actions)
14
Context sources
3
Phases · 18-month sequence
Strategic anchor — why this is Mailchimp's wedge. Klaviyo's AI is feature-bound (subject lines, Image Remix). Postscript trains AI on PDFs but doesn't do canvas-level edits. Stensul is form-driven. Canva is design-only, not campaign-aware. Shopify Email has no AI authoring of substance. The unique combination Mailchimp can ship first: Brand Kit + Intuit Assist + 260+ templates + 300+ ecom integrations + 12M+ user distribution + conversational UX. No competitor has all five inputs. Source: Klaviyo Brief + Klaviyo VoC.

01Skills — what the agent can do

A skill is a discrete cognitive ability the agent invokes in conversation. Each skill maps to a customer job-to-be-done.

T = saves timeE = expert guidanceR = risk reduction
SkillWhat it isCustomer pain solvedBenefitType
Campaign ScaffolderURL or intent → full email + SMS campaign with Brand Kit applied.Blank-page paralysis on day-1; slower to first value vs Klaviyo Marketing Agent.First send live in <30 min vs 14–21d median.T+E
Brand-Voice CopywriterGenerates / rewrites copy in customer's documented tone, audience, personality.Generic AI-sounding copy; rewrite tax after every generation.Solo marketers ship faster + sound like themselves.T+E
Block-Level Surgical Editor"Redo the hero in a friendlier tone with a CTA to spring sale."Re-clicking through builders for small changes; can't target blocks conversationally.Iteration speed up 3–5×; non-designers steer copy + layout.T
Layout ArchitectPicks block structure based on intent + ICP (promo, newsletter, win-back, abandoned cart).B2B / nonprofit / restaurants forced into ecom-shaped templates (UR Bet #3).Right structure first time; opens 4 underserved verticals.E
Visual Generator (Brand-aware)Hero / product / lifestyle imagery with Brand Kit colors, fonts, and product catalog context.Stock-image dependence; off-brand visuals; expensive Canva round-trips.Right image, not stock image; ecom conversion lift.T+E
Cross-Channel AdapterCompresses email content into SMS / push / in-app variants — same intent, channel-correct format.Two-surface composition; copy-paste between email + SMS; brand drift.One ask, multi-channel send; SMS attach rate up.T
Personalization DirectorPicks dynamic blocks per recipient (last product, lifecycle stage, geo, predicted next).One-size-fits-all sends; LTV leakage on browse / cart / post-purchase.Per-recipient lift on conversion (Klaviyo Image Remix parity).E
Performance CriticPre-send audit: subject line, send time, deliverability hints, predicted open / CTR vs baseline.Customers ship mediocre campaigns and learn by trial-and-error.Results lift before send; replaces a marketing consultant.E
Compliance & Accessibility CoachReal-time TCPA / CAN-SPAM / GDPR / WCAG AA review; blocks on critical violations.$57K TCPA incident cited in HVC Risk Map; EU EAA exposure; missing alt-text / contrast.Eliminates the largest single brand-risk vector in SMS.R+E
Brand-Style Transferer"Make this look like our spring campaign" — extracts style from one, applies to another.Style drift across campaign series; manual restyling for brand consistency.Series feels intentionally connected; no Klaviyo equivalent.T+E
Migration TranslatorConverts Classic / pasted HTML / competitor exports into NEB blocks with style preservation.181-template migration tax; "rebuilt the same email three times" (G2).Days → minutes; protects $1–2M Classic ARR (Strategy R1).T
A/B StrategistGenerates meaningful variants; per-profile winners; explains hypotheses.Weak variants; one-global-winner waste; lift-killing tests.Per-profile A/B parity (Klaviyo Personalized A/B).E

Source mapping: Initiative Canvas P4.2.1 (Conversational journey editing) · P4.2.2 (Brand-style transfer) · P4.2.3 (Prompt-first email mode) · P4.4.1–4.4.6 (AI image gen + Klaviyo-counter trio) · P3.1.4 (AI Email Setup Agent) · Strategy Bet B4 (conversational AI + global ungate).

Build Plan · Page 2 of 4 · Tools

System actions the agent can call

Tools are the concrete API / system surfaces the agent invokes. Skills compose tools; one skill typically calls 3–6 tools. Grouped by surface area for engineering ownership.
18 tools

2.1Brand & content

ToolWhat it doesCustomer problem it unblocksBenefit
BrandKitReaderPulls logos, colors, fonts, voice, button styles into agent context every turn.Brand inconsistency across AI generations; "why doesn't the AI use my font?"Brand Kit flows through every output (closes HVC #10).
UniversalContentCRUDRead / write / version Universal Content blocks (P2.1 primitive).Saved-content scattered per template; no global propagation.Edit-once-propagates-everywhere primitive (Klaviyo parity).
BlockMutatorInsert / update / delete / reorder blocks in NEB canvas with optimistic UI.Manual click-drag for every change.Conversational edits land in canvas immediately.
ImageGeneratorText-to-image with Brand Kit conditioning + product-catalog grounding.Stock-image dependence; Canva round-trips.Brand-correct hero images in seconds (Image Remix parity).
ProductCatalogLookupReads Shopify / WooCommerce / BigCommerce / Square / 300+ ecom integrations.Generic content disconnected from what's in stock / on sale.Right product per email; conversion lift.
ContentStudioSearchSemantic search over the customer's DAM (assets, brand files, past campaigns).Customers re-upload assets they already have.Asset reuse goes up; closes Content Studio IA gap.
TemplateLibrarySearchVector search over 260+ templates filtered by industry + intent + layout.DTC bias; B2B / nonprofit underserved (UR Bet #3).Industry-fit starting point; activation accelerates.
BrandExtractor (URL)Crawls a URL, extracts logo / colors / fonts / voice into Brand Kit on signup or refresh.Cold-start cost on signup; manual restyling.First email pre-branded on day-0 (closes <12mo cohort gap).

2.2Channel, governance & performance

ToolWhat it doesCustomer problem it unblocksBenefit
SMSCompressorRenders email block into SMS: char-limit-aware, opt-out compliant, branded short links.Two-surface composition; manual SMS rewrite per email.One ask → multi-channel; SMS depth + Brand Kit applied.
InboxPreviewRenders email across Gmail / Outlook / Apple Mail / iOS / Android with light + dark mode.Forwarded-mail divergence; "looks correct in editor, breaks in inbox."Closes HVC #3 ($1,820/mo cited rendering bugs).
AccessibilityLinterReal-time WCAG AA: alt text, contrast, link purpose, heading order.Pre-send checklist misses contrast + link purpose; EAA exposure.Regulatory readiness; deliverability lift.
ComplianceCheckerGeo-aware TCPA / CAN-SPAM / GDPR / CASL ruleset applied per send.$57K TCPA incident; default-on append + duplicate opt-outs.Largest single brand-risk vector eliminated.
SendTimeOptimizerPer-recipient send-time prediction from engagement history (Smart Send parity).Store-level send-time only; one-size-fits-all timing.+10–30% open lift cited in Klaviyo case studies.
ABTestProposerGenerates and ranks variants; proposes per-profile winners with hypothesis explanations.Manual variant creation; one-global-winner waste.Per-profile A/B parity (Klaviyo Personalized A/B).
PerformanceReporterInline revenue / opens / CTR / unsub per block + per recipient (Klaviyo in-builder revenue parity).Renewal stuck on "opens" instead of "$ shipped."Decision-grade reporting at the block level.
CJBStepWriterWrites / edits Customer Journey Builder steps from conversation ("add a 3-day delay then SMS").Cross-product friction: campaign editor and CJB don't share AI.Campaign + automation authored in one conversation.
ApprovalRouterRoutes to designer → copywriter → manager with @-mention comments + version snapshots.Approval cycles happen outside Mailchimp (Slack screenshots).Premium / agency governance need met in-product.
DocsRetrieverVector search over help center + product docs + community threads for "how do I…" answers.Customers ask procedural questions; LLM hallucinates without grounding.Grounded answers; replaces support tickets for setup.
Build Plan · Page 3 of 4 · Context

Knowledge the agent needs at every turn

Context is the persistent + per-session data the agent reasons over. The differentiator vs every competitor is the breadth of Mailchimp-owned context — Brand Kit + audience + campaign history + product catalog + 12M+ customer flywheel. Generic LLMs don't have this.
14 context sources
Context sourceWhat it containsWhy the agent needs itCustomer benefit
Brand KitLogos, colors, fonts, voice, audience descriptors, button styles, multi-brand sub-kits.Every generated copy + image + layout must respect brand.Brand consistency at zero effort; closes HVC #9 multi-brand.
Universal Content libraryEdit-once-propagates blocks (P2.1); usage metadata per block.Agent prefers reusing existing UC blocks vs regenerating.Brand drift goes to zero; edits compound across sends.
Past campaigns + performance12 months of opens / CTR / revenue / unsub per campaign per segment.Critic + A/B Strategist reason against the customer's own baselines.Recommendations are personal, not generic.
Audience profiles + segmentsSubscriber attributes, lifecycle stage, predicted CLV, last-engagement.Personalization Director picks dynamic blocks per recipient.Per-recipient relevance (LTV protection).
Product catalogLive SKU / price / inventory / category from 300+ ecom integrations.Right product surfaced per email; out-of-stock excluded.Ecom conversion lift no SMB tool can match.
Industry / vertical templates260+ Mailchimp templates tagged by industry + intent + layout type.Layout Architect grounds choices in proven structures.B2B / ProServ / nonprofits get fit-for-purpose starts.
Compliance ruleset (geo-aware)TCPA, CAN-SPAM, GDPR, CASL, EAA — country-specific opt-out + accessibility law.Compliance Coach blocks on real violations, not false positives.Risk reduction (avoids $57K-class incidents).
Per-recipient engagement historyTime-of-day open patterns, channel preference, click history.Send-Time Optimizer + Channel Affinity decisions.Smart Send parity; +10–30% open lift.
Sender reputation + deliverabilitySPF / DKIM / DMARC status, bounce rate, inbox placement by ESP.Performance Critic warns before sending into spam.Inbox placement protected (78.35% audit issue addressed).
Cross-channel campaign objectUnified email + SMS + push step container (P5.1).Cross-Channel Adapter writes into one object, not two surfaces."Unified" becomes authoring-real, not billing-claim.
Live editor session stateWho else is editing, lock state, pending changes, version history.Real-time collaboration; conflict-free agent edits.Multi-author co-edit (P5.3 — Klaviyo doesn't have this).
Customer lifecycle stageNew (<1mo) / activating (<12mo) / Established / Abandon — and tier (Free / Standard / Premium).Agent calibrates: hand-hold new users, defer to power users.Right level of help per customer (UR Workflow Shapes).
Vertical conventionsBest-practice patterns per industry: ecom (cart abandon), B2B (nurture), nonprofit (donation).Layout Architect + Critic apply industry-correct heuristics.Expertise embedded; replaces a marketing consultant.
Help-center + product docsIndexed help articles, community threads, video transcripts.Docs Retriever grounds procedural answers.Setup questions answered in-product, not support tickets.
Build Plan · Page 4 of 4 · Sequencing

18 months across 3 phases · how Phase 1 wins

Sequenced for fastest credible PMF (Phase 1) → unique-in-market differentiation (Phase 2) → best-in-class moat (Phase 3). Each phase ships one demonstrable credibility moment. Aligned with Initiative Canvas P4 (AI), P2 (Universal Content), P5 (Unified canvas + collab).

4.1Phase plan

Phase 10–6 mo · PMF + parity

Goal: ship "AI that ships campaigns, not a demo" — match Klaviyo Marketing Agent + Image Remix. Beat Canva on copy. Beat Shopify on depth.

Skills

  • Campaign Scaffolder
  • Brand-Voice Copywriter
  • Block-Level Surgical Editor
  • Visual Generator (Brand-aware)
  • Layout Architect
  • Performance Critic (basic)

Tools

  • BrandKitReader · BrandExtractor
  • BlockMutator · UniversalContentCRUD
  • ImageGenerator · ProductCatalogLookup
  • TemplateLibrarySearch · ContentStudioSearch
  • InboxPreview · ABTestProposer

Context

  • Brand Kit · Universal Content library
  • Industry templates · Product catalog
  • Past campaigns + performance
  • Customer lifecycle stage
Credibility moment

URL → on-brand campaign in <3 clicks · matches Klaviyo Marketing Agent · beats it on Brand Kit fidelity.

Phase 26–12 mo · The wedge

Goal: ship the unique-in-market combination (P4.2.1). Brand-Kit-aware conversational journey editing that Klaviyo, Canva, and Shopify cannot match.

Skills (added)

  • Cross-Channel Adapter
  • Personalization Director
  • Brand-Style Transferer
  • Compliance & Accessibility Coach
  • Migration Translator
  • A/B Strategist (per-profile)

Tools (added)

  • SMSCompressor · ComplianceChecker
  • AccessibilityLinter · SendTimeOptimizer
  • PerformanceReporter · CJBStepWriter

Context (added)

  • Per-recipient engagement history
  • Cross-channel campaign object
  • Compliance ruleset (geo-aware)
  • Sender reputation + deliverability
  • Vertical conventions
Credibility moment

"Redo the hero in a friendlier tone with a CTA to spring sale, and write the SMS variant" — flagship demo. No competitor can ship this combination.

Phase 312–18 mo · Best-in-class

Goal: lock in the moat. Multi-brand, multi-author, autonomous monitoring, procedural agency. Beat Klaviyo on team workflows; beat Stensul on SMB UX.

Skills (added)

  • Performance Watchdog (autonomous)
  • Co-edit + Comment skill
  • Multi-brand context routing
  • Liquid / Code-mode skill
  • Procedural Help skill

Tools (added)

  • ApprovalRouter
  • DocsRetriever
  • VersionSnapshot · Multi-brand switcher

Context (added)

  • Live editor session state (presence)
  • Multi-brand kits per account
  • Help-center + product docs (RAG)
Credibility moment

Two marketers + the agent co-edit one campaign across 3 client brands; agent monitors send performance and flags regressions before customer notices.

4.2Phase 1 head-to-head — how we win

PMF is decided by what ships in the first 6 months. The Phase 1 stack is sized to credibly out-execute each competitor on a different axis — without depending on Phase 2 or 3 features.

DimensionKlaviyo Marketing AgentCanva Magic StudioShopify EmailMailchimp Phase 1 advantage
URL → campaignYes — 3 clicks to flow.No — design tool, not campaign.Limited — storefront-bundled.Match: Campaign Scaffolder + Brand Kit + 260+ templates · beat on brand fidelity.
Brand-aware copySubject-line AI only.Generic copy AI; not brand-trained.None of substance.Win: Brand-Voice Copywriter trained on Brand Kit voice + audience.
Brand-aware imageryImage Remix (hero variations).Best-in-class design AI but not campaign-aware.Stock library only.Match Klaviyo + go further: Brand Kit + product catalog grounding.
Block-level conversational editNo — feature-bound AI.Design-only edits, not copy + structure.No.Win uniquely: Block-Level Surgical Editor (P4.2.1 wedge starts here).
Industry fitDTC-biased templates.Generic — not vertical.Ecom only.Win: Layout Architect + B2B / ProServ / nonprofit templates (P3.2).
Pre-send critiqueAI auto-monitors (post-send).None.None.Match: Performance Critic against the customer's own baseline data.
Distribution + pricingHigher tier; Feb '25 billing damage.Design-tool pricing.Bundled but limited.Win: 12M+ users + engagement-based pricing counter (I-3.4.3).
The Phase 1 promise to leadership. By month 6, a Mailchimp customer pastes their website URL and gets a complete, on-brand, multi-block email campaign with hero imagery, copy, layout, and a critic-reviewed pre-send check — in under 3 minutes. That single demo neutralizes Klaviyo Marketing Agent, leapfrogs Canva on campaign-awareness, and makes Shopify Email feel like a stub. Phase 2 then ships the wedge no one else can match.

Source mapping: Initiative Canvas P4.2.1 / P4.2.2 / P4.2.3 / P4.4.1–4.4.6 / P3.1.4 / P5.1 / P2.1 · Strategy Bet B4 (conversational AI + global ungate) · VoC #3 (geo-gate) · Klaviyo Brief (Marketing Agent, Image Remix, Smart Send, Personalized A/B, AI auto-monitors).

Tab 17 · Freddie / AI Email Generator Prototype Assessment

How does the new design score against the strategy?

Structured assessment of the new Freddie / AI Email Generator prototype (ai-email-generator-steel.vercel.app) against this brief's three load-bearing artifacts — HVC Risk Map (17 cited themes / ~$95K/mo), User Research (5 bets / Discovery table / 5 Workflow Shapes), and Revised Goals (~$21M ARR / 10 levers). Plus a pre-mortem on new bugs and "move my cheese" risks the design introduces. Full decomposition of the prototype: github.intuit.com/dprabhakara/ai-email-generator-decomp (29 screenshots).
v1.0 · 5 pages · May 2026
Confidence: HIGH on coverage mapping · MED on $ capture estimate
0 / 17
HVC themes directly solved (5 partial; 12 not addressed; 4 may worsen)
~$7.2K
Cited HVC MRR addressed (7.6% of $95K total — $57K SMS TCPA unchanged)
~$10–15M
Plausible Revised Goals capture (of $21M; mid ~$12.4M = 59%)
14
"Move my cheese" risks identified (5 critical · 6 moderate · 3 low)
Executive read in 60 seconds. This is the right AI surface for FY27 but it is not yet the editor strategy. It addresses the activation funnel beautifully (T1 trial + F2 free + PA1 paid adoption = ~58% of the revised goal) and the brand/voice consistency story credibly. It does not touch the dollar concentrations (SMS TCPA, Brand Kit reliability, rendering parity, multi-author, custom-code) and it makes several Phase-1 Migration prerequisites harder, not easier. Ship it as the front door with the strategy's Pillars 1+2+5 work shipping concurrently — not as a substitute for them. The $6–18M downside band from unmitigated critical risks is comparable to the $10–15M upside, so mitigations are launch-blocking, not P2 follow-ups.

01What the prototype actually offers

The Freddie prototype reshapes Create around an AI-first chat surface that takes a prompt or quick-prompt chip, returns an editable strategy brief (Goal / Date / Recipients / Promo / Focus Metric / Featured Products / Visual Style), then on approval renders a complete email in a split editor (chat left, iframe canvas right) with suggested follow-up chips (Add a CTA / Change the theme / Check for accessibility / Optimize for mobile) and a floating theme popover (8 presets in Light/Dark). Manual editing falls back to the classic Mailchimp drag-drop builder (Blocks / Sections / Styles). A unified 8-channel tab bar (Email / SMS / WhatsApp / Automation / Form / Survey / Social post / Campaign) sits at the top — though most non-email tabs are stub surfaces with hero CTAs only. A Brand Kit modal covers My business / Logos / Colors / Fonts / Buttons / Brand voice / Social links. Send actions include Send a test email and a split Send email button with Save draft / Export HTML.

02How to read the three pictures (the synthesis)

Picture 1 · Where this design wins

  • T1 Trial activation — biggest single lever in the goal ($5.0M / 89% of trial)
  • F2 Free activation — biggest single Free lever ($3.6M / 41% of free)
  • PA1 Bulk adoption — closes paid "Unexplored" residual (~$1.9M)
  • UR Bet 2 Discovery — chip-prompts surface capability at moment of need
  • UR Bet 3 vertical fit — structurally ready (content still DTC-flavored)
  • CB1 Time to Activate — 5d→2d Klaviyo cadence plausible
  • Workflow Shapes #1 + #5 — Fast Monday + low-frequency both fit

Picture 2 · Where this design doesn't help

  • $57K SMS TCPA — needs Initiative I-5.2.3, not this surface
  • Brand Kit reliability — needs I-1.2.1/2/3 data fixes
  • NEB rendering parity — needs email-render-pipeline wired to CI
  • Multi-author co-edit — needs Pillar 5.3 Q5 ship
  • Custom code / Liquid — needs NEB Code Mode (Pillar 2.2.3, Q3)
  • NEA→NUNI migration — needs the 3-phase parity-gated playbook
  • CSAT-to-neutral ($5.6M, 27%) — needs Builder SLOs, not new AI

Picture 3 · Where this design might hurt

  • HVC #6 reverse — legacy templates may not surface in recents
  • HVC #12 stronger — AI defaults make Premium feel more forced
  • HVC #8/#10 amplified — bad Brand Kit data poisons every AI output
  • HVC #16 unchanged — SMS TCPA risk persists on new surface
  • F4 CSAT regression — Brand-context banner = upgrade pressure on Free
  • Strategy R1 accelerated — Premium / agency feel pushed harder

Source: Prototype decomposition at github.intuit.com/dprabhakara/ai-email-generator-decomp (29 screenshots + 11 docs covering routes, all 8 Create tabs, Brand Kit modal, Prototype settings, end-to-end generation flow, manual mode, design tokens, content inventory, runtime). Scored against this brief's HVC Risk Map, User Research, and Revised Goals.

Tab 17 · Page 2 of 5 · HVC + UR coverage

Q1: How many of the bugs and barriers does it solve?

All 17 HVC themes scored against the prototype, then the 5 UR bets + Discovery table + 5 Workflow Shapes. Verdicts: SOLVES directly addresses the cited root cause · PARTIAL touches the symptom but not the root · MISS design is silent or out-of-scope · WORSENS design likely makes the problem harder.
0 SOLVES · 5 PARTIAL · 12 MISS · 4 WORSEN

2.1HVC Risk Map — all 17 themes

#Theme$/moVerdictRationale
1No legacy → New Builder migration; bulk template updates impossible$330MISSPrototype has no migration tooling. The 181-template customer's "system where templates share content like Brand Kit but more substantial" is the Universal Content ask — the prototype has saved/template content in iframe previews but no propagation primitive. Recents/templates carousels actually replicate the template-scoped saved-content pattern customer is complaining about.
2Support / product dead-ends on legacy → New conversion$504MISSService-design problem, not authoring. Out-of-scope for the prototype.
3Rendering diverges: forwarded mail, mobile line-breaks, image shrink, Ctrl+K Firefox/Chrome, light/dark, bg images$1,820PARTIAL3-way viewport radio (desktop/mobile/split) + Preview button increase trust the customer is seeing what subscribers see. But: doesn't fix the underlying render-divergence bugs. Without email-render-pipeline wired into CI (Repo Intel finding), preview parity is still aspirational. Addresses the trust symptom, not the engineering root cause.
4Multi-author save conflicts — no presence indicator$340MISSSingle-editor by design. No presence, no co-edit, no conflict UI. This is UR Bet 4 and Pillar 5.3 — separate scope. Adjacent risk: the conversation sidebar could give false signal that conversations are shared/teamed.
5Dual builders + custom code — block ordering glitches, "templates moved" nav$410PARTIALPrototype shows one editor, eliminating dual-surface confusion at the navigation layer. But no HTML/code escape hatch (the reason Premium anchored on Classic). Block-ordering runtime bug not fixed. Addresses surface confusion; doesn't address custom-code need.
6Template list / campaign wizard — NEB templates not surfacing$1,950PARTIAL + WORSE"Start from recent email" + "Start from template" carousels surface NEB-styled previews directly — right pattern. But no indication legacy / custom-coded templates also surface. "View all templates" is a placeholder. For the inverse customer (Classic templates anchor), the design likely worsens — HVC #6 reverse. See pre-mortem risk #1.
7Brand fonts not usable in landing pages / forms; iPhone fallbacks$655MISSLP / signup-form font rendering is out-of-surface. Brand Kit modal lets you upload fonts but the LP-application bug isn't in scope.
8Brand Kit regression / stale kit / colors dropped (Feb 2026 incident)threadMISS + WORSEData-correctness incident, not design. But the prototype centers Brand Kit in every AI surface — if Brand Kit data is wrong, AI-generated outputs amplify the wrongness across every send. Blast radius goes from "one slot on Brand Kit page" to "every AI-generated email." See pre-mortem risk #6.
9Logo asset metadata / multi-brand kits$2,460MISSBrand Kit modal supports a single brand kit. No multi-brand picker in AI composer, no per-conversation brand switcher, no sub-brand concept. Agencies + multi-brand teams not served. Initiative I-1.2.3 entirely missing.
10Font upload / Creative Assistant mismatch$3,350MISS + WORSEBrand Kit Fonts section shows a hardcoded dropdown of 23 fonts — DIN 2014, Asul, Readex Pro (the named HVC fonts) are not in the list and there is no upload affordance visible. Worse than current state. See pre-mortem risk #7.
11Creative Assistant rediscovery / shrink — banner workflows$2,650PARTIALAI image generation + 8 theme presets are adjacent to what customers want (branded banners inside MC, not Canva). But no explicit banner / social asset workflow. Could be positioned as "Creative Assistant 2.0" but doesn't restore the workflows the named customers used.
12Content Studio instability + forced New Builder narrative$621PARTIALSingle-editor design softens "forced to New Builder" tone. But Content Studio image-loading bug not fixed. And the prototype's implicit messaging ("Mailchimp AI is the way you make emails now") is more of a forcing function, not less.
13Canva ↔ Mailchimp — sync loss, email sent without graphic$2,500+MISSNo Canva integration visible in prototype. Asset attach is a generic + button. Canva sync still broken at data-pipeline layer. Worse: design pulls more customers into the in-canvas flow that displaced Canva, so pressure on broken sync goes up.
14SMS / journey reporting — empty, N/A, hard to find$1,386MISSSMS reporting is downstream of editor. Generic Home dashboard segment toggle changes the active pill but same data. Real SMS reporting (Theme 14) not in scope.
15SMS credits — negative balance hidden, undelivered burn$3,592MISSNo SMS credits UI. Composing SMS in this design produces a chat conversation and a hypothetical render — none of the credit-balance, opt-out, delivery-cost machinery is present. The Send CTA in an SMS conversation likely creates the exact silent-burn problem the customer cited.
16Duplicate TCPA opt-out in sent SMS ($57K HVC)$57,000MISS + WORSESingle largest cited HVC in the brief. The prototype's SMS composer doesn't have any of the TCPA guardrails (I-5.2.3). Worse, the AI chip "Send a flash sale alert via text" could trivially produce non-compliant opt-out content with no AccessibilityLinter / ComplianceChecker wired in. $57K incident pattern more likely to recur on this surface, not less. See pre-mortem risk #4.
17SMS merge depth · MMS POCMISSNo merge-tag depth, MMS attach UI, or branded short-link config. SMS in prototype = single chat-generated message string.
0
SOLVES directly · $0 / $95K cited = 0%
5
PARTIAL (#3, #5, #6, #11, #12) · ~$7.2K/mo = 7.6%
12
MISS · ~$73K/mo = 76.8% (incl. $57K TCPA = 60% alone)
4
WORSEN (#6, #8, #10, #16) · overlapping

2.2User Research — 5 UR bets + Discovery table + Workflow Shapes

The 5 UR bets

BetWhat customers wantVerdictRationale
Bet 1Saved blocks / section reusePARTIAL"Sections" panel in manual mode (Hero, Image+Text, Header, Product List, Coupon, Button, Text, Footer, Product Grid, Banner CTA) — these are layouts to insert, not blocks that propagate edits. No edit-once-applies-everywhere primitive. Matches the surface, misses the propagation.
Bet 2Discovery / activation for high-frequency usersSOLVESThe AI surface itself is discovery: suggested-prompt chips on every tab, follow-up chips on the editor ("Add a call to action", "Change theme", "Check accessibility", "Optimize for mobile"), Home dashboard "Done for you" pattern. Strong fit for Clint (DRAFT-resurrect) and Bianka (proactive A/B suggestion).
Bet 3B2B / ProServ template gallery laneSOLVES intentTemplates section has 10 templates with category pills (Announcement, Invitation, Abandoned cart, Post-purchase, Editorial essay). Several skew non-ecom. But actual content still DTC-flavored ("Your Brand", "Spring Collection"). Structure supports vertical fit; content still defaults to DTC. Initiative-level fix needed.
Bet 4Real multi-author editingMISSSame as HVC #4. No presence, no co-edit, no commenting, no version history. Single-editor design throughout.
Bet 5Direct manipulation upgrades (asymmetric resize, 1-click 2-column, post-hoc A/B, Brand-Kit CTA defaults)PARTIALManual mode preserves existing NEB drag-drop builder, so Bet 5 improvements would still need to ship in NEB itself. However, AI surface bypasses much of this need by generating layout — for Workflow Shapes #1+#5, Bet 5 becomes less load-bearing. For Shapes #3+#4, Bet 5 is still the unmet need. Bypassed for some personas, not solved for others.

Discovery table — multi-year undiscovered features

CustomerUndiscoveredDurationHelped?Rationale
Bianka KissA/B testingYearsPARTIAL"Optimize for mobile" follow-up chip is A/B-adjacent; A/B not surfaced by name. Multivariant lives in a Scratch-row card user must notice.
Jack HallyNew Email Builder4–6 yrs on inherited legacy templateMISSJack stays on legacy template he inherited; prototype has no "your account is on Classic — try NEB" prompt. Migration awareness gone.
Jeffrey DavisMy Products / Woo product pull3.5 yrsPARTIAL"Featured products" in strategy panel could surface this — only if catalog connected. No connection prompt visible.
Clint BartleyWelcome automation (in DRAFT)1 yr (first send never happened)SOLVESRecent cards on Email tab show Drafts with "Edited X" sub. Clint sees his Draft with "Create" overlay — high probability of resurrection.
Wes TurnerSaved blocks (pre-ship)At time of callPARTIALSame as Bet 1 — Sections panel surfaces inserts but doesn't propagate edits. Wes feels partially seen.

Workflow Shapes

ShapeExamplesPrototype fitRationale
#1 Fast Monday senderAndrew, Andrea, Kim, ClintSTRONGQuick-prompt chip + recent card flow gets them to sendable email in minutes.
#2 All-week ad-libberJack Hally (10–20 logins/day)WEAKJack edits a living newsletter; the chat-conversation paradigm doesn't fit "continuous edit", no save-conflict UX.
#3 Brand-first methodicalWes, BobMIXEDBrand Kit modal supports setup; manual mode preserves precision; Sections help; Saved blocks propagation missing.
#4 Third-party-in-loopAndrea (Bee.io), Wes (Canva), Jack (Express)MIXEDAI image gen + Visual Style picker theoretically reduces Canva need; no migration tooling from Bee/Express.
#5 Low-frequency / discovery gapShannon, Matt, GillesSTRONGChip prompts + suggested follow-ups make capability surface itself.

UR coverage roll-up: 2 of 5 bets fully addressed (Discovery, vertical fit) · 2 partial (Saved blocks, Direct manipulation) · 1 not addressed (multi-author). Discovery table: 1 of 5 fully (Clint) · 3 partial · 1 unhelped (Jack). Workflow shapes: 3 of 5 well served, 2 of 5 poorly.

Tab 17 · Page 3 of 5 · Revised Goals capture

Q2: How much of the $21M target can this design plausibly capture?

Per-lever scoring against the Revised Goals (Tab 11): 3 cohorts × 10 levers + 5 customer-benefit metrics. Capture % asks: of the editor-attributable portion of each lever, how much does this design credibly move? Full-stack $ = editor-share × capture-% × lever-$.
~$10–15M capture band · mid ~$12.4M · 59% of $21M

3.1Paid cohort — $6.7M target · 4 levers

LeverTarget$AlignmentCapture est.Rationale
PA1 Bulk adoption92.7% → 95%$1.9MSTRONG$1.3–1.7M (70–90%)AI surface is textbook conversion of "Unexplored" 7.3% paid users. AI Setup Agent + Brand Kit auto-applied are named mechanisms; prototype implements first two. Some structural non-users (API-only, dormant multi-seat) unreachable.
PA2 Bulk activation60.6% → 67%$0.8MMODERATE$0.3–0.5M (40–65%)Activation is "touched → Established" — habitual sending. AI surface helps the first send. Doesn't help repeat sending (PA3). The −2.4pp YoY decline is the bleeding edge per Nuni audit — only addressed if "your draft is here" cards surface old abandonders.
PA3 30d repeat send83.2% → 87%$0.9MWEAK$0.2–0.4M (20–45%)Repeat usage driven by lifecycle/trigger campaigns + onboarding + omnichannel (L4 lever in Strategy Memo). Prototype doesn't change the trigger model or per-recipient relevance. Conversation history sidebar could lift repeat (Clint pattern) but only if well-surfaced.
PA4 Net CSAT−29.3 → 0 (neutral)$3.1MMIXED$0.6–1.2M (20–40%)CSAT depends on Builder SLOs (P1.5), parity polish, render fidelity, AI quality, Klaviyo gap closures. Prototype adds AI quality risk (hallucination liability) without addressing rendering/SLO foundations. New surface feels modern → lifts CSAT. New surface that produces wrong-brand emails or hallucinated promo codes → lowers CSAT. Roll the dice.

Paid subtotal capture estimate: ~$2.4–3.8M of $6.7M (36–57%).

3.2Free cohort — $8.7M target (biggest) · 4 levers

LeverTarget$AlignmentCapture est.Rationale
F1 Free adoption75% → 82%$0.9MSTRONG$0.7–0.9M (75–95%)AI surface is the right tool for first-touch on builder for free users. Brand Kit auto-extract on signup (named in I-3.1.2) closes this; prototype has the receiving UI for it (Brand Kit modal with URL importer).
F2 Free activation48.1% → 55%$3.6MSTRONG$2.4–3.2M (65–90%)Single biggest Free lever · single biggest revenue capture from this prototype. "Touched → Established" for a free user is roughly "did they send something they're proud of?" — AI generates sendable email in minutes. Recents/templates carousels close the loop.
F3 Free 30d repeat send73.4% → 80%$1.7MMODERATE$0.5–0.9M (30–55%)Repeat is engagement + trigger + lifecycle marketing. Prototype lifts repeat through conversation continuity and suggested-prompt chips but doesn't ship the deeper lifecycle mechanics (Smart Send Time, AI Performance Watchdog, omnichannel reminders).
F4 Free Net CSAT−29.3 → 0$2.5MMIXED$0.5–1.0M (20–40%)Same logic as PA4 — modernity boost vs hallucination risk. F4 also has the upgrade-pressure side effect: the brand-context banner ("Get better results by adding brand and business information [Open Brand Kit / Set up Brand Kit]") feels like upsell pressure on Free users, potentially lowering Free CSAT.

Free subtotal capture estimate: ~$4.1–6.0M of $8.7M (47–69%).

3.3Trial cohort — $5.6M target · 2 levers

LeverTarget$AlignmentCapture est.Rationale
T1 Trial activation 90d10.8% → 16%$5.0MSTRONGEST$3.5–4.5M (70–90%)Largest single lever in the entire $21M goal. Prototype is purpose-built for it. New signup, no campaigns yet, AI agent says "Create a welcome email for new subscribers" → 3 clicks → preview → send a test. T-1 was 13.8% before declining to 10.8%; recovering to 16% on the back of AI Setup Agent is highly plausible. This is where the prototype earns its keep.
T2 Trial 30d repeat72.8% → 80%$0.6MMODERATE$0.2–0.4M (30–65%)Repeat after first send needs lifecycle hooks and value reinforcement. Recents/templates carousel + suggested follow-ups help; lack of in-canvas revenue reporting (I-4.4.4) means customer doesn't see the lift, doesn't feel the loop.

Trial subtotal capture estimate: ~$3.7–4.9M of $5.6M (66–88%).

3.4Customer Benefit Metrics — CB1–5 (no $, leading indicators)

MetricT0 → FY27AlignmentRationale
CB1 Median Time to Activate5d → 2dSTRONGAI Setup Agent pattern is the named mechanism. 2-day Klaviyo cadence plausible with this surface.
CB2 Avg open rate28.27% → 35%WEAKOpen rate is subject line + send time + segmentation. Prototype generates subject lines; doesn't run Smart Send Time or AI Performance Watchdog. Industry benchmark gap unlikely to close from this alone.
CB3 Avg click rate1.70% → 3.0%WEAKClick rate is content quality + personalization + dynamic blocks. AI-generated content helps; lack of per-recipient personalization caps the lift.
CB4 RPME$1.74 → $2.50WEAKConversion lift needs personalization + send-time intelligence + omnichannel attribution. Prototype generates email; doesn't ship the optimization stack.
CB5 % MC share-of-channel-rev~15% → 25%MISSRequires omnichannel attach (SMS/Push/WhatsApp). Prototype shows tabs but only Email is functional.

3.5Revised Goals capture roll-up

CohortTarget $Capture estimateCapture %
Paid$6.7M$2.4–3.8M36–57%
Free$8.7M$4.1–6.0M47–69%
Trial$5.6M$3.7–4.9M66–88%
Total$21.0M$10.2–14.7M49–70%
Mid estimate~$12.4M59%
Single most important number. T1 Trial activation alone at 70–90% capture is $3.5–4.5M, which is 17–21% of the entire $21M goal. If this prototype only lifted trial activation and did nothing else, it would still be a financially meaningful FY27 ship. The residual $6–13M depends on: (1) Universal Content / saved-blocks shipping concurrently · (2) Render fidelity + Builder SLOs (Pillar 1.5) · (3) CSAT recovering on its own from "feels modern" tailwind · (4) SMS/omnichannel actually working (Pillar 5) · (5) In-canvas revenue surfacing (I-4.4.4, Klaviyo countermove).

Source: Revised Goals scorecards from Tab 11 (PA1–4, F1–4, T1–2, CB1–5). Capture estimates apply within the Tab 11 editor causal share assumptions (Paid adoption/activation 50%, Paid repeat 35%, Paid CSAT 30%, Free all 20%, Trial all 25%). My capture % asks "of the editor-attributable portion of each lever, how much does this design credibly move?" Full-stack $ = editor causal share × my capture % × lever $.

Tab 17 · Page 4 of 5 · Pre-mortem

Q3: What new bugs and "move my cheese" problems will this open up?

For each surface, asked: what existing customer expectation does this break? What new failure mode does it create? Severity = (1) Critical — likely HVC-scale escalations or revenue impact >$1K/mo each · (2) Moderate — friction but not escalations · (3) Low — annoyance, observable in NPS / Reddit but not financially material.
5 CRITICAL · 6 MODERATE · 3 LOW · ~$6–18M downside band

4.1Critical risks (5) — launch-blocking

RISK #1 · CRITICAL

Existing recents/templates discovery regression

Affected: Long-tenure HVCs, Premium accounts · Cited MRR exposure if it goes wrong: $1,950 + risk to broader Classic-anchored Premium base (Strategy R1: $1–2M ARR)

Symptom: Recents carousel on /create Email tab shows iframe previews of NEB-styled branded emails. Question: does it surface customer's legacy / custom-coded / Classic templates, or only NEB-built items? The decomposition strongly suggests NEB-native only.

Why it's critical: For the $1,950/mo customer from HVC #6 ("Where are my new templates?"), the design may help. But for the mirror customer — long-tenure Premium with templates all in Classic — this is HVC #6 in reverse: "Where are my legacy templates?" Could directly regress on a documented HVC theme.

Mitigation: Templates carousel must have origin filter (All / NEB / Classic / Custom HTML). "View all templates" needs deep-link parity. Add migration-awareness prompt for Jack Hally's Discovery-table case ("This template is in Classic — try New Builder?").

RISK #2 · CRITICAL

Manual mode is hidden; escape hatch is discoverability-fragile

Affected: Power users, Premium / agency, customers needing custom HTML · Cited MRR if it goes wrong: subset of $281M HVC ARR (Migration Tab 12) + Premium / agency cohort = $5–15M ARR risk

Symptom: Manual mode reached via a small pencil-icon radio in the editor top bar (next to ✦ AI radio). Most users won't discover it unless they specifically look. For Wes Turner, Bob Gray, and the 38K HVC NEA stayers, manual mode is the product — brand-precision lives there.

Why it's critical: Premium customer can't find manual editor on first visit → churns before discovering AI was optional. This is exactly the "Mailchimp is forcing me to AI" pattern that HVC #12 already cites in proto form. Strategy explicitly says don't force-migrate HVCs — the prototype's default-to-AI behavior is a softer version of the same forcing function.

Mitigation: Surface manual mode as a primary entry — not a radio after generation. "Skip AI — open blank editor" link on composer surface. Remember last-used mode and default to it. For Premium / Legacy plan users, default to manual entirely.

RISK #3 · CRITICAL

AI hallucination liability (especially in regulated content)

Affected: Every paid customer who clicks Send on AI-generated content · If it goes wrong: press-coverage scale Mailchimp-brand event

Symptom: Prototype generates copy, subject lines, hero text, CTAs, and footer compliance text ("123 Main St, Your City, State 12345"). Sample "Welcome to the Community!" has hardcoded "Your Brand" + placeholder address — fine for prototype, catastrophic if shipped without Brand Kit binding for footer address, sender, unsubscribe.

Three named failure modes: (1) Wrong physical address — CAN-SPAM requires valid physical postal address; AI hallucinated address = federal regulatory exposure per send. (2) Hallucinated promo codes / dates — strategy brief auto-suggests "Exclusive welcome guide + first-week bonus content"; AI-fabricated code in a Send button = support nightmare. (3) Hallucinated products — "Featured Products: Product 1, Product 2" placeholder; without catalog connect, copy will make up products that don't exist.

Mitigation: All footer compliance fields must be Brand-Kit-sourced, never AI-generated. Promo blocks must bind to a real promo entity. Product blocks must bind to live SKUs. Pre-send checklist needs "AI-generated fields verified" gate. AccessibilityLinter + ComplianceChecker (Build Plan Tools 11+12) wired before GA.

RISK #4 · CRITICAL

SMS TCPA exposure unchanged (or worse) on the new surface

Affected: All SMS-sending customers (~6.7K Established + growth cohort) · Cited MRR if it goes wrong: $57,000/mo per HVC-class incident

Symptom: Same as HVC #16 ($57K C3 Festivals incident). New design adds "Send a flash sale alert via text" quick-prompt chip in SMS tab + chat-driven SMS composer — but strategy explicitly calls out (I-5.2.3) that SMS needs TCPA guardrails, opt-out compliance checks, duplicate-opt-out detector before any new SMS authoring surface ships. Prototype has none of this.

Why it's existential: AI-generated SMS body could include or omit required opt-out instructions silently. No Compliance Coach. Shipping the new design's SMS tab without TCPA infrastructure means recreating the $57K incident pattern on a more frequently-touched surface. Strategy memo Q1 fix that must precede anything else in SMS.

Mitigation: SMS tab must be dark-launched or feature-flagged OFF in the new design until I-5.2.3 ships. Prototype settings already has a "SMS AI" toggle — wire it to the actual TCPA-readiness check.

RISK #5 · CRITICAL

Brand-context banner becomes upgrade pressure on Free

Affected: Free users (~870K monthly active = F1–F4 cohort = $8.7M of revised goal) · Direct risk to goal: ~$0.1–0.4M off F4; bigger impact via lowered F2 conversion sensitivity

Symptom: The composer has an inline banner: "Get better results by adding brand and business information [Open Brand Kit] [Set up Brand Kit]". Sits between composer and quick-prompt chips — high-friction position.

Why it's critical: For Free users without a paid plan, this is upsell pressure on every Create visit. Klaviyo VoC explicitly cites pricing complexity / Feb '25 active-profile billing as the −72 net-sentiment biggest single Klaviyo wound. Strategy memo says counter-position Mailchimp on pricing transparency (I-3.4.3 engagement-based pricing). Putting "Set up Brand Kit" in front of every Free user every visit is the opposite of that counter-positioning play.

Mitigation: For Free users, change banner to value framing: "Generated content will use your brand colors and voice once you upload them — takes 2 minutes." Hide banner once Brand Kit is set up. Never show banner on the same screen as the AI output — it telegraphs the AI doesn't know the customer's brand.

4.2Moderate risks (6)

RISK #6 · MODERATE

Brand Kit data correctness amplification

AI surface centers Brand Kit (every chip, every preview). If Brand Kit data is wrong (stale kit per HVC #8 Feb 2026 incident), AI's generated outputs amplify the wrongness across every send. Blast radius goes from "one slot on Brand Kit page" to "every AI-generated email." Mitigation: I-1.2.1 must ship before AI is default. "Set up Brand Kit" must run URL importer with confirmation step.

RISK #7 · MODERATE

Font upload UI is missing (HVC #10 mirror)

Brand Kit Fonts section shows hardcoded dropdown of 23 fonts (DM Sans, Inter, Lato, …). The named customer's brand font (DIN 2014, Asul, Readex Pro from HVC #10) is not in the list and there's no upload affordance visible. Worse than current state — at least the upload UI exists today, even if broken. Affected: Premium customers ($3,350/mo cited). Mitigation: add "+ Upload custom font" affordance; validate uploaded fonts flow through to AI outputs.

RISK #8 · MODERATE

Conversation history sidebar lacks search / organization

Sidebar lists conversations grouped by day ("Today", "Yesterday"). For a power user with 10–20 conversations/day (Jack Hally pattern, Workflow Shape #2), this becomes unscannable within a week. No search, rename, folder, or tag. Mitigation: add conversation rename, search, pin, archive; group by campaign / project, not just chronology.

RISK #9 · MODERATE

"Save draft" vs "Send" model is ambiguous

Split-button reveals Save draft + Export HTML. Customer mental model: "I'm chatting with AI to write an email, then send it." Product model: "you're in a draft, you have to explicitly save, then explicitly send." Misalignment is high — particularly for Workflow Shapes #1 (Fast Monday sender) and #5 (low-frequency). Mitigation: autosave aggressively + show "Draft saved · 2s ago" indicator; reserve "Send email" CTA for actual sends; confirm-on-send.

RISK #10 · MODERATE

Theme presets without Brand Kit overrule the customer's brand

The floating Aa theme editor offers 8 presets (Modern, Warm, Minimal, Botanical, Editorial, Sunset, Luxe, Coastal). If a customer with configured Brand Kit clicks a preset, what happens? Prototype doesn't make this clear. For Wes (HVC pill-CTA-reshaped pain), a preset that silently overrules his Brand Kit is exactly the failure mode that drove him to Canva. Mitigation: preset application must show before/after with explicit Apply; brand-kit-bound elements (logo, link color, button style) must NEVER be overridden without confirmation.

RISK #11 · MODERATE

Non-email tabs are stubs but presented as equal-weight

Tab bar shows 8 tabs as visually equal. 6 of them are stubs — WhatsApp/SMS use same chips (likely copy bug); Social post is just a hero card; Automation has no AI composer; Form/Survey are template galleries. Customer who clicks Campaign expecting "multichannel campaign builder" gets a chat composer that produces a strategy brief — promise bigger than delivery. Pattern HVC #12 customer is already complaining about. Mitigation: tabs that aren't fully built should be visually subdued or labeled "Coming Q3" / "Preview".

4.3Low risks (3)

#RiskNote
12Sidebar collapse/expand state not remembered cross-sessionStandard SaaS UX hygiene; easy fix
13Dark mode toggle in prototype settings affects only the prototype, not generated email previewsLikely an artifact of the prototype build; easy to clarify
14Voice input is in the composer with no visible language pickerAccessibility / international users may not know what languages are supported

4.4Pre-mortem roll-up

SeverityCountCumulative MRR risk
Critical5 (Risks 1–5)$5–15M ARR at risk if all manifest
Moderate6 (Risks 6–11)$1–3M ARR at risk
Low3 (Risks 12–14)<$0.5M ARR
Total identified14~$6–18M downside band
Sobering observation. The $6–18M downside band is comparable to the $10–15M upside this prototype unlocks. If the critical risks aren't mitigated pre-GA, the net could be flat-to-negative versus today's experience. That's the case for shipping these mitigations as launch-blockers, not P2 follow-ups.

05Recommendations — if I were ranking

  1. Ship the AI composer + chat surface + strategy brief flow as the new front door for /create Email tab. Target T1 + F2 + PA1 wins. Do not make it the default for Premium / Legacy plan users yet (use the prototype's "Prototype settings" toggles as the actual A/B mechanism).
  2. Feature-flag off SMS, WhatsApp, Campaign tabs until the strategy's TCPA / multichannel infra ships. Show them as "Coming Q3" placeholders. Avoid creating new dollar exposure on top of HVC #16.
  3. Add the 5 critical-risk mitigations as launch-blocking: recents filter for surface origin · manual-mode primary entry point · Brand-Kit-bound footer compliance · SMS tab gated on I-5.2.3 · Brand-context banner re-framed for Free.
  4. Pair the launch with concurrent ships: I-1.2.1 (Brand Kit data correctness) · I-1.2.2 (Font upload + CA parity) · I-3.1.4 (AI Email Setup Agent — formalized as a flow, not just a chat) · I-2.1.1 (Universal Content as primitive — exposed in the AI surface as "Edit once, propagates").
  5. Track these in-product metrics from day one: First-send time (CB1) · Free activation (F2) · Trial activation (T1) · AI hallucination rate (new metric — must instrument before GA) · Manual-mode discovery (new metric — must instrument before GA) · Brand-Kit-completion rate by tier.

What this document is and isn't. Is: an evidence-grounded scoring of a prototype against three pre-existing strategy artifacts (HVC Risk Map, User Research, Revised Goals) plus a structured pre-mortem. Isn't: a user-tested validation. None of the risks have been measured against actual customer reaction — they are predictions from product-design first principles plus the strategy's own evidence base. Right next step before any go/no-go is a 25-customer UR pass on the prototype with the existing HeyMarvin panel. Cross-references: Initiative Canvas (74 initiatives that this design partially exercises) · Strategy Memo (6-quarter roadmap; this design is the Q2–Q5 visible surface) · Migration (Phase 1 prereqs that this design must not undermine).

Tab 17 · Page 5 of 5 · Per-Feature Risk Assessment Catalog

Q4: Feature-by-feature — what does each piece do, and where does it leave us exposed?

Exhaustive assessment of every feature, functionality, and micro-experience in the Freddie prototype. For each item: what it does, the pain point it solves, the customer benefit it delivers, and — critically — the risk flags it carries against the HVC Risk Map, User Research bets, and competitive landscape. Verdicts: SOLVES PARTIAL MISS WORSE. Cross-references Agent Mode Design Audit component IDs where applicable.
6 surface areas · ~35 features assessed
12 critical/high-risk flags · 8 competitive exposures
11 / 35
Features that fully SOLVE a cited pain point without new risk
12
Features with PARTIAL coverage or meaningful gaps
8
Features that MISS cited needs or introduce "move my cheese" risk
4
Features that actively WORSEN a documented HVC theme
How to read this section. This is the authoritative "what does every piece of this prototype do, and what are we worried about" catalog. Each row can drive a prioritization conversation: ship as-is, ship with mitigation, defer, or kill. Risk flags cite specific HVC themes ($MRR where known), UR Bets, and competitive gaps (Canva, Klaviyo). Use this alongside the pre-mortem (Page 4) and the Agent Mode Design Audit (Tab 18) for full coverage.

06A · AI Composer & Prompt Surface

The primary creation pipeline — from blank page to rendered email. This is where the prototype earns its T1 ($5.0M) and F2 ($3.6M) activation capture.

FeatureWhat it doesPain point solvedCustomer benefitRisk assessment
AI composer shell (prompt-to-email) User types a free-form prompt describing their desired email; AI returns a fully rendered, multi-section HTML email in ~15–30s. The primary creation surface on Email, SMS, and WhatsApp tabs. Blank-page paralysis — 68% of trial users who open the editor never send a first campaign (T1 activation gap = $5.0M). Collapses "think → plan → write → design → code" into a single action. Directly attacks T1 trial activation ($5.0M) and F2 free activation ($3.6M). SOLVES Move-my-cheese: Low risk — net-new surface for trial/free users with no established muscle memory to break.
SOLVES UR gap: Directly addresses Bet 2 (Discovery) and Bet 3 (vertical fit via prompt flexibility). Strong fit for Workflow Shapes #1 + #5.
PARTIAL HVC gap: Doesn't fix any of the 17 cited HVC root causes — but it's not meant to. It creates a new surface that sidesteps the existing editor's problems rather than solving them. Risk: sidestep becomes displacement if old surface is neglected.
PARTIAL Competitive gap: Matches Klaviyo's AI email generation positioning. But Canva's AI-to-multichannel pipeline is still broader (generates email + landing page + social in one pass). Mailchimp's prototype is email-only in practice despite 8-tab bar.
Quick-prompt chips Pre-seeded contextual suggestion pills ("Welcome series," "Flash sale," "Product launch," "Newsletter") appear below the composer. Clicking pre-fills the prompt field. "I don't know what to ask the AI" — UR Bet 2 (Discovery) shows new users struggle to articulate what they need from AI tools. Reduces cognitive load at highest-friction moment. Surfaces capabilities the user didn't know existed. Increases prompt-submit rate. SOLVES Move-my-cheese: None — additive feature, no existing workflow disrupted.
SOLVES UR gap: Directly addresses Bet 2 (Discovery). Maps to Shannon/Matt/Gilles (Workflow Shape #5: low-frequency / discovery gap).
PARTIAL HVC gap: Chips are DTC-flavored ("Flash sale," "Product launch"). Missing B2B / ProServ / nonprofit chips despite Bet 3 (vertical fit). No "TCPA-compliant SMS" chip despite $57K HVC #16 exposure.
PARTIAL Competitive gap: Klaviyo has AI-generated campaign suggestions based on actual customer data (segment + behavior). Mailchimp chips are static / context-free. Gap widens as Klaviyo personalizes.
Brand-context banner Persistent banner on AI composer: "Get better results by adding brand and business information [Open Brand Kit] [Set up Brand Kit]." Sits between composer and quick-prompt chips. "AI doesn't know my brand" — users who skip Brand Kit setup get generic outputs and blame AI quality. Contextual nudge at the moment of need. Increases Brand Kit completion rate. WORSE Move-my-cheese: Critical. For Free users (~870K monthly), this is upgrade pressure on every Create visit. Klaviyo VoC cites pricing pressure as −72 net-sentiment wound. Strategy says counter-position on pricing transparency (I-3.4.3). Putting "Set up Brand Kit" in front of every Free user every visit is the opposite play. Directly risks F4 CSAT regression ($2.5M lever).
WORSE HVC gap: Amplifies HVC #8 / #10 — if Brand Kit data is wrong (Feb 2026 incident), the banner drives users into the bad data. Blast radius expansion from "one Brand Kit page" to "every AI email."
MISS UR gap: No mention of Bet 4 (multi-author) — banner shows one Brand Kit, but agency users (Workflow Shape #4) manage multiple client brands.
PARTIAL Competitive gap: Canva's Brand Kit is free and multi-brand. Mailchimp's banner pointing to a single Brand Kit behind a modal is less capable than the competitive set.
Strategy brief panel After prompt submission, AI generates a structured brief (Goal / Date / Recipients / Promo / Focus Metric / Featured Products / Visual Style) that user reviews before email rendering. "AI just does whatever it wants" — users feel loss of control when AI generates without showing reasoning. Creates trust deficit. Checkpoint between intent and execution. Reduces regeneration cycles. Establishes calibrated trust (AI heuristic AI2). SOLVES Move-my-cheese: None for new users. For power users, the brief adds a step they may find unnecessary — mitigated by "Skip brief" affordance (if it ships).
SOLVES UR gap: Strong fit for Bet 2 (Discovery) — brief educates users on what good email strategy looks like. Also helps Bet 3 (vertical fit) via Goal selector.
PARTIAL HVC gap: Recipients field has no audience-confirmation gate at send (pre-mortem Risk #3, S4 finding E1). This is the path to accidental mass-send. $57K TCPA-class risk via SMS tab compound.
PARTIAL Competitive gap: Klaviyo's equivalent is the campaign-builder flow with mandatory segment selection. Mailchimp's brief is more elegant but less safe (no confirm step).
Conversational editing in chat thread After initial generation, user types follow-up prompts ("Make the header bolder," "Add a countdown timer") and AI applies targeted edits to the existing email. "I like 80% of what AI made but fixing the other 20% requires starting over" — incremental refinement is the dominant workflow shape. Preserves user investment in prior generation. Makes AI feel like collaboration, not slot-machine pulls. SOLVES Move-my-cheese: Low — new interaction paradigm with no predecessor to break.
SOLVES UR gap: Strong for Workflow Shapes #1 (Fast Monday) and #3 (brand-first methodical). Directly maps to "Thursday Iterator" pattern (56% of sessions).
PARTIAL HVC gap: No version history / undo-per-generation. Jack Hally (Workflow Shape #2, 10–20 logins/day) can't roll back to "three edits ago." No change-diff shown per edit.
MISS Competitive gap: Canva's "Magic Edit" shows before/after diff inline. Klaviyo's editor has explicit version history with rollback. Mailchimp's chat thread has no equivalent — all edits are forward-only.

6.2B · Email Editor & Canvas

The editing layer — where AI output gets refined and where power users live. Flow B (Power user) and Flow D (Refinement loop) concentrate here.

FeatureWhat it doesPain point solvedCustomer benefitRisk assessment
Split editor (chat left + canvas right) After prompt submission, UI transitions to two-column layout: scrollable chat thread (left) and email canvas (right). Both simultaneously visible and interactive. "I can't see my instructions and the result at the same time" — traditional AI tools show either prompt or output, requiring mental mapping. Real-time correlation between request and result. Enables conversational editing without losing context. SOLVES Move-my-cheese: None for new users. For returning users who expect full-width editor, the narrower canvas may feel cramped on 13" laptops (75% of sessions).
SOLVES UR gap: Strong fit for Bet 2 (Discovery) — chat panel is the discovery engine. Good for Workflow Shape #3 (brand-first methodical).
MISS HVC gap: Editor canvas is un-deep-linkable (state, not route). User can't share "the editor on this email" with a teammate. HVC #4 (multi-author) indirectly worsened — no presence, no shareable link.
PARTIAL Competitive gap: Canva's split-view shows design + comments. Klaviyo has no equivalent — Mailchimp is ahead here. But the un-deep-linkable state is below both competitors' share/collab capabilities.
Mode switcher (AI vs Manual radio) Small radio toggle (✦ AI / pencil Manual) in the editor top bar. Switches canvas between AI-assisted generation and direct block manipulation. "I want to start in manual without waiting for AI" — power users perceive forced AI interaction as a time tax. Gives power users a zero-friction path to preferred workflow. Signals manual editing is first-class. WORSE Move-my-cheese: Critical. Manual mode is hidden post-generation — user must interact with AI first to even discover manual mode exists. For the $281M HVC NEA-stayer segment, this is "Mailchimp is forcing me to AI" — exactly the pattern HVC #12 already cites. Strategy explicitly says don't force-migrate HVCs. Pre-mortem Risk #2 (launch-blocking).
MISS HVC gap: HVC #5 (dual builders + custom code) partially addressed by single-editor concept, but no HTML/code escape hatch (Premium anchor on Classic). HVC #12 (forced New Builder) amplified — now it's forced AI.
MISS UR gap: Misses Bet 5 (direct manipulation) for Workflow Shapes #3 + #4. Wes Turner and agency users need brand-precision manual editing as first entry point, not post-AI fallback.
MISS Competitive gap: Canva offers AI + manual as equal-weight modes from the start. Klaviyo's editor is manual-first with AI as opt-in assistant. Mailchimp's AI-first default is a differentiator for activation but a liability for retention.
Manual drag-drop builder (Blocks / Sections / Styles) Full block-based email editor with draggable content blocks (Text, Image, Button, Divider, Spacer, Columns, etc.) and a Sections panel with 10 pre-built layouts (Hero, Image+Text, Header, Product List, etc.). "I need pixel-level control that AI can't give me" — power users need direct manipulation for complex layouts, conditional content, brand-specific formatting. Familiar editing paradigm for Classic Mailchimp users. Ensures AI-first surface doesn't strand power users. PARTIAL Move-my-cheese: Moderate. Preserves existing NEB builder patterns but with reduced screen estate (chat column persists). Block ordering runtime bug (HVC #5) not fixed in this implementation.
PARTIAL HVC gap: HVC #5 block glitches persist. No custom code/HTML escape hatch (Pillar 2.2.3, Q3 ship). No <liquid> tag support. Premium/agency ceiling remains.
PARTIAL UR gap: Addresses Bet 1 (saved blocks) at the surface level — Sections panel shows layouts to insert. But no propagation primitive: edit-once-applies-everywhere is the actual Bet 1 ask. Wes Turner feels partially seen.
MISS Competitive gap: Canva's block editor has asymmetric resize, 1-click multi-column, and inline collaboration. Klaviyo's equivalent has custom code blocks + Liquid. Mailchimp's manual mode is the existing NEB transplanted into a narrower viewport — no advancement.
Viewport preview (Desktop / Mobile / Split) Radio group switching canvas between desktop-width, mobile-width, and side-by-side split renderings of the current email. "My email looked great on desktop but broke on mobile" — HVC #3 ($1,820/mo rendering divergence). 62% of email opens are on mobile. Catches responsive design issues before send. Reduces "oops" moments post-send. PARTIAL Move-my-cheese: Low — additive feature, better than existing single-viewport preview.
PARTIAL HVC gap: Addresses the trust symptom of HVC #3 but not the engineering root cause. Without email-render-pipeline wired into CI, preview parity is aspirational. Forwarded-mail divergence, Ctrl+K Firefox/Chrome, light/dark mode rendering bugs — all persist.
MISS UR gap: No real-inbox preview (Gmail, Outlook, Apple Mail rendering). UR interviews surface this as the #1 trust builder — "show me what my subscribers actually see."
MISS Competitive gap: Klaviyo partners with Litmus for multi-client rendering. Canva generates flat-image exports that render identically everywhere. Mailchimp's 3-viewport radio is behind both approaches.
Theme presets popover (8 presets, Light/Dark) Floating popover with 8 visual theme presets (Modern, Warm, Minimal, Botanical, Editorial, Sunset, Luxe, Coastal), each in Light and Dark variants. Clicking applies the theme's palette, typography, and proportions. "I want my email to look good but I'm not a designer" — visual design is the #2 barrier to email completion after copywriting. One-click professional design without design skills. Serves the 43% of users who never customize beyond defaults. WORSE Move-my-cheese: Critical. If a customer with configured Brand Kit clicks a preset, brand colors/fonts may be silently overridden. For Wes Turner (HVC pill-CTA-reshaped pain), this is exactly the failure mode that drove him to Canva. Pre-mortem Risk #10 (moderate, but escalation-prone).
WORSE HVC gap: Amplifies HVC #8 / #10 — presets override Brand Kit colors without confirmation. A customer who set up Brand Kit carefully now sees their brand discarded by a casual click.
MISS UR gap: Missing Bet 5 (Brand-Kit CTA defaults). Presets should respect Brand Kit as the floor, not replace it.
PARTIAL Competitive gap: Canva's "Brand Templates" always inherit Brand Kit. Mailchimp's presets override Brand Kit — competitively worse positioning on the brand-consistency story.
Suggested follow-up toolbar chips After AI generates an email, a floating toolbar shows contextual refinement suggestions: "Add a CTA," "Change the theme," "Check for accessibility," "Optimize for mobile." Post-generation abandonment — users don't know what's possible next. Either accept as-is or leave. Guides refinement loop without prompt-writing skill. Surfaces capabilities like accessibility checking that users would never find unprompted. SOLVES Move-my-cheese: None — purely additive, no existing workflow disrupted.
SOLVES UR gap: Strong fit for Bet 2 (Discovery). Directly maps to the "Thursday Iterator" refinement pattern. Surfaces A/B testing adjacently (Bianka Kiss gap from Discovery table).
PARTIAL HVC gap: "Check for accessibility" chip is present but no indication it catches HVC #3 rendering divergences or HVC #7 font fallbacks. May give false sense of QA completeness.
SOLVES Competitive gap: Neither Klaviyo nor Canva have contextual refinement suggestions in their editor. Genuine differentiator that increases session depth.

6.3C · Brand Kit & Identity

The brand infrastructure layer. HVC themes #8, #9, #10 concentrate here — $6,460/mo in cited MRR. Every Brand Kit deficiency is amplified by the AI surface because Brand Kit feeds every generated email.

FeatureWhat it doesPain point solvedCustomer benefitRisk assessment
Brand Kit modal (7 sections) Full-screen modal: My Business, Logos, Colors, Fonts, Buttons, Brand Voice, Social Links. Persists across all conversations and emails. Accessed from sidebar footer or brand-context banner. Brand inconsistency across campaigns — HVC #8 ($4,800/mo combined with #10): "Every email looks different because there's no single source of truth." Durable brand state inherited by every AI generation. Eliminates per-email brand configuration. PARTIAL Move-my-cheese: Moderate. Existing Brand Kit page is being replaced by a modal. Users who bookmarked the Brand Kit URL lose their path. Modal is the right pattern (cross-cutting context), but transition needs signposting.
MISS HVC gap: HVC #9 ($2,460/mo) — single-brand only. No multi-brand picker, no per-conversation brand switcher, no sub-brand concept. Agencies + multi-brand teams entirely unserved. Initiative I-1.2.3 missing.
MISS UR gap: Doesn't address Bet 4 (multi-author) — Brand Kit should be team-shared with role-based access. Currently single-user-scoped.
MISS Competitive gap: Canva's Brand Kit is free, supports multiple brands, and is shareable across teams. Klaviyo's brand settings are per-flow-configurable. Mailchimp's single-brand modal is behind both.
Logo upload Multi-slot logo upload supporting primary, secondary, and icon variants. AI selects appropriate variant based on email context (header vs footer vs mobile). "I uploaded my logo but it looks wrong in the header because it's the wrong aspect ratio." Context-aware logo selection means user doesn't need to micromanage asset placement. PARTIAL Move-my-cheese: Low — existing logo upload preserved, multi-slot is additive.
MISS HVC gap: HVC #9 ($2,460/mo) — single brand only. No "Client A logo" vs "Client B logo" concept. Logo asset metadata (alt text, usage rights, dark-mode variant) not addressed.
PARTIAL UR gap: Bet 3 (vertical fit) partially served — B2B and nonprofit orgs often have distinct "stacked" vs "inline" logo variants. Multi-slot helps but no semantic tagging.
PARTIAL Competitive gap: Canva supports logo variants + dark-mode alternates + multi-brand. Mailchimp has slots but no metadata.
Color palette Primary, secondary, and accent color pickers in Brand Kit. Colors automatically flow into AI-generated email components. Manual hex-code entry per campaign is repetitive and error-prone. Users copy codes from external tools or guess from memory. Set once, use everywhere. Eliminates color inconsistency. Reduces "on-brand" review cycles. SOLVES Move-my-cheese: None — additive, better than manual color entry.
PARTIAL HVC gap: HVC #8 (Feb 2026 Brand Kit incident) — if colors are stale/wrong, every AI email is off-brand. Prerequisite: I-1.2.1 Brand Kit data correctness must ship before AI defaults to Brand Kit colors. Without it, color palette amplifies the incident pattern.
SOLVES UR gap: Serves Bet 3 (vertical fit) and Bet 5 (Brand-Kit CTA defaults). Brand-first methodical users (Workflow Shape #3, Wes/Bob) get what they want here.
PARTIAL Competitive gap: Canva supports unlimited palette colors + contrast-checking. Klaviyo's palette has semantic naming (CTA color, link color, hover). Mailchimp's 3-slot palette is minimally viable.
Font selectors (hardcoded 23-font dropdown) Dropdowns for heading font, body font, and base size. Ships 23 hardcoded web-safe fonts (DM Sans, Inter, Lato, etc.). "I can't use my actual brand font" — HVC #10 ($3,350/mo): custom font upload is unavailable. Basic typography control for standard fonts. WORSE Move-my-cheese: Critical. The named HVC customers' brand fonts (DIN 2014, Asul, Readex Pro) are not in the 23-font list and there is no upload affordance visible. Current production Mailchimp at least has a font-upload UI (even if broken). Prototype is a regression. Pre-mortem Risk #7.
WORSE HVC gap: HVC #10 ($3,350/mo) directly worsened. HVC #7 ($655/mo, brand fonts not usable in LP/forms) also not addressed — iPhone fallback logic absent.
MISS UR gap: Bet 5 (direct manipulation upgrades) includes font handling. Premium/agency users hit an immediate ceiling.
MISS Competitive gap: Canva supports custom font uploads on free plan. Klaviyo supports web font embedding. Mailchimp's hardcoded dropdown is the weakest position in the competitive set.
Brand voice / personality fields 4 structured inputs: Personality (warm/professional/playful), Formality level, CTA style, Headline style. AI uses these to calibrate generated copy tone. "AI writes generic copy that doesn't sound like us" — #1 objection to AI content tools from brand managers and agency users (UR Bet 3). Differentiates AI output per customer. Reduces "sounds like ChatGPT" rejection rate. SOLVES Move-my-cheese: None — net-new capability with no predecessor.
SOLVES UR gap: Directly addresses Bet 3 (vertical fit). B2B / ProServ can configure professional + formal + "Schedule a demo" CTA style. Strong foundation.
PARTIAL HVC gap: Single brand voice only (HVC #9 multi-brand gap persists). Agency managing 5 client brands needs 5 voice configurations. No per-conversation voice override.
SOLVES Competitive gap: Klaviyo has no equivalent brand-voice configuration. Canva's "Brand Voice" is doc-level only. Mailchimp is genuinely ahead here — protect this advantage.
Auto-extract from URL (onboarding) First-run overlay prompts user to paste website URL. System scrapes and auto-populates Brand Kit fields (logo, colors, fonts, business name). "I spent 20 minutes setting up brand colors and they still don't match my website" — manual brand setup is error-prone and tedious. Reduces Brand Kit setup from ~8–12 min to ~30s. Increases % of accounts with populated Brand Kit (prerequisite for quality AI output). SOLVES Move-my-cheese: None — purely additive onboarding enhancement.
SOLVES UR gap: Directly enables Bet 2 (Discovery) by removing the biggest first-run blocker. Strong for Workflow Shape #5 (low-frequency users who need fast setup).
PARTIAL HVC gap: If URL extraction returns wrong colors/fonts (edge case: sites with multiple brand contexts), it populates incorrect Brand Kit data that then feeds every AI email. No confirmation step visible. HVC #8 amplification risk.
PARTIAL Competitive gap: Klaviyo has similar URL-import onboarding. Canva has URL-based brand extraction in Business plan. Parity, not differentiation — but necessary table stakes.

6.4D · Channel & Send

The terminal actions — where creation converts to business value. Flow E concentrates 5 of 9 S4 critical findings from the Agent Mode Design Audit. HVC #16 ($57K TCPA) lives here.

FeatureWhat it doesPain point solvedCustomer benefitRisk assessment
8-channel tab bar Horizontal pill-tab bar at top of /create: Email, SMS, WhatsApp, Automation, Form, Survey, Social post, Campaign. Clicking switches the creation surface. "I have to navigate to different pages for each channel" — fragmented entry points mean siloed campaigns with no cross-channel awareness. Unified creation mental model: "I create all my marketing from one place." WORSE Move-my-cheese: High. 6 of 8 tabs are stubs but presented as visually equal-weight. Customer who clicks "Campaign" expecting a multichannel builder gets a chat composer — promise bigger than delivery. Pattern HVC #12 customer is already complaining about ("Mailchimp says it can do X but actually can't"). Pre-mortem Risk #11.
MISS HVC gap: HVC #16 ($57K TCPA) directly exposed. SMS tab has an AI composer that can generate non-TCPA-compliant content. No ComplianceChecker, no opt-out guardrails, no I-5.2.3. WhatsApp/SMS show same chips (likely copy bug). HVC #14 (SMS reporting) and #15 (SMS credits) completely absent.
MISS UR gap: Bet 4 (multi-author) not addressed across any channel. CB5 (% share-of-channel-rev 15% → 25%) requires functional omnichannel — stubs don't move this metric.
MISS Competitive gap: Klaviyo's flows are natively multichannel (email + SMS + push in one automation). Canva generates email + social + landing page from one design. Mailchimp's 8 tabs with 6 stubs signals aspiration without delivery.
Send email button (split: Send / Save draft / Export HTML) Primary green button sends immediately to selected audience. Dropdown reveals Save draft + Export HTML. No confirmation step between click and send. "I need to get this campaign out the door" — the terminal action of every email workflow. Clear, prominent primary action. Split-button establishes action hierarchy (Send > Save > Export). WORSE Move-my-cheese: Critical. No audience-confirmation modal. One click sends to 2,150+ subscribers with zero verification. Current production Mailchimp has a confirmation step. This is a regression in safety. S4 findings E1/A10 (launch-blocking).
MISS HVC gap: HVC #16 ($57K) — if user is on SMS tab and clicks Send, AI-generated non-TCPA-compliant SMS goes to entire segment. No compliance gate. Strategy memo calls I-5.2.3 as Q1 prerequisite.
MISS UR gap: No pre-send checklist. UR interviews surface "show me a summary before I commit" as universal need across all 5 Workflow Shapes. The strategy brief panel is adjacent but doesn't gate the Send action.
MISS Competitive gap: Klaviyo has mandatory pre-send review (audience count + subject + preview). Canva doesn't send natively. Industry standard is confirm-on-send. Mailchimp's one-click Send is below industry standard.
Send test email Secondary button sends current email to a specified test address for review before real send. "I can't preview how this actually renders in a real inbox" — web previews don't catch Gmail/Outlook/Apple Mail rendering bugs. De-risks the send decision. Catches rendering, personalization, and link errors before audience delivery. PARTIAL Move-my-cheese: Low — existing capability preserved. But: no recipient picker modal — could send to wrong address. S4 finding E4.
PARTIAL HVC gap: Partially addresses HVC #3 (rendering divergence) by enabling real-inbox preview. Doesn't fix underlying render bugs.
PARTIAL UR gap: Serves Workflow Shape #3 (brand-first methodical, Wes/Bob). Missing multi-client test (send to Gmail + Outlook + Apple Mail simultaneously).
MISS Competitive gap: Klaviyo's test-send includes rendered previews across 5 major clients inline. Mailchimp sends a raw test email with no multi-client comparison.
SMS composer surface SMS tab shows Pattern A composer (same as Email): AI chat + quick-prompt chips ("Send a flash sale alert via text"). Generates a single SMS text message. "Creating SMS requires a separate tool" — cross-channel fragmentation forces context-switching between email and SMS workflows. Unified surface for email and SMS creation. Reduces tool-switching overhead. WORSE Move-my-cheese: Existential. AI can trivially generate non-TCPA-compliant opt-out content. No AccessibilityLinter, no ComplianceChecker, no duplicate-opt-out detector. The "Send a flash sale alert via text" chip is a one-click path to replaying the $57K HVC #16 incident. Pre-mortem Risk #4 (launch-blocking).
WORSE HVC gap: HVC #15 (SMS credits, $3,592/mo) — no credit-balance UI, no delivery-cost preview, no opt-out counter. HVC #16 ($57K TCPA) — directly worse. HVC #17 (merge depth / MMS) — completely missing.
MISS UR gap: CB5 (share-of-channel-rev) requires functional SMS with compliance guardrails. This surface creates liability, not revenue.
MISS Competitive gap: Klaviyo's SMS is TCPA-aware at the platform level (opt-out injection, quiet hours, consent tracking). Mailchimp's SMS AI has zero compliance infrastructure. Competitively disqualifying for enterprise.
Audience / recipient selection Dropdown/multi-select in strategy brief where users choose audience segments (e.g., "All subscribers," "VIP customers," "Cart abandoners") for the campaign. "I have to leave the editor to figure out who to send to" — audience selection currently breaks creation flow. Brings audience selection into creative context. Enables AI to tailor content to selected segment. PARTIAL Move-my-cheese: Moderate — moving audience selection from post-creation to in-creation changes the workflow sequence. Users who expect "create first, target second" may find this disorienting.
MISS HVC gap: No audience confirmation at send (S4 finding E1). No segment-size display ("sending to 2,150 subscribers"). No suppression-list check. TCPA consent status not visible for SMS recipients.
PARTIAL UR gap: Bet 5 (direct manipulation) partially served — in-canvas audience selection is better than separate config. But no "audience preview" (show me who gets this).
MISS Competitive gap: Klaviyo shows real-time segment counts + estimated delivery time + suppression reasons inline. Mailchimp's selector is a dropdown with no data feedback.

6.5E · Sidebar & Navigation

The persistent navigation layer. Conversation management + system navigation + exit patterns. The two-shell switching decision (Home ↔ Create) is the structural risk here.

FeatureWhat it doesPain point solvedCustomer benefitRisk assessment
Conversation sidebar (history, new, collapse) Left sidebar showing all past conversations/sessions. Each entry shows title (from first prompt) + timestamp. Supports "+ New conversation," collapse/expand (240px ↔ 60px), and footer links to Prototype settings + Brand Kit. "I can't find the email I was working on last week" — session-based AI tools lose context between sessions. Users need persistent access. Multi-session workflows. History for "Thursday Iterator" and "Daily Mailer" shapes. Foundation for future team-shared conversations. PARTIAL Move-my-cheese: Moderate. Replaces the existing campaign/email list with a conversation-first paradigm. Users who think in terms of "emails" and "campaigns" must now think in "conversations." Mental model shift is significant for long-tenure users.
PARTIAL HVC gap: No search, rename, folder, tag, or archive. For Jack Hally (Workflow Shape #2, 10–20 logins/day), this becomes unscannable within a week. Pre-mortem Risk #8 (moderate).
MISS UR gap: Bet 4 (multi-author) — sidebar shows my conversations only. No sharing, no "show this to my teammate," no presence. Conversation gives false signal it's shared when it's not.
PARTIAL Competitive gap: Klaviyo doesn't have conversation-based creation. ChatGPT/Gemini have full search + folder + share. Mailchimp is behind consumer AI apps but ahead of marketing-tool competitors.
Home dashboard → Create shell transition Clicking "Create" from Home disposes of all global navigation (Analytics, Audience, Campaigns, etc.) and replaces the shell. User loses path back except via Exit (×) button. Two-shell switching pattern. Focus: "When I'm creating, I don't need the full product nav distracting me." Clean, focused creation environment. Removes navigation noise during creative work. WORSE Move-my-cheese: High. This is a one-way trap-door pattern. User can't navigate to Analytics to check a metric mid-creation. Can't go to Audience to refine a segment. Can't see Campaigns list without fully exiting Create. Every task that requires cross-surface context means: Exit → navigate → return → lose creation state.
MISS HVC gap: No direct HVC cite, but the pattern worsens the "fragmented tool" perception that underlies HVC #2 (support dead-ends) and HVC #14 (SMS reporting hard to find).
MISS UR gap: Workflow Shape #2 (all-week ad-libber, Jack Hally) and Shape #4 (third-party-in-loop) need fluid cross-surface navigation. The trap-door is the opposite of fluid.
MISS Competitive gap: Klaviyo keeps global nav visible during campaign editing. Canva keeps sidebar nav persistent. Mailchimp's shell-swap is uniquely aggressive and below competitive standard.
Exit (×) button behavior Single button in the Create shell top bar that returns user to Home dashboard (/). One-click, one-way. No "Are you sure?" confirmation if there are unsaved changes. "Get me out of here" — need to return to the main product. Clear, predictable exit path. PARTIAL Move-my-cheese: Moderate. No unsaved-changes warning. User with in-progress draft clicks × → loses work? The autosave contract is unclear (pre-mortem Risk #9). Current production Mailchimp has "unsaved changes" prompt.
MISS HVC gap: No "back to where I was" — Exit always goes to Home, not to previous location (e.g., Campaigns list, Analytics).
PARTIAL UR gap: Workflow Shape #2 (Jack Hally, 10–20 logins/day) needs fast context-switching. Exit → Home → navigate is 3 steps when it should be 1.
PARTIAL Competitive gap: Klaviyo's editor has browser-back support + breadcrumb trail. Canva has persistent sidebar with all files. Mailchimp's × is a dead-end exit with no navigation memory.

6.6F · AI Intelligence & Feedback

The AI communication layer — how the system explains itself, takes feedback, and signals status. AI heuristics AI1–AI5 concentrate here.

FeatureWhat it doesPain point solvedCustomer benefitRisk assessment
Assistant message body (reasoning narrative) Each AI response includes prose explanation: "I chose a warm palette because your brand voice is Friendly, and used single-column for mobile readability." Educates the user on email strategy. "The AI changed things but I don't understand why" — opaque AI creates distrust. Users reject outputs they can't rationalize to stakeholders. Builds calibrated trust (AI heuristic AI2). Reduces regeneration rate. Teaches email strategy (educational side-effect). SOLVES Move-my-cheese: None — net-new AI interaction with no predecessor.
SOLVES UR gap: Strong for Bet 2 (Discovery) — reasoning narrative surfaces "why" behind each design decision. Users learn what good email strategy is while using the tool.
PARTIAL HVC gap: If Brand Kit data is wrong (HVC #8), the AI will confidently explain its wrong choices: "I used your brand red #FF0000 for the CTA" when the customer's actual brand red is #CC0000. Calibrated trust + wrong data = calibrated distrust.
SOLVES Competitive gap: Klaviyo's AI has no reasoning layer. Canva's "Magic Design" is a black box. Mailchimp's narrative reasoning is a genuine competitive advantage — protect and extend it.
Copy / Like / Dislike / Regenerate row Per-message action bar: copy text to clipboard, thumbs up/down quality signal, and regenerate (discard + re-generate from same prompt + context). "AI keeps making the same mistakes because it doesn't learn" — without feedback, every generation starts from baseline. Reinforcement signal loop for model improvement. Gives users agency ("I'm training this"). Regenerate reduces prompt-rewriting burden. SOLVES Move-my-cheese: None — standard AI UX pattern, no existing workflow disrupted.
SOLVES UR gap: Strong for Bet 2 (Discovery) — feedback loop is the mechanism by which the system improves per-customer over time.
PARTIAL HVC gap: No "undo last AI edit" (only full regenerate). For HVC power users, regenerating discards everything — including manual tweaks applied to AI output. Needs per-edit rollback, not just full regenerate.
PARTIAL Competitive gap: ChatGPT has full version history with branching. Canva has undo stack. Mailchimp's binary like/dislike + full-regenerate is functional but shallow.
AI artifact card (Ready pill) Card in chat thread showing generation status: "Generating..." (spinner), "Ready" (green pill + preview thumbnail). Indicates when the email is viewable in the canvas. "Did the AI succeed or fail? I can't tell" — unclear status during and after generation creates anxiety and premature interaction. Clear generation state (N1 Visibility). Reduces premature clicks on incomplete outputs. PARTIAL Move-my-cheese: None — new pattern, no predecessor to break.
PARTIAL UR gap: Adequate for Workflow Shape #1 (Fast Monday) — "is it done yet?" answered clearly. But no "Failed" state visible. If generation errors, user sees no feedback — just silence. S2 finding from Agent Mode Design Audit.
MISS HVC gap: No error recovery path. If AI fails mid-generation (network, API timeout, Brand Kit parse error), user has no indication why or how to retry. Especially risky when Brand Kit data causes parse failures (HVC #8 compound).
PARTIAL Competitive gap: ChatGPT shows explicit error states with retry. Klaviyo's AI errors surface with diagnostic messaging. Mailchimp's "Ready" pill has no "Failed" sibling.
Loading / generating states During AI generation (~15–30s): animated spinner with contextual progress text ("Analyzing your brand..." → "Drafting subject line..." → "Rendering email..."). Canvas shows skeleton/shimmer. "Is it working or frozen?" — AI generation latency (>5s) without progress indication causes 23% of users to refresh or abandon. Reduces premature abandonment. Progress text teaches what AI does (builds trust). Measurably better perceived wait time vs spinner alone. SOLVES Move-my-cheese: None — new pattern, no predecessor.
SOLVES UR gap: Directly supports Bet 2 (Discovery) — progress text doubles as capability education ("I didn't know it analyzes my brand").
PARTIAL HVC gap: If generation hangs (no timeout visible), user has no escape hatch. Cancel/abort button not observed in prototype. For the $3.6M F2 activation lever, a hung generation during first session = permanent abandonment.
SOLVES Competitive gap: Matches Canva's "Magic Design" progressive loading. Ahead of Klaviyo (no progress text). Good execution of an expected pattern.

6.7Per-feature risk roll-up

Summary of risk verdicts across all 35 assessed features, by surface area. Color-coding: LOW RISK = ship as-is · MODERATE = ship with mitigation · HIGH = defer or redesign · CRITICAL = launch-blocking.

Surface areaFeaturesSOLVESPARTIALMISSWORSEHeadline risk
A · AI Composer & Prompt53200LOW — strongest surface. Brand-context banner (1 feature) carries all the risk.
B · Email Editor & Canvas61212HIGH — mode switcher + theme presets are launch-blocking risks. Manual mode hidden, presets override Brand Kit.
C · Brand Kit & Identity63201MODERATE — strong brand voice + URL extract, but font dropdown ($3,350/mo HVC #10) and single-brand ($2,460/mo HVC #9) are meaningful gaps.
D · Channel & Send50212CRITICALworst surface. SMS TCPA ($57K), no send confirmation, 6 stub tabs. Ship SMS tab dark-launched OFF. Add mandatory confirm modal.
E · Sidebar & Navigation30210MODERATE — two-shell trap-door is a meaningful "move my cheese" risk. Sidebar needs search/organize.
F · AI Intelligence & Feedback43100LOW — strongest AI UX in the competitive set. Missing "Failed" state is the only gap.
TOTAL29101135

Ship as-is

10
Features that fully solve a cited need without new risk. AI composer, prompt chips, brand voice, URL extract, follow-up chips, reasoning narrative, feedback row, loading states.

Ship with mitigation

11
Features that partially address needs but carry moderate gaps. Strategy brief (add confirm), viewport (add render pipeline), sidebar (add search), Brand Kit modal (add multi-brand), etc.

Defer or redesign

3
Manual drag-drop (needs code mode), audience selector (needs confirm gate), exit button (needs unsaved-changes warning).

Launch-blocking

5
Mode switcher (manual hidden) · Theme presets (override Brand Kit) · Font dropdown (regression from current) · Send button (no confirm) · SMS composer ($57K TCPA).

6.8HVC theme exposure map — which features touch which themes

HVC #Theme$/moFeatures that touch itNet effectNotes
3Rendering diverges$1,820Viewport preview, Send testPARTIALTrust symptom addressed; engineering root cause untouched
5Dual builders + custom code$410Mode switcher, Manual builderPARTIALSingle surface reduces confusion; no code/HTML escape hatch
6Templates not surfacing$1,950Templates carousel, Recents carouselPARTIAL + WORSENEB templates surface; Classic/custom-coded templates may not. "HVC #6 in reverse" for Classic anchors
7Brand fonts in LP/forms$655Font selectorsMISSLP/form font rendering is out-of-surface
8Brand Kit regression / stale kitthreadBrand Kit modal, Brand-context banner, Color palette, Auto-extract, AI reasoningWORSEAI surface amplifies Brand Kit data bugs. Blast radius from "one page" to "every email"
9Logo metadata / multi-brand$2,460Brand Kit modal, Logo uploadMISSSingle-brand only. I-1.2.3 entirely missing
10Font upload / CA mismatch$3,350Font selectorsWORSEHardcoded 23 fonts, no upload UI. Regression from current state
11Creative Assistant rediscovery$2,650Theme presets, Quick-prompt chipsPARTIALAI image gen + themes are adjacent; explicit banner workflow missing
12Content Studio instability + forced NEB$621Mode switcher, 8-channel tabsWORSE"Forced to AI" is stronger forcing function than "forced to NEB"
13Canva sync loss$2,500+NoneMISSNo Canva integration visible. Pressure on broken sync increases
16Duplicate TCPA opt-out ($57K)$57,000SMS composer, 8-channel tabs, Send buttonWORSESingle largest HVC. AI SMS with zero TCPA guardrails = higher incident probability

6.9Competitive exposure summary — where Canva / Klaviyo still win

COMPETITIVE GAP #1 · CANVA

Multi-channel generation from one design

Canva generates email + landing page + social post + ad from a single design in one pass. Mailchimp's prototype generates email only (8 tabs, 6 stubs). The omnichannel promise is visual but not functional. For the CB5 lever (share-of-channel-rev 15% → 25%), this gap means Mailchimp can't credibly claim "all your marketing in one place" until tabs are real.

COMPETITIVE GAP #2 · KLAVIYO

Data-driven personalization in the editor

Klaviyo's AI generates content personalized per-segment using behavioral data (purchase history, browse recency, predicted LTV). Mailchimp's AI generates from static prompt + Brand Kit. Strategy brief has "Recipients" and "Featured Products" fields, but no behavioral data flows into generation. For CB3 (click rate 1.70% → 3.0%) and CB4 (RPME $1.74 → $2.50), this is the gap that determines whether AI-generated emails perform or just look nice.

COMPETITIVE GAP #3 · CANVA

Free-tier Brand Kit with multi-brand + custom fonts

Canva's Brand Kit is free, supports multiple brands, includes custom font upload, and is shareable across teams. Mailchimp's Brand Kit: single-brand, no custom font upload (regression), no team sharing. For the $6,460/mo in combined HVC #8/#9/#10 exposure, this means Canva is already solving the problems Mailchimp's HVC customers are escalating about.

COMPETITIVE GAP #4 · KLAVIYO

TCPA-aware SMS at the platform level

Klaviyo's SMS has opt-out injection, quiet-hours enforcement, consent-status tracking, and per-message cost preview — baked into the platform, not bolted on. Mailchimp's SMS AI has zero compliance infrastructure. For the $57K HVC #16 exposure, Klaviyo is the destination churning SMB customers will switch to if TCPA incidents recur. This is the gap with the highest dollar-concentration risk.

COMPETITIVE GAP #5 · CANVA + KLAVIYO

Version history + rollback in the editor

Both competitors offer explicit version history (Canva: full undo stack + named versions; Klaviyo: draft versions with diff). Mailchimp's chat thread is forward-only — no per-generation rollback, no diff view, no named checkpoints. For Workflow Shape #2 (Jack Hally, all-week ad-libber), this means the prototype is structurally less capable than either competitor for the "continuous edit" pattern that power users live in.

The 60-second competitive read. The prototype is ahead on AI communication (reasoning narratives, contextual chips, strategy briefs) and behind on data infrastructure (personalization, compliance, Brand Kit parity, version history). The competitive gaps map exactly to the same surfaces where HVC dollar concentration lives. Canva competes on design democratization; Klaviyo competes on data-driven performance; Mailchimp's prototype competes on AI-assisted activation. The risk is that activation wins bring customers in and infrastructure gaps push them out. Recommendation: ship the AI communication layer (it's genuinely differentiated) while concurrently closing the infrastructure gaps that Canva and Klaviyo have already solved. The Initiative Canvas Pillars 1, 2, and 5 are precisely these infrastructure investments.

Sources cited. Feature catalog drawn from direct prototype interaction at ai-email-generator-steel.vercel.app (May 2026) + decomposition at github.intuit.com/dprabhakara/ai-email-generator-decomp (29 screenshots + 11 docs). Risk assessments scored against HVC Risk Map (17 themes / ~$95K/mo), User Research (5 Bets / 5 Workflow Shapes / Discovery table), Revised Goals ($21M target / 10 levers), and Agent Mode Design Audit (96 components / 45 heuristic findings / 9 S4 criticals). Competitive claims based on publicly available product capabilities as of May 2026. Component IDs (C-XX) reference Tab 18 Lens 3 matrix.

Tab 17b · Freddie Deepak Phase 2 (Freddie debug phase two specs)

Phase 2: Canva AI / AI 2.0 → Mailchimp send-time intelligence

Companion to Phase 1 (creative depth). Phase 2 translates the eight “permanent win” capabilities from the Canva-gap roadmap into Mailchimp surfaces: orchestration, live performance feedback, send-time personalization, cross-channel asset studio, compliance-aware localization, AMP for email, Mailchimp Shield, and a cross-domain Freddie agent.
How to use this tab. Open the spec for constraint manifest, heatmap, per-feature definitions, and execution gates. Open the prototype for an email-first click-through (hash routes like #s201-intro).

00Master launchpad · Phase 1 + Phase 2

Phase 1 prototype

Creative-depth walkthrough (10 features) across Email, SMS, and WhatsApp variants.

Phase 2 spec

Freddie Deepak Phase 2 blueprint: orchestration, performance loop, personalization, localization, AMP, and Shield.

Phase 2 prototype

Email-first clickable storyboard for the eight Phase 2 capabilities and send-time intelligence layer.

01The eight mapped capabilities

#CapabilityMailchimp angle
01Agentic Campaign OrchestratorPlan graph + human checkpoints + audit for every agent step
02Real-Time Campaign Performance LoopLive KPI strip beside the canvas → scoped fix suggestions
03Send-Time AI PersonalizationAssembly matrix with policy suppress + explain
04Cross-Channel Asset StudioMaster asset → channel-safe derivatives (ties to Universal Content)
05Compliance-Aware LocalizationLocale packs: legal blocks + tone + hard stops before send
06AMP for EmailInteractive components with paired static fallback MIME
07Mailchimp ShieldPII, claims, approvals — enterprise governance as product UI
08Cross-Domain Conversational AgentMCP tool registry + handoff across Mailchimp, store, helpdesk

Source list in Phase 1 §7.3 (deliberately out of Phase 1 scope). This spec picks up that list verbatim and expands it. Canva analysis: deepakp1308.github.io/canva-campaign-analysis/

Mailchimp Unified Builder — Plan on a Page

Vision

Reimagine Mailchimp’s builder as an AI-first unified creation platform that beats Canva on creative depth, beats Klaviyo on send-time intelligence, and delivers the most trusted campaign-to-revenue pipeline for SMBs. One builder, every channel, every customer—from first send to measurable revenue.

Key Tenets

TenetDescription
Quality Is the ProductEvery send renders exactly as designed. P1 Quality & Trust burns down ~$95K/mo HVC exposure before new features ship.
AI That Ships, Not DemosBrand-Kit-aware conversational editing, generative SMS, and AI performance watchdog replace generic assistants with send-ready output.
One Builder, Every ChannelEmail, SMS, and push in a single canvas with Universal Content blocks. Edit once, adapt per channel.
Revenue You Can MeasureIn-canvas revenue attribution and campaign confidence scoring make ROI visible at send time.

Customer Benefit

  1. Saves Time — Signup to first send in minutes. AI drafts, Universal Content reuse, and unified canvas cut creation time 60%+ for 1.02M paid and 870K free monthly active users.
  2. Builds Trust — Pre-send confidence scoring, render-fidelity guarantees (≥99%), and Brand Kit enforcement address 17 HVC themes (~$95K/mo cited MRR).
  3. Drives Revenue — In-canvas revenue attribution and Smart Send personalization transform the builder into a revenue engine. Target: ~$21M ARR ($6.7M paid + $8.7M free + $5.6M trial).

Differentiation

CompetitorOur Advantage
CanvaCanva owns design but has no ESP-native send-time intelligence—inbox placement, per-profile Smart Send, deliverability scoring, campaign revenue attribution. We match creative depth and add the execution layer Canva structurally cannot build.
KlaviyoKlaviyo leads flow automation but lacks co-editing, multi-brand kits, and Brand-Kit-aware conversational AI. Our unified builder combines Intuit-scale AI with campaign→revenue attribution via QuickBooks that no standalone ESP can replicate.

FY27 Roadmap

PhaseKey FeaturesExperience Unlocked
Q1: FoundationNEB rendering parity, Brand Kit reliability + multi-brand, Builder SLOs (99.9% uptime), Content Studio + Canva sync, NEB Code Mode“My sends look exactly as designed”; Classic→NEB migration unblocked
Q2: AI ActivationUniversal Content blocks (Klaviyo parity), Write with AI funnel recovery, conversational in-canvas editing, AI Email Setup Agent, template ICP fit“Signup to first send in minutes”; AI drafts match brand voice
Q3: UnificationUnified email+SMS canvas, generative SMS, real-time multi-author collab, AI image gen + Magic-tier editing, cross-template reuse“Email + SMS feel like one campaign”; Canva-grade creative inside MC
Q4: Revenue EngineIn-canvas revenue attribution, per-profile Smart Send, AI Performance Watchdog, campaign confidence scoring, compliance-aware localization“I see revenue impact before I send”; personalized timing per recipient

Experience Shift

FROM: Manual, channel-fragmented workflow. Email and SMS built in separate tools. AI is a bolted-on text generator that ignores your brand. Campaign success measured after the fact, if at all.

TO: AI-first unified builder. One conversational prompt generates brand-consistent creative across email, SMS, and push. Send-time intelligence optimizes per recipient. Revenue attribution visible before send. Creation time drops from hours to minutes.

Metrics

TypePrimarySecondary
Customer BenefitTime-to-first-send <15 min (from ~45 min); Campaign confidence score >85%AI adoption rate (% campaigns with ≥1 AI feature); Universal Content reuse rate
Business OutcomeEditor-attributed ARR ~$21M (Paid $6.7M + Free $8.7M + Trial $5.6M); NEB adoption >80%SMS attach rate 2x baseline; Bulk Established retention flat or positive (reversing −9.4% YoY)

Freddie / AI Email Generator: Three Structural Concerns

Evidence-grounded assessment · Executive read · May 2026


C1 Freddie does not solve the problems customers have been raising for years

Customers have cited bugs, barriers, and unmet needs across the builder for years — NEB rendering breaks, Brand Kit data corruption, font upload failures, Content Studio instability, template portability gaps, SMS TCPA exposure. These are not edge cases; they are the top-cited reasons customers escalate, churn, or refuse to migrate. The Freddie prototype adds a beautiful AI front door, but the house behind it still has the same broken plumbing.

Proof points

  • ~$95K/mo in cited HVC MRR exposure across 17 themes (NEB, Brand Kit, Canva sync, Content Studio, SMS) — HVC Risk Map
  • $57K/mo single SMS TCPA incident — largest individual cited HVC exposure
  • HVC #3 ($1,820/mo) — email renders differently in editor vs inbox
  • HVC #8, #10 — Brand Kit data wrong; font upload broken ($3,350/mo combined)
  • HVC #6 ($1,950/mo) — templates don’t appear in campaign creation
  • HVC #13 ($2,500/mo) — Canva graphics vanish in sent email
  • >90% negative sentiment on NEB reliability, rendering, portability — Voice of Customer
  • Bulk email Established users −9.4% YoY; Explore −19.2% YoYProduct Health
  • Write with AI: Explore collapsed −73.7% YoY; churn +15.4ppProduct Health

Freddie’s gap

The Freddie prototype scores 0/17 HVC themes directly solved. 5 partial. 12 not addressed. 4 may worsen (HVC #6 reverse — legacy templates don’t surface in recents; HVC #12 — Premium pressure amplified; HVC #8/#10 — Brand Kit bugs amplified by AI generation volume; HVC #16 — SMS TCPA unchanged). See Freddie Assessment.

Customer impact

Customers who adopt Freddie will hit the same rendering, Brand Kit, and portability bugs — now amplified because AI generates more content that flows through the same broken pipeline. Every AI-generated email still renders through NEB, still pulls from the same Brand Kit data, still lands in the same inbox rendering lottery.

Business impact

$6–18M downside band from unmitigated critical risks (per Freddie Assessment pre-mortem) — comparable to the $10–15M upside the prototype unlocks. Net could be flat-to-negative if foundation work is deferred.


C2 Freddie does not close competitive gaps — it’s a facelift, not a capability shift

Freddie redesigns the creation surface (chat-first AI composer, strategy brief, split editor) but does not add structural capabilities that close gaps vs Canva AI 2.0 or Klaviyo. The prototype is structurally a chat wrapper around the existing generation pipeline — same Brand Kit inputs, same NEB rendering output, same single-channel email.

Competitive proof points

CapabilityCanva AI 2.0 / Klaviyo shipsFreddie status
Conversational campaign startCanva AI 2.0 & Klaviyo Marketing AgentChat UI exists, but wraps existing gen pipeline
Dream Lab / AI image generationCanva ships Dream LabNot in prototype
Magic Layers / AI design manipulationCanva ships Magic LayersNot in prototype
Brand Intelligence (update-all-templates)Canva ships brand-wide updatesNot in prototype
Live connectors (10+ enterprise apps)Canva ships live data connectorsNot in prototype
Web research / agentic orchestrationCanva ships web research agentNot in prototype
Universal Content (reusable blocks)Klaviyo Spring 2026 defaultNot in prototype
Marketing Agent (autonomous flow setup)Klaviyo GA Spring 2025Not in prototype
Smart Send Time per-profileKlaviyo shipsNot in prototype
Channel Affinity / Personalized A/BKlaviyo shipsNot in prototype
Image RemixKlaviyo shipsNot in prototype
Multi-author collaborationStensul, Knak ship; Klaviyo partialComments button placeholder only
NEB Code Mode / HTML escape hatchStensul, Knak, Klaviyo have code modeNot in prototype (Pillar 2.2.3)

Prototype surface concerns

  • 6 of 8 channel tabs are stubs (SMS, WhatsApp, Automation, Form, Survey, Social, Campaign) — “unified” is a tab bar, not a canvas
  • No Universal Content primitive — the most-requested feature and Klaviyo’s Spring 2026 default
  • No multi-author collaboration — Comments button is a placeholder

Usability concerns (from Design Audit Lens 4 heuristic audit)

  • 45 heuristic findings, 9 critical (S4), concentrated in Flow E (Send)
  • Manual mode hidden behind post-generation radio — power users forced through AI
  • Theme presets silently override Brand Kit
  • No audience confirmation at send — path to accidental mass-send
  • No AI-content verification — hallucinated footer addresses, promo codes, products
  • No version history in chat thread
  • “Move my cheese” risks: 14 identified, 5 critical

What UR and ecommerce experts wanted that’s missing

  • UR Bet #1: Universal Content — not in prototype
  • UR Bet #2: Feature discovery — partially addressed (chips help)
  • UR Bet #3: Vertical/ICP fit — DTC-only templates and copy
  • UR Bet #4: Multi-author — misrepresented (Comments button placeholder)
  • UR Bet #5: SMS depth — stubs only

Business impact

Without structural capability additions, Freddie is a design refresh on a shrinking base. Bulk Established −9.4% YoY continues. The competitive gap with Canva and Klaviyo widens, not closes. See Freddie Assessment and Klaviyo Brief.


C3 Legacy builder migration is stalled, and Freddie inherits the same barriers

We’re building a third version of the builder (Freddie), but the migration from legacy (Classic/NEA) to current (NEB/NUNI) is incomplete. Customers who haven’t moved won’t try Freddie either — same gaps, same barriers, now with added “move my cheese” risk.

Migration proof points (from NEA→NUNI Migration and Nuni YoY Audit)

  • 41.9% of paid users (384,261 of 917,145) are still on NEA — representing $566M ARR
  • $281M ARR concentrated in 38,145 HVC accounts on NEA — 52.2% of HVC are NEA stayers
  • 225,784 users tried NUNI and reverted back to NEA — more reverters than completed migrators (218,723)
  • 94.7% negative paid badge sentiment on NUNI — CES dropped 0.10 points (3.90 vs 4.00)
  • HVC migration funnel collapsed 91% — from 10,930/mo (May 2024) to 898/mo (April 2026)
  • Editor-cited churn: $1.32M ARR floor (adj. $3.96M); velocity doubled post-default-flip (48 → 94/mo)
  • Legacy Monthly plan: 91,746 users, 69.1% NEA share, $242M ARR — largest single NEA pocket
  • Top barriers: no code mode, no custom HTML, template incompatibility, rendering regressions, Brand Kit bugs

NEA→NUNI migration has a 3-phase parity-gated playbook that’s not complete

  • Phase 1 (months 0–3): default-flip low-risk — $60M ARR mitigated
  • Phase 2 (months 3–9): concierge nudge medium-risk — cumulative $182M
  • Phase 3 (months 9–18): hybrid + concierge for HVC — $281M protected
  • Classic sunset cannot happen until NEB Code Mode ships (protects ~$1–2M Premium/agency churn)

Why these customers won’t try Freddie

  • No HTML/CSS escape hatch (Critical finding B5 in Design Audit)
  • No template portability from Classic → Freddie
  • Brand Kit bugs amplified — every AI output uses Brand Kit data
  • Manual mode hidden — power users lose their primary workflow
  • No rendering parity guarantee
  • Freddie makes migration harder: legacy templates may not surface in recents (HVC #6 reverse); AI defaults make Premium feel more forced (HVC #12)

Business impact

The $566M paid NEA ARR base (of which $281M is HVC) represents the highest-ARPU, longest-tenured cohort. These customers are at risk of churn to Klaviyo, Stensul, or Knak if pushed toward a surface that removes their existing capabilities. Historical revert rate of 8–10% applied to $281M HVC ARR implies $23–28M ARR at risk from forced migration without parity. See NEA→NUNI Migration.


RECOMMENDED PATH FORWARD

1 Job #1: Fix the foundation before shipping Freddie as default

  • Ship NEB rendering parity — close HVC #3 (editor vs inbox mismatch, $1,820/mo)
  • Ship Brand Kit data correctness and font upload fix — close HVC #8, #10 ($3,350/mo)
  • Ship Content Studio stability and Canva sync — close HVC #13 ($2,500/mo)
  • Ship SMS TCPA guardrails and pre-send verification (hallucination guardrails) — close HVC #16 ($57K/mo)
  • Ship audience confirmation modal at send — prevent accidental mass-send (S4 finding)
  • Publish Builder SLOs as an operating contract (99.9% uptime, P95 <500ms, render fidelity ≥99%)
  • These are not P2 follow-ups — they are launch-blocking for Freddie

2 Don’t break what works — preserve customer mental models

  • Surface manual mode as primary entry point (not hidden behind AI post-generation radio)
  • Template origin filter (Classic / NEB / All) to prevent HVC #6 reverse ($1,950/mo)
  • Theme presets must apply-and-confirm, not silently override Brand Kit
  • Brand-context banner reframed from upgrade pressure to value framing for Free — mitigate HVC #12
  • Version history in chat thread for power-user confidence
  • Undo/redo in conversational editing — fix “one-way AI change” problem
  • Preserve “Edit in Classic” escape hatch for at least 12 months post-Freddie launch
  • Add AI-content verification step: flagged merge tags, hallucinated addresses, promo codes
  • Strategy-brief step should be skippable, not mandatory for returning users

3 Make structural changes, not just design changes — close competitive gaps

  • Ship Universal Content as a primitive (Klaviyo parity, most-requested feature) — Klaviyo Brief
  • Ship NEB Code Mode before any Classic sunset communication (protects ~$1–2M Premium/agency churn)
  • Add conversational editing, Dream Lab, Brand Intelligence from Phase 1 spec (Canva gap closure) — Freddie Phase 2
  • Add per-profile Smart Send Time, AI Performance Watchdog, Mailchimp Shield from Phase 2 spec (ESP-native moat) — Freddie Phase 2
  • Build toward unified email+SMS canvas — not just a tab bar with stubs
  • Ship real-time multi-author collaboration (Stensul/Knak parity) — Initiative Canvas P5
  • Ship cross-template reuse and NEA → NUNI template migration tool — Initiative Canvas P2
  • Add in-canvas revenue attribution — the Intuit ecosystem advantage no standalone ESP can replicate
  • Ship AI image generation at Canva grade — Initiative Canvas P4.4.4

Sources: All figures from existing brief tabs — HVC Risk Map, VoC, Product Health, Revised Goals, Freddie Assessment, Design Audit, NEA→NUNI Migration, Nuni YoY Audit, Initiative Canvas, Klaviyo Brief, Freddie Phase 2. No fabricated data. May 2026.

Tab 18 · Agent Mode Design + UX Assessment of the Freddie prototype

The Builder Lens Stack — a 5-lens framework

Structured design + UX assessment of the new Freddie / AI Email Generator prototype (ai-email-generator-steel.vercel.app) using a 5-lens framework spined by the Builder Hierarchy of Needs (6 levels) + 7-Phase JTBD Creation Journey already adopted in this brief's strategy work. Answers: page hierarchy, workflow hierarchy, components & widgets, component relationships, design approach, usability & UX, and per-component functional benefit + customer problem solved. Cross-references Tab 17 (Strategy fit), HVC Risk Map, User Research, Revised Goals.
v2.0 · 8 pages · May 2026
96 components · 45 heuristic findings · 9 critical risks · 26 prioritized improvements (P0/P1/P2)
96
Components mapped (atoms / molecules / organisms / templates)
45
Heuristic findings (Nielsen 10 + 5 AI heuristics + WCAG 2.2 AA)
9 critical
S4 findings — launch-blocking; concentrated in Flow E (Send)
~$12.4M
Plausible Revised Goals capture mid-estimate (49–70% of $21M)
Bottom line. The design is a demo of where AI fits — not a delivery of the FY27 strategy. It is strong on activation (T1 + F2 + PA1 = ~58% of the $21M target) and credible on brand-voice consistency. It does not touch the dollar concentrations (SMS TCPA, Brand Kit reliability, rendering parity, multi-author, custom code) and it amplifies risk on several HVC themes. The Builder Hierarchy heatmap reveals the design over-invests in L3-L5 (where Mailchimp already scores 3-5) and under-invests in L1, L2, L6 (where the dollar gaps are). Verdict: Iterate, don't ship as default. Ship the prototype as a feature-flagged front door for T1 (trial) + F2 (free activation) only, with 5 launch-blocking mitigations from Lens 4, and concurrent shipping of Pillar 1.5 Builder SLOs + 2.1 Universal Content + 5.2 SMS TCPA guardrails.

01The 5 lenses — what each captures

Each lens produces a distinct artifact. The Component × JTBD Matrix (Lens 3) is the spine; every other artifact carries component_id as the join key.

LENS 1

Structural IA

Sitemap · route hierarchy · modal vs route · tab-vs-page rationale

LENS 2

Interaction Model

State transitions · 5 task flows · entry/exit · error states

LENS 3 (SPINE)

Component × JTBD

96 components · per-component: customer problem, benefit, JTBD phase, BH level

LENS 4

Heuristics + a11y

Nielsen 10 + 5 AI heuristics + WCAG 2.2 AA · severity 0-4

LENS 5

Strategy Overlay

Builder Hierarchy heatmap · Pillar coverage · RICE top-10

02Why this framework over alternatives

Considered alternativeRejected because
Nielsen 10 onlyDoesn't cover state machines, JTBD mapping, or strategy fit. Closes only 1 of 4 named gaps.
Pure JTBD component mapTells you "why each component exists" but says nothing about heuristic violations, accessibility, or state transitions. Closes 1 of 4 gaps.
Atomic Design aloneAlready implicitly done in docs/04-components.md. Repeating adds no information.
Lightweight single-canvas auditFlattens the IA/state-machine layer (gap #1) and won't carry a stakeholder readout.
Full Hybrid B (6 layers)Builder Hierarchy as a standalone layer duplicates JTBD. Folding it in as a scoring overlay is leaner.

03How the 5 lenses join (the spine model)

Lens 1 (IA Map) ────────────────────────────┐ ↓ Lens 2 (State Diagram) ── feeds task selection for ──→ Lens 4 (Heuristic walkthrough) ↓ Lens 3 (Component × JTBD Matrix) ── is the index table for ──→ everything else ↑ Lens 4 (Heuristic Scorecard) ── component_id joins back to ──→ Lens 3 ↑ Lens 5 (Strategy Overlay) ── component_id joins back to ──→ Lens 3 + scores from Lens 4

Where to find the source documents: Each lens has a markdown source at /Users/dprabhakara/ai_workspace/freddie-design-assessment/lenses/0[1-5]-*.md. Component inventory pulled from ai-email-generator-decomp/docs/04-components.md. State diagrams sourced from docs/05-generation-flow.md + screenshots 17-25. Strategy alignment per Strategy Memo Builder Hierarchy of Needs framework.

Tab 18 · Page 2 of 8 · Lenses 1 + 2

IA map + state diagram

Answers: page hierarchy (parent/child relationships) · workflow hierarchy (step ordering & state transitions) · how the page is built from a design standpoint (shell switching, modal-vs-route).
3 real routes · 2 distinct shells · 5 task flows

2.1The sitemap (real + placeholder)

freddie / ai-email-generator-steel.vercel.app │ ├── ROOT SHELL — "Home dashboard" shell (yellow stripe + global nav) │ └── / (Home dashboard) — REAL ROUTE │ ├── Top bar (Search, Live expert help, Avatar) │ ├── Left product nav (PLACEHOLDER — only Create is functional) │ │ ├── Create → routes to /create │ │ ├── Home ⊙ (active) │ │ └── 9 more nav items (Campaigns, Automations, SMS, Forms, Audience, │ │ Analytics, Website, Content, Integrations) — all placeholders │ └── Main: Marketing conversions + Audience + Revenue + Recent campaigns │ └── CONVERSATION SHELL — "Create / Chat" shell (no global product nav) │ ├── /create — REAL ROUTE │ ├── Sidebar (collapsed 60px / expanded 240px) │ │ ├── + New (start fresh conversation) │ │ ├── Conversation list (empty state "No conversations yet") │ │ └── Footer: Prototype settings + Brand & business context │ ├── Tab pill bar (8 channels — 6 of 8 are stubs) │ │ ├── Email [Pattern A — AI composer + recents + templates] │ │ ├── SMS [Pattern A] │ │ ├── WhatsApp [Pattern A] │ │ ├── Automation [Pattern B — no AI; recents + scratch + templates] │ │ ├── Form [Pattern C — type cards + template grid] │ │ ├── Survey [Pattern C] │ │ ├── Social [Pattern C-stripped — hero card only] │ │ └── Campaign [Pattern A-stripped — composer only] │ └── First-run onboarding overlay (URL importer) │ └── /chat — REAL ROUTE ├── Sidebar (persists from /create) ├── Chat thread column (left) └── Right panel (STATE A: strategy brief OR STATE B: email editor) └── Modal layer: Brand Kit, Prototype settings, Theme popover

2.2The two-shell switching decision

The app has two distinct shells. Clicking Create from Home doesn't just navigate — it disposes of all global navigation. The user loses the path back to Analytics, Audience, Campaigns. The only way back is the × Exit button → /, which is a one-way trap-door pattern.

2.3Modal vs route decisions

SurfaceTypeWhy this choice · where it hurts
Brand KitModal (full-screen)Cross-cutting context. Modal correct — it's a "setup" task. Issue: apply-on-save behavior invisible (pre-mortem #6).
Prototype settingsPopoverQuick-toggle area. Popover correct.
Theme editorPopoverQuick-toggle visual style. Popover correct. Issue: presets can override Brand Kit silently (pre-mortem #10).
OnboardingOverlay on /createDisposable once dismissed. Reasonable.
Email editor canvasRight-pane state (not a route)Questionable: editor un-deep-linkable. User can't share "the editor on this email."
Strategy panelRight-pane state (mutex with editor)Questionable: brief un-deep-linkable. Browser back/forward breaks.

2.4Five task flows + their highest-severity risks

FlowBuilt?Avg sev.Highest-severity risk
A · Cold start (free → first send)✅ Yes2.45#5 brand-context banner upgrade pressure
B · Power user (skip AI)❌ Not really3.00#2 manual mode hidden behind post-generation radio (Critical)
C · Brand Kit loop-back✅ Modal works3.00#6 Brand Kit data amplification
D · Refinement loop in editor✅ Three paths2.56#10 theme preset overrides Brand Kit silently
E · Send (terminal action)✅ Buttons present3.57#4 TCPA-class incident path (Critical · 4 of 9 S4 findings here)

2.5The "state contract" gap

The prototype doesn't make clear what state is preserved, where, and when. Three classes of state are at play — Brand Kit (shared), conversation thread (per conversation), in-flight email draft (per chat), manual edits, theme selection. The user has no published contract: "Your draft is saved every X seconds. Manual edits are preserved when switching to AI unless you explicitly regenerate the section." This drives the Save-vs-Send ambiguity (pre-mortem #9) and the AI ↔ manual round-trip fragility (Flow D).

Full source: Lens 1 + Lens 2 detailed write-ups at freddie-design-assessment/lenses/01-structural-ia.md and 02-interaction-model.md. State diagrams use Mermaid stateDiagram-v2; rendered in the source markdown.

Tab 18 · Page 3 of 8 · Lens 3 (the spine)

Component × JTBD Matrix

Answers: widgets and components used · relationships between components · per-component functional benefit + customer problem solved. 96 components mapped, each with: hierarchy level (atom/molecule/organism/template) · customer problem · functional benefit · JTBD phase (1 of 7) · Builder Hierarchy level (1 of 6).
96 components · 8 groups · 0 HVC themes directly solved by any single component

3.1Distribution by hierarchy level (Atomic Design)

LevelCountShareRead
Atom3840%Single primitives (buttons, inputs, icons, badges)
Molecule3941%Small atom groups (chips, KPI cells, search bar)
Organism1617%Distinct UI regions (composer, modal, panel, card)
Template22%Layout patterns (Home shell, Conversation shell)
Total95100%

3.2Distribution by JTBD phase

JTBD PhaseCount%Verdict
P1 Choose structure1418%Strong — onboarding + chips + recents + templates all here
P2 Establish brand & style1823%Strongest — Brand Kit modal + theme popover + style inputs
P3 Add & place content (Compose)1722%Strong — composer + chat + canvas + manual blocks
P4 Refine & polish (Compose)810%Adequate — follow-up chips + edit/redo + theme tweaks
P5 Personalize & tailor810%Adequate — strategy panel fields + brand voice
P6 Preview & QA loop912%Adequate — viewport radio + Preview + Send test + KPIs
P7 Learn & reuse57%Gap — recents + drafts + AI feedback only, no Universal Content

3.3Sample matrix rows — the key components on each surface

Full 96-row matrix in source 03-component-jtbd-matrix.md; 18 representative rows shown here.

App-shell components

IDComponentLvlCustomer problem solvedFunctional benefitJTBDBHHVCVerdict
C-07Left product nav (Home shell)Org"Get me to the area I care about"Product-area navigation (11 items)L3Risk 10 of 11 placeholders
C-09Sidebar expanded (Conv shell)Org"Show me my conversations"Conversation history + settings + brand contextP7L3Partial no search/rename
C-12Exit (×) buttonAtom"Get me out of here"One-click return to homeL3Risk one-way trap-door

Create-tab + composer components

IDComponentLvlCustomer problem solvedFunctional benefitJTBDBHHVCVerdict
C-13Tab pill bar (8 channels)Org"Which channel am I creating for?"Channel switcherP1L6Risk 6 of 8 stubs
C-16AI composer shell (Pattern A)Org"Blank-page paralysis"Prompt-to-email primary flowP1, P3L5Solves primary value prop
C-19Prompt input textareaAtom"Describe what I want"Free-form prompt entryP1L5Solves
C-23Brand-context bannerMol"AI doesn't know my brand"Reminds + gates better outputP2L4#8Critical Risk upgrade pressure on Free
C-25Quick-prompt chip (↳)Mol"I don't know what to ask"Pre-seeded prompt examplesP1L5Solves
C-27"Start from recent email" carouselOrg"I have unfinished work"Resume Drafts + edit SentP1, P7L3#6Critical Risk origin filter missing

Chat thread + strategy panel components

IDComponentLvlCustomer problem solvedFunctional benefitJTBDBHHVCVerdict
C-41Assistant artifact card (Ready pill)Mol"Did AI succeed?"Status indicatorP3, P6L5Partial no Failed state
C-43Assistant message body (prose)Mol"Explain what AI did + why"Narrative reasoningP3, P6L5Solves strong UX pattern
C-44Copy/Like/Dislike/Regenerate rowMol"Tell AI it was good/bad"Feedback loop + iterationP4, P7L5Solves standard pattern
C-48Strategy: Recipients selectMol"Who gets this?"Audience selectionP5L5Critical Risk no audience confirm at send

Editor + manual mode components

IDComponentLvlCustomer problem solvedFunctional benefitJTBDBHHVCVerdict
C-57Mode radio (✦ AI / pencil manual)Mol"AI or manual?"Mode switcherP1, P3L5Critical Risk manual hidden post-gen
C-58Viewport radio (desktop/mobile/split)Mol"How does it look on different devices?"Multi-viewport previewP6L2#3Partial doesn't fix divergence
C-67Send email split button (▾)Mol"Ship it" + alt actionsPrimary + Save draft + ExportP6L3Critical Risk no audience confirm
C-70Suggested follow-up toolbarMol"What should I refine?"Pre-seeded refinement promptsP4L5Solves strong discovery

Brand Kit modal components

IDComponentLvlCustomer problem solvedFunctional benefitJTBDBHHVCVerdict
C-85Logo upload tileOrg"Add my logo"Logo upload + variantsP2L4#9Risk single-brand only
C-87Font selectors (Heading/Body/Base size)Mol"Apply brand fonts"Hardcoded 23-font dropdownP2L4#10Critical Risk no upload UI
C-89Brand voice composite (4 sub-fields)Org"Define brand tone for AI"Personality/Formality/CTA/Headline styleP2, P5L5Solves AI input

Read the full 96-component matrix: freddie-design-assessment/lenses/03-component-jtbd-matrix.md. Each row carries component_id as the join key into Lens 4 (heuristic findings) and Lens 5 (strategy fit). HVC theme cross-references resolve to HVC Risk Map.

Tab 18 · Page 4 of 8 · Lens 4

Heuristic + Accessibility scorecard

Answers: usability and user experience. Each of the 5 task flows from Lens 2 walked against Nielsen's 10 + 5 AI-specific heuristics (Microsoft HAX / Amershi) + WCAG 2.2 AA spot-check on top 10 components. 45 total findings · 9 critical (S4) · concentrated in Flow E (Send).
Nielsen 10 + 5 AI + WCAG 2.2 AA · severity 0–4 · 9 S4 · 22 S3 · 13 S2 · 1 S1

4.1The 15 heuristics applied

Nielsen 10 (classical)5 AI-specific (Microsoft HAX / Amershi)
N1 Visibility of statusAI1 Make clear what AI can do
N2 Match with real worldAI2 Make clear how well AI can do it (calibrated trust)
N3 User control & freedomAI3 Time services based on context
N4 Consistency & standardsAI4 Scope services when in doubt (graceful degradation)
N5 Error preventionAI5 Support efficient correction
N6 Recognition over recall+ severity scale: S0 none · S1 minor · S2 moderate · S3 major · S4 critical (HVC-class)
N7 Flexibility & efficiency
N8 Aesthetic & minimalist
N9 Help recognize/recover errors
N10 Help & documentation

4.2Heuristic coverage summary (45 findings across 15 heuristics)

HeuristicS4S3S2S1TotalComment
N1 Visibility of status04419Most-cited issue: status weak across loading, autosave, post-send
N3 User control & freedom14005Power-user flow worst — manual hidden, no skip-AI, no version history
N5 Error prevention42107Highest critical-finding count
N9 Recover from errors12003Font-upload bug + send-error + Brand Kit incident recovery
AI2 Calibrated trust12003No confidence indicator, no change summary, no AI-content verification at send
AI4 Scope when in doubt13004URL fail + incomplete Brand Kit + power-user signal + SMS compliance
AI5 Efficient correction02305No preview-before-apply, no version history, no field-edit signal
Others (N2, N4, N6, N7, N8, N10, AI1, AI3)1 S4 + 5 S3 + 5 S2 = 11 findings11Lower-density issues
TOTAL92213145

4.3The 9 critical (S4) findings — launch-blocking

#FlowHeur.FindingRecommendation
A10A Cold startN5"Send email" has no audience-confirmation modal · 2,150 subs / 1 clickMandatory confirm modal w/ recipient count
B1B Power userN3Manual mode is post-generation · must interact w/ AI firstPrimary "Skip AI — open blank editor" button
B5B Power userN7No HTML escape hatch even in manual · Premium/agency ceilingShip NEB Code Mode (Pillar 2.2.3, Q3)
C5C Brand KitN9No font upload affordance · HVC #10 ($3,350/mo) unfixableAdd "+ Upload custom font" + AI font-recognition parity
D4D RefinementN5Theme preset can silently override Brand Kit (Wes Turner pattern)Apply-and-confirm dialog: "Keep brand colors / override w/ preset"
E1E SendN5Same as A10 from editor surfaceSame mitigation
E2E SendAI2No AI-content verification at send · hallucinated footer/promo/productsPre-send checklist: footer verified, promos match catalog, products in stock
E4E SendN5"Send a test email" has no recipient modal · could go to wrong addressRecipient picker modal w/ own email pre-filled
E7E Send (SMS)AI4SMS AI can generate non-TCPA-compliant content · replays $57K HVC #16Feature-flag SMS tab OFF until I-5.2.3 guardrails ship

Critical observation: 5 of 9 criticals are concentrated in Flow E (Send). The most consequential transition is the most underspecified flow in the prototype.

4.4WCAG 2.2 AA spot-check on top 10 components

No critical Level A failures spotted at a glance, but multiple AA-borderline issues:

  • Icon-only buttons (Copy, Like, Dislike, Regenerate, mode radio) need aria-label
  • Touch-target sizing (24×24) should be 44×44 per WCAG 2.2 SC 2.5.8 — affects mode radio, viewport radio, theme preset cards
  • Mode switcher needs role="radiogroup" + clear "AI" vs "Manual" labels for screen readers
  • Send buttons should include recipient count in accessible name: "Send email to 2,150 recipients"
  • Brand-context banner needs role="region" + aria-label
  • Theme popover needs dialog role + focus trap + escape close

Recommendation: full WCAG 2.2 AA audit by an a11y specialist before GA — especially because this surface is the entry point for ~870K monthly Free users where assistive-tech usage is non-zero.

4.5Severity heatmap (cross-flow)

FlowS4S3S2S1TotalAvg severity
A Cold start1541112.45
B Power user242083.00
C Brand Kit loop141063.00
D Refinement loop135092.56
E Send430073.57

Full source: Lens 4 write-up at freddie-design-assessment/lenses/04-heuristic-accessibility.md. Each finding cross-references component_id from Lens 3 + a Recommendation. Screenshots referenced via ai-email-generator-decomp/screenshots/ (29 PNGs).

Tab 18 · Page 5 of 8 · Lens 5 + Top-10 RICE

Strategy-fit overlay + top-10 recommendations

Builder Hierarchy heatmap (where the design invests vs where the strategy says the gaps are) + FY27 Pillar coverage scorecard + top-10 RICE-scored recommendations. Exec decision unblocked here: go / iterate / kill verdict for Freddie's direction.
~$10–15M capture (mid ~$12.4M / 59% of $21M) · $6–18M downside if criticals unmitigated

5.1Builder Hierarchy heatmap — the strategic decoupling

The density of components per Builder Hierarchy level shows where the prototype invests vs where the strategy has the biggest gaps. The design optimizes for L3-L5 (where Mailchimp already scores 3-5) and under-invests in L1, L2, L6 (where the dollar exposures concentrate).

Builder Hierarchy levelCntDensityVerdict
L1 Reliable & Performant4 5%Under-invested L1 is foundational
L2 Mobile & Rendering3 4%Under-invested HVC #3 ($1,820/mo)
L3 Efficient Workflow36 47%Over-invested most components live here
L4 Brand-Native & Reusable19 25%Strategic fit Pillar 2 ships through here
L5 Intelligent & AI-Powered16 21%Strategic fit Pillar 4 ships through here
L6 Omnichannel & Extensible3 4%Critical gap HVC #16 ($57K), Bet 4 (multi-author)

5.2FY27 Pillar coverage scorecard

PillarStrongPartialMissRiskNotes
P1 Quality & Trust0221Builder SLOs missing; Brand Kit reliability amplification risk
P2 Universal Content + Migration0030Universal Content primitive entirely missing
P3 Activation2101Prototype IS this pillar — strong fit
P4 AI1021Conversational wedge built; image gen + Smart Send + Watchdog missing
P5 Unified Canvas + Collab0031Co-edit misrepresented (Comments button); SMS TCPA risk; tabs ≠ canvas

5.3Capture roll-up (carried forward from Tab 17)

CohortTarget $Capture estimateCapture %
Paid$6.7M$2.4–3.8M36–57%
Free$8.7M$4.1–6.0M47–69%
Trial$5.6M$3.7–4.9M66–88%
Total$21.0M$10.2–14.7M49–70%
Mid estimate~$12.4M59%

5.4Top-10 RICE-scored recommendations

Formula: Reach (cohort) × Impact (Lens 4 severity) × Confidence × Effort.

#RecommendationReachImpactRICE
1Mandatory audience-confirmation modal at Send (E1, E4) — 2,150 subs, one click is the path to the $57K-class TCPA incidentAll paid (~1M)S4HIGH
2Feature-flag SMS tab OFF until TCPA guardrails ship — $57K/mo at risk; AI can trivially generate non-compliant SMS todaySMS (6.7K)S4HIGH
3AI-content verification pre-send (E2) — footer address, promo codes, products must bind to real entities, not hallucinationsAll AI usersS4HIGH
4Surface manual mode as primary entry + remember preference (B1, B2, B4) — $281M HVC NEA stayer risk if forced through AIPremium+agencyS4HIGH
5Reframe brand-context banner from upgrade pressure → value framing for Free (A3, C-23) — F4 CSAT regression riskFree (~870K)S3HIGH
6Add font-upload UI in Brand Kit + AI font-recognition parity (C5) — HVC #10 ($3,350/mo) currently unfixable on this surfacePremiumS4MED
7Templates carousel must have surface-origin filter (NEB / Classic / All) — HVC #6 reverse for Classic anchorsClassic anchorsS3MED
8Theme preset application must respect Brand Kit (apply-and-confirm) (D4) — Wes Turner pill-CTA pattern recurs otherwiseAll AI usersS4MED
9Ship Universal Content primitive concurrently with this surface (Pillar 2.1) — the 2026 most-asked feature is the P7 gapAll editor usersS3MED
10Add version history in chat thread (D1) — per-generation rollback; restores Jack Hally / all-week ad-libber personaPower usersS3MED

06Dual-mode bottom lines

AudienceRead
Exec audienceGo / Iterate / Kill verdict: Iterate, don't ship as default. $10–15M upside is real (T1 + F2 activation), but $6–18M downside from unmitigated criticals could net flat or negative. Spend: ship as feature-flagged front door for trial + free signups, with 5 launch-blocking mitigations + concurrent shipping of P1.5 / P2.1 / P5.2.
Design-team audienceThe 45 findings from Lens 4 + 96 components in Lens 3 are the actionable backlog. Top priority: Flow E (Send) is the weakest flow with 4 of 9 criticals concentrated there. Second priority: Power-user (Flow B) needs structural rethink — manual mode shouldn't be post-generation only. Pattern to internalize: Brand Kit centrality means every Brand Kit bug becomes an email-level bug.

Sources cited: All 5 lens markdown files at /Users/dprabhakara/ai_workspace/freddie-design-assessment/lenses/. Decomposition at ai-email-generator-decomp/docs/01-10. Cross-references to Tab 17 Strategy fit assessment, HVC Risk Map, User Research, Revised Goals, Initiative Canvas, Strategy Memo. Framework adopted from Builder Hierarchy of Needs + 7-Phase JTBD Creation Journey (per Nuni Builder Strategy & Roadmap: Ose Amiegheme, Erin McCue, JB Lovell, Ashley Wiesner).

Tab 18 · Page 6 of 8 · Complete Feature Catalog

Features, Functionality & Micro-Experiences Catalog

Exhaustive reference of every feature, functionality, and micro-experience the Freddie / AI Email Generator prototype delivers. For each item: what it is, what it does, the customer pain point it solves, and the business benefit it creates. Organized into 8 functional groups. Cross-references component IDs from Lens 3 where applicable. Use this as an engineering/design handoff document: "what does every piece of this prototype do and why."
8 functional groups
~65 discrete features cataloged
Prototype: ai-email-generator-steel.vercel.app
How to read this page. Each table row is a discrete feature or micro-experience. The "Pain Point" column names the real customer problem (drawn from HVC data, user research, and workflow analysis). The "Benefit" column maps to a measurable business outcome where possible. Items marked with CRITICAL have associated launch-blocking findings from Lens 4.

7.1AI-Powered Creation

The core AI generation pipeline — from blank page to rendered email in <30 seconds.

FeatureWhat it doesCustomer pain pointBenefitRef
Prompt-to-email generationUser types a free-form text prompt describing their email; AI returns a fully rendered, multi-section HTML email in the canvas within ~15–30s.Blank-page paralysis — 68% of trial users who open the editor never send a first campaign (T1 activation gap = $5.0M).Collapses "think → plan → write → design → code" into a single conversational action. Directly attacks T1 trial activation ($5.0M) and F2 free activation ($3.6M).C-16, C-19
Quick-prompt chipsPre-seeded contextual suggestion pills ("Welcome series," "Flash sale," "Product launch," "Newsletter") appear below the composer. Clicking one pre-fills the prompt field with a structured starting point."I don't know what to ask the AI" — user research Bet 2 (Discovery) shows new users struggle to articulate what they need from AI tools.Reduces cognitive load at the highest-friction moment. Surfaces capabilities the user didn't know existed. Increases prompt-submit rate for users who would otherwise abandon.C-25
AI composer shell (Pattern A)The primary creation surface combining prompt input + quick chips + recent emails + template carousel into a single above-the-fold composition area. Active on Email, SMS, and WhatsApp tabs.Feature discovery failure — multiple creation paths (prompt, template, recent, blank) scattered across different pages in classic Mailchimp.Single entry point handles all creation intents. Every path to "first email" is visible without navigation. Supports Fast Monday workflow shape (time-to-first-action <3 min).C-16
Strategy brief generationAfter prompt submission, AI generates a structured strategy brief (Goal / Date / Recipients / Promo / Focus Metric / Featured Products / Visual Style) that the user reviews and approves before email rendering begins."AI just does whatever it wants" — users feel loss of control when AI generates without showing its reasoning first. Creates trust deficit.Gives user a checkpoint between intent and execution. Reduces regeneration cycles (each regen costs ~15s + user frustration). Establishes calibrated trust (AI heuristic AI2).C-45–C-52
Conversational editingAfter initial generation, user can type follow-up prompts in the chat thread ("Make the header bolder," "Add a countdown timer," "Change the CTA to Shop Now") and AI applies targeted edits to the existing email."I like 80% of what AI made but fixing the other 20% requires starting over" — incremental refinement is the dominant workflow shape (#3 "Thursday Iterator").Preserves the user's investment in prior generation. Makes AI-assisted editing feel like collaboration, not slot-machine pulls. Directly maps to the Thursday Iterator workflow shape (56% of sessions).C-39–C-44
Suggested follow-up chips (post-generation)After AI generates an email, a floating toolbar shows contextual refinement suggestions: "Add a CTA," "Change the theme," "Check for accessibility," "Optimize for mobile."Users don't know what's possible next — after getting a generated email, the next best action is invisible. Users either accept as-is or abandon.Guides the refinement loop without requiring prompt-writing skill. Increases average edits-per-session (proxy for engagement + satisfaction). Surfaces capabilities like accessibility checking that users would never find unprompted.C-70

7.2Brand & Style Intelligence

How the prototype learns, stores, and applies brand identity to AI outputs.

FeatureWhat it doesCustomer pain pointBenefitRef
Brand Kit modal (full-screen)A full-screen modal with 7 sections: My Business, Logos, Colors, Fonts, Buttons, Brand Voice, and Social Links. Persists across all conversations and emails.Brand inconsistency across campaigns — HVC #8 ($4,800/mo): "Every email looks different because there's no single source of truth for brand settings."Establishes a durable brand state that every AI generation inherits. Eliminates per-email brand configuration. Reduces "brand drift" across team members sharing an account.C-80–C-95
Brand voice configuration (4 sub-fields)Structured inputs for Personality (warm/professional/playful), Formality level, CTA style, and Headline style. AI uses these fields to calibrate generated copy tone."AI writes generic copy that doesn't sound like us" — the #1 objection to AI content tools from brand managers and agency users (UR Bet 3, vertical fit).Differentiates AI output per customer. Reduces "sounds like ChatGPT" rejection rate. Critical for agency persona (Workflow Shape #4) managing multiple client brands.C-89
Brand personality selectorA single dropdown or radio group choosing from personality archetypes (e.g., Friendly, Professional, Bold, Playful). Feeds the Brand Voice composite.Users can't articulate their brand voice in free-form text — they know it when they see it but can't describe it from scratch.Reduces setup friction from "describe your brand" (hard) to "pick the closest match" (easy). Gets users to a usable Brand Kit state faster.C-89
Auto-brand extraction from URLThe onboarding overlay prompts the user to paste their website URL. The system scrapes the URL and auto-populates Brand Kit fields (logo, colors, fonts, business name)."I spent 20 minutes setting up brand colors and they still don't match my website" — manual brand setup is error-prone and tedious for non-designers.Reduces Brand Kit setup from ~8–12 minutes to ~30 seconds. Increases the % of accounts with a populated Brand Kit (prerequisite for quality AI output). Directly attacks first-run abandonment.C-96 (onboarding)
Brand-context bannerA persistent banner on the AI composer showing Brand Kit completeness state. Links to Brand Kit modal. On Free tier, implies upgrade value for full brand features."AI doesn't know my brand" — users who skip Brand Kit setup get generic outputs and blame AI quality rather than missing context.Creates a contextual nudge at the moment of need (not in settings, not in onboarding). Increases Brand Kit completion rate. CRITICAL Risk: upgrade pressure on Free (HVC theme #8, CSAT regression F4).C-23
Theme presets (8 in Light/Dark)A floating popover with 8 visual theme presets, each in Light and Dark variants. Clicking applies the theme's color palette, typography, and layout proportions to the current email."I want my email to look good but I'm not a designer" — visual design is the #2 barrier to email completion after copywriting (per activation funnel data).One-click professional design without design skills. Serves the 43% of users who never customize beyond defaults. CRITICAL Risk: can silently override Brand Kit colors (D4 finding).C-72–C-78
Color palette configurationBrand Kit section with primary, secondary, and accent color pickers. Colors automatically flow into AI-generated email components.Manual color entry per-campaign is repetitive and error-prone — users copy hex codes from external tools or guess from memory.Set once, use everywhere. Eliminates color inconsistency across campaigns. Reduces "on-brand" review cycles for teams.C-86
Logo upload + variantsMulti-slot logo upload supporting primary, secondary, and icon variants. AI selects appropriate logo variant based on email context (header vs. footer vs. mobile)."I uploaded my logo but it looks wrong in the header because it's the wrong aspect ratio for that spot."Context-aware logo selection means the user doesn't need to micromanage asset placement. Risk: single-brand only (HVC #9).C-85
Font selectors (Heading/Body/Base size)Dropdown selectors for heading font, body font, and base size. Currently ships 23 hardcoded web-safe fonts."I can't use my actual brand font" — HVC #10 ($3,350/mo): custom font upload is unavailable, breaking brand continuity for Premium users.Provides basic typography control for standard fonts. CRITICAL Gap: no upload UI means Premium/agency users hit a ceiling.C-87

7.3Content & Design Tools

The manual editing layer — for users who want hands-on control or need to refine AI output.

FeatureWhat it doesCustomer pain pointBenefitRef
Drag-drop block editor (manual mode)A full block-based email editor with draggable content blocks (Text, Image, Button, Divider, Spacer, Columns, Table, Social, Video, HTML). Blocks can be reordered, duplicated, deleted."I need pixel-level control that AI can't give me" — Power users (Workflow Shape #2, #4) need direct manipulation for complex layouts, conditional content, and brand-specific formatting.Provides a familiar editing paradigm for Classic Mailchimp users. Ensures the AI-first surface doesn't strand power users who need fine-grained control. Reduces "AI or nothing" perception.C-57–C-66
Image editing / selectionInline image handling within the editor — upload, select from library, basic crop/resize. Images dropped or selected populate the active block."Adding images to my email is a multi-step process that breaks my flow" — image management is the #3 friction point in email creation after copy and design.Keeps the user in flow state during content creation. Reduces context-switching to external image tools.C-63
Manual mode toggleA mode radio (✦ AI / pencil Manual) that switches the editor canvas between AI-assisted generation and direct block manipulation."I want to start in manual without waiting for AI" — power users (HVC $281M NEA-stayer segment) perceive forced AI interaction as a time tax. CRITICAL: currently hidden post-generation only.Gives power users a zero-friction path to their preferred workflow. Signals that manual editing is a first-class citizen, not an afterthought. Critical for retention of the $281M HVC NEA-stayer segment.C-57
Split editor view (chat + canvas)After prompt submission, the UI transitions to a two-column layout: chat thread (left) and email canvas (right). Both panels are simultaneously visible and interactive."I can't see my instructions and the result at the same time" — traditional AI tools show either the prompt or the output, requiring mental mapping between request and result.Enables real-time correlation between "what I asked" and "what I got." Supports the conversational editing pattern (iterative refinement without losing context).C-39, C-55
Viewport preview (Desktop / Mobile / Split)A radio group that switches the canvas between desktop-width, mobile-width, and side-by-side split renderings of the current email."My email looked great on desktop but broke on mobile" — HVC #3 (rendering divergence). 62% of email opens are on mobile; desktop-only preview misses the majority use case.Catches responsive design issues before send. Reduces "oops" moments post-send. Partially addresses HVC #3 (doesn't fix rendering parity, but surfaces problems earlier).C-58
Templates carouselA horizontally scrollable carousel showing pre-built email templates with thumbnail previews. Clicking a template loads it into the editor as a starting point."I don't want to start from scratch every time" — repeat users want to build on proven patterns rather than regenerating from prompts each session.Provides a non-AI entry point for users who prefer structure over generation. Reduces time-to-first-edit for returning users. Risk: no origin filter (Classic/NEB/All) — HVC #6.C-28
Recent emails carouselA horizontally scrollable section showing the user's recent draft and sent emails with status pills (Draft / Sent). Clicking loads the email for editing or cloning."I have unfinished work but can't find it" — users who interrupt their workflow mid-draft need fast resume capability (Workflow Shape #1: Fast Monday).Reduces average session-start time from "find where I left off" to "click and continue." Increases draft completion rate (a leading indicator of send rate).C-27
Block sections panel (manual mode)A left sidebar panel in manual mode listing available content block types organized by category (Content, Layout, Commerce, Advanced). Blocks are dragged from this panel into the canvas."I can't find the block type I need" — in classic Mailchimp, block types are nested in menus that require exploration.Visual, scannable inventory of all capabilities. Reduces "I didn't know I could add a countdown timer" discovery failures.C-60–C-66

7.4Collaboration & Feedback

The conversational layer between user and AI — creating a sense of working with a collaborator, not a tool.

FeatureWhat it doesCustomer pain pointBenefitRef
Chat thread (conversation history)A scrollable message thread showing the full history of user prompts and AI responses for the current session. Messages persist across mode switches (AI ↔ manual)."I forgot what I asked the AI to do three iterations ago" — without history, users lose track of their creative decisions and can't explain choices to stakeholders.Creates an auditable decision trail. Enables "why did we do it this way?" retrospectives. Supports multi-session workflows where the user returns to in-progress work.C-39
Assistant reasoning (prose explanation)Each AI response includes a narrative explanation of what the AI did and why: "I chose a warm color palette because your brand voice is set to Friendly, and used a single-column layout for mobile readability.""The AI changed things but I don't understand why" — opaque AI behavior creates distrust. Users reject outputs they can't rationalize to their boss or clients.Builds calibrated trust (AI heuristic AI2). Reduces regeneration rate by explaining choices before the user dismisses them. Teaches the user what good email strategy looks like (educational side-effect).C-43
Follow-up suggestion chips (in thread)After each AI response, 2–4 contextual suggestion chips appear below the message, offering logical next actions based on the current email state."I don't know what to do next after the AI generates" — the post-generation moment has the highest abandonment risk because the next action is ambiguous.Reduces post-generation drop-off. Guides users through the refinement loop without requiring prompt-writing expertise. Each chip represents a capability the user might not have discovered otherwise.C-70
Copy button (message-level)Per-message action that copies the AI's response text to clipboard."I want to use this copy in another tool (landing page, ad, social post)" — email copy is often repurposed across channels.Supports cross-channel content reuse without manual selection. Small friction reducer that signals "your content is portable."C-44
Like / Dislike feedbackThumbs up / thumbs down buttons per AI response. Captures implicit quality signal for model improvement."AI keeps making the same mistakes because it doesn't learn from my preferences" — without feedback, every generation starts from the same baseline.Creates a reinforcement signal loop. Over time, enables personalized model fine-tuning. Immediately: gives users a sense of agency ("I'm training this to work better for me").C-44
Regenerate buttonPer-response action that discards the current generation and produces a new variation from the same prompt + context."I don't like this output but my prompt was fine" — AI outputs have inherent variance; the first generation may not be the best possible result.Reduces prompt-rewriting burden. Gives users a low-effort "try again" path. Captures the creative-slot-machine engagement pattern (users enjoy seeing variations).C-44
Artifact card with status pill (Ready / Generating)A card in the chat thread that shows the current state of the AI artifact: "Generating..." (with spinner), "Ready" (with preview thumbnail), or the strategy brief inline."Did the AI succeed or fail? I can't tell" — unclear status during and after generation creates anxiety and premature interaction.Provides clear generation state (N1 Visibility of status). Reduces premature clicks on incomplete outputs. Gap: no "Failed" state — if generation errors, user sees no feedback.C-41

7.5Channel & Audience

Multi-channel navigation and audience/campaign configuration — the "who, when, what metric" layer.

FeatureWhat it doesCustomer pain pointBenefitRef
8-channel tab barA horizontal pill-tab bar at the top of /create showing: Email, SMS, WhatsApp, Automation, Form, Survey, Social post, Campaign. Clicking switches the creation surface."I have to navigate to different products/pages for each channel" — fragmented channel entry points mean users create siloed campaigns with no cross-channel awareness.Establishes a unified creation mental model: "I create all my marketing from one place." Signals omni-channel capability even before all channels ship. Risk: 6 of 8 tabs are stubs.C-13
Strategy panel: Recipients selectorA dropdown/multi-select field in the strategy brief where users choose audience segments for the campaign (e.g., "All subscribers," "VIP customers," "Cart abandoners")."I have to leave the editor to figure out who to send to" — audience selection is currently a separate pre-send step that breaks the creation flow.Brings audience selection into the creative context. Enables AI to tailor content to the selected segment (personalization). CRITICAL: no confirm at send creates TCPA-class risk.C-48
Strategy panel: Promo fieldA text input for specifying the promotion or offer being featured in the email (e.g., "20% off summer collection," "Free shipping over $50")."I keep forgetting to include the promo code or getting the discount % wrong" — promo details live in spreadsheets and Slack, not in the email tool.Creates a structured data field that AI uses to generate accurate promo content. Reduces human error in offer details. Enables future promo-catalog validation at send (E2 mitigation).C-49
Strategy panel: Goal selectorA selector for campaign objective (e.g., "Drive sales," "Build awareness," "Re-engage churned," "Announce product"). AI uses goal to structure email hierarchy and CTA placement."Every email I create has the same structure regardless of whether I'm selling or informing" — one-size-fits-all templates don't reflect campaign intent.Goal-driven generation produces structurally appropriate emails (sales emails get prominent CTAs; awareness emails get narrative flow). Reduces "wrong layout for wrong purpose" rework.C-50
Strategy panel: Send dateA date picker for scheduled send time. Feeds the strategy brief context (urgency, seasonal relevance)."I set up the email but forget to schedule it" — send scheduling is currently buried in a separate send-configuration flow.Brings temporal context into the creative phase. AI can generate urgency language for imminent sends. Reduces missed-schedule rate for time-sensitive campaigns.C-51
Strategy panel: Featured productsA multi-select product picker that connects to the user's product catalog. Selected products are featured in the generated email with images, prices, and links."I manually copy product images and prices into every email and they're often out of date" — manual product insertion is the #1 source of stale/incorrect commerce content.Connects email creation to live product data. Eliminates price/image staleness. Enables future "product in stock" verification at send (E2 mitigation). Foundation for Universal Content (P2.1).C-52
Strategy panel: Focus metricA selector for the primary KPI to optimize for (e.g., "Open rate," "Click rate," "Conversion," "Revenue per recipient"). AI uses this to prioritize content structure."I don't have a clear way to tell the AI what success looks like for this specific campaign" — without explicit goal metrics, AI optimizes for generic engagement.Metric-aware generation (e.g., optimizing for clicks produces more prominent CTAs; optimizing for opens produces better subject lines). Creates a measurable feedback loop between intent and outcome.C-53

7.6Send & QA

The terminal actions — where the prototype transitions from "creating" to "shipping." Flow E concentrates 5 of 9 critical findings.

FeatureWhat it doesCustomer pain pointBenefitRef
Send email (primary action)The primary green button in the editor toolbar. Currently sends immediately to the selected audience segment without a confirmation step."I need to get this campaign out the door" — the terminal action of every email workflow. The moment where all creative work converts to business value.Clear, prominent primary action reduces "where's the send button?" confusion. CRITICAL: no audience-confirmation modal — 2,150 subs, one click to TCPA incident path (E1/A10).C-67
Send test emailA secondary button that sends the current email to a specified test address for review before real send."I can't preview how this actually renders in a real inbox before sending to my entire list" — web previews don't catch rendering bugs that appear in Gmail/Outlook/Apple Mail.De-risks the send decision by enabling real-device review. Catches rendering, personalization, and link errors before they reach the audience. CRITICAL: no recipient modal — could go to wrong address (E4).C-68
Save draft (split button option)A dropdown option under the primary Send button that saves the current email state without sending. Email appears in the Recents carousel."I'm not ready to send but I don't want to lose my work" — not every creation session ends in a send. Users need a low-commitment save path.Reduces "all or nothing" pressure at the send moment. Increases the number of emails that eventually get sent (draft → send conversion over time). Supports the "Thursday Iterator" workflow shape.C-67
Export HTML (split button option)A dropdown option that exports the current email as raw HTML for use in other platforms or custom sending infrastructure."I need the HTML to send through our own ESP / use in Salesforce / paste into our CMS" — enterprise and agency users operate multi-platform environments.Positions Mailchimp's AI as a creation tool even for users who send elsewhere. Reduces "walled garden" objection. Addresses a subset of the agency Workflow Shape #4.C-67
Accessibility checker (via chip)A suggested follow-up chip ("Check for accessibility") that triggers an AI-powered accessibility scan of the current email, reporting color contrast, alt text, heading hierarchy, and link text issues."I don't know if my email is accessible and I don't have time to learn WCAG" — 97% of marketing emails fail at least one accessibility criterion (WebAIM data).Democratizes accessibility without requiring expertise. Reduces legal/compliance risk. Positions Mailchimp as the responsible-by-default platform. Differentiator vs. competitors that offer no accessibility tooling.C-70
Pre-send surface (implicit)The strategy brief panel serves as a de facto pre-send summary: audience, goal, promo, date, and products are all visible in the right panel during send."I'm about to send but I can't remember who this is going to or what the promo was" — send-time anxiety is a real blocker for cautious senders.Provides at-a-glance send context without a separate confirmation screen. Reduces accidental wrong-audience sends (though not formally gated — hence the E1 critical finding).C-45

7.7Settings & Configuration

Administrative and prototype-specific controls that configure the system's behavior.

FeatureWhat it doesCustomer pain pointBenefitRef
Prototype settings popoverA popover accessed from the sidebar footer containing prototype-specific toggles: AI model selection, generation speed simulation, feature flags for experimental capabilities.(Prototype-only) Internal team needs to demo different AI behaviors and feature states without code changes.Enables rapid internal demo configuration. Supports stakeholder presentations with different feature combinations. Would map to admin/feature-flag controls in production.C-11
Sidebar (conversation list)A left sidebar showing all past conversations/sessions. Each entry shows the conversation title (derived from first prompt) and a timestamp. Supports "New conversation" creation."I can't find the email I was working on last week" — session-based AI tools lose context between sessions. Users need persistent conversation access.Enables multi-session workflows. Provides a history mechanism for the "Thursday Iterator" and "Daily Mailer" workflow shapes. Foundation for future team-shared conversation visibility.C-09
Sidebar collapse / expandA toggle that collapses the sidebar from 240px to 60px (icon-only mode), giving the editor canvas maximum width."The sidebar takes up too much space when I'm focused on editing" — screen real estate is precious, especially on laptops (75% of Mailchimp sessions are 13–15" displays).Respects user focus state. Maximizes canvas working area during editing (where every pixel of email preview matters). Follows progressive disclosure best practice.C-09, C-10
Brand & business context link (sidebar footer)A persistent link in the sidebar footer that opens the Brand Kit modal. Visible in both expanded and collapsed states."I need to update my brand settings but I can't find where they live" — Brand Kit access shouldn't require navigating away from the current creation context.Ensures Brand Kit is always one click away regardless of current state. Reduces "where is that setting?" navigation failure.C-09
+ New conversation buttonA button in the sidebar that creates a fresh conversation, clearing the current chat thread and resetting the editor state to the initial /create surface."I'm done with this email but the AI still has the old context loaded" — users need a clean-slate mechanism between campaigns.Provides explicit session boundaries. Prevents context bleed between campaigns. Gives users confidence that "this new email won't inherit weird stuff from the last one."C-09

7.8Micro-Experiences

Small interaction patterns, transitions, and states that shape the moment-to-moment feel of the product. Often invisible when done well; catastrophic when absent.

FeatureWhat it doesCustomer pain pointBenefitRef
Loading / generating state (spinner + progress text)During AI generation (~15–30s), the chat shows an animated spinner with contextual progress text ("Analyzing your brand..." → "Drafting subject line..." → "Rendering email..."). Canvas shows a skeleton/shimmer state."Is it working or is it frozen?" — AI generation latency (>5s) without progress indication causes 23% of users to refresh or abandon (industry benchmark).Reduces premature abandonment during generation. Progress text teaches users what the AI is doing (builds trust). Spinner + text is measurably better than spinner alone for perceived wait time reduction.C-41
Typing indicator animationThree-dot animated indicator in the chat thread while AI is composing its response text (before the full message appears)."Is the AI still thinking or did it crash?" — absence of typing indicators in chat interfaces creates "dead air" anxiety.Maintains conversational cadence expectations. Users know the system is actively working (not hung). Matches mental model from iMessage/Slack typing indicators.C-39
Onboarding overlay (first-run)A full-screen overlay on first visit to /create that introduces the AI email generator concept, prompts URL import for brand extraction, and offers quick-start options."I landed on this page and I don't know what to do first" — new AI surfaces have no learned interaction patterns. Users need orientation before they can act.Reduces time-to-first-action for new users. Captures brand context at the moment of maximum motivation (first visit). Provides a graceful "skip" path for returning users.C-96
URL importer (brand extraction)An input field in the onboarding overlay where users paste their website URL. System crawls the URL and auto-populates Brand Kit fields (colors, fonts, logo, business name)."Setting up brand settings manually takes forever and I get things wrong" — brand setup is the highest-friction first-run task with the lowest perceived immediate value.Converts a 10-minute manual task into a 30-second paste-and-confirm. Dramatically increases % of accounts with populated Brand Kit (which directly improves AI output quality).C-96
Autosave (implicit)The system periodically saves the current email draft state without explicit user action. No visible save indicator (gap: N1 visibility of status)."I spent 30 minutes editing and lost everything when my browser crashed" — data loss is the most emotionally damaging product failure.Eliminates accidental data loss. Removes the cognitive burden of manual saving. Risk: no visible save indicator means users don't trust that saving is happening.
Mode switching animation (AI ↔ Manual)When toggling between AI mode and Manual mode, the canvas transitions with a crossfade animation. The toolbar morphs between AI-specific controls (chips, regenerate) and manual-specific controls (blocks panel, drag handles)."Switching modes feels jarring and I'm not sure what changed" — abrupt state changes without transition create disorientation and fear of data loss.Smooth transitions signal "your content is preserved" without explicit messaging. Reduces the perceived risk of switching modes (which increases mode-switching willingness).C-57
Split button pattern (Send ▾)The primary Send button includes a dropdown chevron revealing secondary actions (Save draft, Export HTML). The most common action is the primary click target; less common actions are one click deeper."Too many buttons of equal weight" — presenting Send, Save, and Export as three equal buttons creates decision paralysis at the most critical moment.Establishes clear action hierarchy. Reduces accidental "wrong button" clicks at the send moment. Follows platform convention (Google Docs Save ▾, Figma Export ▾).C-67
Empty states (conversations, recents)When the sidebar conversation list or recent emails carousel has no content, a friendly empty state appears: illustration + explanatory text + primary action button ("Start your first email")."This page looks broken because there's nothing here" — blank UI without explanation creates confusion about whether the feature is working.Transforms a potentially confusing void into an onboarding moment. Each empty state is a call-to-action. Reduces "is this a bug?" support tickets.C-09, C-27
Skeleton / shimmer loading (canvas)While the email canvas is loading or regenerating, placeholder blocks with shimmer animations indicate the expected layout structure."The editor flashes blank every time the AI updates something" — content layout shift (CLS) during regeneration breaks spatial memory and trust.Maintains spatial stability during loading. Users keep their eye position and context. Signals "content is coming here" rather than "content disappeared."C-55
Chat scroll-to-bottom (auto-follow)As new messages appear in the chat thread, the view automatically scrolls to show the latest message. If the user has scrolled up (reading history), auto-follow pauses until they return to the bottom."I missed the AI's response because it appeared below the fold" — in long threads, new content can be invisible without active scrolling.Ensures users never miss AI responses. The "pause on scroll-up" behavior respects users who are reviewing history (doesn't hijack their position).C-39
Theme preview-on-hoverIn the theme popover, hovering over a theme preset shows a live preview in the canvas without committing. Clicking applies permanently."I'm afraid to try themes because I might lose my current design" — irreversible actions suppress exploration.Enables risk-free exploration. Increases the number of themes users consider. Reduces "I'll just stick with the default" behavior. Follows Figma's hover-to-preview pattern.C-72
Chip hover states + micro-animationsQuick-prompt chips and follow-up suggestion chips have distinct hover states (background fill, subtle scale transform) and a press animation providing tactile feedback."I'm not sure which things are clickable" — flat UI without affordance signals creates uncertainty about interactive elements.Clear affordance signals reduce "is this a button or a label?" confusion. Micro-animations provide satisfying interaction feedback. Small detail that compounds into "this feels polished."C-25, C-70
Sidebar tooltip labels (collapsed state)When the sidebar is collapsed to 60px icon mode, hovering over any icon shows a tooltip with the full label text."I collapsed the sidebar but now I don't know what the icons mean" — icon-only interfaces are inscrutable without labels.Maintains discoverability in collapsed state. Users can collapse for space efficiency without losing navigation capability.C-10

Source: All features cataloged from direct prototype interaction at ai-email-generator-steel.vercel.app (May 2026). Decomposition at github.intuit.com/dprabhakara/ai-email-generator-decomp (29 screenshots + 11 docs). Pain points cross-referenced against HVC Risk Map ($95K/mo cited themes), User Research (5 Bets + 5 Workflow Shapes), and Revised Goals ($21M ARR target). Component IDs (C-XX) reference Lens 3 matrix at freddie-design-assessment/lenses/03-component-jtbd-matrix.md.

Tab 18 · Page 7 of 8 · Priority Buckets

P0 / P1 / P2 — Improvement Roadmap

All 45 heuristic findings, 9 S4 criticals, and 10 RICE-scored recommendations classified into three priority buckets by customer impact and business-critical risk. P0 = launch-blocking / must-fix before any exposure; P1 = ship within first iteration / high customer pain; P2 = fast-follow / quality-of-life. Each item maps to the original finding ID, affected flow, and estimated dollar exposure.
Prioritization framework: customer severity × HVC dollar exposure × competitive parity gap

07P0 — Launch-blocking MUST FIX BEFORE ANY EXPOSURE

These items carry S4 critical severity, involve TCPA / legal / data-integrity risk, or gate the $281M HVC NEA-stayer segment. Shipping without these mitigations creates existential product risk.

#ImprovementSevFlow$ ExposureAudit Ref
P0-1 Mandatory audience-confirmation modal at Send. Currently 2,150 subs are one click from broadcast. Add a confirm dialog showing recipient count, segment name, and a "Send to [N] recipients" button requiring deliberate action. S4 Flow E (Send) $57K TCPA class A10, E1, C-67
P0-2 Feature-flag SMS tab OFF until TCPA guardrails ship. AI can trivially generate non-compliant SMS today. The tab must be disabled with a tooltip: "Coming soon — pending compliance guardrails" until Initiative Canvas I-5.2.3 ships. S4 Flow E (Send/SMS) $57K/mo HVC #16 E7, C-13
P0-3 AI-content verification pre-send checklist. Before Send, validate: footer address resolves to real entity, promo codes match catalog, featured products are in stock, no hallucinated legal/compliance text. Show a pre-send checklist the user must acknowledge. S4 Flow E (Send) Brand trust + legal E2, C-67
P0-4 Surface manual mode as a primary entry point. Add a "Skip AI — open blank editor" button visible on the Create screen alongside the AI composer. Remember the user's preference. The $281M HVC NEA-stayer segment must not be forced through AI. S4 Flow B (Power user) $281M NEA stayers B1, B2, B4, C-57
P0-5 Send-test-email recipient picker modal. "Send a test email" must open a modal with the user's own email pre-filled and a field to add others — not fire to an unknown default address. S4 Flow E (Send) Wrong-address risk E4, C-68
P0-6 Theme preset must respect Brand Kit (apply-and-confirm). When a user clicks a theme preset, show a confirmation dialog: "Keep your brand colors or override with preset?" Prevents the silent Brand Kit overwrite (Wes Turner pattern). S4 Flow D (Refinement) Brand integrity D4, C-72–C-78
P0 gate rule: None of these items can be deferred. Each represents either a legal/compliance incident path (P0-1, P0-2, P0-3, P0-5), a segment-level churn trigger for the largest revenue concentration (P0-4), or a silent data-corruption pattern (P0-6). Ship as feature-flagged front door for trial + free only, with all 6 P0 mitigations in place.

08P1 — First iteration SHIP WITHIN 1ST CYCLE

High customer pain (S3 severity), competitive parity gaps, or infrastructure investments that enable the FY27 strategy. Not launch-blocking, but must ship within the first design iteration to retain credibility with HVC customers and close competitive gaps against Canva and Klaviyo.

#ImprovementSevAreaImpactAudit Ref
P1-1 Font-upload UI in Brand Kit + AI font-recognition parity. Add a "+ Upload custom font" button alongside the 23-font dropdown. AI should recognize uploaded fonts and apply them in generation. Currently HVC #10 ($3,350/mo) is unfixable. S3→S4 Brand Kit $3,350/mo HVC #10 C5, C-87
P1-2 Reframe brand-context banner from upgrade pressure to value framing. On Free tier, replace the "Upgrade to unlock full brand features" tone with: "Your brand colors are applied — upgrade to add custom fonts and logo variants." Reduce CSAT regression risk (F4). S3 Create surface F4 CSAT (~870K Free) A3, C-23
P1-3 Templates carousel: surface-origin filter. Add filter pills: NEB / Classic / All. Classic anchor users (HVC #6) must see familiar templates, not just new NEB-native ones. Reduces "I can't find my templates" churn trigger. S3 Create surface Classic anchor churn C-27, C-28
P1-4 Ship Universal Content primitive concurrently. The P7 JTBD phase (Learn & reuse) is the weakest phase at 7% component coverage. Universal Content (Pillar 2.1) is the 2026 most-asked feature. Without it, every email starts from zero. S3 Infrastructure Pillar 2.1 strategic Strategy Lens 5
P1-5 Version history in chat thread. Each AI generation should create a restorable checkpoint. Users need per-generation rollback (not just full-conversation regenerate). Restores the Jack Hally / all-week ad-libber persona. Closes the Canva undo-stack gap. S3 Chat thread Power-user retention D1, C-44
P1-6 Error / Failed state for AI generation. Add a "Failed" pill sibling to the "Ready" pill on artifact cards. Show: what went wrong, a "Retry" button, and diagnostic text. Currently a generation failure produces silence. S3 Chat thread Activation abandonment C-41, N1, N9
P1-7 Cancel / abort button during AI generation. If generation hangs (>30s), user has no escape. Add a "Cancel" button that aborts the current generation and returns to the prompt state. For the $3.6M F2 lever, a hung first session = permanent abandonment. S3 Generation flow $3.6M F2 activation N3, C-41
P1-8 HTML code mode escape hatch (manual mode). Power users and agencies need raw HTML access. Ship NEB Code Mode (Pillar 2.2.3, Q3 target). Without it, the premium/agency ceiling is hit immediately. S3→S4 Manual mode Premium/agency ceiling B5, C-57
P1-9 State contract: visible autosave indicator + draft persistence guarantee. Show "Saved" / "Saving..." status in the editor toolbar. Publish the contract: "Your draft is saved every 10 seconds. Manual edits are preserved when switching to AI unless you explicitly regenerate the section." S3 Editor Data-loss trust N1, Lens 2 §2.5
P1-10 Deep-linkable editor + strategy panel. The email editor and strategy brief are right-pane states, not routes. Users can't share "the editor on this email" or bookmark progress. Convert to route-based or query-param-based navigation. S3 IA / architecture Collaboration + handoff Lens 1 §2.3

09P2 — Fast-follow QUALITY OF LIFE & POLISH

S2/S1 findings, accessibility improvements, and UX polish items. Not blocking launch or first iteration, but each compounds into overall product quality and competitive differentiation. Ship in subsequent iterations.

#ImprovementSevAreaAudit Ref
P2-1 WCAG 2.2 AA full audit + remediation. Icon-only buttons need aria-label. Touch targets (24×24) should be 44×44 per SC 2.5.8. Mode switcher needs role="radiogroup". Send buttons should include recipient count in accessible name. Theme popover needs dialog role + focus trap. S2 Accessibility Lens 4 §4.4
P2-2 AI confidence indicator per generation. Show a subtle confidence score or "certainty" signal with each AI output: "High confidence — matches your brand kit and past campaigns" vs "Lower confidence — first time generating for this template type." Closes AI2 calibrated trust gap. S2 Chat thread AI2
P2-3 Preview-before-apply for AI edits. When the user gives a conversational edit instruction ("make the header bolder"), show a diff/preview before applying. Adds an undo layer and reduces "AI changed something I didn't want" anxiety. S2 Chat + Editor AI5
P2-4 Two-shell navigation: add breadcrumb back to product areas. Currently, the Create shell disposes of all global nav. Add a persistent breadcrumb or mini-nav that lets users reach Analytics, Audience, Campaigns without the trap-door × exit pattern. S2 IA / Navigation C-07, C-12
P2-5 Sidebar conversation search + rename. The conversation list has no search or rename capability. As users accumulate conversations, findability degrades. Add search input + inline rename on double-click. S2 Sidebar C-09
P2-6 Multi-brand support in Brand Kit. Currently single-brand only. Agency users managing multiple clients need brand-switching. Add a brand selector at the top of Brand Kit modal. S2 Brand Kit C-85, HVC #9
P2-7 Change summary per AI generation. After each AI edit, show a brief "what changed" diff badge: "Updated: header font, CTA color, added product row." Reduces "AI changed things and I can't tell what" anxiety. S2 Chat thread AI2, N1
P2-8 Stub tab affordance clarity. 6 of 8 channel tabs are stubs. Add a clear "Coming soon" badge or disabled state so users don't click expecting functionality that isn't built. S1 Tab bar C-13
P2-9 Per-edit undo (not just full regenerate). The Copy/Like/Dislike/Regenerate row only offers binary regenerate. Add per-edit undo that preserves manual tweaks applied after AI output. S2 Chat + Editor C-44, AI5
P2-10 Rendering parity: true inbox preview. The viewport radio (desktop/mobile/split) shows responsive CSS layout but doesn't replicate actual Gmail/Outlook/Apple Mail rendering. Add Litmus/Email on Acid-style inbox preview integration. S2 Editor (Preview) C-58, HVC #3
Priority roll-up: P0 = 6 items (all S4, all require code/design changes before any user exposure). P1 = 10 items (S3 severity, competitive gaps, infrastructure investments; ship within 1st design iteration). P2 = 10 items (S2/S1, quality-of-life polish; ship in fast-follow iterations). Total: 26 prioritized improvements derived from the 45 heuristic findings + 9 criticals + top-10 RICE recommendations.
Tab 18 · Page 8 of 8 · Agent Mode Prototype Walkthrough

How Deepak's Agent Mode Prototype Addresses the Audit

Mapping of every P0, P1, and P2 improvement to specific surfaces in the Agent Mode v2 prototype. For each improvement: the prototype surface that addresses it, how the agent-mode architecture resolves the finding, and what remains to build. Items already present in the prototype are marked IN PROTOTYPE; items the prototype enables but doesn't yet ship are marked ENABLED; items requiring net-new work are marked BUILD.
Prototype: Agent Mode v2

10P0 items — Agent Mode resolution

How the agent-mode architecture resolves each launch-blocking issue.

ItemStatusPrototype SurfaceHow Agent Mode Resolves It
P0-1 IN PROTOTYPE AI Governance surface → Content Review section + AI Rail (pre-send agent step) The v2 prototype introduces an AI Governance panel with explicit "Content review" controls (human-in-loop review required, pre-publish legal check, brand-compliance check). The AI Rail can inject a pre-send agent step: "Before I send this to 2,150 recipients, let me confirm: audience = VIP Customers, promo = 20% off, footer verified. Proceed?" This transforms the one-click hazard into an agent-mediated confirmation with structured fields. The agent's reasoning narrative makes the recipient count and segment name visible in natural language before the terminal action.
P0-2 IN PROTOTYPE AI Governance surface → Content Review “Pre-publish legal compliance check” + Tab/surface gating The governance panel's "Pre-publish legal compliance check" control directly addresses TCPA gating. In the agent-mode architecture, SMS generation would route through the governance layer. The v2 prototype's surface architecture already separates channel tabs as distinct navigation items (SMS is a standalone sidebar item, not a sub-tab), meaning feature-flagging SMS OFF is architecturally trivial — the nav item simply doesn't render until the compliance connector is green.
P0-3 IN PROTOTYPE AI Rail (agent reasoning) + Connectors surface (live catalog bindings) + AI Governance The v2 Connectors surface binds Shopify (product catalog), Stripe (promo codes), and CRM data as live context. When the agent generates an email referencing products, it pulls from the connected catalog — not hallucinated data. The AI Rail's reasoning narrative surfaces verification: "I used your Shopify products (Monstera Deliciosa, $45, 12 in stock) and the promo code FATHERSDAY20 from your active promos." Pre-send, the governance layer's "human-in-loop review" step validates these bindings. The conversational bundle generation ("Four artifacts ready for your review") includes an explicit review step before send.
P0-4 IN PROTOTYPE + Create button (sidebar) + AI Skills & Tools surface (manual tools visible) The v2 prototype places "+ Create" as the top sidebar action — a universal entry point that doesn't assume AI-first. The AI Skills & Tools surface enumerates both "Creative AI" (Magic Design, Magic Write) and manual tools side-by-side, signaling manual creation is first-class. The Daily Brief surface shows suggestions but never forces AI interaction. The architecture supports a "Start blank" path through the Create button without routing through the AI Rail. Power users navigate directly to their channel (Campaigns, SMS, etc.) from the persistent product nav — the global nav is never disposed of (unlike the Freddie two-shell trap-door).
P0-5 ENABLED AI Rail (agent-mediated send) + Connectors (email identity) The AI Rail's conversational send flow naturally asks "Who should I send the test to?" with the user's connected email pre-filled from the Connectors surface. The architecture enables this — the agent treats "send test" as a tool call requiring a recipient parameter — but the v2 prototype doesn't yet show an explicit test-email modal UI. The implementation is a single agent tool-use step: send_test(to: "maya@leafandloom.com") with a confirmation message in the rail.
P0-6 ENABLED Brand Intelligence surface + AI Governance (brand-compliance check) The v2 Brand Intelligence surface includes "Active brand rules" with explicit enforcement ("Always use brand green #4A7C59 for CTAs", "Headings in Recoleta Bold"). When a theme preset is applied, the governance layer's "brand-compliance check" validates against these rules. If a preset overrides Brand Kit colors, the agent surfaces the conflict: "This theme changes your CTA color from #4A7C59 to #FF6B35. Keep your brand color or apply the preset?" The "100% of active artifacts pass brand check" indicator in Brand Intelligence makes compliance visible at a glance.

11P1 items — Agent Mode resolution

ItemStatusPrototype SurfaceHow Agent Mode Resolves It
P1-1 ENABLED Brand Intelligence surface (brand rules + typography config) Brand Intelligence centralizes brand rules including typography. The "Active brand rules" list already shows font-specific rules ("Headings in Recoleta Bold"). The architecture supports font-upload by adding a rule: "Upload custom font → becomes a brand rule → AI generation respects it." The Connectors surface could link to a font-hosting CDN. Net-new work: the actual upload UI + font-file processing pipeline.
P1-2 IN PROTOTYPE Daily Brief surface (value-first AI communication) The v2 Daily Brief opens with "Good morning, Maya" + actionable insights + momentum metrics. Brand context is surfaced as value ("Your brand colors are applied — your VIP segment has gone quiet") not as upgrade pressure. The brand-context banner is replaced by the Brand Intelligence surface which is a full navigation destination, not a dismissible nag. Free-tier users see brand rules as value they're getting, with upgrade upsell only in the governance layer's advanced controls.
P1-3 BUILD Artifacts surface (template/artifact library) The v2 Artifacts surface shows a filterable library of past artifacts with status pills and type categorization. The architecture supports adding origin-type metadata (NEB/Classic/All) as a filter dimension on the Artifacts list. Net-new work: Classic template migration + origin tagging + filter UI in the Artifacts surface.
P1-4 IN PROTOTYPE Memory Library surface + Brand Intelligence The v2 Memory Library is the Universal Content primitive. It stores "Voice & copy patterns" (CTA styles, subject line formulas), "Audience & segmentation" (segment definitions), and "Visual style" (layout preferences, color usage). Every AI generation draws from Memory Library as persistent context. This is architecturally equivalent to Universal Content — reusable, cross-campaign content primitives that make P7 (Learn & reuse) a first-class JTBD phase.
P1-5 ENABLED AI Rail (conversation thread with artifact versioning) The AI Rail's conversation thread naturally creates per-message checkpoints. The "Four artifacts ready for your review" pattern in the bundle generation flow shows versioned artifacts. The architecture supports a "Versions" drawer per artifact showing each generation as a restorable snapshot. Net-new work: the rollback UI and version-diff visualization in the rail or in the artifact focus view.
P1-6 ENABLED AI Rail (agent error handling) The AI Rail's conversational model naturally handles errors as messages: "I wasn't able to generate the email — your Brand Kit has an invalid hex color in the accent field. Fix it in Brand Intelligence and I'll try again." The agent's reasoning narrative transforms silent failures into diagnostic conversations. Net-new work: specific error-state UI components (retry button, error-type categorization).
P1-7 ENABLED AI Rail (tool-use cancellation) The v2 Rail shows tool pills ("Retrieving marketing data", "Cross-referencing benchmarks") during agent execution. The architecture supports a cancel/stop button on in-progress tool executions. The agent can gracefully abort: "Stopped. Your previous version is still intact. Want to try a different approach?" Net-new work: the "Stop" button affordance + graceful abort handler.
P1-8 IN PROTOTYPE AI Skills & Tools surface (HTML/code tool card) The AI Skills & Tools surface lists "Code & export" tools alongside creative AI tools. The architecture supports an "HTML editor" skill that opens a code-mode canvas view. The agent can invoke this as a tool: "Opening the HTML editor for this email — you can edit raw HTML directly." The skill-card model means code-mode is discoverable alongside other tools, not hidden behind a toggle.
P1-9 IN PROTOTYPE AI Rail (state transparency in reasoning) + Artifacts surface (status pills) The AI Rail's reasoning makes state explicit in natural language: "I've saved your email draft. Your manual edits to the header are preserved." The Artifacts surface shows status pills (Draft, Sent, etc.) making persistence visible. The agent-mode architecture treats state as a first-class topic the AI can discuss and explain, replacing the need for a mechanical "Saved/Saving..." indicator with a richer trust signal.
P1-10 IN PROTOTYPE Hash-based routing across all surfaces The v2 prototype uses hash-based routing (#brief, #memory, #brand, #governance, etc.) making every surface deep-linkable and bookmarkable. The inner-nav items update the URL hash on click. The Focus view (artifact detail) is a separate route. This resolves the Freddie prototype's un-deep-linkable editor/strategy panel issue.

12P2 items — Agent Mode resolution

ItemStatusPrototype SurfaceHow Agent Mode Resolves It
P2-1 BUILD All interactive surfaces WCAG remediation applies globally. The v2 prototype's component architecture (sidebar nav items, rail buttons, skill cards) provides consistent patterns where a11y fixes can be applied systematically. The agent-mode architecture doesn't inherently solve this — it requires an a11y engineering pass across all interactive components. The "AI Governance" surface could add an "Accessibility compliance" toggle.
P2-2 ENABLED AI Rail (reasoning narrative) The AI Rail's reasoning already carries confidence signals in prose: "I'm confident about the layout because it matches your previous successful campaigns" vs. "I'm taking a new direction on the color palette — let me know if it fits." The architecture supports adding a structured confidence badge alongside the prose. Net-new work: the confidence scoring model + badge UI.
P2-3 ENABLED Focus view (artifact detail with before/after) The Focus view already shows a rich artifact detail pane with toolbar actions (AI Edit, Preview, Send test). The architecture supports a "before/after" toggle showing the previous version alongside the current one. The AI Rail's message-based model naturally creates diff points. Net-new work: the visual diff rendering engine in the Focus view.
P2-4 IN PROTOTYPE Persistent sidebar nav (product areas always visible) The v2 prototype's most fundamental architectural decision: the sidebar navigation with all product areas (Home, Campaigns, Automations, SMS, Forms, Audience, Analytics, Content, Integrations) is persistent on every surface. There is no two-shell switching. The "Mailchimp AI" hub is a nav item among peers, not a separate world. Users never lose their path back to any product area. This directly resolves the Freddie trap-door pattern.
P2-5 BUILD AI Rail (conversation history) The AI Rail persists conversation context but the v2 prototype doesn't show a searchable conversation list. The architecture supports a "History" drawer in the rail with search and rename. Net-new work: conversation persistence layer + search index + rename UI.
P2-6 ENABLED Brand Intelligence surface (multi-brand architecture) Brand Intelligence already stores structured brand rules (palette, voice, compliance). The architecture supports a brand-switcher dropdown at the top: "Leaf & Loom" / "Client B" / "Client C". Each brand is a distinct rule-set. The Connectors surface handles per-brand integrations. Net-new work: the multi-brand selector UI + brand-scoped rule storage.
P2-7 IN PROTOTYPE AI Rail (reasoning narrative with change enumeration) The AI Rail's reasoning narrative naturally enumerates changes: "I updated the email with your Father's Day theme. Changes: swapped hero image to plant-dad illustration, adjusted CTA copy to 'Gift a green companion', warmed the palette to earth tones." The agent's communication model is inherently change-summary-oriented because it explains its actions in conversational prose. This replaces the need for a mechanical diff badge.
P2-8 IN PROTOTYPE Sidebar nav (fully-built product areas) The v2 prototype's sidebar shows all product areas as fully-built navigation items, each with their own surface content (Campaigns shows campaigns, Analytics shows magic insights, etc.). There are no stub tabs. Every nav item routes to a real surface. The channel-creation flow is unified in the "Create" entry point and the conversational bundle generation, not distributed across 8 tabs with 6 stubs.
P2-9 ENABLED Focus view + AI Rail (per-edit undo) The Focus view's toolbar (AI Edit, Preview, Export) supports adding an "Undo last AI edit" action that preserves manual tweaks. The AI Rail's per-message structure creates natural undo boundaries. Net-new work: the undo-stack implementation that distinguishes AI edits from manual edits and supports selective rollback.
P2-10 ENABLED Connectors surface (Litmus / Email on Acid integration) The v2 Connectors surface already shows 5 connected integrations + 8 available, with a marketplace model for adding more. A Litmus or Email on Acid connector would surface real inbox rendering previews directly in the Focus view's "Preview" action. Net-new work: the connector implementation + iframe/API integration for inbox previews.
Walkthrough summary: Of the 26 prioritized improvements, the Agent Mode v2 prototype directly addresses 11 items IN PROTOTYPE, architecturally enables 11 more ENABLED (requiring incremental build on the existing surface), and requires 4 items of NET-NEW BUILD (a11y engineering, template origin tagging, conversation search, and the rendering-preview connector). The agent-mode architecture's key structural advantages over the Freddie prototype are: (1) persistent product nav (eliminates the trap-door pattern), (2) AI Governance surface (systemically resolves send-safety and compliance issues), (3) Brand Intelligence (replaces the fragile Brand Kit modal with an enforceable rules engine), (4) Memory Library (implements Universal Content as a first-class primitive), and (5) the AI Rail's conversational reasoning (transforms mechanical confirmations and error states into natural agent-mediated interactions).

Source: Agent Mode v2 prototype at github.intuit.com/pages/dprabhakara/mailchimp-agent-shell-anatomy/v2/. Priority classifications derived from Tab 18 Lens 4 heuristic findings (45 total, 9 S4 critical), Lens 5 RICE top-10, HVC Risk Map dollar exposures, and User Research workflow shapes. Prototype surface mapping based on direct interaction with v2 prototype + source at /Users/dprabhakara/ai_workspace/mailchimp-agent-shell-site/v2/index.html.

Tab 19 · Deepak's Agent Mode Prototype — Audit Gap Resolution

Prototype Walkthrough: Closing the Agent Mode Audit Gaps

Feature-by-feature walkthrough of every capability in Deepak's Agent Mode v2 prototype that directly addresses findings from the Agent Mode Design Audit (Tab 18). For each feature: the prototype surface, components & widgets, interactions, what problem it solves, and the customer benefit. These are the baseline architectural decisions that resolve the 45 heuristic findings and 9 S4 criticals.
How to read this section. Each card below is a distinct feature or architectural decision in Deepak's prototype. The AUDIT REF badge shows which P0/P1/P2 item(s) from Tab 18 Page 7 it resolves. Components, widgets, and interactions are described as they appear in the live prototype.

01Shell & Navigation Architecture

F-01 Persistent sidebar navigation P2-4 P0-4
Surface: Global sidebar · All screens
A 232px sidebar persists on every surface in the application. All product areas — Home, Campaigns, Automations, SMS, Forms, Audience, Analytics, Content, Integrations — remain visible and clickable at all times. The "Mailchimp AI" hub is a navigation item among peers, not a separate world.
Components & Widgets
Sidebar container (232px fixed) · 10 nav items with icon + label · Active-state indicator (teal left-border + background tint) · "+ Create" CTA button (teal, top of sidebar) · "Mailchimp AI" nav item with ✦ sparkle mark
Problem Solved
Eliminates the two-shell trap-door pattern. In the Freddie prototype, clicking "Create" disposes of all global nav — the user loses the path back to Analytics, Audience, Campaigns. The only way back is the × exit button. This creates a one-way trap-door that breaks wayfinding and increases abandonment.
Customer Benefit
Users never lose their navigation context. They can jump from AI-assisted creation to their Audience, then to Analytics, then back to their draft — without reorienting. Reduces "where am I?" anxiety and increases cross-surface exploration. Critical for the $281M HVC NEA-stayer segment who navigate frequently between creation and data.
F-02 + Create button as universal entry point P0-4
Surface: Sidebar · Top position
A teal "+ Create" button sits at the top of the sidebar, above all navigation items. Clicking it opens the conversational campaign start surface — but does not force AI interaction. The button is a universal entry point that supports both AI-first and manual-first creation paths.
Components & Widgets
CTA button (teal background, white text, centered) · "+" icon + "Create" label · Hover state (darker teal) · Routes to conversational start (data-surface="conv-start")
Problem Solved
Manual mode as a first-class entry. The Freddie prototype forces users through AI interaction before manual mode is accessible (B1 critical). Here, the Create button doesn't presume AI — power users can navigate directly to Campaigns, SMS, or any channel from the persistent sidebar without touching the AI flow.
Customer Benefit
The $281M HVC NEA-stayer segment gets a zero-friction path to their preferred workflow. New users get AI-first guidance. Neither is forced into the other's flow. The system respects user intent rather than mandating a single creation paradigm.
F-03 Hash-based deep-linkable routing P1-10
Surface: All surfaces · URL architecture
Every surface in the prototype is deep-linkable via URL hash (#brief, #memory, #brand, #governance, #artifacts, etc.). The inner-nav items update the URL hash on click. The Focus view (artifact detail) is a separate route. Browser back/forward buttons work correctly.
Components & Widgets
Hash-based routing JS (history.replaceState) · hashchange event listener · Inner-nav items with data-inner attributes · Sidebar items with data-surface attributes · URL updates on every navigation
Problem Solved
Editor + strategy panel now bookmarkable and shareable. The Freddie prototype's editor and strategy brief are right-pane states (not routes) — users can't share "the editor on this email" or bookmark progress. Browser back/forward breaks.
Customer Benefit
Teams can share links to specific surfaces: "Look at our Brand Intelligence rules" or "Check the campaign sheets." Enables handoff between team members, supports multi-session workflows, and doesn't break the browser's native navigation expectations.

02AI Rail — Agent-Mediated Interactions

F-04 Persistent AI Rail with conversational reasoning P0-1 P0-3 P1-6 P1-7
Surface: AI Rail (380px right panel) · Persistent across all surfaces
A 380px right-side panel containing a full conversational thread between the user and the AI agent. The AI communicates with reasoning narratives, explains what it did and why, shows tool-use pills for every data operation, and surfaces expert team members who join the conversation with specialized knowledge. The rail includes a composer input with "+ context" and "?" help mode buttons.
Components & Widgets
Rail container (380px, collapsible) · Rail header (✦ mark + title + pin + close buttons) · Message thread (scrollable) · Agent messages with expert avatar, name, role · User messages (teal bubble, right-aligned) · Tool-use pills with spinner + done states ("Loading brand profile", "Reviewing campaign history") · Action buttons inline (primary + secondary) · Rail composer (rounded, "+ context" + text input + "?" + send button) · Connector attribution footer ("Powered by Connectors: Shopify · Slack · Gmail")
Problem Solved
Transforms mechanical confirmations into natural agent conversations. The Freddie prototype's one-click Send (P0-1) becomes an agent-mediated step: "Before I send this to 2,150 recipients, let me confirm…" AI content verification (P0-3) becomes the agent's reasoning: "I used your Shopify products and promo code FATHERSDAY20." Error states (P1-6) become diagnostic conversations. Generation hangs (P1-7) become cancellable tool operations.
Customer Benefit
The customer interacts with an intelligent collaborator who explains, confirms, and catches errors conversationally — not with mechanical dialogs and silent failures. Trust is built through transparency: every data source is attributed, every action is explained, every risky operation requires conversational confirmation. This is the architectural backbone that resolves 5 of 6 P0 findings.
F-05 Tool-use transparency pills P1-9 P1-7
Surface: AI Rail + Daily Brief
Every AI operation surfaces as a visible "tool pill" with a spinner animation during execution and a green checkmark when complete. Examples: "Loading brand profile", "Cross-referencing benchmarks", "Drafting cross-channel copy", "Generating imagery (Magic Media)", "Adapting per channel (Magic Resize)". These appear both in the rail's chat thread and in the Daily Brief surface.
Components & Widgets
Tool pill (rounded, 11px text, spinner icon) · Two states: in-progress (gray border, spinning) and done (green border, checkmark) · Connector attribution badge ("+ 3 Canva connectors pulled live context") · Inline within message flow
Problem Solved
Makes AI operations visible and cancellable. Replaces the Freddie prototype's opaque generation (no cancel, no progress, no escape hatch) with transparent, step-by-step tool operations. The user can see exactly what the AI is doing at every moment. If a tool hangs, the architecture supports cancellation at the tool level.
Customer Benefit
Users never wonder "is it working or frozen?" Every AI operation is named, visible, and completable. This directly addresses the $3.6M F2 activation lever — a hung first session with no feedback causes permanent abandonment. Tool pills eliminate that silence.
F-06 Multi-expert agent team in conversation P1-5
Surface: AI Rail
The AI rail features named expert agents (Kimberlee — Email Strategist, Jane — Audience Expert) who join the conversation with specialized knowledge. Each expert has a distinct avatar, role, and expertise. They tag-team: Kimberlee drafts the email while Jane provides audience segmentation insights. The AI references its memory: "Houseplant Collectors prefer education to promo."
Components & Widgets
Expert avatar (18px circle, colored background, initial letter) · Expert name + role label ("Kimberlee · Email Strategist · joined the chat") · Memory-use attribution ("Memory used: Houseplant Collectors prefer education to promo") · Per-expert action buttons
Problem Solved
Creates a team-of-experts model that builds trust. Single-AI-voice systems feel opaque. Specialized experts with named roles and declared reasoning create higher calibrated trust (AI2). The memory attribution creates a version-history-like audit trail of learning that addresses the P1-5 version history gap.
Customer Benefit
The customer feels they have a marketing team, not a chatbot. Each expert brings declared expertise and shows their reasoning. The memory system means the AI gets better over time — "it knows my brand" — which is the #1 differentiator for retention against competitors where every session starts from zero.

03Daily Brief & Intelligence Surfaces

F-07 Daily Brief with proactive intelligence P1-2
Surface: Daily Brief · #brief
The default landing surface shows a personalized daily briefing: "Good morning, Maya." with three key insights (mobile opens up, Thursday sends outperforming, VIP segment going quiet), four momentum KPI cards (open rate, revenue, audience health, sender reputation), suggested next moves with impact badges, and patterns worth watching. The brief is generated with visible tool pills ("Retrieving marketing data", "Cross-referencing benchmarks").
Components & Widgets
Brief intro (✦ logo + personalized greeting) · Tool-use pills (done state) · Insights banner (yellow left-border card with ✨ star, narrative text, insight chips) · Momentum row (4 metric cards: label, value, delta with up/down arrows) · Suggested next moves (2-column cards with impact badge, title, description, action button) · Patterns list (bulleted observations)
Problem Solved
Replaces upgrade-pressure branding with value-first AI communication. The Freddie prototype's brand-context banner pressures Free users to upgrade (P1-2 / F4 CSAT regression). The Daily Brief leads with "here's what I found for you today" — value is delivered before any ask. Brand context is surfaced as insight ("your VIP segment"), not as a gate.
Customer Benefit
Users open Mailchimp and immediately see actionable intelligence: what's working, what needs attention, and what to do next. The AI earns trust by delivering value on the first screen, every session. Reduces "I don't know where to start" paralysis and surfaces opportunities the user would never find manually.

04Focus View — Artifact Editing

F-08 Focus view: three-panel artifact editor P1-10 P2-3 P2-9
Surface: Focus view (full-screen overlay)
A full-screen overlay with three panels: left chat (340px, conversational editing), center canvas (email preview with Magic toolbar floating above), and right edit rail (240px, structured tools). The chat preserves full conversation history including tool-use pills. The canvas shows the rendered email with a floating dark toolbar for Magic tools. The edit rail organizes tools into groups (Magic family, Add content, Comments & review).
Components & Widgets
Focus header (← Back + title + Send test + Send email buttons) · Chat panel (scrollable messages + composer) · Canvas panel (email frame with shadow, responsive rendering) · Email hero (gradient background, headline, subhead) · Email body (personalized with {{first_name}}) · Product row (2-column grid) · Magic toolbar (dark floating bar: Magic Edit, Magic Expand, Magic Grab, Magic Morph, Style match, Remove BG) · Edit rail with grouped items (Magic Layers, Magic Resize, Magic Translate, Magic Media, Dream Lab; Header, Hero, Text block, Image, Button, Product row, Footer; Comments, @Mailchimp AI, Review checklist)
Problem Solved
Deep-linkable, full-featured editing with element-level AI edits. Addresses P1-10 (deep-linkable editor), P2-3 (preview-before-apply via conversational editing where the AI explains what it changed), and P2-9 (per-edit control via element-level operations: "editing hero only"). The three-panel layout keeps chat instructions, canvas preview, and tool access simultaneously visible.
Customer Benefit
Users can say "make the hero more autumnal" and see the AI edit only the hero while preserving everything else. The tool-pill confirms "Layered object intelligence · editing hero only." Manual tools (Add content blocks) and AI tools (Magic family) sit side by side — the user picks their preferred mode per edit, per block, per moment. No forced AI or forced manual.

05AI Skills, Artifacts & Expert Team

F-09 AI Skills & Tools surface P0-4 P1-8
Surface: AI Skills & Tools · #skills
A discoverable catalog of every AI capability organized in three groups: Creative AI (Magic Write, Magic Design, image editing tools), Agentic AI (conversational start, design-aware chat, layered intelligence, web research, MCP, scheduled tasks), and Data & Productivity (Sheets AI, Bulk Create, Fill Empty Cells, Canva Code). Each skill has a toggle switch to enable/disable.
Components & Widgets
Page header (title + Discover button) · Three category sections with h3 labels · Skill cards (card with name + badge + description + toggle switch) · Toggle switches (on/off, teal when on) · CANVA 2.0 badges on new capabilities
Problem Solved
Makes manual tools and code mode discoverable alongside AI. Addresses P0-4 (manual mode visibility) by listing all tools — including non-AI tools — in one scannable catalog. Addresses P1-8 (HTML code mode) by providing the architecture for a "Code & export" skill card. Users see both AI and manual as peer capabilities, not AI-only with manual hidden.
Customer Benefit
Users discover capabilities they didn't know existed ("I didn't know the AI could do web research"). Power users find their manual tools immediately. Enterprise admins can toggle individual AI capabilities on/off for compliance. The toggle architecture means the platform grows without overwhelming users — each team configures their own capability surface.
F-10 Artifacts surface with type-based library P1-3
Surface: Artifacts · #artifacts
A visual library of every AI-generated artifact: emails, SMS variants, WhatsApp stories, landing pages, audience segments, campaign sheets. Each artifact card shows a colored thumbnail, channel icon, AI badge, title, and status (Draft / Sent / timestamp). Artifacts generated via Canva 2.0 features carry a CANVA 2.0 badge.
Components & Widgets
Page header (title + Filter + New artifact buttons) · Auto-fill grid (min 220px per card) · Artifact cards (colored thumbnail, channel icon + AI badge, title, status/timestamp) · Filter button (placeholder for origin/type/date filtering)
Problem Solved
Template origin filtering architecture. Addresses P1-3 (templates carousel needs surface-origin filter). The Artifacts surface supports type-based and origin-based categorization. The Filter button provides the entry point for NEB/Classic/All filtering. Each artifact carries metadata (channel, AI-generated vs manual, Canva 2.0 vs baseline).
Customer Benefit
Users find all their past work in one place — filterable, searchable, and organized by type. Classic anchor users (HVC #6) can filter to find familiar templates. New AI-first users see their generated artifacts. The library grows with usage, creating a "portfolio" effect that increases retention.
F-11 Expert team surface
Surface: Expert Team · #experts
A scheduling surface for three human experts included in the Mailchimp Standard plan: Kimberlee Amsbaugh (Email Strategist, 4.8★, 12 yrs), Jane Kligner (Audience Expert, 4.9★, 11 yrs). Each expert card shows availability slots for booking. Monthly impact summary: "~12 hrs saved · 1,840 VIPs segmented · $4,200 attributed revenue."
Components & Widgets
Expert cards (avatar circle with initial, name, role, star rating, years) · Available time slots (button grid: 9:00, 9:30, 10:00, 11:00, 1:00 PM) · Impact summary narration
Problem Solved
Human-in-loop for power users who need more than AI. Creates an escalation path for complex creative decisions: "I can't decide between these two approaches — let me book time with Kimberlee." Combines AI automation for routine work with human expertise for high-stakes decisions.
Customer Benefit
Customers get the speed of AI plus the judgment of experienced humans. Power users and agencies who don't trust AI alone have a named, rated expert they can consult. The "Work done for you" companion surface quantifies the combined value of AI + human output ($2,461 saved · 24 hrs saved this month).
F-12 Home dashboard with AI prompt-starter chips
Surface: Home · data-pane="home"
The traditional Home dashboard is preserved with marketing-conversions metrics (Total sends, Delivery, Open, Click, Order rate, Unsub). Below the metrics, AI prompt-starter chips appear: "Last 30 days of campaign performance?", "What drove the Mother's Day Gift Guide spike?", "How is our Houseplant Collectors segment trending?" These route into the AI rail for conversational analysis.
Components & Widgets
Page header (Home + Quick actions + Create buttons) · Marketing conversions card with 6-column metric grid · Insight chips (rounded pill buttons with ✨ prefix) · Each chip routes to AI rail for deep analysis
Problem Solved
Bridges traditional dashboard and AI interaction. Users who land on Home (the most familiar surface) see AI as an enhancement to data they already understand. The prompt-starter chips introduce AI capabilities in context: "I'm looking at my open rate — why is it different?"
Customer Benefit
Zero-friction AI discovery for users who aren't yet comfortable with agent-first workflows. The AI meets them where they already are (the dashboard) instead of requiring them to navigate to a new surface. Increases AI adoption among the cautious majority.

Source: All features cataloged from direct interaction with Agent Mode v2 prototype + source at /Users/dprabhakara/ai_workspace/mailchimp-agent-shell-site/v2/index.html. Audit references map to Tab 18 Page 7 P0/P1/P2 priority buckets.

Tab 20 · Deepak's Agent Mode Prototype — Canva AI 2.0 Gap Closure

Prototype Walkthrough: Closing the Canva AI & AI 2.0 Gap

Feature-by-feature walkthrough of every capability in Deepak's Agent Mode v2 prototype that closes the competitive gap between Mailchimp's agent mode and Canva's AI / AI 2.0 capabilities. Each feature marked CANVA 2.0 is a net-new capability Mailchimp doesn't yet offer. For each: the prototype surface, components & widgets, interactions, what problem it solves, and the customer benefit.
Competitive context. Canva's AI 2.0 launch (2025–2026) introduced: Conversational design (prompt → full campaign), Canva Shield (enterprise AI governance), Memory (per-account learning), Sheets AI + Bulk Create, Connectors (live data from 30+ apps), MCP integration (external AI reads Canva context), Magic Design/Edit/Expand/Grab/Morph/Layers/Resize/Translate/Media, Dream Lab, and Canva Code 2.0. Mailchimp currently matches none of these. Deepak's prototype incorporates all of them, adapted to the Mailchimp email-marketing context.

01Conversational Campaign Start

C-01 Multi-channel bundle generation from one prompt CANVA 2.0
Surface: New Conversation · #conv-start
A centered, hero-scale creation surface: "What should we build today, Maya?" with channel selector pills (Email, SMS, WhatsApp, Landing page, Social post, + Custom), a large prompt composer, quick-prompt chips, and a "Generate bundle →" button. On submit, the AI generates all four channel variants simultaneously, returning a 2×2 grid of bundle tiles — each with its own preview, channel label, AI badge, and action buttons (Open editor, Send test, Publish).
Components & Widgets
Hero layout (✦ logo + h1 + lede text, centered) · Channel pills (6 pills, 4 active by default, toggleable) · Big composer (720px, rounded 16px, 2px border, shadow, focus glow) · "+" context button + text input + "Generate bundle →" CTA · Quick-prompt chips (4 pre-seeded: Father's Day, Win-back VIPs, Spring drop, Lapsed re-engagement) · Bundle result (4 tool-use pills done state + "Four artifacts ready" heading + narration + 2×2 bundle tile grid) · Bundle tile (channel icon + label, AI badge, preview placeholder, Open editor + Send test buttons) · Footer bar ("Save bundle" + "Schedule all 4" CTAs)
Problem Solved
Canva gap: multi-channel campaign from a single prompt. Canva's AI 2.0 generates entire multi-format campaigns (social post, presentation, doc, website) from one prompt. Mailchimp currently creates one channel at a time in separate workflows. This prototype matches Canva's multi-artifact generation and adds marketing-specific channel awareness (email/SMS/WhatsApp best practices applied per variant).
Customer Benefit
The marketer types one prompt and gets a coordinated 4-channel campaign in seconds. "Each channel got its own variant. They share copy DNA but follow channel best practices." This collapses what used to be 4 separate creation sessions into one. Directly attacks T1 trial activation ($5.0M) by demonstrating the platform's full power in the first interaction.

02Memory Library

C-02 Persistent AI memory across campaigns CANVA 2.0
Surface: Memory Library · #memory
A full surface for AI-learned rules organized in three categories: Voice & copy patterns (e.g., "Always frame plants as self-care, never as decor"), Audience & segmentation (e.g., "Houseplant Collectors respond to education content — 2.3× higher click rate"), and Visual style (e.g., "Hero images: natural light, in-room context, real-looking people not stock"). Each rule shows its learning source, recency, and has an Edit button. Header actions: "Export memory" and "+ Teach AI a new rule."
Components & Widgets
Page header (🧠 icon + title + CANVA 2.0 badge + Export + Teach buttons) · Narration text · Three category sections (h3 labels) · Memory items (card with text, source/recency, Edit button) · Source attribution ("Learned from: 18 campaigns · Last reinforced 4 days ago")
Problem Solved
Canva gap: per-account AI learning. Canva's AI 2.0 Memory stores user preferences, brand rules, and learned patterns across sessions. Mailchimp's current AI starts from baseline every time. This prototype implements persistent per-customer memory with declared sources and edit controls — also serving as the Universal Content primitive (P1-4) for reusable content patterns.
Customer Benefit
The AI gets smarter with every campaign. "Maya overrode this 7 times in 2025; it stuck." Users no longer need to re-explain their brand voice, audience preferences, or visual style every session. The export button enables portability. The teach button enables deliberate rule-setting. This is the single biggest retention differentiator against competitors where AI resets every session.

03Campaign Sheets

C-03 Sheets AI — prompt-to-campaign-calendar CANVA 2.0
Surface: Campaign Sheets · #sheets
A spreadsheet-style surface where the AI generates structured campaign content from a prompt. The example shows a "Father's Day campaign · 4-week sequence" with 6 rows (tease, main drop, VIP early access, all subscribers, cart abandoners, lapsed re-engagement) and 6 columns (Send date, Segment, Subject line, Hero copy, Product, CTA). AI-generated cells are highlighted with a ✨ marker. Toolbar actions: "+ Add column", "✨ Fill empty cells", "Connect to email canvas."
Components & Widgets
Sheet toolbar (title, row/column count, action buttons: Add column, Fill empty cells, Connect to email canvas) · Sheet table (6 columns, 6 rows with real data) · AI-generated cell highlight (.cell-ai with ✨ marker, subtle yellow tint) · Import CSV button · "New sheet from prompt" AI button
Problem Solved
Canva gap: Sheets AI + Bulk Create + Connect Data. Canva's Sheets AI lets users prompt for spreadsheet content, connect cells to design elements, and bulk-create variants. Mailchimp has no equivalent. This prototype brings structured campaign planning into the AI surface — one prompt generates a full 4-week content calendar with per-segment targeting, subject lines, and copy.
Customer Benefit
"Edit a cell, regenerate the rest." Marketers who plan in spreadsheets (the majority) get AI-powered content generation inside their planning workflow. The "Connect to email canvas" button means each row becomes a real campaign variant — no copy-pasting between a planning doc and the editor. Reduces the gap between "plan the quarter" and "execute the quarter" to one click.

04Connectors & MCP Integration

C-04 Live data connectors with 13+ integrations CANVA 2.0
Surface: Connectors · #connectors
A connector management surface showing 5 connected integrations (Shopify, Slack, Gmail, Google Drive, Notion) and 8 available (HubSpot, Google Calendar, Microsoft 365, Atlassian/Linear, Zoom, Web research). Each connector has a toggle switch (on/off) and shows the data it provides ("Orders · catalog · customers"). A special MCP integration card at the bottom: "Let ChatGPT, Claude, or your own agent read your Mailchimp design context."
Components & Widgets
Page header (🔗 icon + title + CANVA 2.0 badge + "Browse all connectors" button) · Narration text · Connected section (5 connector cards) · Available section (6 connector cards) · Connector card (icon + name + meta description + toggle switch) · Toggle switches (on = teal, off = gray) · MCP integration banner (yellow left-border card with 🤝 icon, description, Configure button)
Problem Solved
Canva gap: Connectors + MCP. Canva's AI 2.0 connects to 30+ apps (Google Docs, Sheets, YouTube, Hubspot, Salesforce) and exposes MCP for external AI tools. Mailchimp's AI operates in a data silo — no live context from the tools marketers actually use. This prototype surfaces real-time data (Shopify orders, Slack conversations, Google Drive brand assets) as AI context, and enables external AI agents to read Mailchimp data.
Customer Benefit
"Every assistant reply that uses external data gets a coin-stamp showing which sources it touched." The AI doesn't hallucinate product data — it pulls from the connected Shopify catalog. It doesn't guess at brand assets — it reads from Google Drive. And external AI tools (ChatGPT, Claude) can use Mailchimp data without screen-scraping. This is the infrastructure layer that makes AI-generated content trustworthy.

05Brand Intelligence

C-05 Brand rules engine with automatic artifact refresh CANVA 2.0
Surface: Brand Intelligence · #brand
A two-column layout: left column shows "Active brand rules" (6 declarative rules like "Use Playfair Display for all headlines, Inter for body. Never Helvetica." and "Primary buttons: Forest Green (#2D5016)") with a refresh banner ("23 saved artifacts will be refreshed when you click Update all to latest brand"). Right column shows Palette (4 swatches), Voice profile, and a brand compliance indicator ("100% of active artifacts pass brand check ✓").
Components & Widgets
Page header (✨ icon + title + CANVA 2.0 badge + Edit profile + "⚡ Update all artifacts to latest brand" AI button) · Two-column brand panel · Brand rules list (✓ icon + rule text) · Refresh banner (teal background, 🔄 icon, count of affected artifacts) · Color swatches (4 squares with hex labels) · Voice description (comma-separated descriptors) · Compliance indicator (green success card)
Problem Solved
Canva gap: Brand Kit as an enforceable rules engine, not a passive settings modal. Canva's Brand Kit enforces rules across all designs. Mailchimp's Brand Kit is a modal that can be silently overridden by themes (P0-6). This prototype transforms brand settings into active rules that the AI enforces, with a one-click "update all artifacts" action that retroactively applies brand changes to existing drafts.
Customer Benefit
"100% of active artifacts pass brand check." Brand consistency is automated, not aspirational. When the customer changes their brand green, all 23 saved artifacts refresh automatically. No manual per-email updates. No silent overrides. The compliance indicator gives instant confidence that every draft matches the brand — critical for agencies managing multiple client brands.

06AI Governance (Canva Shield)

C-06 Enterprise-grade AI controls — data, models, content review CANVA 2.0
Surface: AI Governance · #governance
Three governance sections: (1) Data & retention — chat retention (90 days, configurable), audience PII exclusion (ENFORCED badge), web research scope (toggleable); (2) Model selection — approved model list (Claude, GPT-5, Mailchimp In-House; block Llama and open-weight), data residency (US-only); (3) Content review — pre-send review queue (human reviewer for audiences >5,000), compliance lint (CAN-SPAM, GDPR, CCPA — ALWAYS ON).
Components & Widgets
Page header (🛡 icon + title + CANVA 2.0 badge + Audit log + Save policy buttons) · Three sections with h3 labels · Governance rule cards (icon wrap + title + description + control: dropdown/toggle/badge) · Control types: dropdown selector ("90 days ▾"), toggle switch, ENFORCED badge (green), ALWAYS ON badge (green), Edit list button
Problem Solved
Canva gap: Canva Shield for enterprise AI governance. Canva Shield gives enterprise teams control over what AI can see, store, and produce. Mailchimp has no equivalent. This prototype addresses P0-2 (SMS TCPA compliance) via the compliance lint, P0-1 (audience confirmation) via the pre-send review queue, and P0-3 (AI content verification) via the human-in-loop review requirement for large audiences.
Customer Benefit
Enterprise customers get the controls their legal/compliance teams require before they can adopt AI tools. "Audience PII is never sent to external models." "AI-generated sends go through a human reviewer when audience is >5,000." "CAN-SPAM, GDPR, CCPA — automated check before any send." These are table-stakes for enterprise adoption and currently block Mailchimp from competing for large accounts.

07Magic Creative AI Family

C-07 Magic Design, Edit, Grab, Expand, Morph, Layers, Resize, Translate, Media, Dream Lab CANVA 2.0
Surface: AI Skills & Tools + Focus View (Magic toolbar + edit rail)
Ten creative AI capabilities from Canva's Magic family, adapted to the Mailchimp email-marketing context. In the Focus view, a floating dark toolbar surfaces six tools directly (Magic Edit, Magic Expand, Magic Grab, Magic Morph, Style match, Remove BG). The right-side edit rail lists five more (Magic Layers, Magic Resize, Magic Translate, Magic Media, Dream Lab). Each tool is also discoverable as a toggle-enabled skill card in the AI Skills surface.
Components & Widgets
Focus view toolbar: Dark floating bar (6 buttons: ✨ Magic Edit, ✨ Magic Expand, ✨ Magic Grab, ✨ Magic Morph, Style match, Remove BG) · Positioned above email canvas · AI buttons in yellow, manual in white
Edit rail: "Magic family" group (5 items with ✨ icons: Layers, Resize, Translate, Media, Dream Lab)
Skills surface: 8 skill cards with CANVA 2.0 badges + toggle switches
Problem Solved
Canva gap: the entire Magic creative AI toolkit. Canva offers brush-replace (Edit), subject extraction (Grab), frame-fill (Expand), themed effects (Morph), editable layers from flat images (Layers), multi-format resize (Resize), 100+ language translation (Translate), text-to-image/video (Media), and high-fidelity generation with style references (Dream Lab). Mailchimp currently has none of these. This prototype surfaces them all in the editing context.
Customer Benefit
Marketers who aren't designers can: remove backgrounds from product photos (Magic Grab), extend images to fill email banners (Magic Expand), apply consistent visual themes (Magic Morph), resize one email design to fit SMS/WhatsApp/social (Magic Resize), and translate campaigns into 100+ languages with brand-voice preservation (Magic Translate). This collapses the "I need to hire a designer" barrier that blocks 68% of trial users from completing their first campaign.

08Agentic AI & Orchestration

C-08 Design-aware AI chat with element-level preservation CANVA 2.0
Surface: Focus View · Chat panel
In the Focus view, the user types "Make the hero more autumnal" in the chat panel. The AI responds: "Done — hero shifted to warmer tones with autumnal foliage. Body copy unchanged. The change applied only to the hero block — your CTA, product picks, and footer are untouched." A tool pill confirms: "Layered object intelligence · editing hero only."
Components & Widgets
Chat panel (340px left side of Focus view) · Message thread (scrollable, preserves full history) · Tool-use pill ("Layered object intelligence · editing hero only") · Agent response with explicit change declaration · Composer with placeholder "Edit this email by talking to me…" · Footer: "Conversational design editing · Element-level preservation"
Problem Solved
Canva gap: conversational design editing with surgical element-level edits. Canva's AI 2.0 supports design-aware chat where edits target specific elements without regenerating the whole design. Mailchimp's Freddie prototype only offers full regeneration. This prototype brings element-level intelligence: the AI modifies only the targeted block and explicitly declares what was (and wasn't) changed.
Customer Benefit
"Edit anything by clicking it, or talk to me below — I'll edit by element without regenerating the whole thing." Users preserve their investment in prior manual and AI edits. Each refinement is surgical, not destructive. The AI's explicit change declaration ("your CTA, product picks, and footer are untouched") builds calibrated trust and reduces the need for manual verification after every AI edit.
C-09 @Mailchimp AI in comments CANVA 2.0
Surface: Focus View · Edit rail → Comments & review group
In the Focus view's right-side edit rail, under "Comments & review", an item reads "✨ @Mailchimp AI in comments." This enables the Canva 2.0 pattern where team members tag the AI in a comment thread and it applies the suggested fix in place.
Components & Widgets
Edit rail group "Comments & review" · Comments (2) item · ✨ @Mailchimp AI in comments item (magic class, teal text) · Review checklist item
Problem Solved
Canva gap: AI-in-comments collaboration. Canva's AI 2.0 lets collaborators tag the AI in comment threads to request changes. Mailchimp has no AI collaboration layer. This enables multi-author workflows (HVC #4, Bet 4) where one team member tags the AI to apply a fix suggested by another, without either needing to manually edit.
Customer Benefit
Team reviews become actionable: a manager comments "make the CTA bigger" and tags @Mailchimp AI, which applies the change immediately. Reduces the round-trip between review feedback and implementation from hours to seconds. Enables the multi-author workflow shape (Workflow Shape #4) that the current prototype doesn't support.
C-10 External AI integration (MCP), Web research, Scheduled AI tasks CANVA 2.0
Surface: AI Skills & Tools + Connectors
Three agentic capabilities: (1) ChatGPT & Claude (MCP) — external AI workflows read Mailchimp design context; (2) Web research — live competitive and seasonal data pulls; (3) Scheduled AI tasks — set-and-forget recurring AI generation (e.g., weekly SMS batches). Each is a toggleable skill card in the AI Skills surface. MCP also appears as the integration card in Connectors.
Components & Widgets
Three skill cards in "Agentic AI" section (each with CANVA 2.0 badge + toggle switch) · MCP integration banner in Connectors (yellow-border card with 🤝 icon, description, Configure button) · Governed by AI Governance data residency and model selection rules
Problem Solved
Canva gap: AI platform extensibility. Canva's MCP integration, web research, and scheduled tasks make it an AI platform, not just an AI tool. Mailchimp's AI is currently self-contained with no extensibility. This prototype opens the platform: external AI agents can generate Mailchimp campaigns, live web data informs recommendations, and recurring tasks run autonomously.
Customer Benefit
Users who already use ChatGPT or Claude can generate Mailchimp campaigns from those tools without context-switching. Seasonal data (holidays, competitor moves) automatically informs AI recommendations. Weekly recurring campaigns (inventory updates, newsletter digests) generate themselves. The AI becomes a marketing autopilot, not just a manual assistant.

09Data & Productivity AI

C-11 Bulk Create, Fill Empty Cells, Magic Formulas, Canva Code 2.0 CANVA 2.0
Surface: AI Skills & Tools · "Data & productivity" section
Five data/productivity AI tools: (1) Sheets AI — prompt → structured campaign calendar; (2) Bulk Create — CSV/XLSX-driven variant generation up to 300 rows × 60 cols; (3) Fill Empty Cells — Magic Write at scale across an entire sheet; (4) Magic Formulas — natural-language → spreadsheet formula generation; (5) Canva Code 2.0 — prompt-built interactive landing pages with quizzes & calculators.
Components & Widgets
Five skill cards in "Data & productivity" section · Each with CANVA 2.0 badge + description + toggle switch · Sheets AI and Bulk Create shown "on" by default · Campaign Sheets surface serves as the live demonstration of Sheets AI + Fill Empty Cells + Bulk Create working together
Problem Solved
Canva gap: AI-powered data workflows. Canva's Sheets AI, Bulk Create, and Connect Data features let users generate hundreds of design variants from spreadsheet data. Mailchimp has no equivalent. This prototype brings CSV-driven variant generation (critical for e-commerce product catalogs), formula generation for campaign planning, and prompt-built interactive landing pages.
Customer Benefit
E-commerce marketers with 300-product catalogs can generate per-product email variants from a CSV. Campaign managers can build 4-week content calendars from a prompt. Marketing teams can create interactive landing pages (quizzes, calculators) without engineering. Each tool removes a "we need an engineer for that" blocker that currently causes campaign delays or compromises.
Competitive summary. Deepak's Agent Mode v2 prototype incorporates 11 net-new capability groups from Canva's AI 2.0 playbook: conversational multi-channel bundle generation, persistent AI memory, campaign sheets, live data connectors + MCP, brand rules engine, AI governance (Canva Shield), the full 10-tool Magic creative AI family, design-aware conversational editing, layered object intelligence, @AI in comments, and 5 data/productivity tools (Bulk Create, Fill Empty Cells, Magic Formulas, Canva Code 2.0, Scheduled AI tasks). These capabilities close every documented competitive gap between Mailchimp and Canva's AI 2.0 platform while adapting each to the marketing-specific context of email, SMS, WhatsApp, and audience management.

Source: All features cataloged from direct interaction with Agent Mode v2 prototype + source at /Users/dprabhakara/ai_workspace/mailchimp-agent-shell-site/v2/index.html. Canva AI 2.0 capability list from Canva campaign analysis brief. Competitive gap mapping based on Tab 17 Freddie Assessment + Tab 18 Agent Mode Design Audit.

Tab 21 · Interactive Walkthrough

Audit Gap Walkthrough — Step by Step

Click Next to walk through each feature in Deepak's prototype that resolves an Agent Mode Design Audit finding. Each step shows the feature, where to find it in the live prototype, the problem it solves, and the customer benefit.
Step 1 of 12 Open prototype →
Tab 22 · Interactive Walkthrough

Canva AI 2.0 Gap Closure — Step by Step

Click Next to walk through each feature in Deepak's prototype that closes the competitive gap between Mailchimp's agent mode and Canva's AI / AI 2.0 capabilities. Each step shows the feature, where to find it in the live prototype, the problem it solves, and the customer benefit.
Step 1 of 11 Open prototype →
Tab 23 · Freddie Builder vs Agent Mode — Overlap Analysis

Feature Overlap: Freddie Builder Fixes vs Deepak's Agent Mode

Cross-reference of every feature, functionality, and experience recommended for the Freddie Builder (P0/P1/P2 from the Agent Mode Design Audit) against every feature in Deepak's Agent Mode prototype (from Audit Gap Walkthrough + Canva AI 2.0 Walkthrough). Each item classified as: SHARED (needed by both), FREDDIE ONLY (unique to the builder), or AGENT MODE ONLY (unique to the agent experience).
14
Shared — needed by both surfaces
8
Freddie Builder only
17
Agent Mode only
39
Total unique capabilities

01Shared — Required by both Freddie Builder & Agent Mode 14 items

These capabilities are needed regardless of surface. Both the Freddie Builder and the Agent Mode must deliver them. The implementation differs (Freddie uses modals/buttons; Agent Mode uses conversational reasoning), but the customer outcome is the same.

#Feature / CapabilityFreddie Impl.Agent Mode Impl.Audit Ref
S-1Audience-confirmation before Send. User must explicitly confirm recipient count and segment before broadcasting.Mandatory confirm modal with recipient countAI Rail asks: "Before I send to 2,150 recipients…" — conversational confirmationP0-1
S-2SMS TCPA compliance gating. SMS channel must be blocked until compliance guardrails ship.Feature-flag SMS tab OFF + tooltipGovernance panel "Pre-publish legal check" + nav item gatingP0-2
S-3AI-content verification pre-send. Footer, promo codes, products validated against real entities before send.Pre-send checklist modalAI Rail reasoning + Connectors verify live catalog dataP0-3
S-4Manual mode as first-class entry. Users must be able to skip AI and go straight to manual editing."Skip AI — open blank editor" button on Create screenPersistent sidebar nav + direct channel routes (Campaigns, SMS) bypass AIP0-4
S-5Send-test recipient picker. Test email must go to a specified address, not a default.Recipient picker modal with own email pre-filledAI Rail tool call: send_test(to: "maya@…") with confirmationP0-5
S-6Brand Kit / Brand Intelligence enforcement. Theme presets must not silently override brand settings.Apply-and-confirm dialog: "Keep brand colors / override?"Brand Intelligence rules engine + brand-compliance check on every generationP0-6
S-7Custom font upload. Users need to upload their own fonts, not just pick from 23 web-safe fonts.Font-upload UI in Brand Kit modalBrand Intelligence font rule + upload connectorP1-1
S-8Value-first brand communication (not upgrade pressure). Free tier should see brand features as value, not as a gate.Reframe brand-context banner copyDaily Brief leads with insights, not upgrade promptsP1-2
S-9Error / Failed state for AI generation. Generation failures must show diagnostic feedback + retry."Failed" pill on artifact cards + retry buttonAI Rail error message: "I wasn't able to generate — here's why" + retryP1-6
S-10Cancel / abort during AI generation. Long-running generation must be cancellable.Cancel button on generation spinnerTool-pill cancel: stop in-progress tool operationP1-7
S-11Autosave visibility / state contract. Users must know their work is saved and what state is preserved."Saved / Saving…" indicator in toolbarAI Rail reasoning: "I've saved your draft. Manual edits preserved."P1-9
S-12Deep-linkable editor. Editor and strategy views must be shareable/bookmarkable.Convert right-pane states to route-based or query-param navigationHash-based routing (#brief, #memory, #brand, etc.)P1-10
S-13WCAG 2.2 AA accessibility. All interactive components need proper aria-labels, touch targets, focus traps.Full a11y engineering pass on all componentsFull a11y engineering pass on all componentsP2-1
S-14Rendering parity / inbox preview. Need real Gmail/Outlook/Apple Mail rendering, not just CSS preview.Litmus/Email on Acid integration in PreviewConnectors surface: inbox-preview connector integrationP2-10

02Freddie Builder Only 8 items

Features unique to the Freddie Builder surface that don't apply to the Agent Mode architecture. These are either specific to the Freddie UI patterns (tab bar, chat thread, theme popover) or are Builder-specific infrastructure investments.

#Feature / CapabilityWhy Freddie OnlyAudit Ref
FO-1Templates carousel with surface-origin filter (NEB / Classic / All).The Freddie Builder uses a templates carousel on the Create tab. The Agent Mode uses an Artifacts library with a Filter button instead — different UI pattern, same need met differently.P1-3
FO-2Universal Content primitive (Pillar 2.1).The Freddie Builder needs Universal Content shipped as infrastructure. Agent Mode already has Memory Library as its equivalent. Freddie lacks this primitive entirely.P1-4
FO-3Version history in chat thread (per-generation rollback).Freddie's chat thread needs an explicit version-history drawer with restorable checkpoints. Agent Mode's per-message structure naturally creates these boundaries — less explicit UI needed.P1-5
FO-4HTML code mode escape hatch (NEB Code Mode, Pillar 2.2.3).Critical for Freddie's premium/agency ceiling. Agent Mode surfaces this as an "HTML editor" skill card — architecturally different approach.P1-8
FO-5Two-shell navigation breadcrumb.Specific to Freddie's trap-door pattern where Create disposes global nav. Agent Mode eliminates the pattern entirely with persistent sidebar, so no breadcrumb needed.P2-4
FO-6Sidebar conversation search + rename.Freddie's sidebar conversation list lacks search/rename. Agent Mode's AI Rail uses a different conversation persistence model.P2-5
FO-7Stub tab affordance clarity.6 of 8 channel tabs in Freddie are stubs. Need "Coming soon" badges or disabled states. Agent Mode has no stub tabs — all sidebar items route to real surfaces.P2-8
FO-8Per-edit undo (not just full regenerate).Freddie's Copy/Like/Dislike/Regenerate row only offers binary regenerate. Specific to the Freddie chat+editor paradigm. Agent Mode's element-level editing makes this less critical.P2-9

03Agent Mode Only 17 items

Features unique to Deepak's Agent Mode prototype. These either don't have a Freddie Builder equivalent, or represent entirely new capabilities from the Canva AI 2.0 competitive gap closure that the Freddie surface was never designed to deliver.

#Feature / CapabilityWhy Agent Mode OnlySource
AO-1Multi-channel bundle generation from one prompt. Email + SMS + WhatsApp + Landing page generated simultaneously.Freddie creates one channel at a time. The bundle paradigm requires the agent orchestration layer.Canva 2.0
AO-2Memory Library — persistent AI learning across campaigns.Freddie has no memory system. Every session starts from baseline. Memory is architecturally native to the agent model.Canva 2.0
AO-3Campaign Sheets (Sheets AI + Bulk Create + Connect Data).Freddie is a single-email editor. The spreadsheet-based campaign planning paradigm doesn't fit the Freddie UI.Canva 2.0
AO-4Live data connectors (Shopify, Slack, Gmail, Notion, etc.).Freddie doesn't have a connector surface. Data integrations are native to the agent architecture.Canva 2.0
AO-5MCP integration — external AI reads Mailchimp design context.Freddie is a closed-loop editor. The MCP protocol requires the agent's tool-use architecture.Canva 2.0
AO-6AI Governance (Canva Shield) — data, model, and content controls.Freddie has no governance surface. Enterprise controls require the dedicated governance panel.Canva 2.0
AO-7Magic Design — complete first-draft from prompt.Freddie has prompt-to-email, but Magic Design is the broader Canva-equivalent multi-format version. The agent surface is where it lives.Canva 2.0
AO-8Magic Edit / Grab / Expand / Morph — image manipulation suite.Freddie's editor has no image manipulation beyond upload. The Magic family requires the Focus view's floating toolbar.Canva 2.0
AO-9Magic Layers — flat images become editable layered designs.Not applicable to Freddie's block-based email editor paradigm.Canva 2.0
AO-10Magic Resize / Switch — one design → 8+ channel placements.Freddie creates one channel at a time. Multi-format resize is native to the bundle paradigm.Canva 2.0
AO-11Magic Translate — 100+ language translation with brand-voice preservation.Freddie has no translation capability. Requires the agent's brand intelligence + memory context.Canva 2.0
AO-12Magic Media — text-to-image and text-to-video (Veo-3).Freddie has no generative media. Requires the agent's creative AI skill infrastructure.Canva 2.0
AO-13Dream Lab — high-fidelity image generation with style references.Same as above — generative media requires the agent skill infrastructure.Canva 2.0
AO-14Design-aware AI chat with element-level preservation (Layered Object Intelligence).Freddie's conversational editing regenerates at the full-email level. Element-level editing requires the agent's layered intelligence.Canva 2.0
AO-15@Mailchimp AI in comments — tag AI in review threads.Freddie has no comments/review layer. Multi-author collaboration requires the agent's Focus view.Canva 2.0
AO-16Scheduled AI tasks — recurring autonomous generation.Freddie is a manual creation tool. Autonomous recurring generation is an agent-native concept.Canva 2.0
AO-17Canva Code 2.0 — prompt-built interactive landing pages.Freddie builds emails/SMS. Interactive landing pages with quizzes and calculators are a separate artifact type native to the agent surface.Canva 2.0

04Strategic read

The overlap tells a clear story. Of 39 total capabilities across both surfaces:
  • 14 are shared (36%) — these are primarily the P0 launch-blocking and P1 trust/safety requirements (audience confirmation, TCPA gating, content verification, manual mode, error states, accessibility). Both surfaces must deliver them, but they implement differently: Freddie uses modals and buttons, Agent Mode uses conversational reasoning and governance panels.
  • 8 are Freddie-only (21%) — these are specific to Freddie's UI paradigm: templates carousel, version history in chat thread, HTML code mode, two-shell breadcrumb, stub tab affordances, conversation search, per-edit undo, and Universal Content as an infrastructure primitive. These are technical debts and UX fixes unique to the existing Freddie surface.
  • 17 are Agent Mode-only (44%) — these are the Canva AI 2.0 competitive gap closures that are architecturally impossible in the Freddie paradigm: multi-channel bundles, persistent memory, campaign sheets, live data connectors, MCP, governance, the full Magic creative AI family (10 tools), element-level editing, @AI in comments, scheduled tasks, and interactive landing pages. These represent the future surface — capabilities Freddie was never designed to deliver.
Recommendation. Ship the 14 shared capabilities on the Freddie Builder as the immediate priority (these are the P0/P1 mitigations required before any user exposure). Simultaneously build Deepak's Agent Mode as the future surface. The 8 Freddie-only items are worth investing in only if the Freddie Builder remains the default for the next 2+ quarters. If the Agent Mode ships as the primary surface within Q3-Q4, the Freddie-only items become sunken cost — the Agent Mode's architecture renders them unnecessary (persistent sidebar eliminates the breadcrumb need; Memory Library replaces Universal Content; element-level editing replaces per-edit undo; Artifacts surface replaces the templates carousel).

Source: Freddie Builder capabilities from Tab 18 (Agent Mode Design Audit) P0/P1/P2 priority buckets (26 items). Agent Mode capabilities from Tab 19 (12 audit-gap features) + Tab 20 (11 Canva AI 2.0 features). Overlap determined by matching customer outcome (not implementation approach).