ATRIUMsearch → argument graph
AnecdoteVideo · 45:56 — 47:26

We canceled our $600,000-a-year Salesforce contract because we built our own internal, vibe-coded CRM that manages our process better and is more integrated with our agent workflows, and it only took two months to build.

Curative canceled its $600K/year Salesforce contract after building a vibe-coded internal CRM in two months that outperformed it and is fully integrated with their AI agents. ✦ AI generated

Fred Turner · 20VC · 2026-07-18 · original ↗

starts at this moment · 45:56

Elicited by

Do you buy the SAS is dead theory that we will [replace it]?

We just recently canceled our Salesforce contract because we have an internal CRM that was built, you know, was vibe coded, that is working better, that is managing our process better, is more integrated into what we're doing. We run our agents inside of it and no one was using Salesforce anymore.

verbatim transcript · starts at 45:56

Transcript · around this moment

45:37scratch. >> Dude, I have so many questions to ask on the back of this. The first one is you mentioned there kind of the internal agent buildout that you've done for the company and for your specific processes. Yeah. >> Do you buy the SAS is dead theory that we will >> Why? >> Because I see the number of contracts we're canceling. >> Like we we just recently canceled our

45:56Salesforce contract because we have an internal CRM that was built, you know, was vibe coded, that is working better, that is managing our process better, um is more integrated into what we're doing. We run our agents inside of it and no one was using Salesforce anymore. $600,000 a year. >> Wow. >> Gone to zero. How long did it take? >> Two months. >> Is it worth because argument back I

46:20always like to do both sides. I'm never Is it worth the engineering hours to vibe code that and then to maintain it? >> The maintenance is is definitely one of the most challenging pieces. Um I agree with that. I think for most businesses of of any reasonable scale, yes, it is worth it. Now whether they will have the tech resources to do that soon, I think that's like the bigger question is kind

46:42of when will this happen? But when you build those things custom to your workflow, they work better. Like most of these big, you know, systems, you're paying an administrator. Like we had a full-time Salesforce administrator, right? You're paying people whose sole job is to manage this like archaic software platform. Not that Salesforce is archaic, but you know, we have a few other like internal apps that we were

47:06paying for like industry software that is taking multiple FTEEs to maintain it. You can transition that into one great engineer and then whenever you want a custom feature, you just go build it. >> Absolutely [ __ ] wild. [laughter] $600,000 a year on Salesforce. >> Yeah. >> Wow. And so we're seeing, you know, there's pockets of software that I think persist because they are more infrastructure based.

47:34>> Okay. Which persist? >> So we're seeing a lot of backend stuff like uh like Sentry like stuff like that, right? Where it's like kind of become part of your infrastructure. Um Slack has been like notoriously hard internally for us to like too many so many people have built integrations and like workflows that are now working in Slack. Uh, I think that while they keep putting the prices up, if they put the

47:54prices up too much, then eventually it'll make sense to replace that. But, um, >> what else is on the chopping block? >> We we're cutting about 80% of our SAS spend this year. >> Wow. >> So, we have like in in one of our internal meetings, we have a slide of like when when are SAS contracts due and whose job is it to tell them that we're

Around this claim
In practice · 5
This moment responds to