The Platform Race

TAM-CV.11 · The Capital View · The Approximate Mind

The previous essay described the management strip: PE acquires a mid-market firm, installs the AI coordination layer, removes the management positions, captures the margin. The same structural insight the Coordination cluster described as liberation, capital deployed as arbitrage.

But the management strip is a deal-by-deal play. Nora’s fund buys one company, transforms it, sells it. Buy another. Transform it. Sell it. The returns are excellent but the scale is linear. Each deal requires an acquisition, an integration, a hold period, an exit. The fund deploys capital one company at a time.

Marcus is thinking about something else.

If the management strip works because of the AI coordination layer, then the coordination layer is the most valuable asset in the transaction. Not the company. Not the customer relationships. Not the fifteen trucks in the parking lot. The layer that makes the coordination of all of those things performable without the fourteen people who used to perform it.

The dual-asset insight from CV.06 applies with even greater force here than it did in the care services arc. In care services, the orchestration platform was valuable because it coordinated across a complex human delivery system. In the management strip, the coordination layer is valuable because it replaces a structural feature of every mid-market firm in the economy.

There are approximately 200,000 companies in the United States with revenue between $10 million and $100 million. Most have management layers that look like the building supply distributor Nora transformed: organically accumulated, performing real coordination, addressable by AI. The coordination layer that can strip the management from one of these companies can strip it from all of them.

The company is worth one exit. The platform is worth two hundred thousand.

Marcus understood this six months before most of his peers. He is not the only one who understands it now.

The Three Competitors

#

The race to own the coordination infrastructure has three entrants, and they are competing from different positions with different logics.

Private equity sees the coordination layer as a value creation tool. The fund builds or acquires the platform, deploys it across its portfolio, and captures value in two ways: the operational improvement in each portfolio company and the independent value of the platform at exit. This is the dual-asset structure described in CV.06, applied not to care services but to the full landscape of mid-market operations. PE’s advantage is deal flow. It has the relationships with the companies that need the coordination layer. It has the operating partners who know how to implement it. It has the institutional infrastructure for rapid deployment across a portfolio.

PE’s limitation is fund structure. A PE fund has a defined life, typically ten years. It must deploy, improve, and exit within that window. The coordination platform, if it is valuable enough, may be worth holding indefinitely, but the fund’s structure requires a sale. The most valuable asset the fund creates is the asset the fund is least equipped to own permanently.

Venture capital sees the coordination layer as a platform business. The VC thesis is to fund a startup that builds the coordination layer as a product, sells it to mid-market companies on a SaaS model, and grows toward a market position where it becomes the default infrastructure for operational coordination. The exit is an IPO or a strategic acquisition by a technology company. VC’s advantage is patience with growth. It can fund losses for years while the platform acquires customers and builds the data moat that makes it defensible. The SaaS model produces recurring revenue that the public markets reward with technology multiples.

VC’s limitation is that the product has to be sold. PE deploys the coordination layer into companies it already owns. VC must convince companies to adopt it voluntarily, which means the product has to be better than the alternative, and the alternative is the management layer the company already has. Mid-market CEOs do not wake up looking for AI platforms that eliminate their middle managers. They wake up looking for ways to solve specific operational problems. The VC-backed platform must translate a structural argument about the optionality of management into a product pitch that a regional distributor in Ohio will pay for, and that translation is harder than VC pitch decks typically acknowledge.

Big Tech sees the coordination layer as an extension of its existing infrastructure. Microsoft, Google, Amazon, and the large AI companies are building general-purpose AI platforms that can be configured for operational coordination. They do not need to build a specialized coordination product. They need to make their existing platforms capable enough that the coordination use case emerges from general capability. Their advantage is distribution and integration: the mid-market company already uses Microsoft 365 or Google Workspace or AWS. The coordination layer that plugs into the existing stack has a deployment advantage that no standalone product can match.

