Software – Stacking Trades

Intel Joins Terafab. Now the Hard Part Begins.

Stacking Trades — Wed, 08 Apr 2026 18:18:52 +0000

For weeks, Terafab read like a Musk announcement in search of an execution plan. The March 21 unveiling was characteristically ambitious: Tesla, SpaceX, and xAI would construct the largest semiconductor facility ever built in Austin, Texas, targeting one terawatt of annual compute output, combining logic, memory, and packaging under one roof, and breaking from the global foundry supply chain that every other AI hardware company still depends on. It was a compelling vision with one conspicuous gap. None of the three companies announcing it had ever built a chip fab.

That gap closed on April 7, when Intel announced it was joining the project. The announcement arrived as a post on X rather than a press release: “Our ability to design, fabricate, and package ultra-high-performance chips at scale will help accelerate Terafab’s aim to produce 1 TW/year of compute.” Intel CEO Lip-Bu Tan followed with his own post describing Musk as having “a proven track record of reimagining entire industries” and calling Terafab “a step change in how silicon logic, memory and packaging will get built in the future.” Intel shares rose roughly 4% on the news, finishing the day near their 52-week high of $54.60.

The stock reaction is the easiest part to explain. The strategic logic, for both parties, is more complicated, and more important for investors trying to assess whether this partnership changes Intel’s medium-term trajectory or simply adds to a long list of announcements the company has made in the past 18 months that have yet to show up in the revenue line.

What Intel Actually Brings to the Table

When Intel said it would help “refactor silicon fab technology,” the phrasing was deliberate and specific. Refactoring in semiconductor development refers to redesigning or improving existing manufacturing processes, not building from scratch. Scott Bickley, an advisory fellow at Info-Tech Research Group, described the language as implying “a potential redesign or improvement of existing methods” — a narrower scope than the greenfield chip factory that Musk’s March announcement had suggested.

What Intel concretely provides is an end-to-end semiconductor manufacturing capability that no other American company can currently match. Its 18A process node, the most advanced manufacturing technology developed on U.S. soil, is already running at its Chandler, Arizona facility at approximately 40,000 wafer starts per month, and was opened to external customers for the first time earlier this year after being largely reserved for internal use. Terafab, targeting 2-nanometer-class process technology, represents a natural fit for 18A’s capabilities. Intel also brings advanced chip packaging expertise, combining multiple chiplets into high-performance units, which Lip-Bu Tan has called “a very big differentiator” in the current AI hardware race.

The project envisions two fabrication facilities on the grounds of Giga Texas in Austin, one oriented toward automotive and robotics chips, including Tesla’s FSD hardware, Optimus humanoid robots, and Cybercab, and the other focused on high-performance AI data center infrastructure including designs intended for SpaceX’s proposed space-based data centers. According to reporting from The Tech Portal, Terafab plans to start at 100,000 wafers per month in its pilot phase, with total initial capital costs estimated between $20 billion and $25 billion.

“Terafab represents a step change in how silicon logic, memory and packaging will get built in the future.”
— Lip-Bu Tan, CEO, Intel, April 7, 2026, via post on X

What Intel Needs More Than the Announcement

The Intel of 2026 is a company that has been saying the right things for two years and struggling to make them show up in the numbers. Its Q4 2025 earnings, filed as an 8-K with the SEC, showed revenue of $13.7 billion, down 4% year-over-year and Intel’s weakest full-year result since 2010 at $52.9 billion. The Intel Foundry segment, the linchpin of Lip-Bu Tan’s strategic pivot, generated $4.5 billion in quarterly revenue against an operating loss of $2.5 billion, a figure that widened by $188 million from the prior quarter due to the early ramp of the 18A process node. External foundry revenue in Q4 was $222 million, almost entirely from U.S. government projects and residual Altera activity after that subsidiary’s partial sale.

That $222 million figure is the most important number in Intel’s foundry story, and it is the one Terafab is designed to change. Intel has been building foundry capacity for two years with effectively no major commercial anchor customers. Its SEC filings explicitly flagged this as a risk: the company had not secured external foundry customers at meaningful scale on any of its process nodes. Lip-Bu Tan acknowledged on the Q4 earnings call that Intel had “invested too much, too fast” given the demand it had actually secured. The U.S. government holds a roughly 8.4% stake in the company, acquired through an approximately $9 billion equity investment, partly as a strategic backstop for domestic semiconductor capacity. That support has kept the foundry strategy alive. It has not replaced the commercial anchor customer Intel needs to justify its capital program at scale.

