Episode
You Bought a Box of Car Parts. Now What? (the SaaS problem)
- Podcast
- Process Debt
- Published
- Mar 20, 2026
- Duration seconds
- 1327
- Processing state
not_requested- Canonical source
- https://rss.com/podcasts/process-debt/2644261
Actions
POST https://stenobird.com/v1/public/podcasts/process-debt-7039689/episodes/you-bought-a-box-of-car-parts-now-what-the-saas-problem/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/process-debt-7039689/you-bought-a-box-of-car-parts-now-what-the-saas-problem.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
SaaS tools promise to be intuitive. And for a single user, they often are. But add a team, skip the requirements conversation, and you've got a box of 300,000 Legos with no instructions and a deadline. In this episode, Toby and Chris dig into why technology implementations go sideways — and why the problem is almost never the software. Drawing on their work at Magic Button Labs, they cover: Why requirements anchored to your old system will recreate all your old problems in a new environment The difference between a Salesforce F1 crew and a ClickUp free-for-all — and why each demands a different approach Chris's month-long Zoom waiting room nightmare (and what it reveals about SaaS complexity) Why pushing people into the tool before locking in requirements is actually the right move The three non-negotiables for any team tool adoption: right people, clear process, executive sponsor They close with a challenge: if your tool isn't helping, it's because you haven't defined what you're trying to do clearly enough to build it in. The fix isn't a new tool. It's a better conversation.