Back to Issue 08
Rx Perspective
Issue 08 · Issued 8 Nov 2026
The Next Bottleneck Is Not Code
Friday, ten past nine. An offer is going viral, a supplier has pulled a product, a complaint has arrived and checkout runs on PHP the morning a critical flaw is announced. The agents could draft every fix before eleven. Drafting is not the hard part.
AgentsEngineeringOperating ModelArchitectureSecurityEnterprise
Stage 1
The single-lane factory
AI drafts every change, and the review queue becomes the bottleneck. In the general population, a third of AI-written changes ship within a month. At the frontier, one engineer shipped more than 2,000 in a month with the same models. The bottleneck is human attention, not AI.
Stage 2
The multi-lane control tower
AI runs many lanes at once under shared rules: find every affected repository, fix it, test it, review it twice, and let an owner merge. The security lead decides with the evidence in front of them instead of guessing under pressure.
Stage 3
The recursive loop
Customers, partners and their agents build on what a team ships. What stays fixed is the business’s own actions, such as checking eligibility or applying an offer, each with permissions, limits, receipts and a way to reverse mistakes. Products head towards a customer count of one.
Find your stage
You are here if…
  • Stage 1. Reviews pile up and the same changes keep coming back.
  • Stage 2. Many lanes ship safely, but nobody is sure which deserve to run.
  • Stage 3. Customers and partners are starting to build on what you ship.
The models will keep improving for everyone, so efficiency will spread. What a team learns through its own loops will not. Every stage clears one bottleneck and reveals the next. So find what stands in your way today, clear it, and ask again: what is your next bottleneck?