What’s up everyone, today we have the pleasure of sitting down with Hope Barrett, Sr Director of Product Management, Martech at SoundCloud.

Summary: In twelve weeks, Hope led a full messaging stack rebuild with just three people. They cut 200 legacy campaigns down to what mattered, partnered with MoEngage for execution, and shifted messaging into the product org. Now, SoundCloud ships notifications like features that are part of a core product. Governance is clean, data runs through BigQuery, and audiences sync everywhere. The migration was wild and fast, but incredibly meticulous and the ultimate gain was making the whole system make sense again.

About Hope

Hope Barrett has spent the last two decades building the machinery that makes modern marketing work, long before most companies even had names for the roles she was defining. As Senior Director of Product Management for Martech at SoundCloud, she leads the overhaul of their martech stack, making every tool in the chain pull its weight toward growth. She directs both the performance marketing and marketing analytics teams, ensuring the data is not just collected but used with precision to attract fans and artists at the right cost.

Before SoundCloud, she spent over six years at CNN scaling their newsletter program into a real asset, not just a vanity list. She laid the groundwork for data governance, built SEO strategies that actually stuck, and made sure editorial, ad sales, and business development all had the same map of who their readers were. Her career also includes time in consulting, digital analytics agencies, and leadership roles at companies like AT&T, Patch, and McMaster-Carr. Across all of them, she has combined technical fluency with sharp business instincts.

SoundCloud’s Big Messaging Platform Migration and What it Taught Them About Future-Proofing Martech: Diagnosing Broken Martech Starts With Asking Better Questions

Hope stepped into SoundCloud expecting to answer a tactical question: what could replace Nielsen’s multi-touch attribution? That was the assignment. Attribution was being deprecated. Pick something better. What she found was a tangle of infrastructure issues that had very little to do with attribution and everything to do with operational blind spots. Messages were going out, campaigns were triggering, but no one could say how many or to whom with any confidence. The data looked complete until you tried to use it for decision-making.

The core problem wasn’t a single tool. It was a decade of deferred maintenance. The customer engagement platform dated back to 2016. It had been implemented when the vendor’s roadmap was still theoretical, so SoundCloud had built their own infrastructure around it. That included external frequency caps, one-off delivery logic, and measurement layers that sat outside the platform. The platform said it sent X messages, but downstream systems had other opinions. Hope quickly saw the pattern: legacy tooling buried under compensatory systems no one wanted to admit existed.

That initial audit kicked off a full system teardown. The MMP wasn’t viable anymore. Google Analytics was still on Universal. Even the question that brought her in—how to replace MTA—had no great answer. Every path forward required removing layers of guesswork that had been quietly accepted as normal. It was less about choosing new tools and more about restoring the ability to ask direct questions and get direct answers. How many users received a message? What triggered it? Did we actually measure impact or just guess at attribution?

“I came in to answer one question and left rebuilding half the stack. You start with attribution and suddenly you're gut-checking everything else.”

Hope had done this before. At CNN, she had run full vendor evaluations, owned platform migrations, and managed post-rollout adoption. She knew what bloated systems looked like. She also knew they never fix themselves. Every extra workaround comes with a quiet cost: more dependencies, more tribal knowledge, more reasons to avoid change. Once the platforms can’t deliver reliable numbers and every fix depends on asking someone who left last year, you’re past the point of iteration. You’re in rebuild territory.

Key takeaway: If your team can't trace where a number comes from, the stack isn’t helping you operate. It’s hiding decisions behind legacy duct tape. Fixing that starts with hard questions. Ask what systems your data passes through, which rules live outside the platform, and how long it’s been since anyone challenged the architecture. Clarity doesn’t come from adding more tools. It comes from stripping complexity until the answers make sense again.

Why Legacy Messaging Platforms Quietly Break Your Customer Experience

Hope realized SoundCloud’s customer messaging setup was broken the moment she couldn’t get a straight answer to a basic question: how many messages had been sent? The platform could produce a number, but it was useless. Too many things happened after delivery. Support infrastructure kicked in. Frequency caps filtered volume. Campaign logic lived outside the actual platform. There was no single system of record. The tools looked functional, but trust had already eroded.

The core problem came from decisions made years earlier. The customer engagement platform had been implemented in 2016 when the vendor was still early in its lifecycle. At the time, core features didn’t exist, so SoundCloud built their own solutions around it. Frequency management, segmentation logic, even delivery throttling ran outside the tool. These weren’t integrations. They were crutches. And they turned what should have been a centralized system into a loosely coupled set of scripts, API calls, and legacy logic that no one wanted to touch.

Hope had seen this pattern before. At CNN, she dealt with similar issues and recognized the symptoms immediately. Legacy platforms tend to create debt you don’t notice until you start asking precise questions. Things work, but only because internal teams built workarounds that silently age out of relevance. Tech stacks like that don’t fail loudly. They fail in fragments. One missing field, one skipped frequency cap, one number that doesn’t reconcile across tools. By the time it’s clear something’s wrong, the actual root cause is buried under six years of operational shortcuts.

“The platform gave me a number, but it wasn’t the real number. Everything important was happening outside of it.”

Hope’s philosophy around messaging is shaped by how she defines partnership. She prefers vendors who act like partners, not ticket responders. Partners should care about long-term success, not just contract renewals. But partnership also means using the tool as intended. When the platform is bent around missing features, the relationship becomes strained. Every workaround is a vote of no confidence in the roadmap. Eventually, you're not just managing campaigns. You’re managing risk.

Key takeaway: If your customer messaging platform can't report true delivery volume because critical logic happens outside of it, you're already in rebuild territory. Don’t wait for a total failure. Audit where key rules live. Centralize what matters. And only invest in tools where out-of-the-box features can support your real-world use cases. That way you can grow without outsourcing half your stack to workaround scripts and tribal knowledge.

Why Custom Martech Builds Quietly Punish You Later

The worst part of SoundCloud’s legacy stack wasn’t the duct-taped infrastructure. It was how long it took to admit it had become a problem. The platform had been in place since 2016, back when the vendor was still figuring out core features. Instead of switching, SoundCloud stayed locked in ...

The Murder on the Links: Chapter 15