Good timing makes great products (Interview)
Paul Orlando is back to talk about his book titled “Why Now?” You may remember Paul from his last appearance (a fan favorite) talking with Jerod about complex systems & second-order effects. Paul’s book, “Why Now?” explores the concept of timing and the importance of understanding the ‘why now’ in business and product development. We discuss timing examples from the book that were either too early or too late (such as the first video phone and car phones), the need to consider both technological advancements and user demand when assessing timing, the significance of timing in the success of companies like Apple and the launch of the iPhone, Uber and Heroku, and more. Also, join our Slack community for a chance to get a signed copy of Paul’s book.
Join the discussion
Changelog++ members get a bonus 8 minutes at the end of this episode and zero ads. Join today!
Sponsors:
Sentry – Code breaks, fix it faster. Don’t just observe. Take action. Sentry is the only app monitoring platform built for developers that gets to the root cause for every issue. 90,000+ growing teams use sentry to find problems fast. Use the code CHANGELOG when you sign up to get $100 OFF the team plan.
Cloudflare – Read the Developer Week 2024 wrap-up or tune into Developer Week on Cloudflare TV.
Factor – 50% off Factor ready-made meals! Pick your ready-made meals, choose from 35+ fresh, never-frozen meals and 55+ add-ons, every week. Gourmet chefs prepare your meals, so you can enjoy more of your time to focus! Heat, eat & enjoy — No prep. No mess. Factor meals arrive ready to heat and eat in 2 minutes. Learn more at factormeals.com/changelog50
Featuring:
Paul Orlando – Website, LinkedIn, X
Adam Stacoviak – Website, GitHub, LinkedIn, Mastodon, X
Jerod Santo – Website, GitHub, LinkedIn, Mastodon, X
Show Notes:
Why Now: How Good Timing Makes Great Products (by Paul Orlando)
StartupsUnplugged.com
Unintended Consequences (Systems, complexity, second-order effects)
Changelog #474: Complex systems & second-order effects
Catching up with Yahoo’s Fire Eagle geolocation service
The Web 2.0 Show #46 - Fire Eagle
The Conjoined Triangles of Success
The confidential YouTube Investment Memo by Sequoia you were never meant to see
Something missing or broken? PRs welcome!
Net Revenue Retention: CAC, LTV, and Churn Explained
Most SaaS founders get their SaaS metrics wrong. Paul Orlando says if you have one number for CAC and one for LTV, you haven't started measuring net revenue retention properly.
Learn how to calculate customer acquisition cost by channel, model LTV as a river, track net revenue retention by cohort, and why negative SaaS churn is the gold standard.
Paul is a USC professor and author of Growth Units. His breakdown of SaaS metrics including net revenue retention, customer acquisition cost, and churn models helps founders measure what matters.
🔑 Key Lessons
📉 Break SaaS metrics down by acquisition channel: A blended customer acquisition cost hides which channels scale for net revenue retention.
💰 Model LTV as a river, not a single SaaS metric: Map monthly cash flows with retention rates to reveal actual payback periods.
🔄 Track cohort-based net revenue retention: Comparing monthly cohorts shows whether product changes actually reduce SaaS churn.
🚀 Target negative net revenue retention as the ultimate goal: When remaining customers expand faster than churned ones leave, you achieve negative churn.
🧠 The CAC-to-LTV ratio is a starting point for SaaS metrics: Bootstrapped founders may need 1:5 while growth companies accept 1:1.
Chapters
Introduction
How Growth Units came about
Overview: CAC, LTV, and net revenue retention
What is customer acquisition cost
Breaking CAC down by channel
Growing versus scaling
Fixed vs. variable CAC
How much should CAC be
What is LTV as a SaaS metric
LTV as a river
Cohort analysis for net revenue retention
CAC-to-LTV ratio benchmarks
Three SaaS churn models
Negative net revenue retention explained
Lightning round
Resources
Full show notes: https://saasclub.io/313
Join 5,000+ SaaS founders: https://saasclub.io/email
Complex systems & second-order effects (Interview)
Paul Orlando joins Jerod to talk through some unintended consequences that occur when systems operate at scale. We discuss Goodhart’s Law, The Cobra Effect, how to design incentive systems, dependency management decisions, the risks of autonomous vehicles, and much more along the way.
Join the discussion
Changelog++ members save 6 minutes on this episode because they made the ads disappear. Join today!
Sponsors:
InfluxData – InfluxDB empowers developers to build IoT, analytics, and monitoring software. It’s purpose-built to handle massive volumes and countless sources of time-stamped data produced by sensors, applications, and infrastructure. Learn about the wide range of use cases of InfluxDB at influxdata.com/changelog
Square – Develop on the platform that sellers trust. There is a massive opportunity for developers to support Square sellers by building apps for today’s business needs. Learn more at developer.squareup.com to dive into the docs, APIs, SDKs and to create your Square Developer account — tell them Changelog sent you.
FireHydrant – The reliability platform for every developer. Incidents impact everyone, not just SREs. FireHydrant gives teams the tools to maintain service catalogs, respond to incidents, communicate through status pages, and learn with retrospectives. Try FireHydrant free for 14 days at firehydrant.io
Retool – Retool is a low-code platform built specifically for developers that makes it fast and easy to build internal tools. Instead of building internal tools from scratch, the world’s best teams, from startups to Fortune 500s, are using Retool to power their internal apps. Learn more and try it for free at retool.com/changelog
Featuring:
Paul Orlando – Website, LinkedIn, X
Jerod Santo – Website, GitHub, LinkedIn, Mastodon, X
Show Notes:
The Unintended Consequences blog
A New Morality of Attainment (Goodhart’s Law)
The Cobra Effect Redesigned (Examples & Antidotes)
The Cobra Effect (Part 2)
Uncertainty Saves Lives – the Peltzman Effect
Garmin Hack and Dependence
Autonomous Vehicles and Scaling Risk
A Pattern Language
Growth Units: Learn to Calculate Customer Acquisition Cost
Something missing or broken? PRs welcome!