When You Speed Up Code 100x, the Bottleneck Doesn’t Disappear. It Migrates.
And right now it’s migrating straight into the seams of every consulting firm and enterprise client I work with.
When you speed up code 10–100x, the bottleneck doesn’t disappear.
It migrates.
Andrew Ng just named something I’ve been seeing on every engagement for the past year: AI-native teams don’t move faster than traditional ones. They move differently.”
Roles blur. The engineer is also the product manager, the designer, sometimes the marketer. Sales prototypes their own demos and ships proposals without engineering. A team of 2–5 closes work that used to take 20.
But the part Ng added that matters most, and the part most of the AI productivity discourse keeps skipping, is this:
When one function accelerates by 10–100x, the slow ones become the constraint.
The speed of any process is limited by its narrowest point. Right now that point isn’t the model. It’s adoption..how fast actual humans inside an actual organization learn to use these tools.
The bottleneck isn’t inside the dev team. It’s at the seams. Between engineering and every function that didn’t accelerate with it.
The 10x dev team inside a 1x company
This is the part I keep watching play out at every Big Four engagement, every enterprise rollout, every consulting deal in the last twelve months.
A development team adopts Claude Code or Codex. Velocity jumps 3–5x within a quarter. Tickets close faster. PRs ship in hours instead of days. The CTO presents the numbers at the next board meeting. Everyone claps.
Then the work hits the next desk.
Procurement still takes six weeks to approve a vendor. Legal still wants the same redlines on the same MSAs. Compliance still runs the same review cycle on the same risk matrix. Marketing still books the same launch slot eight weeks out. The client’s IT team still needs three change-control boards.
Engineering compressed eight weeks of work into one. Everything around it stayed for eight weeks. So the cycle time for a delivered, paying outcome didn’t move at all. The team just sits idle longer, waiting on the rest of the org to catch up.
This is what Ng is naming. And it’s the thing nobody on the engineering side wants to say out loud, because saying it means the productivity story gets a lot more complicated.
The 10x dev team inside a 1x company is not a 10x company. It’s a 1x company with very fast engineers and a very tall pile of finished features waiting in line.
The generalist of 2026
Ng’s answer is the part most consulting partners haven’t internalized yet: generalists.
Not the generalist of 2018 - the “full-stack” engineer who could touch the database and the UI. The generalist of 2026: someone who can write the code, make the product call, talk to the client, draft the contract, and close the proposal themselves.
The math is brutal, but it’s not new. McKinsey ran on it for 70 years. A senior partner is a generalist with judgment, they’re the ones who scope the work, sell it, run it, and sign it. Below them, the pyramid was specialists. AI is collapsing the pyramid because the specialists are now the generalists. Code is one tool in their stack. Legal review is another. Client comms is another. None of them require a dedicated headcount anymore.
What this means in practice
Four shifts I’m watching the Big Four figure out one painful quarter at a time.
1. Don’t hire a specialist if a generalist with AI can do the job.
The headcount cuts at the major firms this year aren’t about partners being the bottleneck. They’re about the work below the partners no longer requiring the seniors who used to feed them. The base of the pyramid stopped existing. The top followed.
2. Accelerate the whole process, not just engineering.
The agent platform plays from the consulting side: pre-built agents for procurement, legal review, claims processing, vendor onboarding, audit testing, KYC, supplier risk and those aren’t dev tools. They’re seam-removers. Engineering already moves. The smart firms are now de-bottlenecking everything around it.
That’s the actual thesis behind the partnership announcements I’ve been writing about all year. It’s not “more code shipped.” It’s “fewer queues between functions.”
3. The metric isn’t team utilization. It’s how fast value reaches the client.
Most consulting firms still measure people on chargeable hours and utilization. That metric was designed for a world where labor was the input and time was the output. Both halves are wrong now.
The right question is: from the moment a client says “yes,” how many calendar days until they’re seeing value? Six months ago that number was 90+ in most enterprise deals. The teams that have collapsed it to 30 are eating shares. The teams still quoting 90 are getting cut from the shortlist by the same procurement teams that used to love them.
4. Speed up dev without speeding up everything else, and you just hit the wall faster.
This is the hardest one to internalize, because it goes against every dev-team-led narrative of the last three years. “We adopted Claude. Engineering velocity 5x.” Great. Your client onboarding still takes 11 weeks. Your sales cycle is still 4 months. Your contracts still close at 6. The only thing you speed up is idle time.
The honest part
What I appreciated most in Ng’s post: he was honest about the cost.
“I realize these shifts to job roles are tough to navigate for many people.”
Mildly put.
For consulting, this is a paradigm shift. Thousands of people built careers on deep specialization in a single function - tax, audit, M&A diligence, pricing, ServiceNow administration, change management, SAP integration. Most of those careers were premised on the idea that the specialty was the moat. The specialty is now an API call inside someone else’s prompt.
A generalist with AI is more valuable than a deep specialist without one. That’s not a prediction. That’s the rate card I’m seeing on actual deals being signed in 2026.
“Golden age of learning and building,” Ng calls it. Agree.
But only for the people willing to learn.
For everyone else, this is going to be very hard.
Knowledge gets cheap. Judgment gets expensive. And the bottleneck just moves to whoever refuses to move.