Skip to main content

The almighty Metaverse - its Rise and Fate

This is the third part of my return of the undead series. The first two parts dealt with identifying what components or building blocks a metaverse ecosystem needs to consist of. These components basically define how metaverse can work and serve as a model for the identification of how/where participants in an ecosystem could earn their revenues. 

Figure 1: The metaverse ecosystem

These building blocks are mainly independent of the notion of a(n open) metaverse, as described by Tony Parisi in his article The seven Rules of the Metaverse. They also apply to a more multiverse type world of a collection of closed metaverses – something that I really do not want to call metaverse.

The openness, that is necessary for a “metaverse” to thrive can be achieved either by common consent or via regulation – or more likely by a combination thereof. In any case, I believe that some amount of regulation is necessary in order to create and maintain a level playing field and to avoid one or few companies hijacking the area – as this is a platform game and platform games prefer size and allow only few dominant players.

  • Users and creators use front-end applications that enable them to create the and interact with the virtual worlds that are offered. It is here, where the experience happens.
  • These applications run on devices that offer the necessary sensors and actuators.
  • The front-end applications connect to one or more virtual worlds that are provided as a service and that themselves rely on technology platforms.
  • All this gets connected by an infrastructure that includes servers, storage, networks, chips, etc, as well as the necessary services around them. 

Besides my framework, other people or organizations have developed own value chains, e.g., Jon Radoff or Sciencx, to name only two.

In the second article of this mini-series, I searched for compelling use cases that support both, B2B and B2C scenarios. As you can imagine, especially the use case frontier is quite difficult. What we see is a whole lot of use cases that base on existing, sometimes quite innovative, technology which gets quickly rebranded using the “metaverse” moniker.

The whole topic is still evolving, and we are in a situation that can remind us of the gold rush at Klondike: A stampede of hopefuls rush into the “area” with big hopes of getting rich.

We all know what happened back then. 

As I laid out in my article, the currently existing metaverse use cases are mainly focusing on the concept of NFTs and around applying real world concepts, especially scarcity, to the digital world. They mainly address consumers, real estate and retail. B2B use cases are far less evolved and often include statements like “in future”. Another observation is that many existing technologies and solutions are quickly relabeled to leverage the metaverse traction. It is not too difficult to find several year-old demos on e.g., VR and AR, that didn’t use the term metaverse. Except, now they do. The same can be observed for the more recent phenomena of blockchain and NFT.

The good news is that they topical hype seems to subside.

All this brings us to an interesting question.

Who will rule?

“One Ring to rule them all,

One Ring to find them,

One Ring to bring them all

And in the darkness bind them.”

From the Lord of the Rings

To get an idea about a possible answer, it is useful to have a look at above diagram from a slightly different angle and organize it around what happens on which layer. This gives an idea of what services and hence which value vendors on the various layers create for customers. 

Figure 2: The metaverse architecture stack

The diagram could be broken down into further layers, but these four should suffice. This way, we can visualize for ourselves, where there are opportunities for metaverse players. The diagram does not claim to be complete in any way, when it comes to the embedded boxes, which indicate the services that are on which layer.

  • The experience layer holds the applications and services that users and creators are consuming or creating on the devices that they are using,
  • which form the next layer.
  • Via the devices and apps a lot of (cloud) services can be created and consumed that live on the application and technology platform. Think of this as a combination of SaaS and PaaS layer. 
  • Lastly, we have the physical infrastructure that runs the whole thing.

The boxes in the four layers are of course indicative only and do not claim any completeness.

However, what is clear is that there are multiple players in each of these boxes, specialists as well as generalists. Some players do appear in multiple boxes and in more than one layer. 

As figure 1 shows, the metaverse market is an ecosystem play. Ecosystem markets automatically put players at an advantage that already have and/or offer reach, offer a platform for other market participants or are infrastructure players. Of critical interest in this ecosystem are players that provide access to very low latency and high bandwidth mobile communications and those who own the IP for relevant chips.

This seems to favor big companies like telcos and ISPs as well as Microsoft, Google, Meta, Roblox, etc. which already have achieved quite some scale. Or companies like Nvidia, which produces the necessary chips; or ARM, which develops and holds a lot of the IP that is necessary to build these chips.  

On the other hand, big companies often have a challenge with (disruptive) innovation.

Why?

This is a structural challenge. It is not that big companies are less innovative than small companies per se. However, they often need to answer to their shareholders on a frequent basis and therefore to provide fast returns with relatively high margins for every investment, to protect their valuations.

This favors nimble startups and VC companies who enjoy more slack when it comes to fast returns. Some of the startups in the relevant areas will either develop for a niche or sector and be successful – or they will be acquired by bigger players.

So, who will it be?

Neither! Or actually most of them.

This might surprise you, but the answer is quite simple – and obvious from the waning popularity of the term. Some big companies didn’t even jump on the train. 