Terafab is that anchor customer, in theory. Analysts who follow Intel’s foundry strategy note that landing SpaceX, Tesla, and xAI as a combined demand source would provide the volume and technical complexity that Intel’s internal roadmap cannot generate on its own. The question is whether the partnership converts from a handshake-and-X-post to a signed foundry services agreement with committed volumes, and on what timeline.

The TSMC Dependency Musk Is Trying to Break

To understand why Terafab exists, it helps to understand the supply chain problem it is solving. Every major AI chip company, including Nvidia, AMD, Broadcom, and the in-house design teams at Google, Amazon, and Microsoft, currently depends on TSMC for advanced node manufacturing. TSMC’s Taiwan-based fabs produce the majority of the world’s leading-edge chips, and its capacity is spoken for years in advance. The geopolitical risk embedded in that concentration has been discussed at every level of U.S. industrial policy since 2022, which is why the CHIPS Act directed tens of billions of dollars toward domestic semiconductor manufacturing expansion.

Musk’s companies face this dependency acutely. Tesla’s FSD hardware, xAI’s training and inference infrastructure for its Grok models, and SpaceX’s ambitions for radiation-hardened orbital processors all require advanced chips at volumes that cannot be easily secured in the current TSMC queue without multi-year lead times and pricing leverage that smaller customers lack. Terafab’s vertical integration model, where design, fabrication, packaging, and testing happen in a single facility rather than across a fragmented global supply chain, is an explicit attempt to exit that dependency.

Intel’s position in this logic is strategic rather than financial, at least in the near term. It provides the technical credibility Terafab needs to be taken seriously as a manufacturing program rather than a press release. It gets, in return, the largest potential commercial foundry engagement in its history, access to a customer that will push its 18A and packaging capabilities to their limits, and a narrative shift at a moment when its stock is recovering from lows below $18 last year. The Cerebras IPO narrative, covered here in a prior analysis, and now Terafab are two different bets on the same underlying thesis: the AI chip stack is too concentrated in a single supplier, and the companies building alternatives now will extract significant value over a multi-year horizon.

The Execution Risk Nobody Is Pricing Yet

The 4% stock pop reflects enthusiasm. What it does not yet reflect is the difficulty of what has been announced. Building a leading-edge semiconductor fab at the scale Terafab describes is among the most complex industrial undertakings in existence. TSMC’s Arizona facility, by comparison, has faced repeated delays reaching full production despite years of preparation and a workforce that already knew how to make the chips. Terafab is proposing to build not one but two fabs on a site that was previously a vehicle factory, in a state with no existing semiconductor manufacturing ecosystem, on a timeline that analysts at Info-Tech Research Group described as yielding “near-term impact probability for this year close to 0%.”

The partnership is also still scant on contractual detail. Bloomberg reported that Intel’s role involves helping “refactor” an existing chip factory, a narrower mandate than the end-to-end fab construction that Musk’s March announcement implied. TechCrunch noted that the scope of Intel’s contributions “are unclear.” That uncertainty is not a reason to dismiss the announcement, but it is a reason to distinguish between what has been announced, a partnership with intent, and what has been committed, signed agreements with capital allocations and volume targets.

Intel’s next earnings report on April 23 will be the first opportunity to hear Lip-Bu Tan describe the commercial structure of the relationship, whether Terafab is already generating contracted foundry revenue or remains a pipeline commitment. The former would be a material positive for Intel’s foundry narrative. The latter would sustain the stock movement while postponing the fundamental question of when the customer translates into cash.

For investors tracking the AI chip stack broadly, the significance of April 7 is less about Intel’s quarterly trajectory and more about what it signals at the industry level. The era of Nvidia-plus-TSMC as the only viable path to frontier AI compute is being challenged simultaneously from multiple directions, Cerebras on inference speed, Eclipse’s physical AI fund on chip infrastructure investment, and now Terafab on vertically integrated domestic manufacturing. Whether any of these challenges resolves into a durable alternative is a question that will be answered over years, not quarters. What Intel’s participation in Terafab confirms is that the challenge is now serious enough to attract a company with the technical capability to actually execute it.

