AI
Agent Architecture Cost-Success Trade-offs: A Controlled Evaluation across Enterprise-Style SOPs
Publication: cs.AI updates on arXiv.org
Author: Subhrangshu Nandi, Hitesh Arora, Yunfei Bai, Udita Patel, Chirag Shah, Hannah Kwon, Wei Zhang, Weian Chen, Chloe Ruoqi Li, Alberto Sconfienza, Ayush Goyal, Yasmine Lee, Ming Xiong, Prathap Ramachandra
Source published: 11/11/2026, 05:00:00 UTC
Briefing created: 11/11/2026, 05:05:02 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 11/11/2026, 05:03:24 UTC.
Briefings
A controlled evaluation of four agent architectures (single agent, skill-augmented, multi-agent orchestration, and triage swarm) across 13 enterprise SOPs revealed no universal best architecture. Task success ranged from under 10% to near 100%, with added architecture costing 2.6-5.8x more latency and tokens. Implementation quality significantly outweighed architecture choice, as a redesigned multi-agent implementation beat the baseline by 7.2 percentage points.
Key points
- Task success ranges from under 10% on the hardest SOPs to near 100% on the easiest ones, with no architecture being statistically separable in aggregate.
- A targeted redesign of a multi-agent implementation improved success from 67.4% to 75.6%, while degraded skills fell below the baseline.
Context
This study evaluates agent architectures for enterprise SOPs using a rubric to build matched high and low-quality skill corpora. The findings indicate that architecture choice is SOP-dependent, and implementation quality is more critical than architectural complexity.
Limitations
Evidence is limited to 13 enterprise SOPs and a single snapshot at publication. The directional trend for added structure on complex SOPs is not yet statistically significant, and the study does not account for external factors beyond architecture, tasks, and tools.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 11/11/2026, 05:05:02 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeicyzdjkgl46e6peyfo6qspsaxfpeg5yo7h4amdeggulrbz3dcqufa