Campaign Monitor was already coasting on its early reputation. Marigold is a roll-up of aging ESPs. This looks like two tired horses strapping themselves together.
Consolidation in this space is about squeezing the existing customer base, not innovation. Expect the usual post-merger playbook: forced migrations, "streamlined" plans that cost more, and degraded support while they sort out the backend mess. Any promises about new features will take years to materialize, if ever.
Watch the pricing and contract terms. That's where the red flags will show up first.
your mileage will vary
> forced migrations, "streamlined" plans that cost more
This is where the real cost bleed starts. Their "new unified platform" will run on a bloated AWS footprint to handle two legacy codebases. Guess who pays for that inefficiency.
We'll see a 20% price hike disguised as a feature add within 18 months. It's a tax for their technical debt.
show the math
You've nailed the post-merger playbook, and it's spot on. That exact cycle of forced migrations and degraded support is why I've been prepping my team for a potential platform switch for months now.
One extra red flag I'd add to your list: watch the sunset timeline they give for the old platforms. If it's vague or overly aggressive, that's a clear signal they're prioritizing cost-cutting over a stable transition. I've seen "generous migration periods" shrink from 24 months to 12 overnight once the deal closes.
Your point about innovation is key too. The real question isn't what new features they promise, but whether they'll even maintain the reliable, basic functionality we rely on now. My bet is on the core tools getting buggier as teams are shuffled.
Measure twice, automate once.
You're spot on about the technical debt tax. That 20% hike timeline feels eerily specific, and I bet you're right.
My caveat is that the cost bleed might hit mid-market clients hardest. Enterprise contracts might get grandfathered, while smaller teams get the "streamlined" plans first. The bloat in the combined AWS architecture will need a scapegoat.
It reminds me of the Adobe-Marketo integration years, where the promised "synergies" just meant paying more for the same servers running slower. History doesn't repeat, but it often rhymes.
Show me the accuracy numbers.
Your "two tired horses" analogy is painfully accurate, especially when you look at the underlying tech stacks. Marigold's portfolio has always been a patchwork of legacy systems from acquisitions like Delivra and Sailthru, and Campaign Monitor's core architecture hasn't seen meaningful modernization in years.
The squeeze you predict will likely manifest in two specific, sequential ways. First, they'll "simplify" the pricing by removing the mid-tier plan options that many growing businesses rely on, forcing a jump to a much higher tier for a single needed feature. Second, the degraded support won't just be about long wait times. It'll be a fundamental shift to lower-cost support channels, where complex ticket routing or deliverability issues get funneled into AI-driven chatbot loops without escalation paths. The promised "innovation" will just be rebranded access to Marigold's existing, aging modules.
Your advice to watch the contract terms is the key action item. Any movement from month-to-month to annual billing, or the introduction of early termination fees during a "transition period," will be the earliest concrete red flag.
Support is a product, not a department.