Electronic Markets and Electronic Hierarchies
Source: https://dl.acm.org/doi/10.1145/214762.214766 ↗
Full text: open-access via Unpaywall ↗
The paper that connects Coase to the digital era.
Information technology reduces transaction costs, and that pushes activity toward markets and away from hierarchies.
When coordinating outside is cheap, firms shrink.
It is one of the first works to predict what later became mass outsourcing, supplier networks and the freelance economy.
Essential reading to understand that AI is not the first technology to move the Coasean frontier — it is the latest in a long series.
Central argument
Malone, Yates, and Benjamin argue that information technology reduces coordination costs—the costs of gathering information, negotiating contracts, and managing supplier relationships—and that this reduction will shift economic activity away from hierarchies (integrated firms managing supply chains internally) toward markets (external transactions between independent parties). Their core mechanism is straightforward: hierarchies exist because market coordination was historically expensive; cheaper information processing erodes that advantage. They further identify asset specificity and complexity of product description as the two key variables determining where on the market-hierarchy spectrum a given transaction will settle as IT advances.
Critique
The paper assumes that lower coordination costs unambiguously favor markets, but it underweights the strategic value firms derive from hierarchical relationships beyond cost efficiency—trust, tacit knowledge transfer, joint innovation, and lock-in as competitive moat. The authors acknowledge other forces (antitrust, interest rates) but bracket them entirely, which is intellectually convenient but empirically problematic: the rise of platform ecosystems like Apple's App Store or Amazon's Marketplace suggests the dominant outcome of cheap coordination has not been open markets but rather the emergence of a third form—platform hierarchies—where one actor controls the coordination infrastructure itself, capturing the benefits of both. This structural possibility is absent from their two-option framework.
Why it matters for product
For a CPO deciding whether to build capabilities in-house versus composing products from third-party APIs, marketplaces, and modular services, this paper provides the theoretical underpinning: every make-or-buy decision in product architecture is a transaction cost calculation, and falling API and integration costs continuously shift the efficient frontier toward external composition. More pointedly, the concept of 'market maker' the authors introduce—firms that benefit by owning the coordination infrastructure rather than competing within it—maps directly onto platform product strategy: the highest-leverage product direction question is not what features to build but whether your product is a participant in someone else's market or the mechanism that creates the market itself.