The Twenty Minute VCSri Batchu: Biggest Growth Lesson from Instacart & Opendoor; 70% of Experiments Should Fail | E1040
CHAPTERS
- 0:00 – 2:22
Sri’s path into growth: from investor/analytics to operator
Sri explains how growth emerged as a discipline spanning product, marketing, and analytics, and how his own entry point was unusually investment- and data-driven. He walks through his early operator experience at Opendoor, later work at Instacart, and his current role leading growth at Ramp.
- •Growth sits at the intersection of product, marketing, and analytics
- •Sri’s “portfolio of bets/ROI” mindset came from consulting and investing
- •Opendoor: early generalist work across sales, analytics, pricing
- •Instacart: first focused on ads business growth, then broader growth
- •Why more growth leaders will come from analytics/investing backgrounds
- 2:22 – 3:40
Opendoor vs Zillow: first-principles conviction under competitive pressure
Sri recounts how Zillow’s entry into iBuying forced Opendoor to choose between matching aggressive pricing or sticking to accurate pricing models. The lesson: if you’ve reached a decision through first principles, hold the line even when it hurts in the short term.
- •Competitive threat: Zillow entered Opendoor’s core markets
- •Decision fork: price match for volume vs protect pricing accuracy
- •Opendoor’s choice: avoid price matching/negotiation; prioritize accuracy
- •Rationale: preserve long-term edge instead of chasing short-term growth
- •Outcome: Zillow ultimately exited after large losses
- 3:40 – 4:22
Solvency vs irrational markets: unit economics as the hedge
Harry challenges the idea of “being right eventually” if a competitor has deeper pockets. Sri explains that maintaining cohort-level profitability and positive unit economics extends runway and resilience even during irrational competitive behavior.
- •Risk: competitors can outspend you longer than you can endure
- •Mitigation: ensure each cohort/program is profitable
- •Unit economics allow survival even with lower volume
- •Strategic posture: win on fundamentals rather than subsidy battles
- 4:22 – 5:33
Instacart’s four-sided marketplace and the power of saying no
Sri describes Instacart’s complexity—buyers, shoppers, advertisers, and retailers—and what he learned from founder Apoorva: simplification is a superpower. Great leaders focus by choosing one initiative—or sometimes rejecting both—to protect strategy and execution.
- •Instacart complexity: four-sided marketplace with competing incentives
- •Simplification is difficult but high-leverage
- •Temptation: do multiple high-impact initiatives at once
- •Best execs make clear choices; sometimes “neither” is correct
- •Cultural meme: being the “VPs of No” to enforce focus
- 5:33 – 7:53
What ‘growth’ means: scope, timing (post-PMF), and org design tradeoffs
Sri defines growth as the home for high-volume, data- and experimentation-driven acquisition and retention after product-market fit. He argues for putting paid channels, SEO, and product-led growth close together, while acknowledging that reporting lines vary by company and accountability is the real constraint.
- •Growth function is most appropriate post–product-market fit
- •Scope: high-volume acquisition, retention, engagement via experimentation
- •Prefer structural proximity of paid/SEO/PLG/website/product growth
- •“Under one roof” can mean reporting lines or shared accountability
- •Joint accountability can fail when “everyone owns it” → nobody owns it
- 7:53 – 10:31
Choosing North Stars: balancing controllability, simplicity, and value alignment
Sri explains why there is rarely a perfect North Star metric and why revenue is often too lagging. He recommends pairing a volume metric with an efficiency/ROI metric, using examples like SQL pipeline dollars to balance lead quality with team controllability and feedback speed.
- •North Star should be intuitive, influenceable, and aligned to value creation
- •Pure volume goals can drive low-quality gaming; pure profit can be too laggy
- •Humans optimize to the metric they’re given (intentionally or not)
- •Use paired metrics: volume + efficiency/ROI guardrail
- •Example approach for B2B: dollars of SQL pipeline as a middle ground
- 10:31 – 12:16
‘Slow is smooth, smooth is fast’: installing lightweight growth operating systems
Sri describes how early growth can devolve into chaotic ‘spaghetti on the wall’ experimentation with unclear learning. The fix is a brief slowdown to set metrics, prioritization frameworks, and measurement processes—enabling faster iteration and better scaling once the system is in place.
- •Early experimentation without structure becomes undiagnosable chaos
- •Reset involves: metrics, prioritization framework, success criteria, ROI measurement
- •Goal is lightweight process—not bureaucracy
- •Clear experiment selection and scaling process accelerates execution
- 12:16 – 14:25
Experimentation reality: 70% failures, faster cycles, and ‘days’ as a speed unit
Sri sets expectations that growth work has a high failure rate (~30% success). He focuses on reducing cycle time through short sprint cadences and cultural mechanisms—like tracking ‘days since founding’—to reinforce urgency and shipping velocity.
- •Typical growth success rate ~30%; failure is normal
- •Key is failing fast and conclusively
- •Short planning cycles increase speed (e.g., two-week sprints)
- •Cultural reinforcement: talk in “days since founding” to compress time horizons
- •Frequent shipping checkpoints push momentum even for longer projects
- 14:25 – 17:44
A failed Opendoor experiment: listed-home bidding and the hidden risk of adverse selection
Sri shares a growth experiment that increased volume but harmed the business: bidding on already-listed homes. The program suffered from asymmetric information and adverse selection, producing highly unprofitable cohorts and forcing a shutdown—highlighting the need for paired efficiency metrics and selective pre-mortems.
- •Experiment idea: bid on homes already listed to increase acquisition volume
- •Failure mode: sellers had more information from market feedback
- •Added seller costs (agent + Opendoor) changed who would accept offers
- •Result: adverse selection led to major unprofitability; program shut down
- •Lesson: track profitability early; pair volume goals with efficiency guardrails
- 17:44 – 20:41
When to build a growth team—and who to hire first
Sri argues PMF is the founder’s job and shouldn’t be outsourced to ‘growth.’ Once there’s real traction, you can staff a real growth team; early on, generalists (BizOps/analytical profiles) often outperform specialists, and leadership hires make sense when multiple programs already show signal.
- •Pre-PMF: growth is founder + sales + maybe an analytical generalist
- •Build a real growth team after escape velocity/clear PMF
- •Leadership hire becomes useful when multiple growth programs show traction
- •Early preference: generalists (BizOps profile) over narrow specialists
- •You don’t need a prior ‘Head of Growth’; look for T-shaped depth + learnability
- 20:41 – 25:57
Hiring for growth: case studies, panels, and signals of ‘growth mindset’
Sri outlines a hiring process emphasizing work simulations and cross-functional evaluation. He recommends neutral or information-balanced case studies and watches for openness to feedback as a key predictor; defensiveness during critique is a major red flag.
- •Source candidates via networks one to two stages ahead; expect long scope alignment
- •Use job-simulating homework/case studies at all levels
- •Prefer neutral topics or new internal problems to avoid asymmetric information
- •Have candidates present to a cross-functional panel; test on-the-spot thinking
- •Green flag: receptivity to feedback; red flag: defensiveness in review
- 25:57 – 29:30
Culture over org charts: shared currency, translation factors, and planning alignment
Sri explains why culture—speed, comfort with failure, shared mechanisms—matters more than reporting structure for growth teams. He describes how large orgs like Instacart used “translation factors” to connect local team metrics (e.g., load time) to global outcomes (e.g., MAUs) to enable coherent prioritization.
- •Debates on reporting lines matter less than shared outcomes and working norms
- •Misalignment happens when teams reject the shared North Star
- •Need a “common currency” for prioritization across specialized teams
- •Instacart example: translation factors mapping local improvements to MAU impact
- •Planning uses these bridges to assemble a portfolio that hits top-level goals
- 29:30 – 40:00
Leadership and scaling: motivation mapping, hiring slow, and ‘letting fires burn’
Sri shares his management philosophy: great leaders treat people as humans, build motivation clarity early, and invest in coaching rather than doing subordinates’ work. He defends hiring slowly and keeping teams small to avoid diseconomies of scale, emphasizing intentional deprioritization—explicitly naming the ‘fires’ you’ll let burn.
- •Managers must understand individuals’ motivations and goals to close “motivation gaps”
- •Tactical tool: structured first 1:1 template (feedback style, recognition, goals, motivators)
- •No ‘wrong’ motivation—start from honesty and design accordingly
- •Hiring slow + small teams improves prioritization/accountability; big teams slow down
- •Let some fires burn intentionally; planning includes what you will not do
- 40:00 – 43:13
Growth challenges at Ramp: segment strategy shifts, automation vs sales, and engagement decay
Sri discusses strategic tradeoffs that create short-term pain for long-term gain, including reorganizing from channel-based to segment-based growth and shifting from human-led acquisition toward self-serve automation. He also highlights culture/engagement as the first thing to break at scale—even when the company is succeeding—if teams are taken for granted.
- •Short-term pain: move from channel-oriented to segment-oriented cross-functional teams
- •Benefit: deeper customer understanding and improved conversion over time
- •Risk tradeoff: humans outperform automation in places, but long-term scale demands self-serve
- •Scaling failure mode: engagement/culture declines when success is taken for granted
- •Leaders must provide guidance, feedback, and gratitude to prevent burnout/attrition
- 43:13 – 1:03:04
Operator-investors: why they win early, how to avoid distraction/conflicts, and angel mistakes
Sri breaks down the investing game into deal flow, diligence, allocation, and portfolio support, arguing operators have advantages in each—especially at small check sizes. He shares strong views on warm intros, conflict management, and why operator-angels often struggle with saying no or evaluating how a startup could succeed (not just how it fails).
- •Operators’ edge: network-based deal flow, sharper product/buyer diligence, easier allocations
- •Operating experience has a “half-life”; staying current matters (AI, remote management)
- •Avoid distraction via filtering: fewer meetings, higher-reputation warm intros
- •Conflict rules: avoid competitive meetings; be above-board in procurement overlap; talent poaching is fair game
- •Common angel mistakes: inconsistent check sizing, too few bets, difficulty saying no, over-focusing on failure modes
- 1:03:04 – 1:07:44
Rapid-fire: tactics that endure, tactics that died, and inspirations (Pitbull + Notion)
In closing, Sri answers quick questions on what’s changed in growth: PLG fundamentals remain, cold outbound/email still works, while indiscriminate paid spend is largely dead due to efficiency demands and attribution challenges. He also shares a favorite lyric as a decision-making frame and praises Notion’s community-led growth strategy.
- •Enduring: core PLG playbook; cold outbound/email remains effective
- •PLG isn’t dead—economic cycles create temporary headwinds/tailwinds
- •Died: indiscriminate paid marketing (efficiency + attribution constraints)
- •Post-mortems: monthly cadence with experiment tracking and shared learnings
- •Inspirations: ‘ask for advice’ framing; Notion’s multi-pronged community growth