Let’s count some reasons:

  1. The term as such was over-hyped. There is no real concept or overarching value proposition associated with it.
  2. In the next years we will not see the necessary standardization that would be necessary to deliver on any broader concept. Given this, vendors will concentrate on their patches.
  3. Most technologies that are currently touted as “metaverse” technologies existed and often thrived before the term got hyped. They will continue to develop and many of them successful. The overarching dream of “metaverse” is simply not necessary.
  4. Companies will fall back to concrete/specific use cases in which technologies can help solving the issue at hand. This might be a combination of VR/AR and IoT, or robotics, telepresence, holograms, digital twins, sometimes blockchains, etc., in different combinations.

I do think that this would be a good development. The appetite for innovation has been spurred by the hype, interesting use cases that solve actual problems will be solved. These solutions will connect as necessary.

This is business as usual.

What do you think? Let me know!


Comments

Last Year's Top 5 Popular Posts

You are only as good as your customer remembers

As you know, I am very interested in how organizations are using business applications, which problems they do address, and how they review their success. In a next instance of these customer interviews, I had the opportunity to talk with Melissa Gordon , Executive Vice President, Enterprise Solutions at Tidal Basin about their journey with Zoho. You can watch the full interview on YouTube. Tidal Basin is a government contractor that provides various services throughout the government space, including disaster response, technology and financial services, and contact centers. Tidal Basin started with Zoho CRM and was searching for a project management tool in 2019. This was prompted by mainly two drivers. First, employees were asking for tools to help them running their projects. Second, with a focus on organizational growth and bigger projects that involved more people, Tidal Basin wanted to reduce its risk exposure and increase the efficiency of project delivery. This way, the compa...

Sweet Transformation: Inside SugarCRM’s New Direction

Fresh from the 2025 SugarCRM Analyst Summit, waiting for my plane home, it is time to sort my thoughts. From Monday, 1/27 evening to Wednesday 1/29 in the morning we had some time jam packed with information and good conversations with SugarCRM execs, customers, and in between analysts. The main summit started with a bang, namely the announcement that industry icon Bob Stutz joins the SugarCRM board of directors , which is something that few of us, if any, had foreseen. This is exciting news.  With David Roberts , who succeeded Craig Charlton in September 2024, SugarCRM itself has a new CEO with a long time CRM pedigree.  As with every leadership change, this promises some change. Every new CEO evaluates what they see vs. where they want their company to go and then, together with the team, establishes and executes a plan to get there. Usually, this involves some change in the structure of the executive leadership team, too.  This is what happened and happens with SugarCR...

Data Wars: SAP Vs. Salesforce In The AI-Driven Enterprise Future

The past weeks certainly brought a lot of news, with SAP Sapphire and Salesforce's surely strategically timed announcement of acquiring Informatica , ranging at the top. I have covered both in recent articles. The enterprise software landscape is crackling with energy, and Artificial Intelligence (AI) is certainly the star of the show. It isn't anymore about AI as a mere feature; it's about AI as the strategic core of enterprise software. Two recent announcements underscored this shift: SAP's ambitious AI-centric vision that was unveiled at its Sapphire 2025 conference, and, arriving hot on its heels, Salesforce's agreement to acquire data management titan Informatica for $8 billion. Both signal an intensified battle for AI supremacy, where trusted, enterprise-wide data is the undisputed new monarch. Of course, SAP and Salesforce are not the only ones duking this one out. SAP's Sapphire Vision: An AI-Powered, Integrated Enterprise At its Sapphire 2025 event in ...

The CDP is dead – long live the CDP!

In the past few years, I have written about CDPs, what they are and what their value is – or rather can be. My definition of a CDP that I laid out in one of my column articles on CustomerThink is:  A Customer Data Platform is a software that creates persistent, unified customer records that enable business processes that have the customers’ interests and objectives in mind. It is a good thing that CDPs evolved from its origins of being a packaged software owned by marketers, serving marketers. Having looked at CDP’s as a band aid that fixes the proliferation of data silos that emerged for a number of reasons, I have ultimately come to the conclusion and am here to say that the customer data platform as an entity is increasingly becoming irrelevant – or in the typical marketing hyperbole – dead.  Why is that? There are mainly four reasons for it.  For one, many an application has its own CDP variant already embedded as part of enabling its core functionality. Any engageme...

CPQ, Meet Price Optimization: Your Revenue Lifecycle Just Got Serious

The news On October 1, 2025, Conga announced its intent to acquire the B2B business of PROS , following PRO’s acquisition by Thomas Bravo . At the same time, ThomaBravo and PROS announced that PRO’s travel business segment will be run as a standalone business . The bigger picture Revenue operations, revenue management and revenue lifecycle management have become a thing in the past years, as evidenced by the number of specialized companies that solve parts of the overall problem of optimizing revenue. It also got abused to some extent (e.g., surge pricing models) when the users of the corresponding capabilities consider optimizing being the same as maximizing. Reality check: It is not. While optimizing involves a bit of identifying how much a customer is willing to pay, it also involves the thought of repeat business, or in other words customer loyalty, even without a formal loyalty program. And that involves the customer experience, part of which the speed of creating a quote with mat...