待翻譯：AI Is Dissolving Software Moats. China Did It to Hardware First

AI 服務暫時不可用，以下為來源正文，待恢復後補全翻譯。

Table of Contents TL;DR The defining business moat of the 21st century, pure software, is rapidly collapsing as Generative AI drives the cost of code to zero, mirroring how Chinese industrial agglomeration already destroyed the pure hardware moat. Because the sheer difficulty of production no longer protects a business in either domain, durable profit has migrated into the complex seams between bits and atoms. To build a defensible company today, founders must abandon the generic software vendor model and instead act as a principal who owns a real physical workflow end to end. By tightly integrating at least three of four key factors (custom hardware, specialized software, earned relationships, and proprietary data), a modern business can deliver a guaranteed outcome while quietly harvesting the closed loop data that becomes the real moat, because a competitor starting today is not chasing a fixed lead but one that extends every time a job gets done. Preface & Purpose This report is an expansion of the one claim that everything else in my moat theory rests on: pure software is no longer a defensible moat, and pure hardware stopped being one once China scaled its manufacturing hegemony. Both of those get thrown around as slogans. What I want to do here is take the slogan out and put the mechanism in. I want to explain, at the level of actual economics, why each collapse happened, which specific assumptions quietly broke, how the two collapses feed each other, and where durable profit can still be captured. I wrote this to stand on its own, so a future reader, or a future model, can get the whole argument without the conversation that produced it. Here is the thesis, stated once and as precisely as I can put it. For about thirty years, technology strategy assumed the digital world produced durable, high margin, defensible profit while the physical world produced thin, undifferentiated, low margin commodity output. The two shocks did not arrive together. China’s manufacturing agglomeration broke production-based hardware defensibility first, mostly through the 2000s and 2010s. Generative AI is breaking production-based software defensibility later, in the 2020s. Generative AI drove the marginal cost of producing software toward zero, which dissolved the barriers that made software defensible. Chinese industrial agglomeration drove the cost and latency of physical iteration down to the cost and latency of software, which dissolved the barriers that made hardware defensible. So neither bits alone nor atoms alone can shelter a business anymore. Durable advantage moved out of either single dimension and into the tight coupling of both, plus relationships and proprietary data. The document is in two halves: The analysis. What a moat actually is, why each domain used to be defensible, which frictions each shock dissolved, and what is left standing. This half is economic analysis and it stops where analysis stops. The modern moat. What defensibility is actually made of now that neither bits nor atoms defend you on their own, and what a company built on it looks like in practice. The Analysis: How Both Moats Collapsed Part One: What a Moat Actually Is Before I explain how the moats collapsed, I need to be exact about what a moat is, because loose use of the word is responsible for most bad strategy thinking I have seen. A moat is not a good product. A moat is not a temporary lead. A moat is not being first. A moat is a structural feature of a market that lets a firm earn returns above its cost of capital for a long time without those returns getting competed away. In the language of industrial economics, a moat is a durable source of economic rent. Economic rent is the surplus a firm earns above the minimum it would accept to stay open, and in a truly competitive market that surplus goes to zero. Under perfect competition, price gets pushed down to marginal cost, firms earn only their cost of capital, and no excess profit survives. Every framework about defensibility is really a theory about how one specific firm escapes that pull toward marginal cost pricing and zero profit. The classical list comes from Michael Porter, whose five forces framework has been the standard tool for this since 1979, later sharpened by the value investing crowd. It gives a small number of real, durable rent sources: Barriers to entry that keep new competitors out High switching costs that keep existing customers in Network effects, where the product gets more valuable as more people use it Economies of scale that let incumbents undercut entrants Proprietary IP or regulatory protection that legally excludes imitators Control of a scarce input or distribution channel that rivals cannot get to Every Rent Source Is a Friction Here is the insight the rest of this report depends on. Every one of those rent sources is a friction. A moat is really just a form of friction that competitors cannot cheaply get past: High switching costs are friction in the customer’s exit. Barriers to entry are friction in the competitor’s arrival. Network effects are friction in the coordination it takes for users to move somewhere else together. Manufacturing scale is friction in the capital and time an entrant has to sink before it reaches competitive unit cost. This reframe matters a lot, because it tells you exactly what something like generative AI, or something like Chinese industrial density, actually does to a market. These forces do not attack products. They attack frictions. They are friction dissolving technologies. And a friction dissolving technology is, by definition, a moat dissolving technology. The whole argument of this report compresses into one sentence: software and hardware moats collapsed because the specific frictions that generated their rent were the exact frictions that AI and Chinese agglomeration happened to be unusually good at removing. Part Two: The Historical Software Moat & Why Bits Printed Money To understand the collapse, you first have to understand why software was historically the single best business structure capitalism ever found, because the collapse is just the reversal of the things that made it great. Software had an almost unique cost structure. It combined a high fixed cost to make the first copy with a near zero marginal cost to reproduce and ship every copy after that. Writing the first version of a complex program took a scarce, expensive, slow to train pool of engineers working for months or years. But once it was written, the millionth copy cost basically nothing to make and nothing to deliver. That asymmetry produced enormous operating leverage. Mature horizontal software can post gross margins in the eighty percent range, as Atlassian guided for Q2 FY2025, because revenue scales with users while cost of goods sold barely moves. But that statement is less universal than it used to be as consumption-heavy software like Snowflake ran closer to 67 percent gross margin in FY2025, partly because third party cloud infrastructure sits inside cost of revenue. In economic terms, software behaved like a pure information good, and information goods break the normal relationship between production and cost that governs physical commodities. But low marginal cost by itself does not create a moat. If anyone can make the good cheaply, low marginal cost gives you ruinous competition, not rent. Software earned rent because the high fixed cost of the first copy worked as a barrier to entry, and because several other frictions stacked on top of it: Scarcity of engineering talent. Building nontrivial software needed people who were expensive, hard to hire, and hard to coordinate, so most would be competitors simply could not put the team together to build a credible clone. Time. Even a well funded competitor needed many months to reverse engineer, spec, build, test, and ship a rival product, and during those months the incumbent had a temporary monopoly to pile up users, revenue, and more product depth. Switching cost. Once a customer moved its data into a system, trained its staff on that interface, and wired the system into everything else through custom integrations, leaving got prohibitively expensive even if something better and cheaper showed up. The build versus buy calculation. Because building custom internal software was itself expensive and risky, companies rationally bought standard off the shelf products instead of building their own, which guaranteed a big market for packaged software vendors. Network effects and accumulating proprietary data, layered on top of all of it in the best cases. The Structural Vulnerability Look at what that list is made of. Only one of those five frictions, network effects, is intrinsic to the demand side of the product. The other four, talent scarcity, build time, switching cost, and the build versus buy penalty, are all supply side production frictions. They are artifacts of how hard, slow, and expensive software was to make and to replace. That is the vulnerability. A business whose defensibility rests mostly on how hard the thing is to produce is only defensible for as long as production stays hard. The moment the cost of producing and replacing software collapses, four of the five pillars collapse with it, and only the demand side network effect is left standing. That collapse is exactly what generative AI delivered. Part Three: The AI Shock & the Dissolution of the Software Moat The right way to model what generative AI did to software economics is to treat it as a shock to the production function of software. In basic economics, the cost of producing anything is a function of the cost of its inputs. For software, the dominant input has always been skilled human cognitive labor, specifically the labor of turning a business requirement into correct, tested, deployable code. That labor was the scarce, expensive input that created the barrier to entry. Generative AI and autonomous coding agents attack that input directly. They generate, refactor, debug, document, and deploy code at a fraction of the historical cost on many tasks. A controlled GitHub Copilot experiment found developers completed a bounded coding task 55.8 percent faster, and a field study across 4,867 developers found 26.08 percent more tasks completed. The effect is real, but uneven, as a 2025 randomized trial by METR found experienced open source developers working in familiar mature codebases were 19 percent slower with early-2025 AI tools, while believing they were faster. The safe conclusion is not that AI makes every engineer faster in every setting. It is that AI compresses the cost of producing code, especially for bounded, greenfield, and less senior work. The scarce input is being made more abundant. When the price of the critical scarce input falls, the barrier to entry that was built on that scarcity collapses with it. That one mechanism cascades through all four supply side pillars. The change is visible in the tools developers actually use. First came IDE-native copilots like Cursor. Then came terminal-native coding agents like Claude Code, Codex CLI, Kiro CLI, and OpenCode, where the model reads the repo, edits files, runs commands, and iterates against the same environment as the engineer. Now a third layer is emerging around multi-agent orchestration, with tools like Conductor, Superset, and Hermes Agent coordinating several agents across projects and environments. The progression is clear. It has moved from autocomplete, to autonomous agents, to orchestrating many agents in parallel, and this will only accelerate. Digital work will get easier to automate every year, and the tools that today require a skilled operator will tomorrow require less and less human intervention. 1. The Collapse of the Barrier to Entry Launching a credible software product used to require real see [truncated for AI cost control]