Ask buyers who run email what they'd tell their past self and the answers cluster tightly: price it against a year of list growth, treat deliverability as a practice you own, buy for the team you actually have, don't expect the reporting to reach revenue on its own, read the fine print on the "all-in-one" promise, and respect how much a switch really costs. The channel earns its keep; the regrets are all about how it's bought and run. Here they are, in the order buyers hit them — for the money specifically, see what buyers actually pay for an email platform at scale; for the exit, why companies switch email platforms; the strategic cousins are our read on why buyers leave Salesforce Marketing Cloud and the companion buyer-truth pieces on CDPs and SMS.
The seven lessons
The bill scales with your list, not your results — read the pricing dimension
Cost is the most repeated complaint in the corpus, and it's structural: most ESPs price on contacts stored, so you pay for the whole database — dormant cohorts included — and the number climbs as the list grows rather than as revenue does. Buyers describe paying "for the total list size even when audiences aren't engaged," and platforms that become "expensive as the scale of contacts increases." At the enterprise end the pattern repeats as add-ons and services surfacing at renewal — one global cosmetics manufacturer keeps its platform but calls the total cost of ownership hard to justify. The buyers who avoid the surprise price the contract against a year of list growth and sending, and prune unengaged contacts before they renew.
Named in this context: Klaviyo · Mailchimp · Braze · Salesforce Marketing Cloud
Deliverability is a discipline you own — not a feature the ESP delivers
The lesson buyers learn late: inbox placement depends on your sender reputation, list hygiene, and authentication — the platform enables them but doesn't run them for you. So buyers keep bolting dedicated deliverability and rendering monitors onto the stack — Validity, Litmus, and Inbox Monster are the names that recur — precisely because the ESP alone won't tell them what's actually landing. A global hotel group replacing two legacy enterprise tools framed its entire selection around "better deliverability at scale" and fixing list churn. Ask any vendor how it handles reputation warm-up and list hygiene before you sign — and plan for a temporary deliverability dip every time you migrate.
Named in this context: Validity · Litmus · Inbox Monster · SendGrid · Acoustic
Buy for the team you have — ease-of-use and power pull in opposite directions
Every buyer sits somewhere on one fork. The simple tools are loved for exactly that — non-technical marketers get going fast — but buyers report they cap out: one found its platform "not user-friendly for team members without HTML coding skills," complicated and time-consuming to manage at any depth. The powerful tools invert it: a global cosmetics manufacturer rates Braze an 8 with the caveat that "if you have the proper dev team, you can do whatever you want" — and a steep learning curve if you don't. Neither is wrong; the mismatch is. Put your least technical marketer in the demo and have them build a real campaign unassisted before you decide.
Named in this context: Mailchimp · Braze · Klaviyo (automation "not as polished" for larger orgs)
The reporting won't reach revenue on its own
Buyers consistently hit a ceiling connecting email activity to money. One rates its platform's analytics as simply not robust enough — "lacking detailed analytics to track campaigns effectively"; another flags weak reporting on conversion rates and sales attribution specifically. Even buyers who like their ESP say they wanted "deeper data and better attribution" than it gave them, and go shopping for a point solution to fill the gap. Treat native reporting as opens-and-clicks table stakes, and confirm — before signing — exactly how the platform ties a send to a downstream conversion, and whether that survives contact with your warehouse and analytics stack.
Named in this context: Mailchimp · Klaviyo
The "one platform for every channel" promise is thinner than the demo
Consolidating email, SMS, and push into a single tool is the pitch buyers most want to believe — and the one they most often find hollow at the edges. Klaviyo is praised as a holistic email-and-SMS platform, then flagged for SMS that "lacks compared to competitors like Postscript and Attentive." A journey-orchestration buyer hit a wall when its platform offered no RCS support. The bundled channel is usually real but shallow: good enough until that channel becomes central to revenue, at which point buyers add a specialist. Decide which channels are core, and test those specifically — don't let a strong email demo sell you a weak SMS module.
Named in this context: Klaviyo · Iterable · Postscript · Attentive
Segmentation and automation hit manual limits sooner than you think
The feature that sold the platform is often the one buyers outgrow first. Even at the powerful end, buyers describe "a noted reliance on manual processes" that restricts spinning up targeted campaigns on the fly, and a lack of the advanced automation the platform was bought for. Others report having to rebuild the same emails for different geographies because the flows don't flex. The through-line: demos show a clean segment built once; production is a hundred variants maintained forever. In the proof-of-concept, build the messiest real audience you have — the multi-condition, multi-region, frequently-changing one — not the vendor's tidy example.
Named in this context: Braze · Klaviyo · Iterable
Switching ESPs is brutal — budget for flows, reputation, and list churn
The exit is harder than the entrance. A move means rebuilding every automation and template, re-warming sender reputation from zero, and absorbing list churn in the transfer — and the payoff lags. A heritage apparel group that consolidated onto Klaviyo from a prior ESP told us that months in, it still hadn't seen comparable performance. A multi-brand restaurant group rating its incumbent a 6 spent months circling Braze and Iterable before moving. Because switching is expensive, the winning move is often to fix the operating model first — ownership, data hygiene, deliverability practice — and replatform only when the tool is genuinely the constraint, not the scapegoat.
Named in this context: Klaviyo · Listrak · Braze · Iterable · Mailchimp
How buyers rate the platforms
The ratings tell the same story as the lessons: the independent, marketer-friendly tools lead, the all-in-ones cluster just behind, and the legacy enterprise suites — the ones that cost the most and lean hardest on engineers — anchor the bottom.
| Platform | Buyer rating | What buyers say |
|---|---|---|
| 8.3 | Automation depth at a mid-market price; the corpus favorite for teams that have outgrown the simple tools. Rated on a smaller sample than the incumbents. | |
| 7.6 | The e-commerce default and by far the most-rated ESP here — strong segmentation and Shopify integration. Priced by list size; its SMS trails the specialists. | |
| 7.5 | Enterprise-grade cross-channel orchestration; deeply customizable. The recurring cost: it needs a skilled dev team, and buyers call it "very expensive." | |
| 7.4 | All-in-one convenience for teams already living in the CRM; email is one strong module among many. Less specialized than a dedicated ESP at high volume. | |
| 7.3 | The easiest on-ramp for small teams and the most cost-effective at low volume. Reporting and customization thin out as you scale, and list-size pricing bites. | |
| 7.1 | Clean journey orchestration and well-regarded support. Buyers flag clunky data and Shopify integrations, and gaps in SMS/RCS on the messaging side. | |
| 6.9 | The B2B lead-nurture workhorse, now inside Adobe. Capable at scale, but a dated interface and complexity weigh on satisfaction. | |
| 6.8 | Enterprise reach inside the Salesforce estate. The corpus's classic complaint: it costs too much and marketers can't run it without engineers. | |
| 6.2 | Deep enterprise capability for cross-channel campaigns; heavy to implement and integrate, and buyers cite integration friction most. | |
| 5.9 | Legacy enterprise scale and reliability, dragged down by an aging platform and low day-to-day satisfaction — a frequent source of exit conversations. | |
| 5.5 | Pitches a unified suite, but lands lowest of this set in the corpus — buyers report the breadth doesn't translate into day-to-day satisfaction. |
The stories behind the lessons
The counter-current: the platform is rarely the whole problem
The satisfied buyers in the corpus look different before the contract, not after it. They picked for the team they actually have — marketers who need self-serve, or engineers who want control — treated deliverability and list hygiene as their own standing practice, and priced the growth curve honestly. The unhappy buyers' complaints — can't self-serve, cost surprises, weak reporting, poor inbox placement — tend to follow them to the next platform. The lessons above are cheap insurance; a migration is not.
What this means for your ESP evaluation
Five checks before you write the RFP. First, price the growth curve, not the sticker: model a year of list growth and sending, and read exactly which dimension you're billed on. Second, make deliverability a scored test — ask how the vendor handles reputation warm-up, list hygiene, and authentication, and who owns inbox placement after you sign. Third, put your least technical marketer in the demo and have them build a real campaign unassisted. Fourth, confirm how a send ties to a downstream conversion before you believe the reporting. Fifth, if any channel beyond email is core to revenue, test that channel specifically — the bundle is usually shallower than the pitch. And if you're switching, budget for the flows, the reputation reset, and the list churn — then make sure the tool, not the operating model, is the thing you're actually replacing.
For specific head-to-heads, see Klaviyo vs. Iterable and Iterable vs. Bloomreach.
Common questions
Why can't my marketers run our email platform without engineers?
Because the platform sits on the wrong side of the ease-versus-power fork for your team. The most powerful tools — Braze, Salesforce Marketing Cloud — draw consistent "needs a skilled dev team" complaints, while the simplest tools are easy to run but cap out as you scale. Put your least technical marketer in the demo and have them build a real campaign unassisted before you buy — if sending a segment takes an engineering ticket, the capability you're paying for won't convert to output. (What those platforms cost and why buyers leave them get their own reads: pricing at scale and why companies switch.)
Why are my marketing emails going to spam instead of the inbox?
Because deliverability is a discipline you own, not a feature the ESP guarantees. Inbox placement depends on your sender reputation, list hygiene, and authentication — the platform enables them but doesn't run them for you. Buyers routinely bolt on dedicated deliverability and rendering monitors (Validity, Litmus, Inbox Monster recur) precisely because the ESP alone doesn't tell them what's landing. Ask any vendor how it handles reputation warm-up and list hygiene, and expect a temporary dip whenever you migrate.
Should I run email in my all-in-one platform or a dedicated ESP?
It depends on how central email is to revenue and the team you have. Bundling into an all-in-one — HubSpot for teams living in the CRM, Klaviyo for Shopify e-commerce — wins on simplicity and shared data. A dedicated or enterprise tool wins on depth, at the cost of complexity: Braze and Salesforce Marketing Cloud are powerful but draw consistent "needs a dev team" complaints, while the simplest tools cap out as you scale. Match the platform to who will operate it, not to the longest feature list.
Can I trust my email platform's reporting to show what email actually earns?
Only up to a point — connecting email to revenue is where buyers consistently hit a ceiling. They describe native analytics that stop at opens and clicks, reporting too thin to track conversion and sales attribution, and a recurring wish for deeper data and better attribution. Confirm exactly how the platform ties a send to a downstream conversion before you sign — and whether that survives contact with your warehouse, or whether you'll buy a separate tool to close the gap.
This is the aggregate. Your stack is specific.
Evaluating an email platform right now? Do a 15-minute interview about your own stack and get this analysis personalized — what peers in your category rate the tools you're weighing, which lessons apply to your shortlist, and where the migration math actually lands.
Get my personalized briefNo password needed · your interview is anonymized before it ever informs a page like this one.