Build vs. Buy Apps: Avoid Salesforce & Workday Nightmares #shorts
The speaker and Amelia discuss the practical challenges of building vs. buying software applications, arguing that even if you could replicate tools like Salesforce or Workday, the ongoing maintenance burden makes buying far more cost-effective. They use a real-time database connectivity issue as a concrete example of the hidden costs of self-maintained software.
Summary
The speaker opens by addressing a common social media meme suggesting that AI or custom builds could replace enterprise software like Salesforce or Workday. Their core argument is that even if replication were technically possible (which they assert it currently is not), the maintenance burden alone makes building impractical for most users.
The speaker emphasizes a cost-value comparison: most of these apps cost between $5 and $100 per month, while the time of skilled professionals like themselves is worth far more per hour. This makes buying almost always the economically rational choice.
Amelia then illustrates the real-world frustration of software issues by describing how a preview instance database connectivity failure earlier that day caused immediate exasperation. She highlights a key psychological dynamic: when third-party software fails, users can direct their frustration and support requests to the vendor (Salesforce, Squarespace, WordPress, etc.). When you build it yourself, that accountability falls entirely on you, compounding the stress of any outage.
About this episode
Thinking of building your own CRM? Think again. The real cost isn't just the bucks per month, it's the hours spent maintaining it. See why buying might be the smarter move. #AppDevelopment #SaaS #TechTips #BusinessStrategy
Key Insights
- The speaker argues that even if you could technically replicate Salesforce or Workday today, the real unsolved problem is ongoing maintenance — implying that 'who maintains it' is a more important question than 'can it be built'.
- The speaker frames the build vs. buy decision as a straightforward hourly rate arbitrage: SaaS apps cost $5–$100/month, while skilled developers cost far more per hour, making buying the economically dominant choice in most cases.
- Amelia points out that when third-party software fails, users instinctively direct frustration to the vendor, whereas self-built software eliminates that external accountability and places the full burden of blame and resolution on the builder.
Topics
Transcript
[0:00] I want to and I want Amelia to talk about a few of the things we had, but I think this is the meta answer to the meme on social media of oh we're going to kill Salesforce because I can buy but okay even if you could like which you can't you can't do a Salesforce or a workday today, but even if you could who the hell's going to maintain it you? You but you can buy a lot of these apps for like five to a hundred bucks a month you you're so Amelia Amelia and I are worth a lot more than five to hundred dollars an hour. So this is what so so we're…
Full transcript available for MurmurCast members
Sign Up to AccessMore from SaaStr AI
Salesforce Headless: Cut Costs, Boost Data Access! #shorts
The speakers discuss their experience running Salesforce in a headless configuration within an AI-driven marketing platform, which has increased daily usage despite fewer human seats. Paradoxically, their Salesforce bill has grown compared to a year ago, even with fewer human users, due to heavy data and API consumption by AI agents.
Our Agents Drove Our Salesforce Bill Up 80%, Marketo Hates Agents, and We Stealth-Churned Off Notion
Jason and Amelia discuss running a 20-agent AI organization at SaaStr, covering their AI VP of Marketing (10K) autonomously generating campaigns, unexpected Salesforce cost increases despite fewer human seats, Marketo's broken unsubscribe flow that they fixed themselves in 20 minutes, and findings from a Redpoint survey showing 54% of CIOs are consolidating vendors.
Resend vs Marketo: Email API Battle! #shorts
The speaker compares Resend and Marketo as email platforms in an AI-driven marketing context. Resend is praised for its elegant API integration with agentic workflows, while Marketo is criticized harshly for its inaccessible API. Some friction with email domain verification is noted even for Resend.
Figma Fails: Why It Breaks for Print Graphics! #shorts
The speaker discusses recurring failures when using Figma for print production graphics at SaaStr events. Despite warnings, sponsors repeatedly attempt to use Figma for booth graphics, and the files consistently break. The speaker argues Adobe Illustrator remains the gold standard for print production work.