Quote · The MongoDB Podcast
How Rox Is Rebuilding the CRM for the AI Era on MongoDB
Where this was said
ROX vs. Traditional CRM: Siebel, Salesforce, and the Agent Era
At 4:25 · chapter starts 3:35
When asked what distinguishes ROX from legacy CRM tools, Ishan offers a framework that's both simple and damning for incumbents: Siebel was great on-premise; Salesforce is great as SaaS; ROX is an agent product — and the differences are architectural, not incremental. [1] — Ishan Mukherjee "Every major CRM shift has redefined who does the work. Siebel put it on-premise; Salesforce moved it to the cloud; ROX removes the human en…" 03:33 The first key distinction is that agents do the work. In SaaS, a human feeds data into the system; with ROX, the agents conduct research, send outreach, run meetings, and manage contracts autonomously. The second distinction is even more structural: ROX's agents run on top of a customer's internal data warehouse, not on top of the CRM. Most of what you actually need to know about a customer — their business context, past interactions, internal signals — doesn't live in Salesforce. It lives in a data warehouse and a constellation of other systems. That's why ROX coined the term 'warehouse-native revenue agents,' and it's also what drove the architectural decisions that eventually led them to MongoDB.
ROX is built as a three-layer system: a context/knowledge-graph layer at the bottom, an agent swarms orchestration layer in the middle, and consumer applications on top.
Think of ROX as a three-layer cake: a knowledge graph and governance system at the base, an agent swarms orchestration layer in the middle managing potentially millions of agents, and consumer-facing apps (web, mobile, Slack, ChatGPT) on top.
