This article was published in 2026 and references a historical event from 2017, included here for context and accuracy.
- Tension: Enterprise software companies must reconcile their legacy infrastructure strength with the nimble, open ecosystem approach modern marketing demands.
- Noise: The “suite versus best-of-breed” debate obscures how enterprises actually build technology ecosystems in practice.
- Direct Message: The future belongs not to closed platforms or chaotic tool sprawl, but to infrastructure providers who enable controlled openness.
To learn more about our editorial approach, explore The Direct Message methodology.
In 2017, SAP Hybris appeared in Gartner’s Magic Quadrant as a leader in multi-channel marketing. The achievement seemed unlikely for a company known for back-office ERP systems, not marketing clouds.
At the time, SAP’s CTO Moritz Zimmerman acknowledged they needed “to do some work on our brand recognition in this space.” The company had spent years avoiding marketing cloud conversations entirely, focusing instead on microservices and commerce functionality.
Nearly a decade later, that moment reveals something more interesting than one vendor’s product evolution. It captures the exact inflection point where enterprise software’s foundational assumptions began breaking down.
The 2017 SAP Hybris story wasn’t really about whether one vendor could compete with Adobe, Salesforce, and Oracle. It was about whether the entire concept of vendor consolidation could survive in an era demanding both integration and flexibility.
The infrastructure paradox enterprise software can’t escape
Enterprise buyers face a genuine contradiction: they need systems that talk to each other seamlessly, but they also need the freedom to swap components when better options emerge.
Traditional enterprise software promised the first through vendor lock-in. Modern marketing technology promised the second through best-of-breed flexibility. Neither approach actually delivers both.
SAP Hybris in 2017 embodied this tension perfectly. The company promoted a “suite approach” for delivering “first-class customer experience” while simultaneously publishing APIs and claiming to be an “open platform.” Executives couldn’t even agree on terminology. One called it a platform. Another insisted it wasn’t a platform but rather infrastructure supporting ecosystems. A third avoided the word platform entirely.
This wasn’t confusion. It was the sound of a company trying to speak two incompatible languages simultaneously. The suite language promised unified, integrated experiences. The platform language promised openness and flexibility. Enterprise buyers needed both, but the software industry had spent decades pretending they had to choose.
The contradiction runs deeper than product positioning. When Sealed Air evaluated CRM systems around the same time, they expected SAP’s cloud offering to be “on-prem with a different color.” Their 14-month evaluation process against Salesforce revealed the real enterprise decision framework: not which vendor offers the best features, but which infrastructure model accommodates the messy reality of global operations, legacy systems, and future unknowns.
How the suite versus best-of-breed debate masks the real question
Marketing technology discussions still frame vendor decisions as binary: unified suites offering seamless integration versus agile best-of-breed tools enabling flexibility. This framing survives because it simplifies an impossibly complex decision into two clear options.
It’s also completely detached from how enterprises actually operate.
Consider what Sealed Air’s Naveen Kandasami actually evaluated: not features or integration promises, but three operational pillars including defining customer engagement, measuring experience, and synthesizing insights. The technology conversation came second.
Similarly, when SAP Hybris executives discussed their positioning, they kept circling back to a more fundamental point: enterprises don’t need platforms, they need to improve their pipeline. They don’t need 20 products, they need the customer master and the data around it.
The suite versus best-of-breed debate persists because it serves vendor interests, not buyer needs. Vendors can position themselves clearly on one side or the other. Buyers are left choosing between integration nightmares or vendor lock-in, when what they actually need is infrastructure that enables strategic consolidation without eliminating future flexibility.
Meanwhile, the real noise comes from misunderstanding what “integration” actually means in enterprise contexts. SAP’s Marcus Ruebsam noted that even with strong back-end SAP foundations, front-end Hybris integration proved challenging due to legacy processes from mergers and acquisitions. Every large enterprise carries this legacy complexity.
The question isn’t whether a unified suite eliminates integration challenges, but whether your infrastructure choice makes inevitable integration work more or less manageable.
What controlled openness actually looks like
The breakthrough insight from SAP’s 2017 positioning struggle emerged almost accidentally in their internal debates: successful enterprise infrastructure requires being “as open as much as we can” while acknowledging “we can’t acquire companies or employ developers to fill all the gaps.”
Enterprise software infrastructure succeeds by enabling strategic closure around core data and processes while maintaining openness everywhere else.
This isn’t about platforms or suites or best-of-breed tools. It’s about defining which integration points matter enough to control tightly, and which need to remain flexible.
SAP’s decision to create and publish multiple APIs represented a revolutionary internal move precisely because it acknowledged this reality. They couldn’t be everything to everyone, but they could provide stable infrastructure that plays well with others.
The practical implication transforms how enterprises should evaluate vendors. Instead of asking “suite or best-of-breed,” ask: What does this vendor treat as core infrastructure versus optional extensions? How painful will it be to integrate or replace specific components? Where does this vendor enforce tight coupling, and is that coupling actually valuable?
Building technology ecosystems that accommodate reality
Today’s successful marketing technology ecosystems don’t choose between consolidation and flexibility. They practice what might be called “strategic closure”—making deliberate decisions about which components to tightly integrate while maintaining clear boundaries and escape hatches everywhere else.
This mirrors how organizations successfully manage hybrid work: not by forcing everyone into one model, but by being intentional about when synchronization matters and when autonomy serves better.
The SAP Hybris story from 2017 matters because it captured the exact moment when enterprise software began wrestling with this reality. Their struggle to articulate whether they were a platform or infrastructure or ecosystem wasn’t semantic confusion. It was the first draft of a new category that didn’t have language yet: infrastructure that enables controlled openness.
For enterprises building marketing technology stacks today, the lesson isn’t about which vendors won the 2017 positioning battles. It’s about recognizing that your job isn’t choosing between integration and flexibility. Your job is mapping which systems genuinely need tight integration to deliver value, and which benefit from loose coupling that preserves future options.
The question isn’t whether to build a suite or a stack. It’s whether your infrastructure choices today will accommodate the unknowns you’ll face tomorrow. SAP Hybris learned they couldn’t be “the only one.” Smart enterprises are learning they shouldn’t want any vendor to be.