Big Tech’s limitation is attention. The mid-market operational coordination use case is small relative to the enterprise market that drives their revenue. They will build the capability. They will not focus on the specific needs of a forty-seven-person building supply distributor in the mid-Atlantic. The product will be general enough to be useful and not specific enough to be transformative. The gap between general and specific is where the PE and VC plays live.

The Cooperative Alternative

#

There is a fourth entrant, and it is the one the other three are not tracking.

The Coordination cluster described producer cooperatives building their own AI coordination layers. Charlene’s factory in Lordstown, coordinated by AI, owned by the workers. Ravi’s network in Tirupur, connecting fifty manufacturers to consumers, each intermediary’s margin returned to the producers. Sunita’s line item on page forty-seven, funding public coordination infrastructure that any cooperative could use.

The cooperative’s coordination layer is the same technology as PE’s coordination layer and VC’s platform and Big Tech’s infrastructure product. The AI that schedules Nora’s transformed distributor’s trucks is not materially different from the AI that schedules the Lordstown cooperative’s production line. The coordination function is the coordination function. The technology does not care who owns it.

What differs is the ownership structure and therefore the economics. PE’s coordination layer generates return for the fund’s limited partners. VC’s platform generates return for the venture investors. Big Tech’s infrastructure generates revenue for shareholders. The cooperative’s coordination layer generates income for the workers.

The same technology, the same function, four different ownership structures, four different distributions of the value the coordination creates.

The cooperative has a structural disadvantage in the race: it has no institutional mechanism for rapid deployment. PE has fund capital and deal teams. VC has portfolio support and network effects. Big Tech has distribution and integration. The cooperative has meetings in rooms with plastic chairs and insufficient ventilation, where the manufacturers argue about order allocation and the drivers argue about route assignments and the farmers sit quietly because they are accustomed to having no voice.

The cooperative also has a structural advantage that none of the three capital entrants can replicate.

The cooperative cannot be acquired.

PE’s platform, VC’s startup, and Big Tech’s product are all ownable by someone who is not the user. They can be bought, merged, redirected, or shut down by the entity that owns them. The coordination infrastructure that mid-market companies depend on can change hands in a transaction the companies have no say in.

The cooperative’s coordination layer is owned by its users. It cannot be acquired because the owners are not selling. It cannot be redirected because the governance is collective. It cannot be shut down without the consent of the people who depend on it. The cooperative model produces a coordination infrastructure that is, by design, not available for enclosure.

This is not an economic argument. It is a structural one. The cooperative is the entity type that the capital race cannot reach. Not because it is protected by regulation. Because it is protected by its own architecture.

The Enclosure Pattern

#

Here is what is happening, seen from above.

The Coordination cluster described an unlock. AI makes the management layer optional. Workers could own the coordination and keep the surplus. The insight was presented as a possibility, tested through specific people in specific places, held with honest uncertainty about whether it would work.

Capital read the same insight and began moving. Not to contest the argument. To preempt the outcome.

If PE, VC, and Big Tech can establish proprietary ownership of the coordination infrastructure before cooperatives establish collective ownership, the market structure hardens around capital’s version. The mid-market company that adopts PE’s coordination layer becomes dependent on it. The dependency deepens as the company’s operations are reshaped around the platform’s logic. Switching costs rise. The platform becomes infrastructure in the sense Marcus described: the thing that other things depend on, the layer beneath the service layer.

Once the coordination infrastructure is privately owned and widely deployed, the cooperative alternative becomes harder to establish. Not impossible. But the cooperative that forms in a market where most companies already run on a proprietary coordination platform faces a competitive environment that has been structured by the platform. The data advantages, the integration depth, the ecosystem of complementary services, all compound in favor of the incumbent platform and against the cooperative’s independent layer.

This is the enclosure of coordination applied to the coordination template itself. Not enclosing the daughter’s care orchestration. Not enclosing the management layer of a specific firm. Enclosing the infrastructure that enables the enclosure.