What to Watch Next

Intel Q1 2026 earnings, April 23 — Lip-Bu Tan’s first public opportunity to describe the commercial terms of the Terafab partnership. Whether it is characterized as a signed foundry customer agreement or a letter of intent will determine whether the stock’s recent run has fundamental support or has outpaced the contract structure.
External foundry revenue line — In Q4 2025, Intel’s external foundry revenue was $222 million, nearly all from government projects. Any meaningful Terafab volume commitment would need to begin showing up in this line within the next one to two quarters to validate the commercial narrative.
Terafab ground-breaking or construction milestone — Musk-affiliated projects often announce aggressively and build on compressed timelines. A formal ground-breaking at Giga Texas’s north campus would signal that capital is being committed, not just announced.
Nvidia’s response to domestic competition — Nvidia has no domestic foundry relationship that matches Terafab’s implied scale. If the project advances, it forces a strategic question about whether Nvidia’s TSMC dependency becomes a long-term liability in a policy environment that increasingly favors domestic semiconductor production.
Google and Amazon packaging talks with Intel — Separate from Terafab, Intel has been in reported discussions with Google and Amazon for advanced packaging services. If those agreements are announced alongside the Terafab commitment, it would confirm that Intel’s foundry strategy is gaining commercial traction across multiple fronts simultaneously, not just through Musk’s ecosystem.
The Cerebras Nasdaq listing — Cerebras and Terafab are both bets on alternatives to the dominant Nvidia-TSMC supply chain. If Cerebras prices successfully and trades above its $23 billion private valuation, it would increase institutional appetite for the broader AI chip diversification thesis that Terafab represents at the manufacturing layer.

10 Signs Your Industry Is Entering an AI Efficiency Era

Stacking Trades — Thu, 18 Dec 2025 23:04:21 +0000

There is a moment when a technology stops being a “trend” and begins to function like infrastructure. The conversation around it becomes less dramatic. The successes become smaller but more frequent. People stop scheduling meetings to discuss it and start taking it for granted, just like they do with search, spreadsheets, and calendar syncing.

That is what the AI efficiency era looks like in practice. Not a single dramatic leap, but a shift in the baseline of how quickly information moves through an organization and how reliably decisions turn into execution. Survey data suggests AI use is now widespread, with McKinsey reporting a large majority of respondents saying their organizations use AI in at least one business function and that gen AI use has risen sharply since 2023. The more interesting detail is that many companies still struggle to scale that usage into repeatable value.

So the question is not “Is AI here?” The question is whether your industry is crossing the line where AI becomes a reliable efficiency layer, and whether that shift is already changing competitive dynamics.

Sign 1: AI becomes a basic expectation, not a job requirement

One of the clearest signals is how quickly AI literacy stops being advertised and starts being assumed. Recent reporting on job listings suggests that explicit mentions of AI can decline even as employers increasingly expect workers to be fluent with it, similar to how “knowing Excel” is rarely treated as a differentiator anymore.

When this happens, the “AI team” stops being the face of adoption. Instead, the expectation spreads across functions: operations, finance, customer support, product, and compliance. Your industry is entering the efficiency era when AI is treated less like a specialty and more like a minimum competency for modern work.

Sign 2: The pilot phase gives way to repeatable workflows

In the early phase, organizations create demos. In the efficiency phase, they establish routines. McKinsey’s 2025 reporting shows how many organizations are using AI. It also points out the gap between adoption and real scale. Reuters has noted similar issues firsthand: there is a lot of experimentation, but returns are inconsistent. There is a growing shift toward narrower, sector-specific deployments that suit how work is done.

The sign to watch is operational: do teams have standardized prompts, approved use cases, and clear owners for the systems, or do they still treat AI as an optional “try it if you want” tool? Efficiency shows up when use becomes routine.

Sign 3: Customer operations quietly get faster

If your industry has any meaningful customer service footprint, the efficiency era often arrives there first because the economics are direct and the workflows are structured.

Klarna’s public statements about its AI assistant handling a large share of customer service chats shortly after launch became one of the best-known examples of AI reducing load on support operations. Lyft has also described major reductions in resolution time using Anthropic’s Claude for support inquiries.

What matters is not whether every interaction is automated. It is whether the average customer issue moves through the system with fewer handoffs, less time in queue, and better consistency. When competitors can respond faster with the same headcount, your industry starts to reprice “service quality” as an operational capability, not just a brand promise.

