The Martech Assessment That Comes Before the Platform Decision

Companies with identical martech platforms achieve wildly different results. Same vendors, same features, same implementation partners. The difference is whether the organization ran a diagnostic before making the platform decision, or jumped straight to ‘which platform should we buy?’

Replacement Rates Dropped. The Diagnostic Didn’t Start.

Marketing automation replacement dropped from 31% to 19% in a single year. CRM replacement fell from 22% to 10% (1. 2025 MarTech Replacement Survey). After years of routine rip-and-replace cycles, teams stopped swapping platforms.

But they didn’t start doing the work that makes the keeping decision productive. They stopped replacing. They didn’t start diagnosing. What happened instead was a holding pattern: teams kept platforms they were frustrated with, kept the same complaints, and waited for the next vendor release or AI feature to solve what was broken. Whether the team could use what it already had remained an open question nobody assigned anyone to answer.

That gap is where the money burns. When a core platform disappoints, the instinct is to evaluate whether to replace it. The evaluation starts with the tool: features, cost, vendor roadmap, integration architecture. It should start somewhere else entirely.

Capability determines platform value. The same platform produces wildly different results depending on the organization’s ability to configure, govern, and operate it. Before the replace decision has any meaning, three things need to be true: strategic alignment exists, operational capability is honest, and the technology assessment distinguishes platform limitations from organizational ones.

A regional bank considered replacing its marketing automation platform because it “lacked” behavioral scoring. The assessment revealed the platform already had sophisticated scoring features. Nobody had configured them. The constraint was a skills deficit. Building that capability unlocked what the bank was already paying for. The replace question was premature because nobody had asked what the organization could do with what it owned.

Organizations assume the platform is the bottleneck because the platform is the most visible piece of the stack. Features get compared. Roadmaps get evaluated. What rarely gets assessed with the same rigor is whether the team has the skills, data, processes, and governance to operate the features they’ve already purchased. As one independent analysis put it: “The biggest risk with martech is not that the tools don’t work. It’s that organizations buy technology to solve problems that are actually process and strategy problems” (2. Logarithmic, 2026).

The Sequence Has an Order

The diagnostic that precedes the platform decision has three steps. The order matters.

Strategic Alignment

Strategic alignment comes first. What must the technology accomplish? Not “what features do we need” but “what business outcomes does this technology serve?” This sounds obvious, but most organizations can’t articulate it when pressed. The answer they give defaults to the language of their current vendor’s marketing site. Without genuine strategic alignment, every platform evaluation defaults to feature comparison, and the vendor with the flashiest demo wins.

Operational Capability

Operational capability comes second. Can the team use what it already owns? This is where most organizations either get honest for the first time or choose not to. Configuration gaps. Data quality problems. Governance blind spots. Training deficits. These are organizational constraints, and they follow the team to every new platform.

This is verifiable. A specialty lender replaced its marketing automation platform specifically to gain behavioral scoring. Implementation succeeded. The scoring features were live. But the team brought the same skill gaps, fragmented data, and governance problems to the new platform. Behavioral scoring sat unused, the same way it had in the old system. Different vendor, doubled investment, same outcome.

Technology Assessment

Technology assessment comes third. Does the platform genuinely limit you, or is the organization the constraint? Only after steps one and two have run does this question produce a useful answer.

Most teams start at step three. They jump straight to evaluating the platform without evaluating themselves. That’s how platform evaluations produce feature-comparison spreadsheets instead of capability-gap diagnoses. And it’s why the replacement, when it happens, fails at predictable rates.

What Running the Diagnostic Looks Like

Hope Barrett joined SoundCloud to fix one thing: replace their deprecated multi-touch attribution model. Within weeks, she discovered the real problem had nothing to do with attribution (3. Barrett, Humans of Martech, 2025).

