Original title: "Looking for the balance point of web3.0, talking about the qualitative change brought by web3.0 to the commercialization of complements"
Original author: Jesse Walden, Jonathan Glick
Original Compilation: Kyle, Babbitt
About 20 years ago, Joel Spolsky, author of "Software Caprice," created a A phrase that has since informed the decisions of countless startups and tech giants: “Commoditize your Complement.” (Note: Complementary products refer to complementary products purchased together with your product, such as gasoline is the complementary product of a car)
Generally speaking, a It should be in the firm's strategic interest to keep the price of its complement as low as possible. The lowest theoretically sustainable price is the "item price" - the price that occurs when you have a bunch of competitors offering indistinguishable items. So: Smart companies try to commoditize complements of their products. If you can do this, demand for your product will increase, allowing you to charge more and make more money.
When the price of gasoline, milk, and ink falls, companies that sell cars, grain, and printers benefit because the total price of the product includes that product plus your Anything else that needs to be maximized to its potential - a complement. When the cost of complements decreases, the core product becomes more affordable overall. As affordability improves, so do sales—as sales increase, pricing power leverage over complements increases—and it's a virtuous circle. If ink was nearly free, the favorites would be Canon and HP, which would see their products cost less, without having to lower their product prices.
The Web3 team has the opportunity to learn and improve strategies for commoditizing complements. In this post, we discuss why building and commoditizing products on top of user-owned protocols can provide the greatest leverage to execute this strategy, with the potential for a stronger economic equilibrium that drives growth and value, while surpassing traditional Early implementations executed by tech companies.
Let's start with some historical examples.
On the hardware side, "complementary goods Perhaps the best-known example of this is Microsoft's strategy to foster competition among PC hardware makers by licensing its popular operating system, Windows, to anyone who can pay. Doing so would encourage intense competition within the PC industry, undermining the market position of hardware manufacturers. By lowering the overall cost of buying a desktop, Microsoft removed IBM's position as a hegemonic threat and increased the addressable market for PCs, which in turn increased demand for Windows, which increased their pricing power.
On the software side, corporate acceptance of open source projects inhibits the ability of startups to develop profitable and threatening businesses at this layer, while also encouraging Use proprietary services to further expand the advantages of the tech giants. Google's licensing of TensorFlow, whose machine learning engine costs millions of dollars to develop, stifled potential competitors to build general-purpose machine learning frameworks and increased the number of developers using and improving TensorFlow software, thereby driving interest in Google Cloud. Requirements for TensorFlow Enterprise.
In the Web2 era, platforms like Twitter and Facebook ran a powerful but ad-hoc "commoditization of complements" strategy early in their growth phase. By giving away their products and APIs for free, these platforms are able to attract valuable social graphs and user data, which in turn helps attract an ecosystem of third-party developers who build products to reach these users and extend the platform's reach. Function.
But there's a problem: After commoditizing APIs as a way to drive growth, the social networks closed the valve, turning their platforms into proprietary platforms. There are walled gardens to get more value out of them. This puts them in a zero-sum conflict with third-party developers, as well as their users, as their options are eroded.
Web3 protocols have the opportunity to do things differently, as they can distribute tokens to turn users into owners, enabling them to management platform.
The first and largest The “users” of a blockchain — defined as the software services (often referred to as “protocols” in Web3 parlance) running on an open blockchain — are typically the product teams building the underlying platform. The Web3 teams building these platforms wisely build the first product on top and give it away as commodity "free" to bootstrap users, data, and network effects.
Uniswap is an example: Uniswap Labs established app.uniswap.org, the first and main interface to the Uniswap protocol, which is open and Runs on the Ethereum blockchain. Compound Labs is also a company that did the same for the Compound money market protocol.
Making these early DeFi protocols accessible through an intuitive, user-friendly front-end is critical to bootstrapping liquidity on each market platform - once liquidity comes in , and network effects ensue, where the product is priced better for each additional user. A growing user base, coupled with solid developer documentation, facilitates the integration of the underlying protocol into new products and services by third-party developers.
For example, Metamask includes token swaps directly in its Ethereum wallet, where liquidity comes directly from Uniswap. Crucially, Metamask can do this without asking for permission and without having to worry about APIs being pulled from the bottom as is common in Web2, since the Uniswap protocol and all its data is on the public blockchain runs on and is owned by the user.
To summarize: Accessing supplementation (Uniswap trading applications) at zero cost is a way to maximize the benefits of end users whose usage mobilizes the underlying platform (Uniswap protocol) network effects. These network effects led by commoditized products can help attract third-party developers who build more features and attract more users and usage, compounding these network effects. Finally, the distribution of ownership of the underlying platform—in the form of tokens—can be distributed to those who drive value, typically users and developers.
In other words, Web3 companies can commoditize complements - but not as a means of extracting profits and status from potential competitors, as in Web2 , but as a practical means of promoting sustainable innovation.
This approach to progressive decentralization aligns all parties’ incentives around growing value in the underlying platform or protocol—and enables Teams earning tokens are able to commoditize their own products to capture value in the underlying platform.
This Web3 model of commoditizing complements — and the consequent structural separation of protocols from products — creates the need for an economic balance in which protocols incentivize developers to commoditize their complementary products while reaching the widest possible user base and leveraging their Success and the development of the underlying platform.
As more and more teams join Web3, it's worth highlighting best practices for achieving this balance. Two steps appear particularly important:
First, as the Web3 platform matures, it may be beneficial to structure the core project development work between two teams: those A team that focuses on the underlying platform or protocol, and a team that builds the initial product for end users (each team may have its own distinct brand to avoid confusion). Product teams understand end-user needs and can help inform protocol design. As the protocol team understands the needs of product developers, they can consider adding features that will attract more developers.
Secondly, both product and protocol teams should align around a single goal: a KPI focused on protocol growth. Measuring against protocol-level metrics helps ensure that products are truly complementary, driving the expected value of the underlying protocol. With dedicated product and protocol teams aligned around a shared metric (a protocol or platform-level KPI), it should be possible to measure contributions to that KPI and assign the value of the underlying platform to the developers and users who drive it.
The initial product team helps steer the network effects of the underlying protocol and should be rewarded for its significant contribution to the ecosystem. But at the end of the day, a protocol library is best optimized at the top level for multiple product teams, because that's potentially a way to make the platform bigger and faster. An economic balance that can achieve this has the potential to be the wave that lifts all boats.
In this balance, products that try to extract too much value from the protocol layer will face stiff competition from other products that commoditize their products to capture value elsewhere.
This excessive value capture will replicate rather than reform the Web2 model - 3rd party innovation will be stifled, developers will tend to fork, users will seek A cheaper, more innovative alternative.
Some early examples of protocols working to achieve the right balance include grant programs from large DeFi protocols like Uniswap, Compound, AAVE, etc., which reward 3rd party development People provide products and services that grow the ecosystem in their native treasury token. The Liquity protocol rewards developers who build front-ends for its stablecoin protocol, and LQTY tokens are rewarded proportionally to users who deposit funds into the protocol.
These front-end operators can earn a portion of these rewards by marking deposits facilitated by their interface and specifying a percentage of the LQTY rewards to distribute to users. The UMA protocol attempts something similar with its Developer Mining program, which encourages distributed innovation, using economic incentives to reward developers who contribute directly to sustainably increasing UMA's Total Value Locked (TVL) KPI. If you've built or seen other good examples, I'd love to hear about them.
The commoditization of complements is a concept deeply entrenched in technology strategy. The ownership economy of Web3 gives us new tools to use it, not as a means of stifling innovation and community, but encouraging them.
Thanks to Jonathan Glick for his help, Li Jin, Spencer Noon and the many builders in the Variant portfolio and community who Dialogue helped shape these ideas in the text.
Original link blockquote>
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia