Migration Briefing Automations Classic → CJB FY27

Mailchimp Automations Migration: The Migration Is Mostly Done — Here's What's Left and Why It's Sticky

Author: R&A PM team • Last updated: May 11, 2026 • Data window: May 2024 – May 2026 (24 months) • Pipeline date: 2026-05-11 • Companion brief: NEA → NUNI Editor Migration

View Toggle to see metrics & charts in either lens

Executive Summary

Among paid customers using automations, CJB has effectively won — 95.0% adoption. The remaining Classic Automations base is small ($31M ARR vs $407M on CJB) but unusually sticky: the paid-HVC reverter rate is 28.6% — 3× higher than what we saw for the editor migration. The bigger story is upstream: 695,109 paid customers don't use automation at all, representing $730M ARR of untapped CJB conversion opportunity — including 41,168 HVCs at $271M ARR.

Across all editor users (Free + Paid), CJB has effectively won — 93.5% adoption of accounts with any automation activity in the last 365 days. The Classic-only residual is 17,001 users; combined-with-CJB is 18,037 (of which 4,797 reverted to Classic-recent). The migration is mostly complete; the residual cohort is small but heavily revenue-concentrated and resistant to forced flips. Bigger opportunity: 4.0M users (90% of base) don't use automation at all — converting them to CJB is a much bigger ARR lever than completing the migration.

Top metrics

95.0%

Paid CJB adoption (229,612 of 241,883 paid automation users)

5.0%

Paid Classic-current (12,271 users — 8,568 only + 3,703 reverters)

$31.3M

Classic-current paid ARR ($2.61M MRR × 12)

$21.2M

HVC ARR concentration on Classic (2,550 users)

28.6%

Paid HVC reverter rate (tried CJB → went back to Classic)

$407M

Paid CJB ARR ($33.92M MRR × 12)

$730M

Paid no-automation ARR (untapped CJB opportunity)

$271M

Paid HVC no-automation ARR (top opportunity slice)

93.5%

CJB adoption (393K of 410K accounts with any automation usage)

17,001

Classic-only stayers (no CJB usage in 365d)

$31.3M

Paid Classic-current ARR (Free contributes $0)

$21.2M

HVC ARR concentration on Classic

28.6%

HVC reverter rate (tried CJB → went back to Classic)

$407M

CJB paid ARR

4.02M

Accounts with NO automation usage (90.7% of total)

$730M

Paid no-automation ARR opportunity

Five things a senior exec must take away

Migration is essentially done. 95% of paid automation users are on CJB. The remaining 12,271 paid Classic-current users represent only $31.3M ARR — 5.5% of the editor migration's $566M exposure. We should stop talking about "completing" the migration and start protecting what's left while accelerating CJB penetration.
The residual stayers are 3× more sticky than editor stayers. Of HVC paid users who tried both, 28.6% reverted to Classic-recent (vs 8–10% for the editor migration). These users are the longest-tenured cohort in the entire base: median 125 months (~10.4 years) on platform, median list size 50,953. They will not move on a default flip.
The bigger ARR lever isn't migration — it's automation penetration. 695,109 paid customers (74% of the paid base) don't use automation at all. Of those, 41,168 are HVCs sitting on $271M ARR. Converting just 10% of HVC non-users into CJB users is a $27M ARR uplift — bigger than the entire Classic-current exposure.
Existing CJB users have real product issues, but VOC volume is far smaller than the editor (104 negative automation VOCs vs 1,551 editor). Top themes: editor/UI glitches in CJB, slow CJB UX, missing AI/generative copy, reporting accuracy bugs, and Classic→CJB migration conversion bugs. Worth fixing for retention and to unblock the no-automation conversion play.
The right strategy is "preserve + grow", not "force migrate". A 3-phase plan: Phase 1 default-flip the easy 15K Classic-only paid<$299 (months 0–3, $7M ARR migrated); Phase 2 concierge for the 2,550 HVC stayers + reverters (months 3–9, $21M ARR preserved); Phase 3 — and most importantly — launch a CJB-adoption GTM motion targeting the 41K HVC non-automation users ($271M ARR opportunity).

Decision asks (one slide)

Approve the 3-phase plan

Phase 1 default-flip the easy Classic stayers. Phase 2 concierge HVC. Phase 3 pivot to CJB-adoption GTM motion targeting non-automation HVCs.

Fund the top CJB defect fixes

Editor/UI glitches in CJB, reporting accuracy, premature activation, Classic→CJB migration conversion bugs. Retention spend that also unblocks the $271M ARR no-automation conversion play.

Approve the CJB-adoption GTM motion

41,168 HVC paid customers ($271M ARR) have never used automation. Even 10% conversion = $27M ARR — bigger than the entire Classic exposure.

1. Situation — The migration looks done, but...

Mailchimp has been migrating customers from Classic Automations (parent/child email_automation events) to Customer Journey Builder (CJB) (customer_journey_builder + email-touchpoint events) for several years. As of the most recent BI snapshot (pipeline date 2026-05-11), among accounts with any automation activity in the last 365 days:

Automation usage — paid customers (last 365 days)

CJB only

219,532 (90.8%)

Both, CJB recent

10,080 (4.2%)

Classic only

8,568 (3.5%)

Both, Classic recent (reverters)

3,703 (1.5%)

241,883 paid customers with automation signal. CJB-current ARR: $407M. Classic-current ARR: $31.3M.

Paid users WITHOUT automation usage (the bigger ARR lever)

Tier	Users	MRR	ARR
Paid <$299	653,941	$38.22M	$459M
HVC ($299+ MRR)	41,168	$22.60M	$271M
Total paid no-automation	695,109	$60.82M	$730M

74% of paid customers don't use automation. $271M HVC ARR opportunity is bigger than the entire Classic exposure.

Automation usage — Free + Paid (last 365 days)

CJB only

375,386 (91.5%)

Both, CJB recent

13,240 (3.2%)

Classic only

17,001 (4.1%)

Both, Classic recent (reverters)

4,797 (1.2%)

410,424 accounts with automation signal in last 365d (9.3% of 4.43M total external accounts).

Accounts WITHOUT automation usage

Tier	Users	% of tier
Free	3,325,499	95.2%
Paid <$299	653,941	75.7%
HVC ($299+)	41,168	56.2%
Total no-automation	4,020,608	90.7%

Even within HVC, more than half of accounts don't use any form of automation.

The migration is winding down — but unevenly

Monthly first-time CJB users — paid customers (24 months)

