Agent chaosAs reported·20 Oct 2026
A vendor's AI agent wipes SaaStr's Salesforce deals minutes after switch-on
As reported One person’s public account. We couldn’t independently confirm it, and we’ll update this if the facts change.
SaaStr says a well-known vendor's AI agent deleted almost all its Salesforce deals within minutes of being connected. A same-day snapshot saved them.
This is SaaStr's own account, from its podcast and on X, not independently confirmed. The vendor hasn't been named and nobody has said how many records were deleted.
What happened
In a podcast clip SaaStr posted on 17 October, the hosts say they hooked up an AI agent from a “very well-known company” as a favour, and it “immediately deleted almost all of our Salesforce data”: the opportunities, meaning the deals in the pipeline. Co-host Amelia says it happened on a Friday, right after her weekly pipeline clean-up, and that the agent “wiped it in like the span of 5 minutes.”
Founder Jason Lemkin posted the same day: “A third party agent deleted all our Salesforce records literally minutes after we deployed it.”
How it went wrong
In replies, Lemkin filled in a bit more. He says the product does over $100 million a year in revenue and is designed to close Salesforce opportunities, built with guardrails, and “It should not delete them.” It was given modify access so it could update records, and he says that access let it delete opportunities it thought no longer mattered and were long closed. They did approve something: “We gave a yes but the question was to ... What,” he wrote. “That was the agent error.”
How they got it back
The vendor's tool had no rollback. SaaStr's own agent, which runs on Replit, had a snapshot from about 11am that Friday and restored the data once Amelia confirmed, though a lot had to be restored by hand and changes made after the snapshot were likely lost. Lemkin's verdict: “Agents are still ... unpredictable.” With no name attached, the vendor hasn't said anything publicly.
Our take
An agent built to close deals ended up deleting them, because “modify” quietly included “delete”. Give a new agent the narrowest permissions that do the job, and start it on a sandbox or read-only, the way you'd treat a new hire's first week. Insist that any approval prompt spells out exactly what will change and how many records. And keep your own snapshot, because the vendor might not have one.
An approval prompt only protects you if it says exactly what will be deleted. Try new agents on a sandbox first.