Wednesday, July 26, 2017
Go Horizontal or Vertical in Acquisition Strategy?
Thursday, September 21, 2017
Up the Stack, Down the Stack Or Not?
Tuesday, January 19, 2016
You can Move Down the Stack on Your Own; To Move Up, You Have to Partner
So there are only three rules for service providers creating important new apps, and moving up the stack. Partner, partner, partner.
Saturday, November 7, 2020
Combining Network Access and Apps Businesses a Growing Trend
Are new service provider models--combining connectivity and apps--emerging? Some point to the examples of Rakuten, the Japanese online e-tailer that also has entered the mobile service provider business, or Reliance Jio, which includes both the Reliance Jio mobile business and a collection of digital content, transactions and apps businesses.
Others would point to moves by telcos and cable companies into content ownership.
“Infrastructure is intersecting with digital services such as you have seen with Rakuten and Jio,” says Steve Mollenkopf, Qualcomm CEO.
Others might add moves by the likes of Google, Facebook into connectivity service provider businesses (satellite, fiber to the home, mobile service provider) or infrastructure (Telecom Infra Project) or devices (e-readers, smart speakers, video streaming devices).
In fact, what all those moves show is expansion across the internet value chain by app providers into connectivity services, infrastructure and device portions of the ecosystem. Connectivity providers have made some moves into new applications, primarily entertainment video, and some are hopeful about new roles in edge computing or the internet of things.
At least so far, one might well argue that it has proven easier for app providers to move into adjacencies than for connectivity providers to do so.
It might be a fruitful question to ask why that is the case, as any move into adjacent value chain roles involves moving outside the area of core competency. Such moves often also involve mastery of functions higher or lower on the protocol stack, so there is a possible challenge in terms of moving up the stack or down the stack.
Some might argue it is--all other things being equal--easier to move down the stack than up the stack. When moving down the stack, the entity making the move is the “end user” or “business process” provider. Put simply, the advantage is that the business process provider knows exactly what it requires from lower levels of the stack.
Matters are different for an entity moving from lower in the stack to higher levels. Lower levels increasingly are “horizontal” in focus, designed to support literally any conceivable buyer, entity or business function. A connectivity network is designed to support any device or user with a need for internet protocol communications, or any device using a specific standard, such as 4G or 5G or Wi-Fi.
That is a lowest common denominator approach, and makes sense. In contrast, a business process provider knows precisely what it requires from lower levels, as those levels support its specific business. In many cases, it is not so much features but costs that are of concern.
As “same functionality, lower price” or “higher functionality, lower price” always is an easily understood value proposition, so too are business process provider value drivers when moving down the stack. The reason hyperscale app providers build and own their own subsea networks is that they get what they want at lower overall costs.
In other words, the business process provider knows precisely what it requires. The companies lower in the stack “have to guess” at what potential buyers will want, and have to be prepared to support all potential buyers (lowest common denominator) or optimize for a few verticals.
The lowest common denominator strategy offers the greatest potential scale, but also the least differentiation. That is one reason many believe network slicing--the ability to create custom virtual private networks with distinct performance characteristics--is important.
Network slicing might solve this problem (lowest common denominator versus optimized features), as experienced by connectivity providers.
There are some other, perhaps more subtle advantages for business process providers moving down the stack. Ubiquitous internet access helps app providers since their ability to gain and keep a customer requires internet access. That makes hyperscale app providers big supporters of ubiquitous, high quality, affordable internet access.
There are fewer obvious synergies for entities trying to move up the stack. It is hard to displace dominant suppliers in any of the stacks, so it almost always makes sense to specialize or differentiate when moving into any new adjacency, and especially up the stack.
But that also poses a problem of scale, as differentiation necessarily means aiming for a segment of the market. Essentially, that narrows the potential financial return. Consider the possible roles for connectivity providers as internet of things platforms.
Most would likely agree that no single provider can be successful in every business vertical. So Verizon has attempted to be a platform provider in the automotive space, and pitches its ThingSpace as a platform for connecting IoT devices to Verizon’s network. Some might note that the “platform” is mostly subscriber identification modules providing the communication function on Verizon’s mobile network. Some will question whether that is what it meant by the term “platform.”
Still, possible moves up or down the stack seem a growing issue for some tier-one service providers, simply because revenue growth opportunities in the core business are reaching, or already have reached, saturation. That can be seen in the percentage of total revenue coming from outside the communications service core.
As this chart suggests, tier-one service providers are betting on growth outside their legacy communications core, and many have made substantial progress.
If it is true that infrastructure and apps/content businesses are becoming synergistic, we can expect to see more moves blending the two--connectivity and apps--in the future, under common ownership.
Wednesday, September 27, 2017
Up the Stack or Forward in the Value Chain?
Saturday, May 16, 2015
In Defense of "Harvesting," Not "Moving Up the Stack"
Apps can be bundled. Apps can be designed to work collaboratively with access services. But that might not be the “usual” way. Instead, apps are designed to work on any access and any device.
So the point is that sometimes, all that can be done is to harvest what is dying, to nurture what might grow.
Wednesday, September 20, 2017
Why So Many are Skeptical about "Moving up the Stack"
Thursday, January 26, 2023
Why it is Hard to Move up the Stack, Much Easier to Move Down the Stack
Vertical integration and adding new roles in any value chain are traditional ways firms seek to increase value or control costs and value. As much as connectivity providers talk about “moving up the stack,” app providers also can move “down the stack.”
And we might as well just acknowledge that it is easier for an app provider to move down the stack than for a connectivity provider to move up the stack.
The reasons are somewhat obvious if you think about the issue long enough. Any app, service or product provider already knows lots about their customers. In other words, a business operating above the app level knows what its customers want, why they buy and how much they prefer to pay.
A connectivity provider has to learn what its connectivity customers want, but typically has no direct knowledge of the intimate details of how those connectivity customers actually create value in their businesses.
In other words, firms operating at higher levels of the stack are intimately involved with the actual business functions connectivity supports. Transport and computing functions at the lower levels are less involved--if involved at all--in the higher level business processes.
Bluntly, a connectivity supplier only knows what a class or type of customer typically wants to buy, in terms of computing and connectivity services, but has no direct and detailed knowledge of the connectivity customer’s actual business.
That is why connectivity provider enterprise sales forces have to build domain knowledge. Those in the domain already know all that, in detail.
It no longer is unusual for an app provider to become an access provider, for example. Google Fiber provides only one example, operating as a retail internet service provider and as an owner and builder of substantial wide area networks across the globe. Meta, Microsoft and other app providers also are anchor tenants if not full owners of WAN assets.
Tucows, originally a domain name registrar, has become both a mobile services provider and now a gigabit Internet service provider.
There also is movement by new providers into existing connectivity roles. Cable companies, satellite companies and other original equipment manufacturers likewise have moved into additional parts of the retail connectivity services business, ranging from internet access to mobile services.
Facebook now leases transponder time to support internet access operations in sub-Saharan Africa and sponsors the Telecom Infra Project that develops new open source tools across the connectivity ecosystem.
In other words, it is far easier to move down the stack than to move up the stack.
Directv-Dish Merger Fails
Directv’’s termination of its deal to merge with EchoStar, apparently because EchoStar bondholders did not approve, means EchoStar continue...
-
We have all repeatedly seen comparisons of equity value of hyperscale app providers compared to the value of connectivity providers, which s...
-
It really is surprising how often a Pareto distribution--the “80/20 rule--appears in business life, or in life, generally. Basically, the...
-
One recurring issue with forecasts of multi-access edge computing is that it is easier to make predictions about cost than revenue and infra...