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
Cold open: Mercury’s “no PMs” era and the question that changed
Lenny opens with Mercury CEO Emad’s famous stance about not needing product managers—and the reality that Mercury now has a substantial PM org. Rohini previews the core reason: as companies scale, bottlenecks and hidden PM work inevitably emerge.
- •Mercury once celebrated operating without product managers
- •The central question: what signals it’s time to hire PMs?
- •Early hint: design/engineering end up doing PM duties anyway
- •Preview of frameworks: PM “flavors” and multi-product scaling
Rohini’s background: Square/Block, Mercury expansion, investing, and mission work
Lenny introduces Rohini’s path from Square/Block to leading Mercury’s product expansion team. The episode’s agenda is set: why founders resist PMs, how Mercury scaled product discipline, how to attract talent, why quality matters, and how Mercury launched multiple new product lines.
- •Rohini leads Mercury’s product expansion/incubation efforts
- •Prior work: Square Payments, Invoicing, and Bitkey
- •Co-founder of Transparent Collective; active angel investor
- •Episode roadmap: PM hiring, quality, and multi-product playbook
Sponsor segment and show start: ads, welcome, and framing the anti-PM “meme”
Sponsor messages run, then Lenny and Rohini begin the conversation by naming the common founder belief that PMs slow teams down. They frame the episode as an honest look at when the “no PMs” approach works—and when it stops working.
- •Sponsor messages (Cloudinary, OneSchema)
- •The founder narrative: “engineers/designers can do PM work”
- •Why many companies eventually reverse course
- •Goal: extract practical signals and lessons from Mercury’s journey
How Mercury scaled to ~400 employees before official PM titles
Rohini shares the surprising detail: Mercury had no official PMs until roughly 400 employees. She explains the difference between “no PM title” and “PM work still happening,” and where she joined during the transition.
- •Mercury hired first official PMs around ~400 employees
- •PM work existed informally even without the title
- •Mercury now has ~30 PMs, many at senior levels
- •Rohini joined after the first year of “official PMs” to refine the discipline
Why “no PMs” can work early: founders as original PMs + strong product-minded builders
Rohini explains what made the no-PM structure viable early: founders who act as the product function and exceptionally strong, product-obsessed engineers and designers. The emphasis is on customer closeness, empowered teams, and local decision-making.
- •Founders must serve as the earliest product managers
- •Staying close to customers and the built solution is non-negotiable
- •Hiring “product-minded” engineers/designers can compensate temporarily
- •Autonomous teams with strong intuition reduce reliance on formal PM processes
Signals it’s time to hire PMs: bottlenecks, complexity, and cross-functional load
The conversation gets concrete on trigger points: founder decision bottlenecks, increased operational complexity, and regulated fintech requirements. Rohini also describes Mercury’s intermediate step—creating “business lead” generalist roles that later converted into PM titles.
- •Scaling decisions can’t depend on founders indefinitely
- •Fintech complexity adds legal/compliance/risk coordination needs
- •When eng/design shoulder PM duties, core work suffers
- •Mercury used “business leads” as de facto PMs before formalizing the role
- •Early misses: strategy, roadmaps, prioritization, customer research, goal-setting
Building the product org: defining the PM role, career ladder, and interview signals
Rohini outlines Mercury’s foundational work to professionalize product: write down expectations, create a PM career ladder, and align hiring to the same competencies. She highlights Mercury’s emphasis on low ego, customer love, and business impact.
- •Start by defining what PM success looks like internally
- •Build a career ladder matrix by level and competencies
- •Mercury values: humility/low ego paired with outcomes and craft
- •Hiring tests map to the ladder: product sense, quality obsession, analytics, systems thinking
- •Interest in adding a writing component to PM interviews
Don’t hire PMs too early: when founders should keep the reins
Rohini gives clear guidance for seed-stage teams: founders should stay in the PM seat until they truly can’t. The “now is the time” moment comes when the founder becomes the bottleneck, or when adjacent product expansion requires dedicated learning and ownership.
- •Early PM hiring can prematurely outsource founder-customer-product intimacy
- •Hire PMs when work can’t progress without the founder’s decisions
- •Hire when eng/design are doing PM work at scale (and paying the opportunity cost)
- •Another trigger: moving into adjacent products/segments with new customer learning needs
The ‘flavors’ of PMs: pioneer vs. town settler vs. city planner
Rohini introduces a Square-inspired framework to avoid mismatched PM hires. Different stages of product maturity require fundamentally different PM strengths—from zero-to-one creation to scaling growth to managing mature, high-impact systems.
- •Pioneer PM: thrives in 0→1 ambiguity and building from nothing
- •Town settler PM: grows and systematizes an early product with experimentation
- •City planner PM: optimizes mature products with massive scale and risk considerations
- •Founders often dislike “city planner” behaviors but actually need pioneers/settlers
- •Interview for receipts: validate what candidates truly did vs. resume claims
Attracting top product talent: the S-curve, challenge sizing, and interview ‘dogfooding’
Rohini explains how great PMs choose roles: they’re optimizing for the next step on their personal growth curve (ambiguity vs. scale) and the caliber of teammates. She also notes that senior candidates judge companies by the quality and relevance of interview questions.
- •Use an ‘S-curve’ lens: ambiguity (Y) vs. scale (X) across a career
- •Sell the right “next challenge” based on where a candidate is on the curve
- •Top talent cares deeply about who they’ll learn from (strong functional peers)
- •Transparency matters: share the good, bad, and ugly to build trust
- •Revamp interviews because candidates evaluate the company as much as vice versa
Advocating for quality in ‘boring’ products: trust, craft, and compounding advantage
Rohini argues that investing in quality can look irrational in KPI-first cultures, but becomes a strategic moat—especially in fintech, where trust is paramount. She shares a Bill Pay example where a small UX detail delights users without obviously moving a single metric.
- •False dichotomy: metric-driven speed vs. design-driven craft (you need both)
- •In fintech, quality signals trustworthiness with customers’ money
- •Example: invoice OCR + zoom-to-field detail creates delight and confidence
- •Quality compounds into differentiation, talent attraction, and customer loyalty
- •Quality has to be cultural and top-down to sustain
Going multi-product at Mercury: what launched and why speed increased each time
Rohini walks through Mercury’s 2024 expansion: personal banking plus a suite of workflows on top of business banking (bill pay, invoicing, spend controls, reimbursements). A key operational insight: each successive product launch went from concept-to-launch faster than the last.
- •2024 launches: Mercury Personal Banking, Bill Pay, Invoicing, spend controls/reimbursements
- •Expansion into consumer is a major strategic step
- •Building SaaS-like workflows atop banking (AP/AR/accounting processes)
- •Learning curve benefits: subsequent launches accelerate over time
- •Focus on building repeatable product velocity and launch muscles
Multi-product organizational design: protect ‘seedlings’ with dedicated teams and funding reviews
Rohini explains the org insight Mercury learned the hard way: new products fail when they’re too tightly coupled to mature product orgs that constantly pull them back into maintenance and high-certainty work. Mercury created a separate expansion org and treats new products like internal seed-stage companies with periodic investment reviews.
- •Seedlings near the core get pulled into mature-product gravity
- •Solution: separate orgs with dedicated cross-functional squads
- •Operate like venture investing: quarterly/biannual investment check-ins
- •Balance goals with learning—expect pivots rather than rigid kill criteria
- •Staffing varies by complexity and market shift (e.g., personal banking vs. invoicing)
Choosing the next products: adjacency, de-risking demand, and distribution advantages
Rohini outlines how Mercury selects new bets: stay adjacent to the core, validate demand through precursor features, and leverage built-in distribution. She uses payment requests as a “seed signal” that helped de-risk invoicing and reduce go-to-market friction.
- •Pick adjacent product lines—not random new features or far-flung bets
- •De-risk via existing traction (e.g., payment requests → invoicing)
- •Exploit distribution: sell/attach inside existing workflows
- •Use contextual prompts in-product to drive adoption (e.g., payments → bill pay upsell)
- •Launch is only hurdle one; PMF discovery is the longer game
Customer obsession in practice: high cadence research, avoiding bias, and triangulating with business needs
Rohini describes Mercury’s customer-calling culture—weekly at minimum, often far more during discovery. She emphasizes avoiding leading questions and interpreting what customers mean (not just what they say), while also anchoring decisions in business viability and value-based pricing context.
- •Teams often do 20–25 calls in heavy discovery phases
- •Multiple customer touchpoints: calls, surveys, RM/CS sidecar, social feedback, churn reasons
- •Research mindset: observe without bias; find patterns, then validate with prototypes/betas
- •Customer desire must be balanced with business sustainability
- •Operational tactics: UXR support, dedicated research weeks, centralized scheduling help
Transparent Collective and lightning round: nonprofit impact, personal recommendations, and wrap-up
Rohini shares Transparent Collective’s mission to help underrepresented founders access resources, fundraising preparation, and investor networks—and the measurable outcomes of its cohorts. The episode closes with a lightning round covering books, shows, favorite products, life motto, and an angel investing story, plus where to find Rohini and Mercury hiring info.
- •Transparent Collective: nonprofit supporting underrepresented founders (SF seed programming weeks)
- •Impact: ~90+ alumni, majority raising funding; notable total capital raised and exits
- •Lightning round: books (Vectors, Inner Game of Tennis), fiction recs, Apple TV shows, Waymo
- •Life motto: connect, create delight, expect magic/miracles
- •Where to find Rohini + Mercury jobs + request for product feedback and personal banking waitlist skip