SoundCloud’s customer engagement platform dated back to 2016. The team had implemented it when the vendor’s roadmap was still theoretical, so they built their own infrastructure around it. Frequency caps, segmentation logic, delivery throttling: all living in homegrown scripts outside the platform. The platform reported message volume. Downstream systems disagreed. Every support escalation got the same response: “You’ve got a custom implementation. Go talk to your engineers.”

Barrett had seen this before. At CNN, she’d dealt with similar legacy platforms and recognized the symptoms. Tools 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 is wrong, the root cause is buried under years of operational shortcuts.

The Discovery

Barrett didn’t start with vendor evaluation. She started with the capability question: can this organization use what it owns?

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

Critical operational logic had migrated outside the platform over six years of workarounds. Nobody could trace where a number came from. The organization couldn’t get reliable data out of any platform because the real decision logic lived in scattered scripts that nobody owned.

So Barrett restructured how the team worked before touching the platform decision. Martech moved inside the product org. Data centralized in BigQuery with reverse ETL pushing audiences to downstream tools. Governance redesigned: anyone at SoundCloud could draft a message, but only the lifecycle team could send it.

The Decision

She built the case for migration by pulling a Confluence document from 2019 that cataloged every known platform issue. The problems weren’t new. They’d been tolerated for years. She ran an RFP with over 200 questions across 16 evaluation categories, making every vendor answer against the same criteria. The process surfaced how vendors behaved under pressure, not how they performed in scripted demos.

Then the triage. Every campaign, all 200, scored 0 to 3. Most didn’t survive. “What we had was so old and dated,” Barrett said. “If we’re starting over, we might as well start clean.”

Only then did the platform decision happen. The diagnostic had determined this was a genuine platform problem. SoundCloud’s vendor couldn’t support the architecture, and the response to every escalation confirmed it. MoEngage won the RFP with a project plan. Three people rebuilt the surviving campaigns in 12 weeks.

Barrett’s diagnostic revealed both that the organization needed to change (team structure, data architecture, governance) and that the platform was genuinely the constraint. She knew it was a platform problem because she ran steps one and two first. Without them, the replacement would have ported the same broken operating model into a new tool. Same scripts. Same workarounds. Different vendor.

Orchestration Is Organizational Muscle

There’s a word that keeps surfacing in these conversations: orchestration. It gets used loosely, sometimes as a synonym for integration. The distinction matters.

Integration is plumbing. Getting data from system A to system B. Most IT teams can solve integration problems with middleware, APIs, and patience.

Orchestration is the coordinated logic that makes connected systems act together in sequence. It demands people who can design trigger logic, processes for cross-channel workflows, data practices that make activation rules reliable, and content operations that keep pace. You can integrate five platforms in a quarter. Building the orchestration capability to make those platforms act as a system takes longer, and the investment is in people and processes.

A health system integrated its CDP, CMS, analytics, and automation platforms. Data flowed between all of them. Campaign performance barely moved. The platforms could talk to each other. They didn’t know what to do together. Nobody had designed the trigger logic that turns a clinical content download into a nurture sequence, or the governance rules that prevent a patient from receiving three emails in the same week from three different departments. The integration was technically sound. The orchestration capability didn’t exist.

The Time Objection

The objection to running the diagnostic is usually time. “We don’t have time for a three-step assessment. We need to move.” Barrett had a hard contract deadline of January 19. Three people. Two hundred campaigns to audit. The diagnostic is what made the 12-week migration survivable. Campaign triage alone eliminated most of the migration work. Teams that skip the diagnostic aren’t saving time. They’re deferring it to a second migration they’ll run for the same reasons.

Orchestration is the capability that determines whether any platform delivers value: the one you have now and the one you’re considering. Without it, even the right platform underperforms. With it, the platform you already own might be enough. That’s what the diagnostic reveals.

Skip the diagnostic, and you bring immature operations into a new platform. The stack changes. The constraints don’t.

The next time a core platform disappoints, resist the instinct to evaluate replacements. Run the diagnostic first. Strategic alignment. Operational capability. Technology assessment. In that order. The platform decision is downstream of all three.