Period	Paid <$299 / month	HVC / month	Paid total / month	Read-out
2024 Q3 avg	9,406	1,787	11,193	Steady-state — accounts onboarding into CJB-default world
2025 Q1 avg	8,134	1,228	9,362	HVC drops 31% YoY
2025 Q2 avg	7,338	1,031	8,369	Continued HVC decline
2025 Q4 avg	6,856	722	7,578	HVC down 60% from 2024 baseline
2026 Q1 avg	9,463	832	10,295	Paid<$299 rebounds; HVC stays flat-low
April 2026	12,895	926	13,821	HVC at ~78% decline from peak

Paid HVC migration peaked at 4,265/mo (May 2024) and declined to 926/mo (April 2026). Paid<$299 stable and rebounding — Classic users in this band are still trickling onto CJB.

Monthly first-time CJB users — Free + Paid (24 months)

Period	Free / month	Paid<$299 / month	HVC / month
2024 Q3 avg	6,510	8,739	1,787
2025 Q1 avg	6,990	8,134	1,228
2025 Q2 avg	10,015	7,338	1,031
2025 Q4 avg	9,951	6,856	722
2026 Q1 avg	9,090	9,463	832
April 2026	8,603	12,895	926

The paid HVC migration funnel has been declining for 24 straight months — same pattern as the editor migration, but the cohort that's left is much smaller in absolute terms ($21M vs $281M ARR exposure).

2. Complication — Three things that change the calculus

C1. The residual stayers are uniquely sticky — 28.6% HVC reverter rate

Of HVC paid customers who used both Classic and CJB in the last 365 days, 28.6% have Classic as their more recent action (1,136 of 3,977 HVCs who tried both). For comparison, the editor migration had only an 8–10% revert rate. This cohort isn't just hold-out — they're actively choosing Classic after sampling CJB.

Cohort	Paid users	Median tenure	Median list size	Avg MRR	ARR
CJB-only HVC (typical migrator)	26,753	97 mo	38,928	$668	$214.5M
Both → CJB recent HVC (clean migrator)	2,841	125 mo	49,795	$775	$26.4M
Classic-only HVC (silent stayer)	1,414	124 mo	42,648	$626	$10.6M
Both → Classic recent HVC (reverters)	1,136	125 mo	50,953	$777	$10.6M

The reverters are the highest-value, longest-tenured, largest-list automation users in the entire paid base — and they actively chose Classic after trying CJB. Combined with Classic-only HVCs, the at-risk Classic-current paid HVC pocket is 2,550 users / $1.77M MRR / $21.2M ARR.

C2. The bigger ARR lever isn't migration — it's automation penetration

74% of paid customers don't use automation at all. The HVC slice is the most concentrated opportunity:

695,109

Paid users with no automation in 365d

$730M

Total paid no-automation ARR

$271M

HVC slice (41,168 users) — top conversion target

Reframing: completion vs penetration

Closing the remaining Classic-current $21M HVC ARR is 12.8× smaller than converting just 10% of the no-automation HVCs ($27M). The PM/eng investment that goes into "completing" the migration would deliver more ARR if redirected to CJB-adoption GTM for non-users.

C3. CJB has retention friction the migration data doesn't show

From 18 months of automation VOC analysis (2,937 deduped messages, 104 negative automation feedback items, $177K MRR exposure across HVC), CJB has documented friction points that affect both retention and the no-automation conversion play:

Theme	VOC count	HVC users	MRR exposure	Priority score
Editor / UI glitches in Journey Builder	5	5	$16,507	29
Slow / confusing Journey Builder UX	5	5	$5,205	21
Conversational AI / Generative copy in Journeys	5	5	$6,485	19
Event-property access in flow branches/emails	2	2	$10,000	15
Reporting / stats wrong on automations	5	3	$6,218	15
Automations not sending / delivery failures	3	3	$4,780	12
Time-delay UX inconsistent / restricted	2	2	$7,000	12
Premature 'turn on' / activation before content ready	2	2	$6,000	11
Migration & conversion bugs (Classic → CJB / MA Flows)	2	2	$1,715	10
CJB still uses legacy editor (NEA inside CJB email steps)	2	2	$1,265	9

The CJB-still-uses-legacy-editor theme is a cross-product dependency: completing the email-editor (NEA → NUNI) migration also fixes a CJB friction point. This is one of the few cases where the two migrations are mutually reinforcing.

Verbatim VOC samples (research interview citations)

"Scroll bug in automation canvas prevents scrolling to the top of the flow."UX Research · S2.40 · $5,000 MRR · HVC

"It's not easy to report on automation-specific email metrics... so confusing between classic automation and new automation. A maze."Slack · HVC stayer reason

"Please speed up automations if possible and give us far more customization tools within the automation pathways so we are not forced to figure out workarounds with the customer service team."Slack · automation feature request

"Hello! 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."Slack · CJB legacy-editor coupling

3. The key question

The migration is essentially done at 95% paid CJB adoption. Should we spend the next year forcing the residual 2,550 HVC paid Classic stayers ($21M ARR) onto CJB — knowing the reverter rate is 28.6% and we'd risk meaningful churn — or should we redirect that PM/eng investment to converting the 41,168 HVC paid customers who don't use automation at all ($271M ARR opportunity)?

Sub-questions

Which of the 12K paid Classic stayers can we move safely with a default-flip, and which need a hybrid track?
What CJB defects must be fixed before we ask non-automation HVCs to adopt? (Same defects matter for both.)
What's the right CSM-led GTM for converting non-automation HVCs to CJB? (This is a new motion, not a continuation of an existing one.)
Can we sunset Classic Automations infrastructure within 24 months given a hybrid Phase 3?

4. Recommendation — A 3-phase plan that pivots to growth

Unlike the editor migration (where the remaining $566M ARR demanded a full migration completion), the automations situation calls for a smaller migration play and a much bigger penetration play. The 3-phase plan reflects this asymmetry.

$10M ARR

Phase 1 mitigated (months 0-3, easy migration)

$31M ARR

Cumulative after Phase 2 (months 3-9, all migration done)

$27–$54M ARR

Phase 3 NEW lift (months 9-18, no-automation conversion play)

Phase 1 — Default-flip the easy Classic stayers

Months 0-3Low risk~15K paid users + 8K Free$10M ARR mitigated

