Back To All

Agents can build software without limit. Your ability to trust it has a limit.

October 8th, 2026
Topics
AI
AI ADOPTION
AI Agents
AI IMPACT
AI ROI
AI SDLC
Share Article
AI SDLC

Agents can build software without limit. Your ability to trust it has a limit.

Repos, PRs, commits Human review capacity The trust gap Copilots Coding agents Infinite factory Illustrative, not measured data

Satya Nadella just described a world where any business can describe what it needs and have agents build it. Software development is where that world showed up first. Here is what it means for the AI SDLC, and what engineering leaders should be measuring before the factory runs at full speed.

AC Alex Circei CEO and Co-Founder, Waydev

This week Satya Nadella published a long post on X titled “The Infinite SaaS Factory.” The headline idea is Copilot as an operating system for work: a front end (the “head”) sitting on a governed, “headless” layer that exposes business logic, context and systems of record to agents. Add a managed runtime where generated code runs safely inside the company, and any team can describe a missing module and have it built on top of the systems they already run.

Most of the coverage will focus on CRM, ERP and the future of business SaaS. The more interesting part for engineering leaders is a few sentences near the top. Nadella points to software development as one of the first areas to adopt agents at scale, and notes that GitHub has seen repo creation, pull request and commit activity accelerate as agentic development has grown.

“More agents don’t make systems of record less important.”

Satya Nadella, The Infinite SaaS Factory. His point: they make trusted places to hold information, coordinate changes and manage state matter more.

That is the lesson every engineering organization is living through right now. The SDLC was the pilot program for the infinite SaaS factory. What happened to engineering is a preview of what will happen to every function that starts building with agents.

What an infinite factory does to your SDLC

When building gets close to free, the constraint moves. It moves out of writing code and into everything around it. Four pressure points show up first.

1 Volume More repos, more pull requests, more commits, produced by agents that never get tired.
! What breaks Activity metrics stop meaning anything. A doubling of PRs tells you nothing about whether more value shipped.
2 Verification Every generated change still needs someone, or something, to decide it is safe to merge and deploy.
! What breaks Review becomes the bottleneck. Senior engineers turn into full-time approvers, or reviews quietly become rubber stamps.
3 Personal software Anyone can tailor or build an app around the way they work.
! What breaks Fragmentation. Duplicated services and orphaned repos with no clear owner. Nadella names this risk himself.
4 Cost Tokens become a line item in every stage of delivery, from planning to code to review to incident response.
! What breaks Without cost per outcome, AI spend grows faster than anyone can justify it to a CFO.
The architecture

Head, headless, and the engineering system of record

Nadella’s model has three layers: the head where people and agents express intent, a headless layer of business context and logic, and the systems of record underneath. Map that onto engineering and the picture gets very concrete.

THE HEAD Agents and copilots Coding agents, chat, review bots THE HEADLESS LAYER Engineering context Who owns what, standards, history, delivery and quality metrics SYSTEMS OF RECORD Git, tickets, CI/CD, deploys Where every change actually lives

Most companies have invested heavily in the top layer, buying seats for coding assistants and agents. The bottom layer already exists: Git, Jira, CI pipelines, deployment logs. The middle layer is the one almost nobody has built, and it is the one that decides whether agents help or hurt.

An agent with no engineering context does exactly what Nadella warns against. It works around the system instead of with it. It does not know which team owns a service, which patterns your org has standardized on, or which parts of the codebase are fragile. Nadella makes the same point about business apps: exposing existing APIs to a model is not enough. The context itself has to be designed for AI.

The shift

Engineering systems of record have to be reinvented too

Nadella argues systems of record must be rebuilt for an agentic world: able to handle high-volume agent access, pull context together across data sources, and work natively with assistants. Apply that to the SDLC and four requirements fall out.

A Attribution Know which work was done by a human, which by an agent, and which by both. Without it, every other metric is ambiguous.
B Connected context Join code, tickets, reviews, deployments and incidents so a change can be traced from intent to production.
C Agent-readable Agents should be able to query engineering context directly, the same way a new engineer would ask a senior colleague.
D Governed Policies about what agents may change, and where, need to be enforced and audited, not just documented.

Tokens where they add value, deterministic software everywhere else

One line in the post deserves more attention than it will get. Nadella says the goal is not to use an LLM for everything: spend tokens where intelligence adds value, and rely on deterministic software where it is faster, cheaper and more reliable.

That is the right discipline for the AI SDLC too. Linting, formatting, dependency checks, test execution and most measurement do not need a model. Design, debugging unfamiliar code and reasoning across systems often do. Teams that let agents burn tokens on deterministic work will see AI costs climb while delivery stays flat.

Spend tokens Design trade-offs Debugging theunfamiliar Cross-systemreasoning Go deterministic Linting, formatting Tests and builds Dependency checks Delivery metrics

An infinite factory without a system of record is just an infinite backlog of things nobody can explain.

Alex Circei, CEO, Waydev

What to measure

Six signals for an agentic SDLC

If agent activity is about to multiply, the metrics you report need to survive it. These are the signals we recommend engineering leaders put in place now.

Agent share of shipped work What portion of merged and deployed changes came from agents, and how that share is trending by team.
Review load per reviewer How many changes each reviewer handles, and how review depth and time to approve shift as agent volume grows.
Change failure rate, split by origin Compare incidents and rollbacks for agent-authored versus human-authored changes, so trust is earned with evidence.
Rework on generated code How much agent-written code is rewritten or reverted within weeks. Fast output that churns is a deferred cost.
Repo and service sprawl New repositories and services created, how many have a clear owner, and how many overlap with something that already exists.
Cost per shipped outcome AI spend tied to features and fixes that reached production, not to seats or tokens consumed. This is the number your CFO will ask for.
Where Waydev fits Waydev is built to be the engineering intelligence layer in this picture: it connects your Git, ticketing and CI/CD data, separates human and AI contribution, and measures AI adoption, impact and ROI across the SDLC, so both leaders and agents work from the same trusted view of how software gets built.

The factory is already running in engineering

Nadella’s vision is that every business will soon build software the way engineering teams do today. That makes engineering the proving ground. The organizations that figure out how to measure, govern and trust agent-built software now will be the ones ready when the rest of the company starts building too.

The infinite SaaS factory is a real opportunity. But a factory is only as good as its quality control, and in software, quality control starts with knowing what was built, by whom, at what cost, and whether it worked.

Build the system of record for your AI SDLC

See how agents and engineers are changing your delivery, from adoption and output to quality and cost per outcome, in one trusted view.

Book a demo

Source: Satya Nadella, “The Infinite SaaS Factory,” published on X (@satyanadella), October 2026.

Ready to unlock your SDLC productivity?

Request a Demo Call