A unifying framework for digital business models
In the fall of 2013, Paul Graham rattled out two tweets in quick succession:
Exercise for founders: How would you describe your idea without using the word “platform?”
— Paul Graham (@paulg) October 27, 2013
28.2% of the applications for the upcoming YC batch call what they’re building a “platform.” — Paul Graham (@paulg) October 31, 2013
This highlights an interesting issue.
Because of what I do, I meet a lot of people who say they’re building platforms. The problem isn’t that they actually aren’t building one. The problem, often, is that:
Different people mean vastly different things when they use the word ‘platform’.
Within the software development community itself, the discussion on platforms is never ending, and the jury’s still out on the various terminologies that float right there. We call Android, Salesforce, Facebook Connect and a host of other things ‘platforms’.
Moving away from the developer community, we talk about Medium and WordPress as blogging platforms. YouTube, Facebook, and even Instagram are described as platforms. Uber, Airbnb and their ilk are widely described as ‘marketplaces’, ‘platforms’ or ‘marketplace platforms.’
To make things, even more, complex, the Nest thermostat is called a platform, Nike says it’s building a platform to connect its shoes and GE claims to be using a platform approach to manage its factories. The Internet of Things movement repeatedly talks about platforms, but those definitions don’t align with any of Uber, Medium or Android. And none of these align with each other either.
So what exactly is a platform? Through this essay, I want to propose a unifying framework for thinking through the concept of platforms.
This is a long analysis, but it’s heavily illustrated. Stay on for the ride!
Let me try and propose a definition and then validate it through a framework that follows.
Let’s start with the WHY of platforms. Why does a platform exist?
The goal of a platform is to enable interactions between producers and consumers.
HOW does it do that?
It achieves this by
WHAT is a platform?
A platform is a plug-and-play business model that allows multiple participants (producers and consumers) to connect to it, interact with each other and create and exchange value.
So how does this bring together Android, Airbnb, Alibaba, YouTube, Nike and GE? Let’s dive into this further.
The most important aspect of this definition is to understand the following:
This is where the fun starts. Let’s revisit the three key roles of the platform business model:
1.Architecting incentives that repeatedly pull these participants to the platform,
2.Providing a central infrastructure on which participants create and exchange value,
3.Matching participants with each other and with content/goods/services created on the platform
Across all platforms, we repeatedly see three layers, as follows:
Network/Marketplace/Community Layer: Some platforms may have users explicitly connecting with each other, as in social networks. Some may have users not connecting but exchanging items as in marketplaces. And some platforms may have an implicit community layer. e.g. If you use the Nest Thermostat or Mint.com, your usage is benchmarked against others. So you are benefiting from the community implicitly but you don’t explicitly connect with them.
More importantly, this is also the layer at which the external network of producers creates value. To enable this value creation, we need the second layer: Infrastructure.
Infrastructure Layer: This is what you ‘build’. Of itself, it has little value unless users and partners create value on top. External producers build on top of this infrastructure. On Android, developers build apps. On YouTube, video creators host videos. On eBay, sellers build/host product availability. In some cases, the infrastructure layer may be very dominant, e.g. development platforms like Android. In other cases, the infrastructure layer may be much thinner e.g. Instagram. The infrastructure layer essentially provides the infrastructure on top of which value can be created.
However, with a lot of value creation comes the problem of abundance. Relevance dips. If YouTube has too many videos, how do you find the best ones? This brings us to the third layer: Data.
Data Layer: The final layer is the data layer. Every platform uses data in some way. But in some cases, the data layer may play a more dominant role than in others. In most cases, data serves to provide relevance, matching the most relevant content/goods/services with the right users. In other cases, the value may exclusively lie in the data layer. The Nest Thermostat example, as we will revisit below, is what one would think of as a data-intensive platform, where the value is entirely in the data being aggregated with a minimal.
The reason I propose the Platform Stack is to highlight that we’re increasingly not talking about different families of platforms. It’s not one vs. the other. Development platforms are building out marketplaces. Marketplaces are opening up APIs for platform extension. We are talking about different configurations of one stack.
Let’s play around with some of these configurations for a bit. As we mentioned, all platforms have all 3 layers but the degrees to which each dominates may vary.
To start with, let’s lay out the 3 basic configurations. These are merely for illustration. To understand specific platforms, it may help to tweak these around a bit.
When we think of Airbnb, Uber, all those sharing economy platforms, we’re looking at a configuration that is heavy on the marketplace/community layer. The key source of value is the network. Online communities like Reddit also fall into this category.
One would naturally argue that all parts play a role. Data is important too. In some cases, infrastructure plays a role along with the community. And that is precisely the point. The idea of using this stack is to illustrate that we’re not talking about one vs. the other. Every platform will have its unique configuration.
Having said that, there are examples of Craigslist or discussion forums that are pure marketplaces or communities with almost no infrastructure play and not leveraging data at all. They still exhibit many of the platform dynamics that an Airbnb and Facebook demonstrate but they lie at an extreme end, almost perfectly demonstrated by the stack above.
This is the basic configuration we would associate with a development platform like Android, which provides the infrastructure on top of which apps may be created. Of course, a key chunk of the value is in the marketplace created on top: the Play store. (We’ll explore that configuration in a minute) But the infrastructure is clearly important. Almost all traditional views of development platforms focus entirely on the infrastructure layer.
WordPress is a platform that provides the infrastructure exclusively and doesn’t provide network benefits or any value through data. Medium, as we shall soon see, has a different configuration.
Let’s move to the third configuration.
The third – and often, least evident – basic configuration is the one where data dominates. Data plays a role with every platform. Facebook uses data to fashion your news feed; Airbnb uses data to show you relevant accommodation. But in certain cases, the data itself is the key value created on the platform. We discuss those platforms here.
This brings us to a whole family of platforms that often don’t look like platforms:
Wearables: Nike’s shoes and fuelband constantly create data, and the underlying platform integrates the user experience across the shoe, the wearable and the mobile apps. Jawbone – and most wearables for that matter – create value through the data platform. The wearable acts as the producer of data. The platform provides value back to the user but also pools the data from many users to create network-level insights.
Nest Thermostat and the Internet of Things: When we talk about the internet of things, we are obsessed with the ‘thing’ rather than with the ‘internet’. Nest Thermostat, as an example, uses a platform approach to make sense of all the data being produced by the thermostat. Aggregating all the data from a city’s thermostats, it provides analytics and other services to the city’s utilities board. This is made possible because of the data platform.
Industrial Internet: GE’s theme of the industrial internet is another example of data platforms. Machines, enabled with sensors, constantly stream activity data into a platform that helps each machine learn from other machines and provides network-wide intelligence.
Enterprise 2.0: Andy McAfee talks about the rise of social software in the enterprise and how it’s replacing traditional enterprise systems. All of this needs an underlying data platform to make sense of the many workflows and many knowledge exchanges within an organization.
Omnichannel Customer Journeys: Retailers like Burberry and Target use an underlying data platform to unify customer journeys across the store and other remote touchpoints. Actions that a user takes on an app lead to a change in the in-store experience and vice versa. This is possible because an underlying data platform manages the users’ interactions with the store. Over time, this data can be used to actually create explicit communities by connecting users with similar shopping behavior in the same area with each other.
Data platforms like the above are a unique category where the platform works like a pool into which, different sources bring in data and from which, different participants derive value.
To do that, let’s leave the world of data platforms behind and revisit the Platform Stack:
Let’s illustrate this with a few case studies.
Let’s visualize the competition between Craigslist and Airbnb using this stack.
In a well-known move, Airbnb disrupted Craigslist and created a whole new playbook for platform competition. (Access the playbook here.)
If we use the Platform Stack to stack up Craigslist, we see immense network effects because of a strong network/marketplace. However, Craigslist does very little on infrastructure (no handling of payments, no facilitation mechanisms like trust, etc.).
Airbnb started out with poor network effects, but better use of data and a more robust infrastructure to enable interactions between hosts and guests. Over time, it has built out arguably much stronger network effects within the travel/accommodation vertical and has a treasure trove of data which powers the business model.
In it’s early days, YouTube’s hosting and bandwidth infrastructure coupled with its flash-based in-browser, embeddable player formed a compelling value proposition for content creators. As YouTube gained traction, the focus of the platform moved from improving video hosting (technology/infrastructure layer) to improving match-making of videos with consumers (data layer) and increasing viewer engagement (network layer). Vimeo decided, instead, to focus its platform on the content creators and provide them with superior video infrastructure (HD player, a netter embeddable player for bloggers). This has helped the two co-exist despite YouTube’s dominance.
Development platforms, by default, have a strong infrastructure layer. But ever since Apple launched the app store, they’ve come bundled with a strong marketplace layer as well.
Microsoft beat Apple with a more open platform for developers to create apps on. Arguably, through developer ecosystem management, Microsoft did invest in nurturing the ecosystem. But it was nowhere near as structured as the Android – Play Store combination. Ever since Apple’s and Android’s app stores, the idea of combining app stores with development platforms has gained a lot of traction among existing and emerging platforms.
Much like the earlier example, WordPress only provided a technology infrastructure for writers to create blog posts on. Medium is WordPress on steroids and more. It keeps the technology infrastructure simple: easier plug-and-play. But it also leverages data to better help content discover its market. It also allows a community to form on top of Medium and allows writers and curators to build a following. In doing this, Medium has built a much more comprehensive platform stack than any blogging platform before it.
Myspace and Facebook are two social networks with vastly different platform stacks. Facebook’s largest draw, arguably, is the News Feed. By focusing on using data better and engaging the community in a much more stronger way, Facebook built out an entirely different business even though the two may appear similar on the face of it. When Myspace started feeling the heat from Facebook, it tried to respond with many feature and functionality changes that mimicked Facebook’s infrastructure but couldn’t quite get to building out the rest of the stack quite as effectively. Facebook has done much to strengthen the data layer in creating the Social Graph and the Open Graph. Most social networks of “The Myspace Era” were largely focused on the community and building network effects through connecting people. Facebook, instead, through Connect, has ended up creating a social data layer for the web.
Quicken isn’t really a platform, but the Quicken vs. Mint illustration using the Platform Stack is a good illustration to show platform business models beating software product based business models. Quicken provides users with the infrastructure to manage finances. In its initial days, Mint did the same but provided it for free. This allowed Mint to gain traction through a superior product. Moving forward, Mint expanded to fill out the rest of the Platform Stack. It creates an implicit network of consumers who benefit from social analytics that benchmarks their spending habits vis-a-vis peers. It also creates a marketplace that allows financial institutions to sell their offerings to these consumers. All of this is powered through a constant stream of data coming in from consumer accounts connected to Mint.
Hipstamatic and Instagram are deceptively similar. Both allow you to take photos and put on cool filters. But here’s the difference. Hipstamatic simply provided the technology to take cool photos using filters. As a result, Hipstamatic based its revenue model on charging for the app and premium filters. On the other hand, even in its early days, Instagram focused on the network through its Facebook integration and, over time, built out the entire platform stack. The core value provided by Instagram – and the reason it succeeded despite a late start – was not the filters, it was the network and community for sharing pictures. Ironically, one of the most popular hashtags on Instagram was #hipstamatic, indicating that while the pictures were taken using Hipstamatic, they were being shared on Instagram.
Despite Flickr’s earlier start, Facebook hosts the largest number of photos online today. Flickr still attracts those who want to use it for its storage infrastructure. Facebook, in contrast, is used to generate conversations around photos which it effectively does through a superior community and data layer.
Monster would have never seen LinkedIn as a potential competitor. It was too busy focusing on other job portals. Job portals utilized basic data to help users find jobs and recruiters find resumes. LinkedIn uses more holistic data on the user to match them with jobs. By building out a network of professionals, it helps activate even passive job seekers who wouldn’t visit job portals. LinkedIn has, effectively, eaten Monster by building out an entirely different stack.
The Platform Stack is a tool for us to think through platforms and plan them. Irrespective of what you’re building, the stack helps to figure which layers you differentiate yourself in and how. It helps understand the key strengths of businesses that are already out there in the market. Without getting lost in the quagmire of features and functionalities, the stack helps us understand the key drivers of value and helps us benchmark ourselves on those parameters against competition and substitutes.
P.S. I’ve removed comments from the new blog design because they attracted a lot of bots and the best discussions around blog posts were happening on Twitter. If you’d like to discuss this topic further, just hit me on @sanguit on Twitter and be sure to hashtag your comment #PlatformThinking so that others can join in.
The platform stack: for everyone building a platform… and for everyone else Share this
A framework for understanding different platform business models Share this
Using the platform stack to decode different strategies Share this
Marketplaces, dev platforms, data lakes and more, with one framework Share this
The business stack of the #nexteconomy Share this
In the future, algorithms and users will do what your employees do today.
Can making product usage difficult for users actually be a good idea? In some cases, yes!