Rox raised $100 million to take on Salesforce. Its docs say your Salesforce data lands in a managed Snowflake warehouse, minus your sharing rules.
Rox calls itself a system of record for revenue. Before you pilot it, or any agent built on its own copy of your CRM, decide which system wins and who can see what.
Analysis. This piece contains the author’s interpretation. Where it relies on reporting, sources are listed below.
Rox, an AI sales agent startup, raised a $100 million Series B at a $1.3 billion valuation, Fortune reported on November 11. General Catalyst and March Capital co-led, and Fortune’s headline says Rox is “betting it can take on Salesforce.”
Rox’s own setup docs describe how that works today. Rox “uses Fivetran to ingest Salesforce data into a managed Snowflake warehouse,” located in the United States, and “Salesforce sharing rules and role hierarchies are not mirrored in Rox.” We’d treat a pilot of Rox, or of any agent that keeps its own copy of CRM data, as a data governance project: settle access and the source of truth before reps start using it.
What Rox says it is
In an essay written for Rox’s public beta and funding announcement, CEO Ishan Mukherjee writes that Rox’s agents “are powered by the Rox system of record” and that Rox “is not a thin application sitting on top of incumbent systems.” The product page describes one agent that handles “pipeline generation, lead qualification, meeting prep, deal management, proposals, and account expansion,” and promises to “consolidate SaaS tools.”
Named customers include Ramp, MongoDB, and New Relic. Fortune reports that Rox’s ARR has grown more than tenfold since its first year and that it plans to expand its US commercial team fivefold next year. Pricing starts at $100 a month for an individual and $255 a month for a team, metered in “Agent Actions” that expire at the end of each billing cycle.
What the integration actually does
Rox’s Salesforce docs describe a sync. Accounts, contacts, leads, campaigns, and mapped fields come in every 30 minutes by default, and activities every 5. Opportunity sync is Enterprise-only. Writeback needs a managed package installed in Salesforce, and without it “the connection will be read-only.” Rox can log sequence activities as Salesforce tasks and write engagement status and selected fields back.
For the simplest setup, the docs recommend a dedicated integration user “with a full Salesforce license and the System Administrator profile.” Rox decides who sees which accounts with its own assignment rules: “Users without a matching assignment rule do not see Accounts.”
So Salesforce stays in place, and Rox keeps a second copy with its own access model. That’s a reasonable design for an agent that also reads email, calls, and documents. It also means the access rules you’ve built in Salesforce don’t carry over automatically.
How we’d run the pilot
- Start read-only. Leave the managed package out until you’ve seen what the agent does with the data.
- Scope the integration user. If you can’t avoid a System Administrator profile, write down why, and limit the objects and fields you map.
- Rebuild access on purpose. List the Salesforce sharing rules that matter (territories, named accounts, partner data) and check that Rox’s assignment rules match before anyone else logs in.
- Decide which system wins. Pick, field by field, whether Salesforce or Rox is the source of truth, and test what happens when both change the same record.
- Ask where the data lives. The docs name a US Snowflake warehouse managed through Fivetran. If you have residency requirements, ask whether the Enterprise warehouse sync can run in your own account.
We made a similar point about Salesforce in Claude, which runs on your existing Salesforce permissions. Rox uses its own, so someone has to keep them in step with Salesforce’s.
What would change our mind
We’d treat Rox as a lighter lift if its docs showed Salesforce sharing rules mirrored automatically, or a supported deployment where the data stays in the customer’s own warehouse. A customer running Rox as its only CRM, with Salesforce turned off, would also show the “system of record” claim working in practice.
If you’ve piloted Rox or another agent-first CRM, how did you handle access rules, and which system did you let win?
Sources
- Fortune: “Meet Rox, the $1.3 billion AI sales startup betting it can take on Salesforce,” November 11, 2026
- Rox docs: Syncing with Salesforce
- Rox docs: Configuring Salesforce integration writeback
- Rox docs: System of Context
- Rox (Ishan Mukherjee): “Make the Best Better”
- Rox: Platform
- Rox: Pricing
Spotted an error? See how we handle corrections.
Responses
No responses yet.
Responses open when reader accounts launch. Until then, you can write a full post in response. Responses will follow our moderation guidelines.