Anthropic’s Claude popularity with paying consumers is skyrocketing

TechCrunch AI reported: Anthropic refused to allow the DoD to use its AI models for lethal autonomous operations (AI potentially killing people) or mass surveillance of American citizens. That beef grew increasingly public, with Anthropic's CEO Dario Amodei issuing a making firm public statement on February 26 amid the DoD's threats to hurt Anthropic's business by labeling the company a supply risk. Which the DoD did. Lawsuits are now flying, although a federal judge this week temporarily blocked the department's designation. New user growth climbed sharply during this period. The increase is especially pronounced between those late January media reports and Amodei's statement on February 26. Beyond the drama, Claude Code and Claude Cowork — developer and productivity tools released in January — have been drivers of subscriptions. The Computer Use feature, released this week, has also sparked a surge, Anthropic tells TechCrunch. That feature allows Claude to navigate a computer independently — clicking, scrolling, and taking actions on its own. It works with Dispatch, which lets users assign tasks from their phones. These features are not available to free-tier users. Still, for all of Anthropic's growth among U.S. consumers willing to pay for AI, Claude remains a long way behind ChatGPT. April 30 San Francisco, CA StrictlyVC kicks off the year in SF. G.

The story lands in a market where demand is already assumed. The more useful question is whether the supporting layer around cloud infrastructure is flexible enough to turn that demand into available capacity. The constraint is execution. AI infrastructure demand is visible, but turning it into usable capacity requires power, equipment, permitting, supply-chain coordination, and customers that are ready to commit.

The pressure point is timing. Execution speed, supply-chain coordination, and regional delivery risk remain more important than headline ambition.

That is why operators, cloud buyers, and investors are watching the operating details more closely than the headline. The winner is usually not the party with the loudest demand signal, but the one that removes bottlenecks soon enough to deliver capacity when customers need it.

The financial question is whether this development improves pricing power, locks in scarce capacity, or exposes execution risk that the market may still be discounting, the operating question is procurement timing, facility readiness, network design, and the likelihood that adjacent constraints will slow realized deployment, and the customer question is whether this changes build sequencing, partner dependence, or the economics of scaling regions and clusters over the next few quarters.

This is where AI infrastructure differs from ordinary software growth. Capacity has to be financed, permitted, powered, cooled, connected, staffed, and then sold into real workloads before the economics are visible.

The practical read is that infrastructure advantage is becoming more local and more operational. Two companies can chase the same AI demand and end up with very different outcomes if one has better access to power, more credible delivery dates, or a cleaner path through procurement and permitting.

The next signal to watch is the next disclosures on customer commitments, infrastructure readiness, and any evidence that power, cooling, silicon supply, or permitting becomes the real gating factor. The next test is whether the project details support the ambition in the announcement.