Skip to main content

Clash of Titans - Platform Play

Platform Play, photo by Gabriel Jimenez

A lot has evolved since my Clash of the Titans post that looked into how the big 4.5 (Microsoft, Oracle, Salesforce, SAP, and Adobe) and others are positioning themselves in the greater CRM arena.
First, the commoditization of the business application has accelerated and the vendors’ focus on the underlying platform has increased. CRM, and enterprise software in general, has always been a platform play although this has not always been recognized and sometimes even negated. The obvious reason for it being a platform play is that the creation of positive customer and user experiences need a consistent technical platform. Or else we are ending up in engagements that are fragmented across interactions. This results in inconsistent and poor experiences.
So far, so well known.
A bit less obvious is the fact that there will be only few dominant platforms. Vendors, who want to become and stay successful on a grand scale need to be one of these few platform providers and attract partners and customers.
This is the reason why I consult my customers that one of the very first IT strategy decisions that they need to take is the platform decision.
As the article got a little longer this time and as I do not tend to write articles that are as long as dear friend Paull Greenberg’s (maybe I should consider to?) this revisit of the Clash of the Titans will become a two or three piece series, first covering the framework I want to use, the very definition of what I talk of when saying that CRM is a ‘platform play’. The subsequent articles then cover the big 4, thoughts about the big infrastructure providers, which are coincidently also 4, and maybe (yeah, it is not yet fully written) some words about one of the smaller and upcoming players.

So, what is a platform?

Of course all of the players that I mentioned above have their own definition of ‘platform’.
So have other vendors that are tackling the SMB portion of the market rather than the saturated enterprise end of it.
Most commonly, platform refers to both, infrastructure (IaaS) and functional, as well as development, (PaaS) platform.
However, when talking about the (technical) platform I will concentrate more on the PaaS aspects although IaaS capabilities are crucial for every SaaS vendor; but then IaaS is a commodity in a multi cloud world, too. And we are not even in a pure cloud world, yet. Many organizations still choose to run essential applications in house.
However, the platform that is needed to enable experiences at scale for organizations consists of more than IaaS and PaaS. Software vendors that want to be platform players need to be able to deliver on four areas to succeed:
  • Platform (IaaS/PaaS)
  • Ecosystem
  • Insight
  • Productivity

The building blocks of enabling experiences

There is more to being able to create an experience than just a technical platform. Apart from an appropriate, customer oriented strategy and a culture to match, I mean.
The Building Blocks of enabling Customer Experience


While the technical platform, in particular the development platform, is an important piece of the puzzle, it is not the only one.
Probably not even the most important one.
This platform holds and exposes the main capabilities that all enterprise software needs in order to be able to create a great experience: Analytics, integration, machine learning/AI, IoT services, blockchain, database access, security, to name just a few of the more important ones. The ability of organizations to innovate in fast cycles while maintaining a stable core is another one.
Customer Experience Architecture
This platform is crucial for any customer experience architecture.
So, why might there be something that is at least equally important? Because, apart from enabling the creation of own applications, the platform is only the foundation for scale.


Being a platform player requires scale. This scale is achieved by building and nurturing an ecosystem of partners. These partners are developing more solutions; oher partners are implementing solutions across the ecosystem. To thrive, this ecosystem needs to be fair and transparent. Fair, in a sense that generated value is distributed in a way that distributes the value between the participants in a way that every partner feels treated fairly. This is very different from equal distribution. Transparent means that the ecosystem’s rules are clear, clearly understood and that adherence to them is visible for all parties. Not adhering to the rules leads to sanctions.
A side condition is that the ecosystem must not be run on cost of the society that surrounds/embeds it.
A thriving ecosystem is valuable for all three involved parties
  • The vendor or provider of the ecosystem who participates in the transactions that are executed via the ecosystem.
  • The customers who will get more value for their specific challenges at a better price, which is a result of more competition in the ecosystem
  • The provider on the ecosystem who have a broader audience


The third necessity for providing positive experiences is insight.
Insight, not data!
Also not information. Information is data in a context. Information is needed to generate insight.
Insight is actionable information with the objective of achieving an outcome. Insight is what enables companies or individuals to turn raw data into actions that yield positive results for customers and therefore for themselves.
But there is a simple truth: Not enough data – no insight!
Although data is only the raw material that enables rational decision making, there needs to be access to plenty of different types of data to be able to generate insight. This data may be structured or unstructured, transactional or behavioural, etc. Data may be first party, second party, or third party data.
Through the use of analytics, data can be turned into information and through the use of advanced analytics and AI into insight. The services to enable this are delivered via the PaaS part of the platform.


Effective and efficient process automation where possible, combined with an efficient way for people to get their jobs done. This is what productivity is about.
There are four types of collaboration and communication that need to be enabled:
  • Human to human
  • Human to machine
  • Machine to human
  • Machine to machine

Whatever the desired outcome, people need to be able to achieve it efficiently, with minimal friction, ideally their own way. Especially within a business, but also across businesses, people need to collaborate easily and efficiently. This requires a lot of tools, services, and a strong data sharing ability.
It also requires people to interact with computers not in the computer way but the same way people interact. This is one of the main reasons for the rise of speech and voice interfaces.
And efficient collaboration is not only necessary for people, but for interacting software systems as well; it is needed for an effective process automation.
Hence the focus of the big software vendors – and not only theirs – in this quadruple play.
But this is a topic for the next article, starting with the big 4. How do they stand, move, what are their strenghts and possibly their weaknesses.
Stay tuned.


Last Year's Top 5 Popular Posts

SAP CRM into S/4HANA - Did SAP Hit Bulls Eye?

After having talked with Volker Hildebrand about the future of SAP CRM and whether or not there will be a CRM component in S/4HANA at CRM evolution 2017 I now had the chance to follow up with some folks back at SAP in Walldorf. A little RecapVolker told me that, unsurprisingly, SAP is working actively on adding CRM functionality into S/4HANA. In fact, they are merging SAP CRM into it. This is in my eyes meanwhile also the preferred of the two possible options; the other one would be marrying SAP Hybris C4C into S/4HANA. This is the approach which I originally preferred as it would lead to a cleaner code base. I changed my mind, putting customer friendliness reasons over technological cleanliness. The main advantages of merging SAP CRM into S4/HANA over SAP Hybris C4C are that this approach a)Opens a future roadmap for current SAP CRM customers that stretches beyond 2025. These customers else are at risk of defecting. b)Provides the continued chance for customers to run their SAP instance…

SAP CRM for S/4HANA - News from the Customer Frontier

It has been a little more than half a year now that I didn’t update on what is going on with SAP CRM and S/4HANA (which I will refer to as S/4 from now on; SAP it is time for you to change the unwieldy name to something more manageable). What Happened – So FarAs you are well aware SAP is working on integrating a simplified version of SAP CRM into S4. The original roadmap offered a first customer release of an integrated product in early 2018, based on the September 2017 release of S4. The integration was planned as an add-on to S4. The initial scope of this CRM add on for S/4 was supposed to cover what is referred to as ‘core service’ functionality. This initial release shall be followed by ‘core sales’ functionality later in 2018. 2019 then is supposed to be dedicated to another round-off release covering further sales and service functionality, including loyalty management and migration tools. Roadmap and statements also so far have been fairly fuzzy about the strategic distinction b…

Ten questions you always wanted to ask about CX

SAP - CallidusCloud Acquisition Take Two