The Adjacent Brief

TL;DR: ChatGPT crossed 1 billion monthly active users while Claude's user base grew 640% year-over-year — consumer AI adoption numbers at a scale most enterprise budgets haven't prepared for. Indian IT firms spent $7.1B on acquisitions to buy client relationships that organic growth can no longer deliver. Google offered Play Store developers cash for their codebases to feed model training. Two separate industries reaching for the same lever when their existing growth model stops working.

Worth Reading

Commerce Rewired

When organic growth stalls, you buy your way in

Indian IT services firms — Infosys, Wipro, and peers — have spent $7.1B on acquisitions since the start of 2025 to secure client access that AI-led pricing pressure has made harder to win on margin. When AI commoditizes the billable hour, the defensible asset becomes the client relationship itself. M&A is how you buy a decade of trust in a quarter. Whether $7.1B buys enough of it — or whether the underlying margin problem reasserts itself inside the acquired books — is the question the next two earnings cycles will answer.

Pricing models that misalign with how people actually use things

Azeem Azhar's piece in Exponential View on token bundle pricing asks the right question: gym-membership economics work when the provider benefits from underuse, but AI's value is realized only through use. Bundle a user into 100,000 tokens a month and they either hit the ceiling and churn, or underconsume and never build the habit. Neither outcome serves the provider's long-term interest. This tension sits under every AI subscription decision an enterprise buyer is making right now.

The codebase acquisition nobody announced

Google's offer to Play Store developers — pay for codebase access, use it to train AI tools — is a different species of data acquisition than scraping or licensing. It's transactional and voluntary, which insulates Google from the legal exposure that scraping creates. The "confidential content offer pilot" framing tells you everything about Google's appetite for scrutiny on this. Developers who accept are essentially licensing their IP twice: once to Google Play for distribution, and again to Google's training pipeline for model improvement.

Connected World

Hardware as environmental theater, or hardware as actual solution

Google's commitment to reduce data center water consumption is worth reading alongside the Semianalysis case for space datacenters — two very different answers to the same supply constraint. Google's approach is operational: better cooling, smarter siting, water recycling. The space datacenter argument is infrastructural: remove the problem by removing the facility from the biosphere. Both responses reflect genuine pressure. Google's commitment is measurable and auditable this decade; orbital compute is a capital-allocation argument for the 2030s.

Thermal design as product philosophy

Microsoft's RTX Dev Box — 1,000 deliberate perforations as its defining design feature — is a minor story on its own, but it sits inside a larger one: hardware built around AI workloads generates heat at a different order of magnitude than hardware built around productivity software. The thermal engineering challenge isn't cosmetic. When the primary workload is model inference rather than document editing, the physical design of the device becomes a constraint on what it can actually do. Microsoft is building public acknowledgment of that into the chassis itself.

Culture & Signal

The AI jobs debate is more useful when economists run it

Labor economist Kathryn Anne Edwards, in a Q&A with Casey Newton at Platformer, makes the case against AI job apocalypse predictions while simultaneously arguing the US has inadequate policy infrastructure to handle actual displacement if it does arrive. That's a more precise position than most of the discourse manages: "the panic is overblown" and "we're underprepared" are both true at once, and conflating them makes policy harder. AI job displacement, if it comes, will be sectoral and asynchronous — the same pattern as previous automation waves — not a simultaneous collapse that any single policy lever could address.

Environmental cost as the next AI credibility question

The piece Your AI Use Is Destroying the Planet from Shae O. on Substack is representative of a widening genre — consumer-facing moral accounting for AI's resource footprint. Whether the per-query numbers hold up to scrutiny matters less than the cultural function the argument is serving: environmental framing is becoming the vocabulary through which AI skepticism gets expressed outside tech circles. Brands that have made AI use a public part of their identity should expect this framing to come up in ways that press releases about "responsible AI" don't adequately address.

Brand & Growth

Ad creative technology is perennially almost there

Forrester's post on ad creative as a technology problem covers ground the industry has been covering for a decade: dynamic creative optimization, AI-generated variants, personalization at scale. The persistent gap between what the technology promises and what gets deployed at scale is organizational, not technical. Creative teams, media teams, and data teams are rarely integrated enough to operationalize the loop. AI makes the generation side faster; it doesn't resolve the internal structure that makes deployment slow. Brands treating this as a tool selection question are solving the wrong part of the problem.

Machines & Minds

The enterprise AI shift from demo to production has a specific mechanism

Custom model training on internal, governed data — not fine-tuning a public model on scraped inputs — is what enterprise AI deployments look like when they move from proof-of-concept to production, per reporting from SiliconANGLE out of Snowflake Summit. The difference matters: a generic model integrated into a workflow is still someone else's model operating on your data. A custom-trained model on governed internal data is infrastructure you own. The companies that cleared the procurement, legal, and data governance hurdles to get there are building something that won't be easily ripped out — which is exactly what enterprise software buyers want when they're committing to a platform.

Microsoft is building an OS for a world where agents are the workload

Project Solara — Microsoft's operating system designed around AI agents as primary workload rather than applications — is the architectural consequence of the bet Microsoft made when it embedded Copilot across its product line. If agents become the interface layer, the OS underneath them needs to be designed for agent orchestration, not app management. This is early and the product details remain thin, but the directional claim is clear: Microsoft is treating the current app-centric OS model as transitional, not permanent. That's a significant architectural stake to plant.

Open-source AI in the hands of a worm author

University of Toronto researchers built an AI-powered worm that uses open-source LLMs to customize attacks per target system, rather than deploying fixed payloads. The New York Times piece is careful to note this is a research demonstration, not a deployed threat. But the mechanism — per-target adaptation, open-source model, no novel capability required — describes an attack surface that scales with model availability, not attacker sophistication. That's a different risk profile than anything the prior generation of malware created.

The New Consumer

A billion users is a distribution fact, not a product verdict

ChatGPT reaching 1 billion monthly active users — per Sensor Tower data reported by Reuters — is a genuine scale milestone. The 62% year-over-year growth in Q2 to date, and Claude's 640% growth to 56 million MAUs, show that consumer AI is still in a growth phase where both the dominant player and smaller alternatives are adding users at the same time. That's a healthy market structure for now. The number to watch next is retention at six months and revenue per user, neither of which the Sensor Tower data addresses. A billion people opened the app; how many built a habit is a different question.


16 articles across 6 themes · 15 sources · Powered by Folo + Claude