Sign 4: Document-heavy work stops feeling like a bottleneck

Every industry has its paperwork. This includes contracts, policies, claims, compliance files, vendor terms, audits, underwriting notes, clinical documentation, and procurement packets. These documents are the weighty centers of modern organizations.

AI’s most immediate contribution is not creativity. It is compression: turning large piles of documents into searchable, reviewable, explainable work products. In corporate and M&A legal practice, for example, legal publishers describe extractive AI scanning data rooms and surfacing key provisions for human review.

Your industry is entering the efficiency era when document review shifts from “weeks of reading” to “hours of verification,” and when the competitive edge becomes judgment and escalation, not raw throughput.

Sign 5: Software delivery metrics become business metrics

This sign shows up even outside software companies. The fastest industries now behave like software companies because so much value is delivered through systems.

DORA’s “four keys” metrics, deployment frequency, lead time for changes, change failure rate, and time to restore service, have become a mainstream way to measure delivery performance.

When AI starts to matter, leadership begins to care about these numbers for a simple reason: AI makes it possible to build more, but only if the path to production is smooth.

If your industry is suddenly investing in platform engineering, internal developer portals, and standardized “golden paths,” it is not a tooling fad. It is a signal that speed, stability, and iteration are becoming core competitive dimensions.

Sign 6: Internal platforms and self-service become a strategic priority

In the efficiency era, companies stop trying to make every team reinvent the same workflow. They build internal platforms that make it easy to do the right thing by default.

Gartner defines internal developer portals as tools that enable self-service discovery, automation, and access to reusable components and knowledge assets. Forecasts associated with Gartner’s market framing point toward broad adoption among organizations with platform engineering teams in the next few years.

This matters beyond engineering. The same internal-platform logic spreads to sales enablement, compliance intake, vendor onboarding, and customer operations. When your industry starts building self-service layers, it is admitting that “coordination” is the real cost center, and automation is the path out.

Sign 7: Middle management shifts from coordinating to curating

AI does not eliminate work. It changes the shape of it.

As AI accelerates drafting and first-pass analysis, the role of managers shifts toward curating what matters, validating outputs, setting standards, and managing risk. Business reporting and industry commentary increasingly describe a world where AI fluency is expected across roles and where leaders are judged on how well they integrate AI into day-to-day operations.

In practice, this means fewer meetings that exist to move information around, and more mechanisms that move information automatically, with managers acting as editors and exception-handlers. Your industry is entering the efficiency era when “keeping things aligned” becomes less about chasing people and more about maintaining systems.

Sign 8: AI is embedded into existing tools, not introduced as a new destination

In the hype phase, companies add AI as a standalone product. In the efficiency phase, AI gets absorbed into the tools people already use.

Reuters has reported that AI vendors are increasingly embedding specialists inside businesses and focusing on tailored implementations rather than generic, one-size-fits-all tooling, reflecting demand for practical fit. This pattern is visible across enterprise software, where “agentic” features are positioned as assistants inside workflows, not new workflows that users must learn from scratch.

A simple test: if workers in your industry describe AI as “part of the process” rather than “a new thing we’re trying,” you are watching the efficiency era arrive.

Sign 9: Governance becomes a feature, not a brake

When AI begins to matter operationally, industries move past vague principles and into real governance: documentation, risk controls, auditability, and accountability.

In the EU, the General-Purpose AI Code of Practice published in July 2025 is framed as a voluntary tool to help providers demonstrate compliance with AI Act obligations around transparency, copyright, and safety and security.

Even outside Europe, this shapes expectations because customers, partners, and regulators increasingly treat AI like other regulated capabilities. The sign to watch is cultural: do companies talk about safety and oversight as part of product quality, or as a separate compliance obstacle? The efficiency era favors the former.

Sign 10: ROI conversations shift from cost cutting to capacity

The earliest AI business case was simple: reduce headcount, automate tasks, lower costs. The efficiency era is different. The real advantage is capacity, the ability to do more with the same team, ship faster, respond sooner, and iterate with less friction.

McKinsey’s reporting emphasizes broad adoption and rising gen AI use, while also underscoring that scaling is the hard part. That gap is where competitive advantage forms. Industries that cross into the efficiency era stop asking whether AI can save money. They start asking what they can build, serve, approve, and deliver that competitors cannot match at the same speed.