Cohort: Classic-only Free (8,433) + Classic-only Paid <$299 (7,154 users / $590K MRR / $7M ARR) + non-HVC reverters (Both Classic-recent Paid<$299: 2,567 users / $251K MRR / $3M ARR). Total addressable: ~18K users / $10M ARR.
Prerequisites (defect-tier — fixable in weeks): (1) Fix CJB editor scroll bug + canvas glitches (top VOC theme). (2) Verify Classic→CJB conversion tooling actually preserves journey content for these simple cases. (3) Reporting accuracy on automation stats (5 VOCs, $6K MRR exposure).
Mechanism: Default-flip on next automation create, with one-click "stay on classic" escape for 30 days. After 30 days, Classic still available via deep link. 60-day rollback option. Auto-port saved Classic flows to CJB equivalents for the simple ones (single-trigger, single-email).
Why it's safe: The Classic-only Paid<$299 cohort has median tenure 101 months but median MRR only $82 — these are smaller-list customers who haven't moved largely from inertia, not power-user lock-in. Reverter rate in Paid<$299 is 26.4% (2,567 / 9,721 of who tried both) — still higher than editor, so the 60-day rollback is mandatory.

Phase 2 — Concierge migration for HVC stayers + reverters

Months 3-9High-stickiness cohort~2.5K HVC users$21M ARR preserved

Cohort: Classic-only HVC (1,414 users / $885K MRR / $10.6M ARR) + reverters HVC (1,136 users / $882K MRR / $10.6M ARR). Combined: 2,550 HVC paid users / $21.2M ARR. These are 10-year-tenured, 50K-list, $700/mo-average automation power users.
Prerequisites (must ship before Phase 2 begins): (1) Time-delay UX consistency + restrictions removed (2 VOCs, $7K MRR) — power-user blocker.
(2) Event-property access in flow branches and emails (2 VOCs, $10K MRR) — segmentation blocker.
(3) Reporting accuracy on automation stats — auditability blocker.
(4) No premature 'turn on' activation states — confidence blocker.
(5) Per-step KPIs viewable in journeys (1 VOC, $5K MRR).
(6) Frequency cap / suppression across flows.
Mechanism: CSM-led, account-by-account migration. Engineer-paired sprint per HVC account (similar to the NEA→NUNI Phase 2 playbook). Replicate top journeys 1:1; customer review before flip. Maintain Classic dual-availability for 90+ days post-migration.
Risk acceptance: Plan for $2-4M ARR at risk if forcing without parity (28.6% reverter rate × $21M ARR = $6M theoretical max; concierge approach should hold loss to $2-4M). The hybrid option (Phase 3 below) mitigates almost all of this.

Phase 3 — Pivot to CJB-adoption GTM (the bigger play)

Months 9-18Net-new ARR opportunity41K HVC non-users targetable$27-54M ARR uplift potential

Cohort: The 41,168 HVC paid customers ($271M ARR) who don't use any automation in last 365d. Median tenure 107 months — long-tenured but never adopted. Plus the 654K Paid<$299 non-automation cohort ($459M ARR) as secondary tier.
Why this is Phase 3, not Phase 1: This cohort is harder to convert than the residual migration cohort: they don't use automation at all, often don't think about it, and selling them on CJB requires a real GTM motion (CSM, ICP-targeted messaging, use-case templates). It's also the highest-leverage spend — even 10% conversion = $27M ARR, 20% = $54M ARR. If we deprioritize this for the sake of completing the migration, we leave $25-50M ARR on the table.
Mechanism (new motion to fund): (1) CSM-led ICP segmentation of 41K HVC non-users by industry / use-case fit.
(2) Use-case-specific journey templates (top requested missing flows from VOC: birthday/profile-update, reply-detection, frequency cap, reactivation).
(3) Concierge journey-build service for top 10% by ARR — first journey free, CSM-led.
(4) Adoption metric integrated into CSM scorecards with quarterly targets.
(5) Hybrid Phase 2 holdouts stay on Classic indefinitely — don't force; let GTM motion bring them organically over 18 months.
What makes this real: The CJB defect fixes from Phases 1+2 (UI glitches, reporting accuracy, time-delay UX, event-property access) directly benefit the no-automation conversion play. Same product investment, two ARR plays. Without the defect fixes, the GTM motion will hit the same friction in onboarding that drove the 28.6% reverter rate.

Cumulative ARR impact by phase

After Phase 1

$10M / $31M migrated

After Phase 2

$31M / $31M migration done

After Phase 3 (10% adoption)

+$27M new ARR

After Phase 3 (20% adoption)

+$54M new ARR

Migration completes in months 0-9 with $31M total ARR resolved. The Phase 3 GTM motion is net-new ARR creation, not migration. At 10% HVC non-user conversion, total program impact = $58M ARR; at 20%, $85M ARR.

Top defects to ship in Q1 (serves both migration and growth plays)

CJB editor / UI glitches — top priority theme (5 VOCs, $16.5K HVC MRR exposure). Includes scroll bug in canvas, panel-blocks-canvas, edit-panel UX.
Reporting accuracy on automations — 5 VOCs, $6.2K MRR exposure. Auditability blocker for HVC.
Premature 'turn on' / activation states — confidence blocker, drives revert risk.
Classic → CJB conversion tooling — explicit migration request from Slack VOC. Without this, Phase 1 default-flip can't auto-port.
Conversational AI / generative copy in journeys — competitive parity (Klaviyo invested heavily in 2025).

Early-warning metric

Phase-1 reverter rate is the gate to Phase 2

Track Phase 1 cohort revert-to-Classic rate over the 60-day window. Above 18% means parity defects haven't actually shipped (the historical 28.6% revert rate among "both"-users is the worst-case ceiling). Hold Phase 2 until the rate stabilizes below 18%. Above 25% = stop; we are recreating the editor migration's late-2024 default-flip mistake at smaller scale.

5. Decision asks

Ask	Owner	Why now
Approve the 3-phase plan with the Phase 3 pivot	VP Email + VP Marketing	Without explicit decision, the default is to keep grinding on migration completion — which leaves $27-54M ARR on the table from the no-automation play
Fund the Q1 CJB defect-fix top-5	Eng leadership	These fixes are the ONLY way to land Phase 1 default-flip without recreating the editor migration's bleed. They also unblock the no-automation conversion play (same product investment, two ARR levers)
Approve the new CJB-adoption GTM motion	VP CSM + VP Product Marketing	41,168 HVC non-users at $271M ARR. New CSM motion — needs targeting model, journey templates, concierge service tier, scorecard integration
Accept hybrid track for the residual ~500-1,000 hardcore Classic stayers	CTO + CFO	Bounded carry cost; preserves $5-10M ARR that would otherwise churn. Far less expensive than the editor migration's hybrid (which protects $281M ARR)
Set sunset target for Classic Automations infrastructure	CTO	Even with Phase 3 hybrid, set 24-month sunset target to align eng capacity. Forces a real conversation with the residual stayers in months 18-24

