When should you build one agent vs. many? And what even is Single-Org Multi-Agent Orchestration (SOMA)? 

Jennifer W. Lee breaks it all down in this must-read post for anyone designing Agentforce solutions. ✨ 

SOMA lets multiple specialized agents work together in one Salesforce org — coordinated by a Super Agent that acts as the unified front door. From the user's perspective, it's one seamless conversation. Behind the scenes, the right agent is handling the right work. 

The key question isn't "how many agents can I build?" — it's knowing when a single agent with subagents is enough vs. when your use case calls for SOMA. 

A few signals you need SOMA:

• Your workflows span multiple domains (HR, IT, Facilities, etc.)
• Context overload is causing your agent to misroute or skip guardrails
• You need failures isolated so one process crashing doesn't take down the whole experience

And a simple gut check from Jen: if you can't describe a subagent's purpose in one sentence without using the word "and" — it needs to be split further. 💡