What follows is not a single winner-take-all moment. It is a gradual repricing of execution. The companies that learn to turn AI into reliable workflow speed will look, from the outside, like they simply became better at business.

The Last Mile of Automation

Stacking Trades — Fri, 12 Dec 2025 19:01:57 +0000

The demo usually looks flawless

A bot copies data from one system to another. A workflow routes a request without the back-and-forth of emails. A dashboard displays clear “time saved” estimates. In the conference room, it seems unavoidable. Then the pilot begins, but people continue to do it the old way. They open the same spreadsheets. They forward the same attachments. The automation is there, but it doesn’t take hold.

If you want to understand why so many automation projects fail, stop staring at the technology. Look at adoption. Look at the tiny, everyday decisions workers make when they are rushing, when they are unsure, when the new system asks for one extra field, when the error message is vague, when there is no clear owner to fix the workflow that broke. That is the last mile. It is also where most programs quietly lose.

The pilot that proves nothing

Enterprise automation has always had a credibility problem: it is easier to automate a process than to automate a company.

Most pilots are created to work well in controlled settings. They choose cooperative users, stable inputs, and a limited scope. The results are not dishonest, but they are weak. When the automation meets the real world, exceptions increase. Edge cases show up. Approvals become political. The data is messier than anyone acknowledged. Suddenly, the system requires humans again, and humans do what they always do under pressure. They find ways to bypass the tool.

This is why “we built it” is not the same as “it works.” The relevant question is whether it changes behavior at scale. McKinsey’s 2025 global survey captures the gap in plain terms: a large share of organizations report using AI in at least one function, but most have not yet scaled the technologies across the enterprise.

The story is similar for automation more broadly. The problem is rarely capability. The problem is absorption.

Adoption is a product problem, not a training problem

When adoption stalls, organizations often reach for the same solutions: more training, more comms, another roadshow. Those help, but they are not the core fix. If a workflow is not being used, assume it is not designed like a product.

Good products minimize cognitive load. They anticipate user intent. They make the next action obvious. They recover gracefully when something goes wrong. In many companies, internal automations are the opposite. They are launched with the mindset of a systems project, not a user experience.

The result is a familiar pattern. The automation creates a new interface, but it does not remove the old one. People now have two ways to do the job, and the old way is still faster when you are experienced, especially when you are dealing with exceptions. Adoption then becomes a social negotiation rather than a natural shift.

This is also where leadership behavior matters more than memos. Recent reporting has emphasized that worker trust and buy-in are now central constraints on rolling out AI and automation, pushing functions like HR and operations into the role of adoption architects rather than policy enforcers.

“Automation doesn’t fail in the lab. It fails in the inbox.”

The myth of the invisible robot

Automation leaders love to say that the best automation is invisible. That is sometimes true for infrastructure, and often false for work.

For most roles, the point is not invisibility. It is reliability and clarity. Workers need to know what the automation did, what it is doing now, and what they are responsible for when something breaks. When that is unclear, automation feels like a black box that can create risk.

This is why “agentic” automation has become such a revealing stress test. It promises autonomy, but it also increases the surface area of uncertainty: what was the agent trying to do, what did it touch, and what happens if it drifts? Gartner has predicted that more than 40% of agentic AI projects will be canceled by the end of 2027, citing issues like rising costs, unclear value, and inadequate risk controls.

Even in the hype cycle, the market is already admitting that the last mile is not just about capability. It is about governance, ownership, and operational fit.

Incentives beat enthusiasm

Adoption fails when the workflow asks people to take on new effort without a clear payoff that is felt immediately.

A sales team will not use a new automation if it adds steps before a deal can move forward. A support team will not trust an automated routing system if it occasionally sends high priority tickets into a void. A finance team will not rely on a bot that cannot explain why an invoice was flagged. In each case, the rational choice is to build a parallel manual process “just in case,” and that parallel process quietly becomes the real one.

The deeper issue is incentives. Many automation programs measure success by output metrics, how many workflows were built, how many hours were “saved” on paper, how many bots are in production. Those numbers can look great while adoption is flat. The incentives reward shipping, not usage.

When the metric becomes adoption, the program changes shape. Rollouts become slower and more iterative. Exceptions become the main product. Documentation stops being an afterthought. Owners get named, not as governance theater, but as the people who will respond when the workflow fails at 4:55 p.m.