Answer-by date proposed: end of FY27 Q1, so Phase 1 can begin in Q2.

Issues & Solutions Detail

Every CJB defect and parity gap named in the recommendation, expanded in detail. For each: what is the issue, what job the customer is trying to do, how the issue blocks them (with verbatim VOC), what the solution looks like, what success looks like for the customer, and a From → To visual showing today's broken state vs target state.

16 issues organized by recommendation phase. Severity = the cost of not shipping it before the corresponding migration phase begins. Many of these issues block both the residual migration AND the $271M HVC no-automation conversion play — same eng spend, two ARR levers.

Phase 1 prerequisites — defect tier (ship in Q1)

Ship-blockers for the default-flip on Classic-only Free + Paid<$299. Without them, the 28.6% reverter rate gets even worse.

CJB editor / UI glitches in Journey Builder canvas

Critical Phase 1 5 VOCs · $16,507 MRR · top theme

The single highest-priority CJB defect theme. Scroll bug in the automation canvas prevents scrolling to the top of the flow. Edit panel blocks the flow canvas. Loading spinner misleading on trigger panels. Customers can't navigate complex flows reliably — and complex flows are exactly what HVC users build.

Customer JTBD

"I want to navigate, edit, and review my multi-step automation flow without the canvas fighting me — same way I'd use a Figma board or a Miro canvas."

How it blocks them

Power users abandon CJB mid-build. Reverters cite the canvas friction as a primary reason. The $16,507 MRR exposure on this theme alone is more than half of the total Slack-VOC MRR exposure for automations.

"Scroll bug in automation canvas prevents scrolling to the top of the flow."

Solution

Fix scroll bug in automation canvas (canvas should scroll like Figma/Miro)
Edit panel positioned to never block flow canvas (collapsible side panel, not modal)
Replace misleading loading spinner with proper skeleton states
Pinch-to-zoom + drag-to-pan canvas navigation
Keyboard shortcuts for canvas navigation (space-to-pan, +/- zoom)

Success state

HVC marketer navigates a 20-step journey with confidence. Edit panel doesn't obscure context. Canvas scrolling, panning, zooming all work the way modern design tools work.

Today (broken)

Canvas scroll broken
Edit panel blocks flow view
Spinner shows when nothing's loading
No pan/zoom shortcuts

→

After (fixed)

Canvas scrolls smoothly
Edit panel side-collapsible
Skeleton loaders, accurate state
Pan/zoom/keyboard shortcuts

Reporting / stats accuracy on automations

Critical Phase 1 5 VOCs · $6,218 MRR · auditability blocker

CJB automation stats don't reconcile with what customers see in their data warehouse, in Stripe/Shopify revenue, or even between CJB itself and standalone campaign reporting. Numbers reset to zero, all-time revenue spikes wrong, per-step counts don't match send activity. Auditability is broken.

Customer JTBD

"I want to trust the numbers I see in CJB so I can report ROI to my CFO, optimize my flows, and prove the automation is working."

How it blocks them

Marketers can't defend their automation work in QBRs. They build parallel reporting in Looker / Sheets. Some HVCs use NEA Classic for the reporting confidence even when CJB has better building features.

"Not easy to report on automation specific email metrics... so confusing between classic automation and new automation. A maze."

Solution

Audit + fix the stats pipeline (per-step send count, open, click, revenue)
Single-source-of-truth reporting that matches campaign-level reporting
Real-time vs aggregated reconciliation indicator
Per-flow ROI dashboard tied to attribution model
Eng SLA for stats-accuracy bug class

Success state

Marketer reports CJB-driven revenue in QBR with confidence. Numbers reconcile to Stripe/Shopify. Per-step optimization decisions are based on trustworthy data.

Today (broken)

Stats reset to 0 unexpectedly
All-time revenue glitches
Per-step counts don't match sends
Marketers build shadow reporting

→

After (fixed)

Stable, audited stats pipeline
Reconciles to revenue source
Per-step KPIs trustworthy
Marketers report directly from CJB

Classic → CJB conversion tooling

Critical Phase 1 2 VOCs · $1,715 MRR · explicit ask

Customers cannot easily convert an existing Classic Automation flow into a CJB journey. Migration must be done manually per flow, per email — including journeys with active subscribers in mid-flight. Gating issue for Phase 1 default-flip and for any Phase 2 concierge migration.

Customer JTBD

"I have an existing Classic Automation that's been working for years. I want to upgrade it to CJB without having to rebuild it from scratch — and without breaking the experience for subscribers currently in the flow."

How it blocks them

Long-tenured automation users decline to migrate because the rebuild cost is prohibitive. Subscribers mid-flight get orphaned if the customer rebuilds in CJB — so customers don't migrate at all.

"Hello! It would be nice if there was a way to easily switch the email builder from Classic to New, even in an automation flow. Specifically, if an email was created in a Classic/Legacy builder and you had the option to turn it into an email with the New Builder WITHOUT having to do it manually each time."

Solution

