CHAPTERS
- 0:00 – 0:39
Second product or loss of faith? The core question founders must answer
The conversation opens with a blunt diagnostic: many "second products" are really a sign that the founder has stopped believing in the first. Dalton frames it as a story founders sometimes tell others (investors, the market), but warns against telling it to yourself.
- •A second product can be a rational expansion—or a concealed abandonment of the original idea
- •Using "multi-product" as a narrative for outsiders is different from internal clarity
- •The most important first step is honest self-diagnosis about why you’re switching focus
- 0:39 – 1:21
Two starting scenarios: failing core vs breakout hit
Dalton lays out the primary decision fork: if product one is failing, adding another product rarely fixes the underlying problem; it’s usually a pivot. If the first product is compounding quickly, a second product may be justified—depending on the strategic story.
- •If the first product is failing, a second failing product doesn’t help—consider a pivot
- •If the first product is a smash hit, expansion can make sense
- •The right answer depends heavily on context, not a generic rule
- 1:21 – 1:51
The underrated risk: winning but expanding too slowly
Michael adds a less-discussed failure mode: things are going well, but the company doesn’t build the suite fast enough to compete with incumbents. Startups often benchmark against peers rather than the established platforms they ultimately face.
- •A company can lose despite early success by not expanding its product surface area
- •Startups often mis-measure competition by comparing to peers, not incumbents
- •Incumbents typically win with suites, not single features
- 1:51 – 2:18
Suite competition examples: Slack vs Microsoft, Notion, and the Office analogy
Michael uses Slack as a cautionary tale: lacking a broader suite made it vulnerable when Microsoft Teams arrived. He contrasts this with companies that anticipate suite competition (e.g., Notion) and with the historical lesson of Google Docs taking on Office by building a full set of tools.
- •Slack’s limited suite left it exposed to Microsoft Teams in enterprise
- •Competing with platform incumbents often requires a competing suite
- •Office-like markets tend to converge toward bundled products
- 2:18 – 2:47
Reality check on playbooks: incumbents weren’t multi-product at year one
Dalton points out the irony of very young startups trying to copy late-stage strategies. Microsoft and Google were single-product companies for years before expanding, and the timing of expansion matters as much as the decision itself.
- •Microsoft and Google spent many years as largely single-product companies
- •A one-year-old startup copying a decades-old playbook is often misguided
- •Timing and maturity influence whether multi-product is wise
- 2:47 – 3:39
The VC trap: stacking small 'PMF' businesses rarely builds a great company
Michael critiques a common venture pattern: calling limited traction “PMF in a small market” and then trying to stack multiple ~$20M businesses into IPO scale. Both suggest this rarely works unless a core product becomes a true breakout.
- •“PMF with asterisks” often signals constrained demand or weak growth
- •The idea of stacking multiple mediocre revenue lines is usually a dead end
- •Multi-product works best when anchored by a clear hit, not a plateau
- 3:39 – 4:06
Second product vs pivot: semantics vs substance
Dalton reframes the terminology: if the first product isn’t working, the next thing isn’t really a “second product,” it’s a pivot. Labels can be retroactively justified, but the underlying situation should guide the decision.
- •If the first product isn’t a hit, the new product is effectively a pivot
- •With hindsight, teams rewrite narratives—but founders need clarity in real time
- •Avoid using language to obscure the real strategic reset
- 4:06 – 4:28
What good multi-product looks like: product suite expansion (PostHog)
They highlight PostHog as a strong example: the initial analytics product worked, and adjacent products (like session replay) fit naturally into a cohesive suite. The key is building additions that deepen value for the same customer and workflow.
- •A hit core product can be expanded into a logical suite
- •Adjacency matters: new products should share users, data, and workflows
- •PostHog’s analytics → session replay shows coherent multi-product strategy
- 4:28 – 4:49
Defensive expansion: when you must broaden or someone else will (DoorDash)
Michael describes cases where expansion is almost mandatory once you have an advantage. DoorDash is used as an example where extending from food delivery into groceries and convenience can be a competitive necessity.
- •Once a company wins a wedge, it may need to expand to defend the position
- •Adjacent markets can be captured using the same logistics/customer base
- •Not expanding can invite competitors to take the next layer of value
- 4:49 – 6:03
Scaling luck into durability: Zoom’s COVID surge and the suite problem
Zoom illustrates how hard it is to shift attention away from a product that’s working extremely well—yet that may be exactly what’s required to create a durable business. They argue Zoom is effectively in an office-suite competitive arena whether it wants to be or not.
- •Extraordinary growth moments create pressure to expand into enduring use cases
- •Founders struggle to divert focus away from a high-performing core product
- •Office-suite gravity pulls tools into competition with Microsoft/Google ecosystems
- 6:03 – 6:34
Hockey stick that didn’t compound: Peloton as a cautionary example
Dalton brings up Peloton: explosive growth prompted attempts to broaden offerings, but the company didn’t turn that moment into sustained multi-product compounding. They caution against assuming that initial success automatically implies successful expansion.
- •Rapid growth can mask fragility if expansion doesn’t land
- •Trying “a bunch of stuff” without cohesive fit can fail to create durability
- •Success at one product doesn’t guarantee suite-building ability
- 6:34 – 7:55
How Google got multi-product right: Gmail → broader suite (plus acquisitions)
They credit Gmail as a landmark second product that overcame internal resistance and became massively successful. They also note Google’s suite grew quickly afterward, with important components coming via acquisition, reinforcing that “multi-product” can be built, bought, or both.
- •Gmail faced internal resistance but became a dominant global product
- •Google Docs/YouTube show how powerful multi-product compounding can be
- •Acquisitions played a meaningful role in building the broader suite
- 7:55 – 9:27
Final diagnostic: are you truly multi-product, or just pivoting with a cover story?
They close by returning to founder honesty: calling it a second product can be a convenient narrative, but the real issue is whether you’ve lost faith in the original. Michael shares Twitch/JustinTV as an example where funding from an older product didn’t make it a true multi-product company, and they note many businesses plateau around ~$20M revenue.
- •Don’t confuse external narrative with internal truth about strategy
- •Funding/support from an old product doesn’t necessarily mean multi-product (Twitch example)
- •Plateauing revenue is common; acknowledge it instead of rationalizing it away