From project to product, the only move that scales

One of the most consistent observations in recent management discussions is that initiatives fail when organizations are not set up to support them. Harvard Business Review has stated this clearly in relation to AI. Failures often arise not from weak models, but from companies lacking the structure, operating rhythm, and accountability needed to maintain systems effectively after launch.

The best automation programs look less like implementations and more like product lines. They have backlogs driven by real user pain. They ship small improvements continuously. They treat governance as part of design rather than as a gate at the end. They invest in measurement frameworks that track workflow outcomes, not just activity.

This mindset also counters a newer failure mode: transformation fatigue, the exhaustion that sets in after too many top-down tools arrive with big promises and small practical value. When workers have lived through enough underwhelming change, adoption stops being a tool-by-tool decision and becomes a cultural reflex: wait it out.

If the last decade of automation taught enterprises how to build, the next one will teach them how to land.

The Developer Experience Economy

Stacking Trades — Wed, 10 Dec 2025 21:32:35 +0000

The first sign that something had changed was not a new programming language or a popular open source library. It was a slide in a board meeting. Alongside revenue, margins, and churn, a fourth chart showed up: deployment frequency and DevEx score. The message was clear. How developers felt about their tools had become a business metric.

For years, companies treated internal developer experience as a kind of housekeeping, important but rarely urgent. In 2025, it has become a competitive weapon. Research from Google and independent DevEx labs now treats productivity as a function of speed, ease, and quality, measured through a mix of telemetry and direct surveys. Gartner tracks a growing market for “internal developer portals,” and consulting firms sell playbooks for unlocking revenue growth through happier engineers. What used to be tickets in a backlog is now a line in the strategy memo.

When productivity became a product

The shift starts with a simple arithmetic problem. In the 2024 Stack Overflow Developer Survey, a majority of professional developers reported spending more than thirty minutes every day just searching for answers to work problems. That is time spent in documentation mazes, chat histories, and half-remembered Confluence pages rather than in the codebase.

At the same time, the average toolchain has grown more complex. A developer working on a single feature might interact with the source repository, a feature flag service, a build pipeline, a cloud console, an observability platform, and several chat channels before the change reaches production. Each step adds friction. Each missing script or unclear error message adds a small cost.

The result is that developer experience itself has started to look like a product surface. Companies now build internal platforms with the same care they once reserved for customer facing apps: user research, design reviews, roadmaps, and service-level objectives tailored to engineers.

The rise of the internal developer platform

Platform engineering emerged as a response to this sprawl. Rather than ask every team to stitch together its own path to production, organizations began building centralized “golden paths” that abstract away infrastructure and policy decisions. The idea is not new, but the tooling is.

Open source frameworks like Backstage, created at Spotify and donated to the Cloud Native Computing Foundation, turned the concept of an internal portal into reusable software. Backstage catalogs services, pipelines, and documentation in one place, so engineers can discover what exists and scaffold new projects with consistent templates. A growing ecosystem of SaaS platforms now wraps these ideas in managed offerings, promising faster onboarding and reliable standards without the pain of building everything in house.

Analysts have started to quantify the trend. Gartner defines internal developer portals as the front door to reusable components, tools, and knowledge, and projects that by 2028 most organizations with platform engineering teams will offer one, up from about sixty percent in 2025. What was once a niche initiative now looks like the default infrastructure pattern for serious software companies.

“Developer experience used to be what was left over after the tools were chosen. Now it is the thing being designed.”

Metrics move into the boardroom

Once internal platforms are in place, leaders want to know if they are effective. This has led to a surge of frameworks that aim to measure not just lines of code or tickets closed; they also focus on the real experience of delivering software.

Google’s productivity researchers have described an approach that blends survey data with system metrics to capture speed and ease in a way that developers recognize as real. Academic and industry teams have published frameworks such as SPACE and DevEx that frame productivity across satisfaction, performance, communication, and flow. More recently, the Core 4 model has tried to unify these ideas into a concise set of outcomes that leadership can track without turning engineers into KPI collectors.

