The New Bottleneck The bottleneck is no longer intelligence. Over the last six months, intelligence has accelerated dramatically. But smarter models are not enough for everyone to benefit from novel intelligence. New form factors are required. GPT-3 needed Chat. Opus 4.5 needed Code and Cowork. Today, with Astra and Fable, we’re in a familiar position. Intelligence is advancing faster than it can reach people in useful forms. The model overhang is back. The new bottleneck is diffusion. Increased intelligence needs to translate to human progress. Microsoft’s mission is to empower every person and every organization to achieve more. If we fail to create new ways to utilize increased intelligence, this mission is at risk. The New Copilot Our next step is the new Copilot. Home, Code, and Autopilot. Home is your new starting point, unifying Chat and Cowork into a single experience. Ask a quick question or delegate a whole project. No need to decide where to start. Home also features Today, our new proactive view that spans Outlook, Teams, meetings, and tasks. Today doesn’t just flag things you missed; it moves work forward. The draft is already written, and the schedule change is already proposed. We’re also bringing Office into Copilot. For the first time, you don’t have to choose between AI editing and human collaboration. We’ve brought the full power of Word, Excel, and PowerPoint into Copilot, so you can create, edit, and collaborate with colleagues and Copilot at the same time. Next, Code is coming to Copilot. Models can write code but environments, hosting, and sharing get in the way. With Code, just describe an app, tracker or workflow in plain English. Code runs sandboxed on your machine or safely in your tenant in the cloud. Now, hosting and sharing an app is as easy as a Word document. Finally, Autopilot. Your digital teammate. Give it a name, an appearance, a role, and a goal. Your Autopilot has it’s own identity, memory, computer, and workspace. Autopilot is enterprise grade, with real permissions, audit, and governance, all from Agent365. It can monitor work, coordinate with your team, and keep projects running over weeks -- just tag it in a document, forward it an email, or message it on Teams! Home. Code. Autopilot. Intelligence is here. Put it to work.
The diffusion framing is the clearest way I've seen to describe where clients are stuck. Models keep improving, but the value only shows up when someone redesigns the work so people can actually use them. That is a change management problem long before it's a technology one, Jacob.
Well said, Jacob. Innovation only creates value when it reaches people in ways that are useful and accessible at scale. Looking forward to seeing how our customers use these new capabilities to drive even greater impact.
A very interesting shift in how enterprise AI is being positioned. The real challenge is no longer simply building more capable models, but making that intelligence accessible through practical, secure, and integrated workflows. The combination of Home, Code, and Autopilot points toward a future where AI moves from being a tool we interact with to a digital teammate that can execute, collaborate, and continuously move work forward. For businesses, the key question will be how to adopt these capabilities while maintaining security, governance, permissions, and data control. 🤖☁️🔐
The bottleneck framing is right. Most tools still assume people will come to them — the ones that actually diffuse are the ones that show up inside workflows people already have. The Home bet makes sense: the hard problem was never more capability, it was removing the decision of where to start.
The bottleneck being diffusion rather than intelligence matches what I see. Plenty of capability available, very little of it in a form most people would reach for.
Defining the bottleneck as diffusion treats an economic shortfall as an interface challenge, its not! Enterprise adoption remains limited because software expenditure must show a verified reduction in operating costs and/or a tangible increase in billable output. Bundling chat, coding, background agents, etc into a single portal does not resolve whether a $30 per seat per month yields a positive & tangible ROI. Also , autonomous agents running unattended over weeks introduce severe liability and compliance exposure. When staff must continuously audit outputs to prevent errors, the cost of human supervision remains intact alongside the recurring subscription. Organisations do not require novel form factors to adopt systems that reliably save labour or expand capacity. I would focus on helping clients on ROI first, diffusion second. All the best
The line I'd watch is 'give it a name, an appearance, a role, and a goal.' The day an Autopilot works for a week straight, the enterprise question won't be what it can do but whose authority it acted under. Every service-account lesson from the last decade applies, and agents will have to become first-class principals in the identity system, not features in a launcher.
The diffusion point becomes especially interesting once agents run continuously rather than as short interactive sessions. A persistent agent changes the infrastructure profile: longer GPU occupancy, sustained memory traffic, less predictable workload timing, and potentially different rack-level power transients. That means the “new form factor” is not only the software interface. It also changes the physical envelope the infrastructure must support. I’d be curious whether Microsoft is modeling Copilot workloads as a distinct infrastructure class yet, rather than treating them as another inference workload.
The bottleneck is intelligence that vendors can make money on, so they don't exit the business suddenly and take us all down with them.
Yes, Diffusion is key, but this needs streamlining for 'Line of Business' teams. A trusted resource is needed to put things together and make sure agents don't 'run amok' inside the org.