Fetching from the wire…
Top 5 · 2026-06-07 · source-backed
If the Anthropic story is AI writing the code, this is AI running the company. In a SaaStr deep dive around June 5, Vercel CPO Tom Occhino said roughly 96% of the company's marketing content now starts with an AI agent, and a support agent resolves 93% of inquiries with zero human intervention. A lead-qualifying agent replaced a large chunk of the SDR team, and those people got redeployed instead of cut. Source: SaaStr
The detail I keep chewing on isn't the percentages. It's the sequencing. Vercel built hundreds of internal agents on its own stack before it productized any of them. They ate their own dog food at the org-chart level first. That's the part most companies skip. They want to sell the agent before they've run their own GTM on it.
Now, a healthy dose of skepticism. "96% of marketing content starts with an agent" is doing a lot of work in that sentence. "Starts with" is not "ships from." There's a human in that loop deciding what's good. And compare it to the SaaS-disruption finding lower in this issue: real-world support deflection across actual deployments lands at 41 to 58%, not the 80%+ vendors love to claim. Vercel's 93% is either an outlier, a generous definition of "resolved," or both. I don't have the underlying ticket data, so I'm not going to pretend the number is gospel.
But the strategic move is the lesson, not the stat. Build internal agents on your own stack before you try to sell them. You learn where they break on workflows you actually understand, with stakes you can afford. By the time you productize, you've already paid the tuition.
For solo builders and small teams, the takeaway scales down cleanly. You don't need hundreds of agents. You need to pick the one repetitive function eating your week. Support triage, content drafts, lead sorting, and wire an agent into it before you reach for the next shiny side project. The companies winning here aren't the ones with the best models. They're the ones who turned their own operations into the testing ground.
Each link below shares sources, entities, or timing with this story.
Vercel uses Anthropic / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Vercel uses Anthropic); both cover Anthropic, GTM, SDR, Support; reported by the same outlet (saastr.com).
Zendesk uses SaaS / Shared entities / Same source domain / Shared topic / What happened next / Tension
Linked by a graph relationship (Zendesk uses SaaS); both cover GTM, SaaStr, SDR, Vercel; reported by the same outlet (saastr.com).
Vercel partners with Slack / Shared entities / Same source domain / Shared topic / What happened next / Tension
Linked by a graph relationship (Vercel partners with Slack); both cover Anthropic, Build, SaaS, SaaStr; reported by the same outlet (saastr.com).
Jason Lemkin works at SaaStr / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Jason Lemkin works at SaaStr); both cover SaaS, SaaStr, SDR; reported by the same outlet (saastr.com).
SaaStr uses Agentforce / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (SaaStr uses Agentforce); both cover SaaS, SaaStr, Support; reported by the same outlet (saastr.com).
Vercel uses Anthropic / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Vercel uses Anthropic); both cover Anthropic, SaaS, SaaStr; reported by the same outlet (saastr.com).
Intercom uses SaaS / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Intercom uses SaaS); both cover SaaS, SaaStr, Support; reported by the same outlet (saastr.com).
SaaStr uses Monaco / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Monaco); both cover GTM, SaaS, SaaStr; reported by the same outlet (saastr.com).