This feels like the monolith vs. microservices debate all over again, just one layer up the stack.With a monolith, one bad deploy can take down the whole app. With microservices, you isolate the blast radius but pay for it in coordination overhead. I think the same trade shows up with agents, but the cost that matters most to me isn’t failure isolation, it’s iteration speed.

If one agent handles support, sales, and onboarding, every improvement to how it handles refunds risks quietly changing how it handles a sales question, so you end up retesting the whole thing for a narrow fix. Specialized agents let you ship a fix to the refund agent on Tuesday without anyone touching sales logic at all. That’s less about safety and more about how fast the product can actually get better once it’s live.

The catch is that specialization only pays off once you have enough usage data to know where the real seams are. Split too early on guesses about workflows, and you’ve built five agents to solve a problem one agent could’ve handled; wait too long, and the monolithic agent’s tangled logic becomes the thing slowing you down.