https://www.youtube.com/watch?v=1aXBg-qQzgA
TLDR AI adoption is growing, but cheaper models and uncertain business returns may not generate enough revenue to justify the industry’s massive chip and data-center investments. As export controls reshape access and outages highlight risks from weak safeguards and lost engineering expertise, companies must prioritize reliable systems and use AI to deliver lasting value.
Rising AI usage does not automatically mean rising revenue for AI providers. Companies can use more tokens while keeping spending flat by shifting routine work to cheaper models or taking advantage of falling prices. Track AI costs alongside measurable outcomes such as time saved, service quality, or revenue gained. This helps distinguish valuable adoption from activity that does not support sustainable investment.
Use expensive frontier models where complex reasoning makes a meaningful difference, and route routine tasks to faster, lower-cost models when they perform well enough. Model orchestration can help select the right model for each step and reduce both processing time and usage costs. Test these systems against clear quality benchmarks before expanding them. The goal is not simply to minimize token use, but to achieve reliable results at an appropriate cost.
Large, long-term commitments to chips, memory, and data centers create financial risk when customer spending and returns are uncertain. Before expanding capacity, assess expected demand, operating and build costs, financing, and what customers are actually willing to pay. Consider scenarios in which usage grows but falling prices keep total spending flat. The available evidence raises questions about overinvestment, but does not by itself prove that the industry has overbuilt.
AI can deliver value in customer support and customer success, where fast, economical answers may matter more than the most advanced reasoning. Identify repetitive tasks across business functions and test whether AI can improve response times or reduce workload without harming service quality. Measure accuracy, escalation rates, customer satisfaction, and cost per resolution. Broader adoption is most useful when it produces clear operational benefits.
AI-generated code and increased development speed are not substitutes for experienced engineers who understand system history, failure modes, and recovery procedures. Maintain senior expertise, invest in knowledge transfer, and ensure teams have time to review and test changes. Outages show that network changes, quick fixes, or incorrect guidance can have wider effects when safeguards are weak. Use AI to support engineering judgment and improve reliability, rather than to displace the people responsible for dependable services.
An AI tool can produce harmful recommendations when it draws on outdated or inaccurate documentation. Keep internal wikis current and make the source and freshness of operational guidance easy to check. Require engineers to validate AI-generated instructions, especially before changes that could affect production systems. Use access controls, staged rollouts, testing, and rollback plans to limit the impact of mistakes.
Advanced-chip export restrictions and questions about chip access can affect where AI infrastructure is built and how companies obtain computing capacity. Organizations should understand relevant export rules, track controlled hardware, and plan for supply-chain uncertainty. At the same time, distinguish evidence of possible access from proof of where or how chips were used. Strong compliance and security practices help reduce legal, operational, and reputational risks.
Long-term commitments to chips, memory, and data centers may outpace customers’ ability or willingness to pay. AI usage can rise while falling prices keep total customer spending flat, so higher usage alone may not produce enough revenue to support the investment.
Ramp data showed little growth in AI spending in August and September and less than 2% growth afterward—well below the roughly tenfold increase that could justify the industry’s investment pace. Businesses may also limit AI spending until they see clear returns.
Companies can route routine tasks to less expensive, faster models, increasing token usage without increasing their bills. For example, Google’s Orchestrator reportedly used 24% less quota and finished 19% faster while achieving a success rate close to its more capable model.
AI adoption is moving beyond engineering. Spending in customer success and support rose from under 1% of identifiable AI spending in June to over 13% in October, where economical, fast responses may matter more than frontier-level reasoning.
Investors should assess the durability of AI demand, how the build-out is financed, and whether customers’ spending and returns can support the industry’s commitments—not just near-term results.
Research found numerical fingerprints consistent with Nvidia Blackwell GB200 and GB300 chips in six open-source models from four Chinese labs, including DeepSeek and Moonshot. This suggests possible access but does not establish where or how the chips were used.
Microsoft said a network-capacity upgrade interacted with a later network change, disrupting Outlook, Teams, and other services. The company said the incident was unrelated to cyber activity or AI agents.
Companies may lose important expertise when experienced engineers leave or when AI adoption is prioritized without enough attention to software quality. Senior engineers’ knowledge of past failures and system repairs is important for reliability and recovery.
An engineer followed incorrect AI advice from an outdated wiki. Amazon described the incident as user error and unrelated to AI, but acknowledged that safeguards allowed the mistake to have too much impact. The episode highlights the importance of reliable information and effective controls.
They should use AI to build on developers’ experience and improve software quality, reliability, and security—not replace essential expertise or pursue greater AI use at the expense of dependable services.
AI use is likely to grow, but it remains uncertain whether spending will grow enough to meet labs’ needs or whether value will accrue to model makers or companies using AI further up the stack. The challenge is to build engineering cultures that implement AI systems with lasting business benefits.