Lenny's PodcastRohini Pandhi: Why founders should be the PM until it breaks
Through pioneer, town settler, and city planner PM archetypes; Mercury scaled from zero PMs to 30 by matching type to product maturity stage.
CHAPTERS
- 0:00 – 5:55
Mercury’s “no PMs” stance—and what finally changed
The episode opens with the provocative premise: Mercury’s CEO once bragged about having no product managers, yet Mercury now has a real PM org. Lenny and Rohini set up the central question: what signals tell founders it’s time to bring PMs in?
- •Mercury’s early philosophy: engineers/designers can cover PM duties
- •Why founders often resist PMs (fear of bureaucracy, slowing down, disempowerment)
- •The key question: what tipping point made leadership hire PMs?
- •Framing the conversation around lessons for founders building product orgs
- 5:55 – 9:51
How Mercury scaled so far without PMs (and the conditions that made it work)
Rohini explains that Mercury didn’t truly operate without product leadership—founders filled that role, supported by strong product-minded engineers and designers. The segment clarifies what needs to be true for “no PMs” to work for a meaningful period of time.
- •Mercury hired its first official PM surprisingly late (~400 employees, ~200 in R&D)
- •Founders function as the original PMs; don’t outsource product thinking too early
- •Success without PMs requires exceptional, autonomous engineers and designers
- •Staying close to customers and the built solution is non-negotiable
- •Parallels to early Square/Block operating similarly
- 9:51 – 13:18
The real trigger: bottlenecks, complexity, and hidden PM work
Mercury’s growth created decision-making and coordination bottlenecks, plus increased regulatory and cross-functional complexity. Rohini describes how “PM work” always exists—without PMs, it simply gets absorbed by engineers/designers or ad-hoc generalists.
- •Scale made founders a decision bottleneck; execution slowed or stalled
- •Fintech complexity: compliance, legal, risk, partnerships, cross-functional checks
- •Without PMs, engineers/designers spend time on PM/project work instead of their craft
- •Mercury created “business lead” generalist roles to handle coordination
- •Title changes to PM happened later; missing core PM fundamentals created gaps
- 13:18 – 19:52
Building Mercury’s PM discipline: defining the job, leveling, and hiring
Rohini walks through the practical build-out of Mercury’s product function: clarifying expectations, creating a career ladder, and aligning hiring and interviews to the capabilities Mercury values. The focus is on making PM success legible internally.
- •First step: define what PM means at Mercury (role clarity and alignment)
- •Create a PM career ladder/matrix tied to company values (humility, low ego)
- •Success dimensions: customer love + measurable business impact
- •Additional expectations: long-term vision, communication, cross-functional leadership
- •Interview process designed to test the same skills emphasized in the ladder
- 19:52 – 26:16
Don’t hire PMs too early—and hire the right “flavor” of PM
Rohini offers clear guidance on when *not* to hire PMs and what milestones make it necessary. She then shares a Square framework for matching PM types to the product’s maturity stage.
- •Avoid hiring PMs before founders can’t do the job anymore
- •Hire when founders are a bottleneck or when PM work is crowding out eng/design work
- •Hiring becomes critical when expanding into new segments or product areas
- •Three PM archetypes: pioneer (0→1), town settler (growth), city planner (mature/scale)
- •Interview for “receipts”—validate what candidates actually did, not just resumes
- 26:16 – 35:39
How to attract top product talent: the S-curve, the problem, and the people
Rohini explains what makes senior PMs excited to join: the right next step in their growth curve, meaningful scope, and high-caliber peers. She emphasizes transparency and an interview process that signals competence and seriousness.
- •Use an ambiguity-vs-scale ‘S-curve’ to understand a candidate’s next growth step
- •Senior candidates want a meaty problem and a chance to become better PMs
- •The team matters: strong functional peers (PM/design/eng) are a major draw
- •Be radically transparent about the good/bad/ugly—build trust during recruiting
- •Candidates judge companies by interview quality; revamp interviews to match seniority
- 35:39 – 43:50
Advocating for product quality: craft as a compounding advantage
Rohini makes the case that investing in quality is not irrational—it builds trust, differentiation, customer love, and talent magnetism, especially in fintech. She shares a concrete example from Mercury’s Bill Pay experience to show how small details can create outsized brand impact.
- •Reject the false dichotomy: metrics-driven experimentation vs design craft
- •In fintech, details and precision build trust with customers’ money
- •Bill Pay example: invoice OCR + UI zoom detail that delights users (even if not metric-moving)
- •Quality compounds into a moat over time and becomes a durable differentiator
- •Quality must be a top-down cultural value, not just a PM preference
- 43:50 – 47:01
Going multi-product: what Mercury launched and why it’s hard
The conversation shifts to Mercury’s multi-product expansion—an aspiration for many startups that often fails in execution. Rohini lays out Mercury’s recent launches and what “getting good at launching” looks like in practice.
- •Mercury’s 2024 expansion: Personal Banking + software suite atop business banking
- •Key launches: Bill Pay, Invoicing, spend controls/management, reimbursements
- •Notable metric: each subsequent launch took less time from concept → launch
- •Multi-product is framed as a ‘holy grail’ (TAM expansion, revenue, deeper workflows)
- •Mercury still battles perception as “just a bank,” highlighting go-to-market challenges
- 47:01 – 52:07
Org structure for multi-product success: protect seedlings from the core
Rohini explains that structure can make or break new product bets. Seed products need dedicated teams and insulation from the gravitational pull of mature product priorities, which otherwise starve new bets of focus and momentum.
- •New product ‘seedlings’ struggle when embedded too close to mature orgs
- •Core products generate urgent roadmap/maintenance work that overwhelms seedlings
- •Mercury created a separate expansion org to give new bets air cover and focus
- •Seed teams are evaluated periodically (quarterly/half-yearly) like venture investments
- •Resource model: full cross-functional squads, leveraging central teams as needed
- 52:07 – 57:30
Customer obsession as an operating system (and how it can still go wrong)
Rohini breaks down how Mercury operationalizes customer obsession through frequent calls, continuous feedback loops, and internal visibility. She also warns that “talking to customers” isn’t enough if teams misinterpret feedback or don’t connect it to business reality.
- •Customer calls are treated as the heartbeat—1/week is a low bar; discovery can be 20–25 calls
- •Signals come from many channels: CS/RM calls, offboarding reasons, social posts, surveys
- •Avoid bias: what customers say vs what they actually need can differ
- •Validate patterns, prototype, beta, and triangulate qualitative + quantitative inputs
- •Balance customer obsession with business viability (pricing/value depends on context)
- 57:30 – 1:05:58
Picking the next products, finding distribution leverage, and pricing learnings
Rohini shares how Mercury chooses what to build next: stay adjacent to the core, de-risk via existing usage, and exploit distribution advantages inside the product. She also covers pricing philosophy and common multi-product missteps like doing too much with too little staffing.
- •Choose adjacencies—not random new directions—tied to ICP and existing ecosystem
- •De-risk by spotting traction in ‘baby’ versions (e.g., Payment Requests → Invoicing)
- •Use in-product distribution: surface new products in natural workflows
- •Pricing approach: drive adoption/learning first, charge more as complexity/value increases
- •Missteps: too many bets at once, understaffing seedlings, internal debate on bundling vs à la carte
- 1:05:58 – 1:10:00
Transparent Collective: expanding access for underrepresented founders
Rohini describes Transparent Collective, a nonprofit designed to share “tribal knowledge” and open doors for founders outside traditional coastal networks. She outlines the programming model, outcomes, and how people can apply or donate.
- •Transparent Collective is a 501(c)(3) supporting underrepresented founders
- •Origin story: inequities and knowledge gaps across Midwest/NYC/West Coast fundraising
- •Programs focus on fundraising readiness, mentorship, and investor-founder matchmaking
- •Flagship: fly 8–10 founders to SF for a week-long seed program (from 200–250 applicants)
- •Impact: 90+ alumni, ~65–70% raised venture funding, ~$125M raised, ~10% exited
- 1:10:00 – 1:19:24
Lightning round: books, shows, favorite products, mottos, and closing notes
The episode closes with a lightning round spanning reading recommendations, TV picks, product inspiration, and personal guiding principles. Rohini also shares where to find her, Mercury hiring info, and a special Mercury Personal Banking waitlist-skip offer for listeners.
- •Book recs: Vectors; The Inner Game of Tennis; plus fiction picks (Pachinko, etc.)
- •TV recs: Apple TV shows (Slow Horses, Severance, Shrinking, Bad Sisters)
- •Favorite product experience: Waymo—and how quickly trust forms
- •Life motto: connect with others, create delight, expect magic/miracles
- •Where to find Rohini + Mercury jobs + listener feedback request + limited waitlist skip link
