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.
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
Full transcript available for MurmurCast members
Sign Up to Access