It is enclosure at the architectural level. The most consequential round, because it determines the terms on which all subsequent coordination occurs.

CV.07 named the pattern: AI makes coordination legible, capital encloses what becomes legible. CV.10 applied it to the firm. This essay applies it to the platform. Each round is deeper. Each round is harder to reverse.

The Rails

#

The Coordination cluster’s most structurally interesting essay was Sunita’s. The Government Question described India’s public digital infrastructure, built for other purposes, turning out to be precisely the rails the cooperative coordination layer needed. UPI for payments. ONDC for commerce. Aadhaar for identity. Public rails. Not owned by Amazon or Google or any PE fund. Owned by the state, available to anyone.

The cooperative coordination layer running on public rails is the structure that the capital race cannot enclose. Not because the cooperative is large enough to resist. Because the rails themselves are not available for purchase.

In the United States, those rails do not exist. There is no public digital commerce protocol. No zero-cost payment infrastructure. No universal digital identity. The American mid-market company that wants an AI coordination layer must buy it from PE, license it from a VC-backed startup, or adopt it from Big Tech. The cooperative alternative requires the cooperative to build not only its own coordination layer but its own infrastructure, which compounds the capital disadvantage and the speed disadvantage and makes the race even more asymmetric.

This is the policy dimension that the Coordination cluster named and the Capital View must acknowledge. The race between capital and the cooperative is not conducted on neutral ground. The ground is shaped by public infrastructure decisions that have already been made, or not made, and those decisions determine whether the cooperative has rails to run on or must build its own track.

Sunita’s fourteen crore rupees is not buying a cooperative. It is buying a template on public rails. If the template works, any cooperative in India can adopt it at near-zero cost. The propagation is free because the infrastructure is public.

In the United States, the propagation is not free because the infrastructure is private. Every cooperative must license the technology, pay the platform fee, and accept the dependency. The race is not just speed vs. durability. It is private infrastructure vs. public infrastructure, and the country that has public infrastructure gives the cooperative a structural advantage that no amount of governance meetings with plastic chairs can produce on their own.

Marcus does not think about public digital infrastructure. It is not in his frame. His frame is deal structure, return modeling, platform economics. Within his frame, the analysis is correct and the play is sound: build the coordination platform, deploy it across the portfolio, establish it as the default, exit at technology multiples.

He is not wrong about the play. He may be wrong about the game.

The Window

#

The window is the same one named in the previous essay, but seen from the platform level rather than the deal level.

If capital establishes proprietary ownership of the dominant coordination platform within the next three to five years, the market structure hardens. The coordination economy runs on private rails. Every firm, every cooperative, every solo operator that needs AI coordination rents it from the entity that built and owns the platform. The toll booth that the Coordination cluster described as removable returns at the architectural level, and at the architectural level it is far more durable than any individual intermediary in any individual supply chain.

If cooperatives, supported by public infrastructure where it exists and by patient capital where it does not, establish viable collective ownership of coordination infrastructure within the same window, the market structure bifurcates. Private and cooperative coordination coexist. Neither dominates. The choice between them becomes a structural feature of the economy rather than a transitional question.

The third possibility is that Big Tech wins by default. Not through deliberate strategy but through the gravitational pull of existing market position. The coordination capability becomes a feature of general-purpose platforms rather than a specialized product. Microsoft embeds it in 365. Google embeds it in Workspace. Amazon embeds it in AWS. The mid-market company does not choose a coordination platform. It uses the one that is already in its stack. The race is over before most of the competitors realize it was a race.

This third possibility is the one that worries Marcus most, because it is the one where his platform becomes a feature rather than a product. The thing he is building, with its specific insight into mid-market operations and its accumulated data from Nora’s portfolio transformations, would be competing against the gravitational pull of platforms that have distribution advantages no standalone product can overcome.

