Jun 22, 2023 · 55m · in-depth
Lessons from Stripe on adding new products | Tara Seshan (Watershed, Stripe)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Tara Seshan, Head of Product at Watershed and former Stripe leader, provides an actionable blueprint for scaling multi-product SaaS companies, structuring autonomous zero-to-one teams, and hiring high-potential product managers.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Brett holds 17.4% of the talking time here. How this is scored →
Brett as informed peer 4.6 Guest teaching 6.4 Guest disagreement 1.2 Brett pushing back 1.3
speaking balance: gold is Brett, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 36:25 Contrasting analytical rigor with intuitive home runs
Tara politely pushes back against purely analytical multi-product frameworks, pointing out that Jack Dorsey's instinctual Cash App bet produced a massive home run that analytical models would have missed.
Hardest push from Brett ▶ 37:15 Brett questions the risk of organizational atrophyBrett challenges the conventional wisdom of waiting to build new products, arguing that companies risk organizational atrophy if they fail to develop the multi-product capability early.
Biggest teaching moment ▶ 22:15 The unexpected buyer pivot in Stripe BillingTara educates the host on how fast-growing customers rapidly outgrew developer-centric tooling, forcing Stripe to overhaul Billing for enterprise finance buyers and Florentine accounting principles.
Brett holds their own ▶ 28:10 Brett synthesizes three distinct multi-product categoriesBrett clearly articulates a crisp, three-part product taxonomy (same buyer, same customer/new buyer, and net-new TAM) to anchor Tara's organizational design insights.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Brett as informed peer | Guest teaching | Guest disagreement | Brett pushing back | Why |
|---|---|---|---|---|---|---|
| Stripe's Early Days as a Single-Product Developer Tool | 4 | 6 | 1 | 1 | Brett sets the stage asking about Stripe's transition from single to multi-product. Tara shares detailed historical context on Stripe's initial card payments focus and how products like Radar and Connect naturally evolved to serve existing buyers and unlock new segments. | |
| Lean Resourcing and Organizational Design for Initial Product Bets | 5 | 6 | 1 | 2 | Brett probes into the sophistication of resource allocation between core products and secondary bets. Tara explains that lean resourcing (2-3 engineers) is an intentional constraint to maintain velocity and minimize coordination drag before proof of concept. | |
| Filtering Bottom-Up Ideas and Applying the 'Why Now' Test | 5 | 7 | 1 | 2 | Brett asks whether bottoms-up idea selection relies on taste or systematic frameworks. Tara elaborates on the 'why now' filter and Patrick Collison's high bar of painting a path to $10B in enterprise value. | |
| Constructing Autonomous, Highly Versatile 0-to-1 Teams | 4 | 6 | 1 | 1 | Tara breaks down the archetypes needed for 0-to-1 squads: autonomous, generalist engineers and PMs who can sell, design, and interpret ML models. She emphasizes hiring for potential rather than pedigree or conventional PM specialization in early stages. | |
| Core Hiring Pillars: Hunger, Horsepower, and Wins Above Replacement | 4 | 7 | 1 | 1 | Brett asks for Tara's internal algorithm for assessing unproven talent. Tara outlines her three-pillar framework: hunger, horsepower, and wins above replacement, illustrated with concrete behavioral examples like Chris Cox's learning question. | |
| PM Failure Modes, Cultural Fit, and Interviewing Tactics | 4 | 6 | 1 | 1 | Tara discusses PM anti-patterns, specifically the trap of hiring someone brilliant whose strengths do not match organizational needs (e.g., Stripe's heavy written culture). She also explains how to unearth hidden drivers versus passengers during interviews. | |
| The Stripe Billing Pivot: Shifting from Developers to Finance Buyers | 5 | 8 | 2 | 1 | Tara details a major strategic failure mode when launching Stripe Billing under the assumption that developers would remain the sole buyer. As target accounts scaled, the buyer shifted to finance leaders, breaking sales quotas and necessitating extensive architectural refactoring. | |
| Preventing Customer Churn and Scaling Alongside Enterprise Clients | 5 | 6 | 1 | 1 | Brett asks if Stripe considered shelving Billing once the enterprise buyer complexity emerged. Tara explains that preventing high-growth customers like Notion and Figma from churning off Stripe was an existential imperative, making it easier to solve retention than to win net-new replacements. | |
| Structuring Net-New Expansion Bets as Internal Startups | 5 | 6 | 1 | 1 | Brett structures product expansions into three distinct categories. Tara explains how targeting net-new customers requires treating the team as an autonomous internal startup with dedicated sales motions, modified quotas, and board-style governance. | |
| Strategic Vision and Multi-Product Timing: Stripe vs. Watershed | 4 | 7 | 1 | 1 | Tara contrasts Stripe's sequential multi-product approach with Watershed's early expansion into supply chain decarbonization. She highlights Peter Thiel's concept of definite optimism and how foundational interdependencies dictated Watershed going multi-product much earlier. | |
| Methodical Growth Levers vs. Intuitive Product Home Runs | 5 | 6 | 2 | 2 | Brett asks how much timing can be governed methodically versus intuitively. Tara contrasts Stripe's analytical 4-lever expansion model with Jack Dorsey's intuitive bet on Cash App, arguing that home runs often require intuition over incremental analysis. | |
| Developing Multi-Product Capability and Cultural Protection | 6 | 5 | 2 | 3 | Brett challenges conventional wisdom, raising the risk of organizational atrophy if companies wait too long to build multi-product capability (citing Atlassian). Tara acknowledges this but cautions against premature expansion and explains how leadership must shield new bets from core company metrics. | |
| Operational Governance: QBRs, Product Reviews, and Founder PMs | 4 | 6 | 1 | 1 | Tara outlines the operational governance rhythms for internal bets, including quarterly board-style QBRs and monthly product reviews. She notes the value of staffing ex-founders who thrive amid ambiguity and proactively ensure core compatibility. | |
| The 12-Question Product Review Framework and Target User Discipline | 4 | 7 | 1 | 1 | Tara details her 12-question product review framework, stressing that teams cannot proceed past Question 1 without identifying their target user. She uses the Enterprise Rent-A-Car wedge case study to illustrate how strategic target user definition dictates winning product tradeoffs. | |
| Conducting Rigorous Written Reviews and Accelerating Learning Cycles | 4 | 6 | 1 | 1 | Tara explains how product reviews operate asynchronously through rigorous written documents and pre-reads. For net-new bets, she places heavy weight on accelerating feedback loops through creative early proxies like pitching contract CFOs rather than awaiting full sales cycles. | |
| Formulating Product Mental Models and Applying Default Skepticism | 5 | 7 | 1 | 1 | Tara warns against relying on user research like a drunkard using a lamppost, advocating instead for a strong mental model validated through default skepticism. She concludes with lessons learned from Patrick Collison and Shreyas Doshi on rigorous prioritization. |
Statements from this episode (29)
Seshan: Amber Feng and Christina Cordova built Stripe Connect's initial multi-party version
“And then we had started exploring this thing called Connect where Amber Feng and Christina Cordova had built an initial version of this, like, multi-party payments idea that Someone like Shopify or someone like Lyft could be able to route payments in multiple …”
Seshan: Multi-product startups succeed more often by selling to existing buyers
“The angle I think is really fruitful within a company, is sell something else to your same buyer. And you kind of know that user and you know their needs. You're much more likely to succeed by giving them an additional product than trying to launch a product t…”
Seshan: Stripe core payments took around 75% of engineering bandwidth
“Core payments maybe took 75% of the engineering bandwidth.”
Seshan: Overfunding early product bets creates coordination drag and slows progress
“Actually in that early stage of, Trying to establish something. Actually having more resourcing holds you back, as counterintuitively as that seems. Like, more people to bring along versus people who you're ideating with actually create drag on that process.”
Seshan: Bottom-up ideation yields three to four good ideas per fifty
“Initially, there'll be, like, 50 bad ideas on the table for those types of ancillary products, and probably, like, three or four good ones, and so you want to be able to bottoms-up identify what are those three to four good ones.”
Patrick Collison required new Stripe products to plausibly add $10B in enterprise value
“When Stripe got larger and larger, the question became not only why now, but like, what's the opportunity on the table for this idea? Like, this has to be an idea where we could eventually work it out to Patrick's, you know, sort of bar was, is this gonna add,…”
Seshan: Zero-to-one teams should have two to four engineers and zero dependencies
“Yeah, I think you want the team to be really self-sufficient. So you want the team to not have to reach outside of itself to borrow expertise from other parts of the organization. Like certainly within the organization, there are parts of the code base that th…”
Seshan: High-potential hires generate more value than experienced, prestigious candidates
“Hungry and high potential person who's dedicated to growing quickly can build more value for the business than a statusy or experienced person who is less high potential.”
Seshan: Most Smart People Lack the Drive to Finish Projects
“Like, most smart people are actually terrible at having the drives or follow through to take the thing over the finish line, drag it through.”
Seshan: High-potential hires fail most often from organizational mismatch
“Honestly, that's the most common failure mode with this kind of thing, where you hire someone who you do see glimmers of greatness in them, but they're just not great in the way the organization needs, and the organization, like, Oregon rejects them in some wa…”
Seshan: Promotions in low-quality orgs signal diamond-in-the-rough talent
“Also, another, like, factor that can hide folks, like, make them really diamonds in the rough, is that they might do high-quality work in a low-quality org, so they might be doing a lot of great stuff in a place that just doesn't, that isn't great. When you lo…”
Seshan: Stripe's subscription buyer shifted from developers to finance teams
“It was actually over the course of A couple years where the decision-making power sort of shifted in our existing user base to more of a finance buyer.”
Seshan: Stripe's core business model relies on retaining scaling customers
“The whole engine of Stripe's business is your users should not grow, grow off you. Like as they scale, you make more money. And they make more money.”
Seshan: Building products to prevent churn is easier than winning net-new buyers
“It's like always easier in a lot of ways to do the prevent churn off of you versus win someone out of the gate.”
Seshan: Unseating incumbents requires 10x quality, but retention products just need baseline utility
“You have to be tenx better at that phase than whatever they had before versus we just didn't, we just need to not suck with the other way.”
Seshan predicts every public company will require carbon accounting in 10 years
“In 10 years, every public company will need to do some level of carbon accounting and have a decarbonization plan to underscore that.”
Seshan: Stripe did not expand multi-product until core payments was deeply working
“The engine that powers Stripe is payments. It is payments. It's always gonna be payments. Like, payments is really, really vital, and Stripe should not have, and did not, like, overreach into multi-product before payments was, like, really, really, really work…”
Seshan: Analytical expansion yields doubles, but product home runs require intuition
“The analytical approach will get you a lot of, like, doubles and triples. But I think the home runs really come from this, like, intuitive call for, like, how do I think the market is going to work? How do I think the world is going to work? And, like, let me …”
Seshan: Companies should not launch new products early just to build muscle
“I mean, I think it's, it would be hard to say that folks should do this early for the sake of building the muscle alone, just because cost of doing it is quite high.”
Seshan: Judging new bets by core business yardsticks causes them to fail
“One of the most common reasons for this not working within companies is that people judge the net new bet by the same yardstick that the rest of the company is judged on. And that is not just an executive decision. It cascades all the way down.”
Seshan: Treat internal net-new product teams like startups acting as their board
“With net new bets, especially ones that have a, their own go-to market, selling to a new buyer, selling differently, almost want to treat the team as if you were their board and they were starting a startup in some ways.
Like you're being a lot more hands-on t…”
Seshan: Incubation teams instinctively underemphasize compatibility with the core business
“The team's instinct is almost always going to be like, hey, we're building our new thing.
And we have so many important questions to solve about whether people care about fraud management or not.
They're going to under emphasize the compatibility with the core…”
Seshan: Watershed and Stripe hired mostly ex-founders for zero-to-one PM roles
“A lot of the PMs that we've hired to do that type of work are ex-founders, and that was true of Stripe as well.”
Seshan enforces strict 12-question product review starting with target user
“I have a set of 12 questions that I ask in every product review, and there's a very strict guidance of, like, you cannot move on to question two until you've sufficiently answered question one, and question one starts off, like, very basically, who is your tar…”
Seshan: Defining the target user is the most important product strategy choice
“Your target user is the most important question, full stop for your product area. Like that is the best strategy choice you can make. And so if you cannot clearly outline to me who your target user is and why, and therefore like You know, as you go through my …”
Seshan: Early software versions are inherently bad and require user context to evaluate
“Like, software is never done, and software is always bad in the first version of it, and so with the assumption that you are looking at a bad piece of software because it's the first version that someone's built, it is very hard to evaluate a bad piece of soft…”
Seshan: Product development must flow from research to model to product
“The best product stems from a very, very strong mental model of the domain and the users. Like, and UXR can help you get to such a model and validate it along the way, but it's important to view the sort Syllogism as UXR model product, not UXR to product.”
Seshan: Product teams should enter user interviews with default skepticism
“Go into the, that meeting expecting the user to sell you on the product rather you selling them. Like your default skepticism should be so high that the user is actually trying to convince you that this thing is necessary.”
Seshan: Building the 'Best Product' Matters Less Than Target User Fit
“Everyone always, like, overestimates the impact of, like, specific features and being the best product. Like, being the best product is not an answer. You have to be, like, the right product for your target user. Being the best means nothing.”