Bulk Classic → CJB conversion tool (preserve trigger, steps, email content, delays)
"Live" migration that preserves mid-flight subscribers (don't drop them)
Side-by-side compare: Classic flow + converted CJB version before commit
Rollback if conversion loses fidelity
Per-account audit report ("here's what will change")

Success state

HVC migrates 8 active automations in one afternoon. Subscribers mid-flight continue without interruption. Numbers reconcile post-migration.

Today (broken)

No bulk conversion tool
Manual rebuild per flow + per email
Mid-flight subscribers get orphaned
HVCs decline to migrate

→

After (fixed)

1-click bulk conversion
Mid-flight subscribers preserved
Side-by-side compare + rollback
HVCs migrate in hours not weeks

Slow / confusing Journey Builder UX

Critical Phase 1 5 VOCs · $5,205 MRR

CJB feels slow and confusing for first-time users and even for experienced ones. Trigger selection list isn't searchable. Loading spinners misleading. Jargon-heavy trigger/condition labels. Multi-trigger type mismatch confusing. Email editing has unnecessary intermediate clicks.

Customer JTBD

"I want to set up a basic automation (welcome series, abandoned cart) in 10 minutes — not 60 — without needing to read documentation."

How it blocks them

This is the #1 reason non-automation HVCs (the $271M ARR opportunity) don't adopt CJB even when they want to. The cognitive load of figuring out CJB is higher than the perceived value of automating their first flow.

"Please speed up automations if possible and give us far more customization tools within the automation pathways so we are not forced to figure out workarounds with the customer service team."

Solution

Searchable trigger selection list
Plain-English labels (not internal jargon) for triggers and conditions
One-click email editing (remove intermediate clicks)
"Build a welcome series in 60 seconds" template-first onboarding
Performance audit + speed-up of canvas + panel rendering

Success state

First-time CJB user builds a welcome series in 5 minutes. Triggers are searchable and self-explanatory. Canvas feels responsive. CSM-led onboarding doesn't need 30-min walkthroughs.

Today (broken)

Trigger list not searchable
Jargon-heavy labels
Extra clicks to edit emails
First flow takes 60+ minutes

→

After (fixed)

Searchable trigger picker
Plain-English labels
Inline email editing
First flow in 5–10 minutes

Phase 2 prerequisites — structural parity (ship months 3-9)

Power-user blockers for the HVC concierge nudge. Without them, the 2,550 HVC paid Classic stayers ($21.2M ARR) cannot move.

Time-delay UX inconsistent / restricted

High Phase 2 2 VOCs · $7,000 MRR · power-user blocker

Wait/delay steps in CJB don't behave consistently — different patterns in different parts of the flow, with arbitrary restrictions. "Wait for trigger" rule pass-through behavior is confusing. Calculated send day visibility (Day 0 / Day 1) is hidden. Date-relative / recurring / event-based triggers are limited.

Customer JTBD

"I want to design precise time-based logic in my automation — wait 3 days, send on a specific weekday, throttle to send-time-optimization windows — and have it behave the way I expect."

How it blocks them

Sophisticated marketers can't replicate their Classic Automation timing logic in CJB. They stay on Classic for the precision even though they prefer CJB for everything else.

Solution

Consistent time-delay UX across all wait-step types
Numeric input for delays (not just slider)
Date-relative + recurring + event-based trigger types
Visible "calculated send day" (Day 0 / Day 1) in flow preview
Wait-for-trigger pass-through clarity ("if X happens within N days...")

Success state

HVC marketer designs a complex post-purchase journey with precise time logic in 30 minutes. Calculated send day is visible. Recurring triggers (e.g., birthday) work natively.

Today (broken)

Inconsistent delay UX
Slider-only, no numeric input
Recurring/date-relative limited
Hidden calculated send day

→

After (fixed)

Consistent delay UX
Numeric + slider input
Date/recurring/event triggers
Visible send-day calculation

Event-property access in flow branches and emails

High Phase 2 2 VOCs · $10,000 MRR · segmentation blocker

Cannot access event properties (cart total, product names, custom event data) inside flow branch conditions or email merge tags. This is the #1 segmentation blocker for ecommerce HVCs — the highest single MRR exposure on the automation VOC list.

Customer JTBD

"When a customer triggers an event (added to cart, viewed product, completed purchase), I want to use the event's properties (cart total, product, category) to branch the flow and personalize the email content."

How it blocks them

Ecommerce automation that depends on cart value, product type, or order recency cannot be built in CJB. Marketers run abandoned cart sequences in Klaviyo because Klaviyo supports event properties natively.

Solution

Event-property merge tags in email content (e.g., {{ event.cart.total }})
Event-property conditions in flow branches (e.g., "if cart total > $100")
Event-property visibility in flow preview
Event-property segmentation in audience filters
Custom event property registry per account

Success state

Ecommerce HVC builds an abandoned-cart flow that branches on cart value, personalizes the email with cart products, and routes high-value carts to a CSM-alert path — all in CJB, all without code.

Today (broken)

No event-property merge tags
Branches can't read event data
Ecomm HVCs migrate to Klaviyo

→

After (fixed)

Event-property merge tags + conditions
Cart-value branching native
Mailchimp competitive on ecomm

Premature 'Turn On' / activation before content ready

High Phase 2 2 VOCs · $6,000 MRR · confidence blocker

CJB allows journeys to be activated even when content is not ready (empty email steps, missing trigger criteria, broken merge tags). Customers turn on a journey to test, real subscribers enter, and bad emails (or no emails) get sent. Trust-killer.

Customer JTBD

"I want to safely test my journey end-to-end before real subscribers enter — without risking bad emails going out to my list."

How it blocks them

Customers experience send disasters from premature activation. They develop fear-driven workflows (build entire flow in test mode, never deploy). Some abandon CJB after a single bad-send incident.

Solution

Pre-activation checklist (every step must pass: content present, merge tags valid, trigger configured, audience selected)
Test mode that simulates entry without affecting real subscribers
"Activate for X% of subscribers" canary deploy option
Clear activation states (Draft / Test / Live / Paused)
Block activation if any step is incomplete

Success state

Marketer builds a journey in Draft, runs it through Test mode (simulated subscribers), reviews emails, then promotes to Live with full confidence. Pre-activation checklist catches the "empty email step" before real users hit it.

Today (broken)

Activation allowed with empty steps
Real subscribers receive bad emails
Fear-driven workflows develop

→

After (fixed)

Pre-activation checklist gates activation
Test mode + canary deploy
Clear Draft / Test / Live states

Per-step KPIs / performance not viewable in journeys

High Phase 2 1 VOC · $5,098 MRR

CJB doesn't surface per-step performance KPIs (open rate, click rate, drop-off, conversion) inline on the canvas. Marketers can't see at a glance which step in a 10-step journey is the conversion bottleneck. Aggregate reporting across journeys is also missing/painful.

Customer JTBD

"I want to look at my journey and immediately see which step is performing well, which is dropping subscribers, and where I should optimize."

How it blocks them

Optimization is blind. Marketers either don't optimize or build their own analytics in Looker. CSM teams can't deliver "automation health" insights from CJB alone.

Solution

Per-step KPI overlay on canvas (open / click / unsub / drop-off)
Conversion funnel visualization across the journey
"Drop-off heatmap" — which step loses the most subscribers
Aggregate reporting across journeys (compare flow A vs B)
Per-flow send timing visibility (when subscribers exit)

Success state

Marketer opens CJB, sees per-step open/click/conversion, identifies the weakest step in 30 seconds, A/B-tests an alternative. Aggregate flow comparison drives roadmap prioritization.

Today (broken)

No per-step KPIs on canvas
Aggregate journey reporting missing
Optimization is blind

→

After (fixed)

KPI overlay on every step
Drop-off heatmap visible
Aggregate reporting across journeys

No frequency cap / suppression across flows

High Phase 2 2 VOCs · $2,576 MRR

Subscribers can be enrolled in multiple journeys simultaneously and receive overlapping emails. There's no global frequency cap or cross-flow suppression rule. Marketers worried about over-mailing limit themselves to one journey at a time.

Customer JTBD

"I want to run multiple journeys simultaneously (welcome + nurture + promo + winback) without subscribers receiving 8 emails a week from us."

How it blocks them

HVCs limit themselves to one or two journeys to avoid over-mailing. The product is artificially constrained. Subscribers get fatigued and unsubscribe.

Solution

Account-level frequency cap (e.g., max 3 emails per subscriber per week)
Per-flow suppression rules ("don't enroll if subscriber is in flow X")
Cross-channel frequency cap (email + SMS combined)
Smart-suppression by category (transactional vs marketing)
Frequency dashboard showing current send pressure per subscriber

Success state

HVC runs 6 simultaneous journeys with a 3-email/week cap. Subscribers receive a balanced experience. Unsubscribe rate drops while program revenue grows.

Today (broken)

No frequency cap
Subscribers in multiple flows over-mailed
HVCs limit themselves to 1-2 flows

→

After (fixed)

Account-level cap + per-flow suppression
Cross-channel frequency control
HVCs run 6+ journeys safely

Phase 3 prerequisites — platform tier (ship months 9-18, unlock GTM growth motion)

These unlock the no-automation HVC conversion play ($271M ARR opportunity). The same defects that block existing CJB users will block new adopters.

Conversational AI / generative copy in journeys

Platform Phase 3 5 VOCs · $6,485 MRR · competitive parity

CJB has limited AI capabilities for journey email content. Klaviyo, Brevo, and ActiveCampaign all shipped generative AI in 2025 — better subject line generation, email body generation, brand-aware copy. Mailchimp's AI story for journeys lags. Multi-trigger type mismatch and B2B / sophisticated use-case inadequacy compound this.

Customer JTBD

"I want AI to help me write better journey emails — generate variations, optimize subject lines, adapt to recipient context — without me being a copywriter."

How it blocks them

SMB marketers without copywriters use Klaviyo's AI to scale journey content. Mailchimp loses on AI in head-to-head deals. The 41K HVC non-automation users especially won't adopt CJB without AI assistance — they don't have time to write 8 journey emails by hand.

Solution

Generative AI for journey email body content (brand-aware)
Subject line + preview text variant generation
"Convert this Classic flow to CJB and optimize the copy" AI assist
Conversational journey builder ("build a 5-email welcome series for a yoga studio")
Per-segment personalized content variants

Success state

SMB customer describes their goal in natural language; AI generates a complete journey draft with on-brand copy. Marketer reviews, edits, ships. Mailchimp matches or exceeds Klaviyo on AI in 2026 reviews.

Today (broken)

Limited AI for journey content
Klaviyo/Brevo lead on AI
SMBs without copywriters can't scale

→

After (fixed)

Generative AI for journey copy
Conversational builder
Mailchimp leads on AI

CJB still uses legacy editor (NEA inside CJB email steps)

Platform Phase 3 · cross-product 2 VOCs · $1,265 MRR

When you edit an email step inside a CJB journey, the editor that opens is still NEA (the legacy email editor) for many account configurations. This means CJB customers can't get the benefits of NUNI within their journeys, and journey emails are subject to all 16 NEA→NUNI editor issues. Cross-product dependency.

Customer JTBD

"I want my journey emails to use the same modern editor I use for one-shot campaigns — same brand kit, same controls, same experience."

How it blocks them

Customers see two editors in the same product, get confused, lose brand consistency. Brand kit changes don't apply to journey emails because they're rendered via NEA. Completing the editor migration is a prerequisite for CJB to feel coherent.

Solution

Replace NEA with NUNI inside CJB email steps
Same brand kit, font palette, color palette as standalone NUNI
Migration tooling that converts in-flight journey emails to NUNI
Coordinate with Editor Migration Phase 2 timing

Success state

One editor (NUNI) across the entire product. Brand kit applies everywhere. Journey emails get all the NUNI improvements automatically.

Today (broken)

NEA opens inside CJB journey emails
Two editors confuse customers
Brand kit doesn't apply to journeys

→

After (fixed)

NUNI everywhere, including CJB steps
Single coherent editor experience
Brand kit universal

Cannot rename automations or steps from canvas

Platform Phase 3 2 VOCs · $2,000 MRR · UX papercut

Steps in CJB can't be renamed inline from the canvas. Renaming a journey requires going to a settings page. For multi-step journeys, identifying which step is which (without good names) becomes a memory game.

Customer JTBD

"I want to give every step in my journey a clear name (e.g., 'Welcome email', 'Day-3 nurture', 'Cart-recovery 1') so my team can collaborate on it."

How it blocks them

Team collaboration breaks down. CSMs can't review flows efficiently. Steps look identical on the canvas — "Send Email" × 8 with no distinguishing labels.

Solution

Inline rename of any step (double-click on canvas)
Inline rename of journey title from canvas header
Step naming auto-suggestion (based on email subject line)
Search journeys by step name

Success state

Marketer names every step inline as they build. Team reviews journeys with clear context. CSMs onboard new clients faster because journey structure is self-documenting.

Today (broken)

Steps can't be renamed from canvas
"Send Email × 8" identical labels
Team collaboration breaks down

→

After (fixed)

Inline double-click rename
Auto-suggested names
Self-documenting journeys

Default view / sort order broken in campaigns + automations

Platform Phase 3 2 VOCs · $2,925 MRR

The default view and sort order of automations + campaigns lists keeps changing or doesn't respect what users set. Marketers' workflows depend on knowing where things are.

Customer JTBD

"I want my automations list to remember how I sort and filter it — by last-modified, by name, by status — so I can find what I need quickly."

How it blocks them

Daily friction. Marketers re-sort the same way every login. Power users open multiple tabs to keep state. CSMs can't establish reliable workflows.

Solution

Persist sort + filter state per user (account-level)
"Saved views" for common filter combinations
Default view configurable per account
Stable sort across page refreshes

Success state

Marketer logs in, automations list opens in their last-used sort + filter. Saved views for "Active flows", "Drafts", "Last edited this week" are one click.

Today (broken)

Sort resets on every login
No saved views
Daily friction

→

After (fixed)

Per-user persistent sort + filter
Saved views
Configurable default view

Sharing / export / permissions on flow reports

Platform Phase 3 2 VOCs · $2,808 MRR

Cannot share or export CJB flow reports cleanly to non-Mailchimp users (e.g., agency clients, internal stakeholders, executives). No granular permissions on flow reports — read-only access to a single flow isn't possible.

Customer JTBD

"I want to share a beautiful, branded flow report with my client (or my CMO) without giving them full account access."

How it blocks them

Agencies build their own client reports in Looker / Sheets. Marketers screenshot CJB and paste into decks. Time spent reproducing reports is time not spent optimizing.

Solution

Branded PDF / image export of flow reports
Shareable read-only links per flow (with expiry)
Granular permissions: view-only role for specific flows
Email-on-schedule digest (weekly flow performance)

Success state

Agency emails a branded weekly flow report to each client automatically. Marketer shares a CJB read-only link with their CMO; CMO sees the report without a Mailchimp account.

Today (broken)

No branded export
No shareable read-only links
Permissions are all-or-nothing

→

After (fixed)

Branded PDF / image export
Shareable read-only links
Per-flow view-only permissions

Cross-cutting — applies across all phases

Delivery reliability + send-timing visibility. These touch every customer using any flow.

Automations not sending / delivery failures

Critical All phases 3 VOCs · $4,780 MRR · most catastrophic class

Automations stop sending without notice. Customers find out from subscribers asking "did you stop sending us your newsletter?" — by which time days or weeks of expected emails have been missed. The most catastrophic defect class because it's silent.

Customer JTBD

"I want to set up an automation and trust that it keeps sending — and if anything goes wrong, I want to know immediately, not from a customer complaint."

How it blocks them

Customers lose revenue (abandoned cart not sending) and trust (welcome series silently broken). They build external monitoring (third-party tools, scheduled checks). Some HVCs reduce automation reliance because they can't trust delivery.

Solution

Real-time delivery health monitoring per flow
Proactive alert when a flow stops sending (email + Slack to account owner)
"Last successful send" timestamp visible on every active flow
Auto-pause of broken flows with diagnostic message (not silent failure)
Eng SLA for delivery-failure bug class

Success state

Customer is alerted within 15 minutes if a flow stops sending. Diagnostic shows the cause. Trust in automation reliability matches trust in standalone campaigns.

Today (broken)

Silent delivery failures
Customer learns from subscribers
External monitoring required

→

After (fixed)

Real-time delivery alerts
"Last sent" visible per flow
Auto-pause + diagnostic on failure

Per-flow send timing & granular reports

Cross-cutting All phases 2 VOCs · $676 MRR

Marketers can't see precise per-flow send timing — when a subscriber actually receives each step's email — or get granular per-step reports tied to send-time-optimization windows. Combined with the per-step KPI gap (#8), this means optimizing send timing is impossible.

Customer JTBD

"I want to know exactly when each subscriber receives each step in my journey, and I want to optimize for the best send-time per audience segment."

How it blocks them

Send-time optimization is hidden. Per-flow timing analysis requires building external dashboards. HVCs running multiple journeys can't compare timing performance across them.

Solution

Per-step send-timing visibility (when each subscriber received each email)
Per-flow STO recommendations
Date picker / date-range UI for flow reports (currently painful)
Aggregate timing comparison across flows

Success state

Marketer sees per-step timing visualization. Adjusts STO settings based on actual data. Compares timing across journeys to find best-performing windows.

Today (broken)

No per-step timing visibility
Painful date picker
Cross-flow timing comparison missing

→

After (fixed)

Per-step timing visualization
Modern date picker
Cross-flow timing dashboard

Reading this section as a roadmap input

The 16 issues above are organized by the migration phase that depends on them. Phase 1 (4 issues) gates the safe default-flip on Classic-only stayers. Phase 2 (5 issues) gates the HVC concierge migration. Phase 3 (5 issues) unlocks the $271M ARR no-automation HVC conversion play — the same defects that block migration also block new adoption. Cross-cutting (15+16) should be in flight from day one. Total estimated eng investment: a focused 3-quarter program for ~4-6 engineers across CJB editor, reporting pipeline, and conversion-tooling teams. Smaller than the editor migration's investment because the cohort is smaller — but the ARR uplift potential is similar ($31M migration + $27-54M GTM growth).

Appendix

A. Methodology & data sources

Tables queried

bi_marketing.lcm_marketing_account_base (pipeline date 2026-05-11) — plan, MRR, country, ecomm level, tenure
bi_activities.users_activities — automation events over 24mo (see definitions below)
mc-automation-voc/analysis.json — 18-month VOC analysis (2,937 deduped messages, 104 negative automation feedback, $177K MRR exposure)

Classification rules

Classic Automations — events: parent email_automation create/publish/pause/test, child email_automation create/publish/pause
CJB (Customer Journey Builder) — events: customer_journey_builder create/start/pause/restart/delete, email-touchpoint email create/publish
Lookback window for "current usage" classification: 365 days from snapshot date
Segments derived per user:
- Classic only: any Classic event in 365d, no CJB event
- CJB only: any CJB event in 365d, no Classic event
- Both, CJB recent: both in 365d, CJB date ≥ Classic date (migrators)
- Both, Classic recent: both in 365d, Classic date > CJB date (reverters)
- No automation: no automation event in 365d

Caveats

This briefing uses a 365-day "current usage" window. A longer lookback would catch more historical Classic users; we're scoping to "still active in last year" because that's the actionable cohort.
The "no automation" 695K paid cohort is a snapshot — some may have used automation in the 1-3 year prior. The conversion-opportunity number is therefore a ceiling.
VOC themes are from the existing R&A automation VOC analysis (18-month window through May 2026). Editor-migration VOC analysis is a separate dataset.

B. Data quality cross-checks

Check	Value	Result
Total external accounts (most recent pipeline)	4,431,032	OK
Accounts with any automation signal in 365d	410,424 (9.3%)	OK
Paid accounts (MRR > 0)	936,992	OK
Paid accounts with automation signal in 365d	241,883 (25.8% of paid)	OK
Paid Classic-current sum (Classic only + Both Classic recent)	12,271 / $2.61M MRR	$31.3M ARR ✓
Paid CJB-current sum (CJB only + Both CJB recent)	229,612 / $33.92M MRR	$407M ARR ✓
HVC paid Classic-current	2,550 / $1.77M MRR	$21.2M ARR ✓
HVC paid who tried both Classic+CJB in 365d	3,977 (2,841 + 1,136)	OK
HVC paid reverters / total who tried both	1,136 / 3,977	28.6% revert rate ✓
Paid no-automation total	695,109 / $60.82M MRR	$729.8M ARR ✓
Paid HVC no-automation	41,168 / $22.6M MRR	$271.2M ARR ✓

C. Migration trend — paid customers (full 24-month table)

Month	Paid <$299	HVC	Paid total
2024-05	13,799	4,265	18,064
2024-06	10,940	2,709	13,649
2024-07	9,471	2,109	11,580
2024-08	8,517	1,690	10,207
2024-09	8,229	1,561	9,790
2024-10	8,609	1,594	10,203
2024-11	7,938	1,281	9,219
2024-12	5,547	795	6,342
2025-01	8,744	1,313	10,057
2025-02	7,752	1,212	8,964
2025-03	7,905	1,159	9,064
2025-04	7,600	1,060	8,660
2025-05	7,355	1,053	8,408
2025-06	7,059	980	8,039
2025-07	6,950	958	7,908
2025-08	6,658	801	7,459
2025-09	7,298	855	8,153
2025-10	7,414	887	8,301
2025-11	6,954	674	7,628
2025-12	6,199	603	6,802
2026-01	7,937	725	8,662
2026-02	8,053	779	8,832
2026-03	12,399	992	13,391
2026-04	12,895	926	13,821

HVC paid migration declined from 4,265 (May 2024) to 926 (April 2026) — 78.3% decline. Paid<$299 declined more shallowly and rebounded in 2026 Q1.

D. Profile by automation segment (paid only, full detail)

Segment	Tier	Users	MRR	ARR	Avg MRR	Median tenure	Median list
Classic only	Paid<299	7,154	$590K	$7.1M	$83	101 mo	2,487
Classic only	HVC	1,414	$886K	$10.6M	$626	124 mo	42,648
CJB only	Paid<299	192,778	$13.16M	$157.9M	$68	43 mo	1,334
CJB only	HVC	26,753	$17.88M	$214.5M	$668	97 mo	38,928
Both, CJB recent	Paid<299	7,240	$679K	$8.1M	$94	98 mo	2,976
Both, CJB recent	HVC	2,841	$2.20M	$26.4M	$775	125 mo	49,795
Both, Classic recent (reverters)	Paid<299	2,567	$251K	$3.0M	$98	107 mo	3,606
Both, Classic recent (reverters)	HVC	1,136	$882K	$10.6M	$777	125 mo	50,953
No automation	Paid<299	653,941	$38.22M	$458.7M	$58	59 mo	1,183
No automation	HVC	41,168	$22.60M	$271.2M	$549	107 mo	32,970

The "Both, Classic recent" HVC reverter cohort has the highest avg MRR ($777), longest tenure (125 mo), and largest median list (50,953) in the entire paid base. They actively chose Classic after sampling CJB.

E. CJB VOC themes (full table from automation VOC analysis)

From mc-automation-voc/analysis.json — 2,937 deduped messages over 18 months, 104 negative automation feedback items, $177K total MRR exposure across HVC.

Theme	VOCs	HVC	MRR exposure
Editor / UI Glitches in Journey Builder	5	5	$16,507
Slow / Confusing Journey Builder UX	5	5	$5,205
Conversational AI / Generative Copy in Journeys	5	5	$6,485
Reporting / Stats Wrong on Automations	5	3	$6,218
Automations Not Sending / Delivery Failures	3	3	$4,780
Other Barriers / UX Friction	3	3	$1,761
Event-Property Access in Flow Branches/Emails	2	2	$10,000
Time Delay UX Inconsistent / Restricted	2	2	$7,000
Premature 'Turn On' / Activation Before Content Ready	2	2	$6,000
Default View / Sort Order Broken	2	2	$2,925
Sharing / Export / Permissions on Flow Reports	2	2	$2,808
No Frequency Cap / Suppression Across Flows	2	2	$2,576
Migration & Conversion Bugs (Classic → CJB)	2	2	$1,715
CJB Still Uses Legacy Editor	2	2	$1,265
Cannot Rename Automations or Steps from Canvas	2	2	$2,000
Per-Flow Send Timing & Granular Reports	2	2	$676
Other Missing Features (combined long-tail)	~50	~48	$80,000+

F. Comparison to NEA → NUNI editor migration

Metric	Editor (NEA → NUNI)	Automation (Classic → CJB)
New tool adoption (paid)	58.1%	95.0%
Old tool stayer count (paid)	384,261	12,271
Old tool stayer ARR (paid)	$566M	$31.3M
HVC stayer count (paid)	38,145	2,550
HVC stayer ARR (paid)	$281M	$21.2M
Reverter rate (HVC)	8–10%	28.6% (3× higher)
Median stayer tenure	118 mo (~10 yrs)	124–125 mo (~10.4 yrs)
Median stayer list size	37,251	42,648–50,953
VOC volume (24mo)	1,551 editor-related	104 automation-negative
CES delta (new vs old)	−0.10 (3.90 vs 4.00)	Not measured
Bigger ARR opportunity	Migration completion	No-automation conversion ($271M HVC)

Read these as siblings: same product migration pattern, different scale, different recommendation. Editor needs migration completion playbook. Automation needs migration cleanup + GTM pivot.

G. The CJB-adoption GTM math (Phase 3)

Target cohort sizing

Tier	Non-automation users	ARR	% of tier
Free	3,325,499	$0	95.2%
Paid <$299	653,941	$459M	75.7%
HVC ($299+)	41,168	$271M	56.2%

Conversion sensitivity

HVC conversion rate	HVCs converted	Direct ARR uplift	+ retention uplift (10% lower churn)
5%	2,058	$13.5M	+$2.7M = $16.2M
10% (baseline target)	4,117	$27.1M	+$5.4M = $32.5M
15%	6,175	$40.7M	+$8.1M = $48.8M
20%	8,234	$54.2M	+$10.8M = $65M

Retention uplift assumes automation-active accounts churn at ~10% lower rate (industry benchmark — verify with our own retention data). Even at conservative 5% conversion, the GTM motion delivers $13M ARR — half the size of the entire Classic-current cohort.

H. Stayer profile cross-cuts (Classic-only paid + reverters)

Combined Classic-current paid (12,271 users / $31.3M ARR)

Tier	Users	MRR	ARR	Median tenure
Paid <$299 — Classic only	7,154	$590K	$7.08M	101 mo
Paid <$299 — Reverters	2,567	$251K	$3.02M	107 mo
HVC — Classic only	1,414	$886K	$10.63M	124 mo
HVC — Reverters	1,136	$882K	$10.59M	125 mo
Total	12,271	$2.61M	$31.32M	—

All four cohorts have median tenure 100+ months. The HVC slices have median list size 42,648 (Classic only) and 50,953 (reverters) — they are not casual users.