He mentioned this once, briefly, at the end of a conversation about exit timing. He said: “The question is whether we are building a company or a feature.”

He did not answer his own question. The trawler was still on the windowsill. He looked at it for a moment, which is the first time I have seen him look at it deliberately rather than catching it in his peripheral vision.

Then he said: “It depends on who gets there first.”

I asked him who he meant.

“Everyone,” he said. “All of us. The question is which version of the coordination economy we end up with. The one someone owns, or the one nobody owns.”

He paused.

“I am building the one someone owns. That is what I know how to do.”

The honesty was specific and unsettling. He was not defending his position. He was locating it. He knows what he is building. He knows there is another version. He is building his version because it is the version his institutional structure can produce, the version his capital can fund, the version his operating partners can deploy. Whether it is the version the world needs is a question his structure is not designed to answer.

The Coordination cluster asked the question from the other side. This arc asks it from his.

This is the eleventh essay in The Capital View, examining the competition to own the AI coordination infrastructure that enables both the management strip described in TAM-CV.10 and the cooperative model described in the Coordination cluster. The three capital entrants, PE, VC, and Big Tech, are racing to establish proprietary ownership of the coordination economy’s infrastructure. The cooperative alternative, described in TAM-RIM.6-04 through TAM-RIM.6-08, offers a model where the users own the infrastructure collectively. The race is between private and collective ownership of the most consequential economic infrastructure since the internet, and its outcome depends on speed, policy, and the presence or absence of public rails. The essay that follows (TAM-CV.12) holds the genuine uncertainty about which model prevails. This essay connects to the dual-asset structure in TAM-CV.06, applied here to the coordination platform itself; to the enclosure of coordination in TAM-CV.07, applied at the architectural level; to the government question in TAM-RIM.6-08, where Sunita’s line item funds public coordination infrastructure; to the new collective in TAM-RIM.6-07, where the cooperative model extends across the supply chain; to the toll booth economy in TAM-033 and TAM-051; and to the choreographed market in TAM-051.

References

#

Platform Economics and Market Structure

Evans, David S., and Richard Schmalensee. Matchmakers: The New Economics of Multisided Platforms. Harvard Business Review Press, 2016.

Parker, Geoffrey G., et al. Platform Revolution: How Networked Markets Are Transforming the Economy and How to Make Them Work for You. W. W. Norton, 2016.

Zuboff, Shoshana. The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power. PublicAffairs, 2019.

Enclosure, Commons, and Infrastructure

Boyle, James. The Public Domain: Enclosing the Commons of the Mind. Yale University Press, 2008.

Frischmann, Brett M. Infrastructure: The Social Value of Shared Resources. Oxford University Press, 2012.

Ostrom, Elinor. Governing the Commons: The Evolution of Institutions for Collective Action. Cambridge University Press, 1990.

Digital Public Infrastructure

Nilekani, Nandan, and Viral Shah. Rebooting India: Realizing a Billion Aspirations. Penguin, 2015.

Raghavan, Srinath. “India’s Digital Public Infrastructure: Aadhaar, UPI, and the Emerging Stack.” Carnegie Endowment for International Peace, 2023.

Venture Capital, Big Tech, and Market Power

Kenney, Martin, and John Zysman. “The Rise of the Platform Economy.” Issues in Science and Technology, vol. 32, no. 3, 2016, pp. 61-69.

Khan, Lina M. “Amazon’s Antitrust Paradox.” Yale Law Journal, vol. 126, no. 3, 2017, pp. 710-805.

Wu, Tim. The Curse of Bigness: Antitrust in the New Gilded Age. Columbia Global Reports, 2018.

Worker Cooperatives and Alternative Ownership

Cheney, George. Values at Work: Employee Participation Meets Market Pressure at Mondragon. Cornell University Press, 1999.

Scholz, Trebor. Platform Cooperativism: Challenging the Corporate Sharing Economy. Rosa Luxemburg Stiftung, 2016.