Consultancies and vendors have leaned into the story. Deloitte describes DevEx as a lever for product innovation and operational efficiency. Studies aggregated by DevEx tooling companies suggest that organizations investing in better developer workflows see significantly faster time to market and improved customer acquisition. HashiCorp cites McKinsey research that links strong developer experience to higher operating margins. The numbers are imperfect, but they share a direction. Developer friction is now described not as “annoying” but as a drag on revenue.

AI tools and the new bottleneck

The timing is not accidental. As AI coding assistants spread through the industry, the cost of writing syntax has fallen. According to recent survey data, more than eighty percent of developers now use or plan to use AI tools in their workflows, yet many still spend large chunks of the day hunting for context and debugging almost-right suggestions. The bottleneck has shifted from typing code to orchestrating the environment in which that code runs.

That is where internal platforms matter. An AI tool can write a microservice, but the organization still needs an opinionated way to connect that service to authentication, observability, and deployment. A cluttered CI system or inconsistent staging environment can erase the gains of even the best assistive model.

The companies that benefit most from AI coding tools are often the ones that already invested in clean paths to production. When a scaffolded project comes with batteries included, an AI agent can safely generate more of it. Developer experience becomes the substrate that makes automation trustworthy instead of chaotic.

From perk to strategy

For a long time, improving developer experience was framed as a retention play. The logic was that happier engineers were less likely to leave, and perks like better laptops or cleaner tooling were part of that equation. That lens has not gone away, but it is no longer sufficient.

What is changing is that DevEx is being folded into the core story of how a company competes. Internal portals, standardized workflows, and thoughtful documentation become part of the answer to investor questions about how a business will ship new products faster than rivals. Platform teams are judged not only on internal satisfaction scores but on their contribution to time to market and stability.

The organizations that treat developer experience as an economy of its own are starting to look different inside. Projects spin up with fewer meetings. New hires find their footing in days instead of weeks. AI tools amplify good patterns instead of copying bad ones. The work of building internal tools and platforms is still largely invisible to customers, but its effects are not.

In an era where the external technology frontier is moving quickly, the real differentiator is often what happens inside the walls of a company. The developer experience economy is the quiet infrastructure behind that edge, turning the messy, improvised workflows of the last decade into something more deliberate, measurable, and, increasingly, strategic.

The Disruption We Cannot Measure Yet

Stacking Trades — Tue, 25 Nov 2025 20:15:44 +0000

The Shift We Can Feel But Cannot Quantify

Companies have always measured progress. They look at productivity, throughput, efficiency, and margin improvement. Reporting has shaped our understanding of reality. However, a curious change is happening as AI takes on more tasks. The old methods of measuring output can’t reflect the real activity anymore. There is a shift happening beneath the surface that is changing how work flows, but the dashboards remain flat.

In 2025, AI systems will make more decisions, coordinate tasks, and solve complex issues before humans see them. The work is there. The impact is real. However, the metrics designed for human-centered processes cannot capture this. Most organizations monitor what goes through people, not what gets resolved before it reaches them. We are seeing disruption that leaves no trace in the tools meant to spot it.

When Metrics Miss the Work

The signs appear first in operations. A logistics team reports fewer delays, but there is no clear reason. A support team sees a drop in escalations, but workflows remain unchanged. A finance group closes faster than before, but staffing is static. The output improves without any visible inputs.

Multi-agent systems, routing engines, and autonomous workflows now handle edge cases, reorganize queues, and resolve dependencies without surfacing the activity. Problems that would have appeared in reports simply never materialize. The data shows stability. The underlying work is in motion.

A 2024 analysis by McKinsey found that a significant amount of AI-driven productivity improvements had no clear source in traditional KPIs, particularly in operational layers. At the same time, Gartner predicts that by 2026, half of enterprise AI value will come from machine-only workflows that standard performance metrics do not capture.

We are witnessing the rise of invisible productivity.

“The greatest impact of AI is happening where traditional metrics cannot see it.”

The Economy of Invisible Systems

This is not inefficiency. It is evolution. AI systems work at speeds and sizes that human reporting never anticipated. They rearrange data structures, stop errors, highlight contradictions, fix routes, rewrite queries, and improve queues. However, since no human is involved in the task, the system does not log anything significant.

Organizations built measurement frameworks for human bottlenecks. AI removes the bottlenecks, and the frameworks lose their anchor.

Economists are beginning to question how to measure output when machines generate value without involving human labor. There are no timestamps. No check-ins. No handoffs.
There isn’t a model for this yet. Everyone realizes that something significant is getting lost on the dashboards.

