↓ Skip to main content
Background Image
  1. Posts/

Agents are here to stay, how can companies really go faster ?

·3 mins
Clément Sauvage
Author
Clément Sauvage
I like to make softwares

I disconnect more and more from tech forums, reddit, HN, youtube, etc… but whenever I come back to it, and I face a piece of content about AI agents, there’s still many of those naysayers claiming AI can’t do the coding, the planning, debugging, presenting, or whatever else.

I am not sure if we live in the same world, but AI is definetly a crazy speedup for almost everything.

This actually highlights more than ever the main speed bottleneck we always had: human sync. The bigger the company, the bigger the overhead, as the network of people who need to align keeps growing. Agentic coding and workflows accelerate so many things, but the main bottleneck stays the same, and it might even get worse. If syncing used to eat 50% of the time, it can easily become 90%. The cost is communication.

Amdahl’s law pretty much already stated that, the increase of velocity that can be achieved in a team was already capped by the proportion of the bottleneck, which is most likely going to be meetings/reviews/alignment.

Say execution takes 80% of a sprint and sync takes 20%. Speeding up execution is very impactful. But even if agents bring execution close to zero, the remaining 20% caps your maximum speedup at 5x (1 / 0.20).

Now take a team where sync is 50% of the time. Make execution 10x faster and total time goes from 1.0 to 0.55. That’s a 1.8x speedup, and sync is now about 91% of what’s left. The theoretical cap is 2x, however fast the agents get.

Brooks’s law explains why this gets worse as companies grow. Communication channels scale as n(n-1)/2, so 5 people means 10 channels, 10 people means 45, and 50 people means 1,225. Agents increase what each person produces, but not their ability to align with everyone else. More output per person means more things to sync on, so the quadratic term hurts even more than before.

But enough with the theorical laws, and math to make it sound smart. They were more about explaining the point. Smaller companies have a speed edge, or at least small teams. Settings where people are more autonomous, where agents can iterate on their own. This is where you’re removing the speedup cap that you get when adopting agentic workflows.

And it doesn’t have to come in at the expense of product quality/code quality/architecture/security, etc… No. Now, we see more and more Product Engineer: software engineer who owns the full product cycle, from what to build, designing the user experience, writing the code, measuring the user impact, etc… and even maybe defining a big picture direction. These will probably become the norm.