Fetching from the wire…
Top 5 · 2026-07-18 · source-backed
A pharma company with a market cap in the hundreds of billions is pulling roughly 80% of its ServiceNow and adjacent app workloads onto an internal platform called Concierge, built with Cursor and Claude Code, targeting about $10M in savings. Matterfact's SaaS recap has the details.
I've been waiting for this specific story for about a year. Not "enterprise adopts AI coding tools." Not "company automates around a vendor." A named large enterprise using agentic coding to displace a system-of-record vendor. That's the category marker.
The reason it matters is that the workflow layer above a system of record has always been where SaaS vendors made their money. The database underneath ServiceNow isn't the moat. The 400 workflows, forms, approval chains, and integrations built on top of it are, because rebuilding those was a multi-year professional services engagement. When rebuilding them becomes a quarter of engineering effort instead, the moat is a puddle.
Corroboration from the smaller end: SaaStr's Episode #010 of The Agents has Jason Lemkin and Amelia Ruzzo detailing a migration of ~300 campaigns and ten years of member data off Marketo to Salesforce Marketing Cloud Next for $14.28 in token cost. The agency quote was ~$200K and a one-year timeline. An agent also rebuilt HeySummit (registration, reminders, livestream links, pre-submitted questions) in about an hour, killing a ~$10K/year subscription. Their stack is heterogeneous on purpose: Claude runs Opus, Replit runs Sonnet, Replit spawns an architect sub-agent on Codex. 21+ agents in production at an eight-figure business.
$14.28 against $200K is a 14,000x ratio. I don't fully believe it as a like-for-like comparison, because the agency quote includes accountability, warranty, and someone to yell at, and $14.28 includes none of that. But even discounting hard, the order of magnitude holds.
Here's the honest caveat, and it's the most useful number in this story. The 2026 Build vs Buy Shift Report finds 35% of teams have already replaced at least one SaaS tool with a custom build and 78% plan more. But Futurum's own survey shows in-house build preference at 56.0%, essentially flat from 56.6% six months earlier. Preference didn't move. Execution cost collapsed.
That distinction is the whole thing. Enterprises always wanted to build. They were blocked on cost, not desire. So don't read this as a change in what buyers want. Read it as the removal of the thing that was stopping them, which is a much more durable shift than a preference swing.
If you sell software: the question isn't whether your product is good. It's whether the part customers pay for is the part that's now cheap to rebuild.
Each link below shares sources, entities, or timing with this story.
Claude Code competes with Cursor / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code competes with Cursor); both cover Build, Claude Code, Cursor, Opus; overlapping topics (agent, been, claude, code, cursor).
SaaStr uses Claude / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (SaaStr uses Claude); both cover CLAUDE, Claude Code, Codex, Cursor; overlapping topics (agent, claude, code, coding, cost).
SaaStr uses Replit / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Replit); both cover Claude Code, Replit, SaaS, SaaStr; reported by the same outlet (saastr.com).
SaaStr uses Claude / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (SaaStr uses Claude); both cover Claude, Claude Code, Codex, Opus; overlapping topics (agent, been, claude, code, coding).
SaaStr uses Qualified / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Qualified); both cover Claude Code, Codex, Cursor, SaaS; reported by the same outlet (saastr.com).
SaaStr uses Claude / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Claude); both cover Build, Claude, Claude Code, Codex; overlapping topics (agent, claude, code).
SaaStr uses Claude / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (SaaStr uses Claude); both cover Claude, Claude Code, Codex, Opus; overlapping topics (agent, claude, code, coding).
SaaStr uses Claude / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Claude); both cover Build, Claude, Replit, SaaS; reported by the same outlet (saastr.com).