The Strategic Blind Spot

Leadership teams face a new challenge. When the most valuable work leaves no metrics, how do you assign credit? How do you identify what to invest in? How do you manage risk? If AI prevents a thousand issues that never occur, what does success look like? If a cluster of agents makes strategic adjustments before anyone sees the underlying problem, who decides whether the system should continue?

In the early 2000s, digitization created new metrics. AI creates fewer. This is the paradox. As intelligence becomes more autonomous, its contribution becomes less visible. Executives who are used to charts and slides must now learn to manage systems where the value is sensed, not measured.

The Coming Redefinition of Measurement

New tools will eventually appear. New metrics and frameworks will emerge. We will see benchmarks that capture stability, prevention, coordination, and invisible orchestration. But for now, we remain in the gap between ability and understanding.

AI is already creating value that organizations cannot quantify. Competition is shifting in ways that do not show up in reports. The advantage lies not in what companies track, but in what their systems quietly resolve.

The disruption is here. We just have not learned how to measure it.

The Multi Agent Workplace

Stacking Trades — Mon, 24 Nov 2025 20:18:05 +0000

The First Signs of a Shift

Workplaces have always been structured around teams of people. Groups with different skills coordinate, pass on tasks, and work through issues together. In 2025, a new layer will join that structure. It’s not just one assistant working quietly in the background. Instead, there will be clusters of AI agents working together, sharing information, and managing tasks before they even come to a human. It’s subtle, but the first signs are already visible.

You can see it in early deployments of AI orchestration systems inside companies. In customer service, multiple agents now work together to search knowledge bases, classify tone, propose responses, and check compliance before handing a draft to a human. In software development, tools like GitHub Copilot Workspace coordinate multiple models across planning, coding, and testing workflows. In operations, AI agents handle routing, forecasting, and scheduling across logistics networks that once required full teams.

The workplace is starting to feel less like a single model helping a human and more like a distributed team where machines collaborate with each other.

When Agents Begin to Coordinate

The shift is rooted in simple economics. Enterprises that once experimented with single AI assistants found that one model alone could not cover the complexity of their work. The solution was not a bigger model. It was a cluster of narrow ones, each tuned to a specific function.

Research groups anticipated this trend. A 2024 Microsoft study on multi-agent systems found that agents working together on structured tasks performed more reliably than a single general model on its own. Stanford’s 2024 AI Index noted the same trend in workflow automation: coordination is better than scale. Early results from Anthropic’s multi-agent experiments showed better reasoning through division of labor instead of sheer force.

Companies started using the same structure. A planning agent divides a project into steps. A research agent gathers context. A reasoning agent writes decisions. A verification agent reviews constraints. A summarization agent presents the result for a human. Each agent becomes a specialist.

The model is not replacing teams. It is joining them.

The Human in the Loop Evolves

In this environment, the role of the human shifts. Instead of performing all the steps, people become reviewers, supervisors, and strategic guides. They focus on interpretation rather than execution. Work feels less like a stream of tasks and more like a series of decisions supported by systems that do the heavy lifting.

This is not automation in the old sense. It is collaboration. Your teammates just happen to be machines with perfect recall, continuous attention, and the ability to work in parallel.

You can already see early examples of these dynamics in real-world settings. Retail companies operate small fleets of forecasting agents that update inventory in real time. Financial firms test research agents that collect filings, earnings data, and sentiment analysis before analysts sit down to review. Logistics platforms depend on groups of agents for route optimization and predicting delays. The models are not taking the place of people. They are cutting down on the overhead that used to slow them down.

“The workplace is shifting from one model helping one person to clusters of models working together before the work reaches a human.”

Where the Friction Lives

The multi agent workplace is not without issues. Coordination problems appear when agents over interpret instructions or reinforce each other’s errors. Enterprises report that agent clusters often need supervision until guardrails mature. And compliance teams warn that too many interconnected decision points can make audits more complex.

But the trajectory is clear. As companies move beyond isolated pilots and into integrated workflows, multi agent systems become a natural way to scale intelligence without scaling headcount.

The workplace is beginning to reorganize itself around networks of cooperating models. It is early, but real. The structure forming underneath is not science fiction. It is a preview of how organizations will function when intelligence is abundant and coordination is cheap.