Skip to content
The Shift

xAI Macrohard: Attack of the Clones

With Macrohard, Elon Musk is stating plainly what anyone building with agents already knows: software, and even entire companies, are now cloneable by AI.

Photo of Aron Brand
4 min read
xAI Macrohard: Attack of the Clones

With Macrohard, Elon Musk is stating plainly what anyone building with agents already knows: software, and even entire companies, are now cloneable by AI.

That sounds extreme. It is not.

A modern digital company takes inputs such as requirements, customer tickets, product usage, competitor signals, logs, and pricing feedback, and produces outputs such as shipped features, uptime, onboarding success, renewals, and revenue. When those mappings become observable, the company starts to look less like an institution and more like a function.

AI agents change the cost of recreating that function. They reduce the marginal cost of producing code, tests, documentation, integrations, and operational responses. They also reduce the fixed cost of hiring and coordinating people to do that work.

Most people think about cloning as feature copying. That is a category error. Feature copying happens when human teams chase roadmaps. Company cloning happens when an automated system can approximate the full input-output behavior of a business. It does not need access to your code. It needs a sufficiently rich view of your interfaces, workflows, customer-facing behavior, and operating cadence.

Once that threshold is crossed, a swarm of agents use a clean-room approach to reproduce the firm’s outputs at lower cost.

In software-heavy categories like SaaS, entry barriers fall further. SaaS has three characteristics that make it unusually exposed in an AI-driven production era:

  1. 01

    It is purely digital

  2. 02

    Its value proposition is exposed through UI and APIs

    Workflows, schemas, and logic are easily observable from the outside.

  3. 03

    It is priced as if code were scarce

When the scarcity assumption breaks, margin structure follows. If many sellers can offer near-substitutes, feature parity no longer supports premium pricing. Returns concentrate in whatever remains scarce. Scarcity migrates from code to complements:

  1. Distribution
  2. Network effects and ecosystem
  3. Data rights
  4. Compliance and trust
  5. Defensible deep technologies.

Only one of these moats needs to be strong. But at least one must exist.

The profit pool does not disappear. The SaaS market does not collapse. Profit simply relocates to what cannot be cheaply reproduced.

Automated company cloning is unprecedented. IP regimes were designed around human-scale copying and human-scale competition.

Two implications follow.

First, incumbents will push back against AI-native firms that clone their businesses, and they will reach first for legal weapons. Patents will be asserted. EULAs will prohibit scraping, reverse engineering, and automated access. But law moves slower than code. Software patents are narrow and litigated for years. Contract restrictions are uneven across jurisdictions and hard to prove when competitors learn from observable behavior rather than source code. These tools create friction, not scarcity. They arrive after markets have repriced and rarely stop replication outright.

Second, the incentive landscape changes. If it becomes trivial to clone the functional outputs of a young SaaS firm that has a great idea, the expected value of building code-first businesses declines. That is not a moral judgment. It is economics. When appropriation becomes faster and cheaper, rational actors invest less in innovations that can be quickly reproduced, unless they secure a moat elsewhere

What should companies do now?

If you run or fund software businesses, the adaptation plan is straightforward, even if uncomfortable.

  1. Stop treating code - or business processes - as the moat.Assume they will be replicated.
  2. Turn your early-mover experience into proprietary datasets that can be used to deliver superior outcomes.
  3. Engineer switching costs through network effects and deep integrations.Become part of the customer’s operating system, not just another application. Migration cost is one of the few durable defenses in commodity markets.
  4. Shift pricing toward outcomes.Outcome-based or usage-based pricing aligns with where durable value will remain.
  5. Own distribution where possible.Partnerships, bundling, and embedded channels matter more when product parity is cheap.
  6. Use patents and EULAs as delay tactics, not salvation.They can buy time. Time only matters if you use it to build a moat that exists before the lawsuits.

Macrohard is not important because it involves Elon. It is important because it gives a name to what those building with agents already see: once the inputs and outputs of a digital firm can be learned and optimized by machines, that firm becomes reproducible.

So, if you are a builder or investor you need to ask yourself this: When code becomes abundant, what defensible asset in your business survives replication?

Originally published on LinkedIn.

The Shift, in your inbox

Occasional essays on AI, cloud, and the systems shaping what comes next. Subscribe on LinkedIn — no spam, unfollow anytime.

Prefer a reader? RSS delivers every new essay.

Keep reading

10 min read

Every Reachable System Is Now Worth Attacking

In 1883 a Dutch linguist and cryptographer named Auguste Kerckhoffs laid down what became the closest thing computer security has to scripture: a system should remain secure even if everything about it, save the key, is public knowledge.

Search titles, topics, and article text.