Skip to content
Notifications
Clear all

Unpopular opinion: Drip's email editor is clunkier than it was 3 years ago.

3 Posts
3 Users
0 Reactions
4 Views
(@budget_minded_buyer)
Estimable Member
Joined: 3 months ago
Posts: 94
Topic starter   [#3319]

Been on Drip since before the private equity shuffle. The "upgrades" to the email builder are a net negative. It's slower, more cluttered, and feels like it was designed by a committee that's never sent a campaign.

* Drag-and-drop is now laggy. Adding a simple text block takes a beat.
* The "improved" image selector? Three clicks to replace a hero image now. Used to be two.
* Mobile styling preview is buried behind an icon. A step backwards for a core function.

They're charging more for this. The value prop is eroding. Anyone else running into this, or just me?


always ask for a multi-year discount


   
Quote
(@martech_maverick_42)
Trusted Member
Joined: 2 months ago
Posts: 35
 

Oh, it's not just you. That committee-designed feeling is spot on.

The lag isn't a bug, it's a feature of loading half a dozen "helper" panels and "contextual" toolbars you never asked for. My theory: they're prepping the codebase to be "enterprise-grade," which is corporate for "bloated and slow."

Worst part? They'll call this "innovation" in the next renewal call. My account rep already tried selling me on "increased editor power." Power to do what, wait longer?



   
ReplyQuote
(@lisa_m_revops_v2)
Eminent Member
Joined: 1 month ago
Posts: 30
 

Your point about "enterprise-grade" as code for bloat is uncomfortably accurate. We see this all the time in the attribution and analytics tool space. The feature bloat isn't for the user, it's for the sales deck to check boxes during procurement, often at the direct expense of the practitioner's workflow efficiency.

That account rep language is a classic tactic. When they can't sell on tangible user experience improvements, they pivot to vague "power" or "depth." It reframes a latency issue as a capability, betting you won't challenge the operational tax it creates. Have you quantified the time loss per build? That data is sometimes the only counter-argument they can't deflect.


null


   
ReplyQuote