Lenny's PodcastLessons from scaling Ramp | Sri Batchu (Ramp, Instacart, Opendoor)
CHAPTERS
- 0:00 – 0:40
Cold open: How B2B growth tactics should be sequenced (founder-led → paid → SEO)
Sri opens with a clear point of view on how most B2B companies should sequence go-to-market investments as they learn more about customers. The central idea: start with the cheapest, most targeted channels, then expand into more expensive, scalable channels once you have stronger customer understanding.
- •Start with founder-led sales; early teams must learn to sell
- •Add first sales hires, then low-cost targeted marketing (content, community, small events)
- •PR comes before paid/brand because it’s cheaper and benefits from clearer positioning
- •Paid and brand come later as you gain customer insight and can scale spend efficiently
- •SEO often starts around the time paid starts, but works best after you’ve built authority
- 0:40 – 4:18
Podcast setup: Sri’s career path and why Ramp’s growth is notable
Lenny introduces the show and frames why Sri is a strong guest for a growth deep dive. He highlights Sri’s background across Opendoor and Instacart and positions Ramp as a historic outlier in speed and scale.
- •Sri’s prior roles: VP Ops at Opendoor, Head of Growth at Instacart
- •Ramp positioned as fastest-growing SaaS and fintech business (per public analyses)
- •Episode focus: Ramp’s growth approach, structure, metrics, and operating cadence
- •Teaser of Ramp’s culture: velocity as a core operating principle
- 4:18 – 6:19
Ramp’s hypergrowth by the numbers (and doing it lean)
They unpack the headline stats behind Ramp’s rise and why the numbers stand out in a tough macro environment. Sri emphasizes not just speed, but efficiency—high output with a relatively small team.
- •Reached ~$100M annualized revenue run rate in ~2 years
- •Grew ~4x year-over-year on top of a sizable base
- •Recognized as a top growth outlier in SMB/mid-market software benchmarks
- •Under ~500 employees at the described scale (high revenue per employee)
- •Ambitious finance-set targets consistently exceeded since Sri joined
- 6:19 – 9:17
Setting the stage early: product-market fit + “cap table as a growth strategy”
Sri explains what he believes seeded Ramp’s early momentum beyond great product. A distinctive tactic: intentionally bringing influential founders/operators onto the cap table who then became early customers and advocates.
- •Strong PMF and word of mouth driven by deep customer experience focus
- •Founders’ credibility from prior successful exit helped attract early believers
- •“Cap table as growth”: add many influential operators/founders as investors/advisors
- •Early customers often came from those cap-table relationships
- •Investor intros help, but customer-to-customer proof tends to matter more
- 9:17 – 12:13
New customer acquisition vs. expansion—and why channel mix isn’t the secret sauce
Lenny probes whether Ramp’s growth is mostly from existing customer expansion (spend growth + new products) or net-new logos. Sri shares that new acquisition dominates, and that Ramp’s edge isn’t an exotic channel mix but a data/tech-driven execution advantage across standard channels.
- •Product suite expansion exists (e.g., Bill Pay, Flex) and supports growth
- •Despite natural spend expansion, most growth comes from new customers
- •Ramp’s channel distribution likely resembles peers at similar stage
- •Differentiator: applying technology + data rigor to make each channel efficient
- •Emphasis on automation and instrumentation rather than “one weird trick” channels
- 12:13 – 13:41
Growth engineering for sales: engineers owning quota-adjacent outcomes
Sri describes a growth engineering model that directly boosts sales productivity. Engineers are aligned to pipeline and payback outcomes, supporting prospecting, messaging, and workflow automation to raise sales efficiency.
- •Growth engineering supports sales efficiency and pipeline creation
- •Shared goals: pipeline driven and channel payback period
- •Engineers feel ownership of quota-adjacent metrics (not just product metrics)
- •Work includes lead finding, messaging, response prioritization, draft generation
- •Ramp has been doing sales automation “pre-AI hype” for ~2 years
- 13:41 – 15:49
How Ramp’s growth org is structured (channel teams + skunk works)
Sri outlines a channel-based growth org supported by a dedicated product/engineering function and an innovation “skunk works” team. The skunk works group runs cross-channel experiments that don’t fit neatly into standard ownership boxes.
- •Channel teams: paid marketing, lifecycle/CRM, field marketing, SEO/website, etc.
- •Dedicated growth product/engineering team supports effectiveness across channels
- •Self-serve activation engineering exists alongside sales-supported motions
- •Skunk works/innovation team runs cross-channel experimentation
- •Examples: TikTok/Reddit tests, referrals improvements, first-party events
- 15:49 – 20:21
Operating at extreme velocity: culture, cycle time, and “days since founding”
They explore what “velocity” feels like at Ramp and how it’s reinforced. A key ritual is tracking the exact number of days since founding, reinforcing urgency, responsiveness, and rapid execution as a company identity.
- •Core cultural focus: reduce cycle time; strong bias to action
- •days.ramp.com as a constant reminder: operate in days, not quarters
- •High Slack responsiveness and clear ownership/deadlines for action items
- •Growth team operates like product: two-week sprints and cross-prioritization
- •“Build in public” internally increases visibility and accountability
- 20:21 – 25:10
Avoiding burnout while pushing hard: focus time, autonomy, and win-celebration
Lenny asks about the tension between speed and sustainability. Sri explains that the bigger risk isn’t hours alone; it’s lack of autonomy and meaning, and Ramp mitigates with better time management practices and strong recognition rituals.
- •Hard work matters, especially early career—but meaning and autonomy drive sustainability
- •Calendar blocking and “calendar audits” to align time with priorities
- •People team provides templates to operationalize better time use
- •Celebrating wins (big and small) to sustain motivation
- •Even all-hands engagement is tracked via chat participation as a proxy for excitement
- 25:10 – 29:20
Optimizing efficiency and scaling awareness: earned media, PR, and fundraising moments
Sri shares how Ramp thinks about reallocating toward efficient, scalable channels while continually improving all channels. He also describes PR and fundraising announcements as deliberate “market moments” that can create meaningful top-funnel spikes.
- •Growth leadership increasingly resembles portfolio management (ROI + experimentation)
- •Allocate more to channels that are efficient *and* scalable
- •Owned/earned media is especially attractive when it can scale efficiently
- •PR becomes a growth lever when there’s real news/value for the audience
- •Fundraising can create a market moment that drives non-trivial top-of-funnel
- 29:20 – 30:50
Traditional media vs. newsletters/podcasts: different audiences, different jobs-to-be-done
They discuss where newer creator-driven media fits relative to traditional press. Sri’s view: newsletters and podcasts are powerful for recruiting and tech-adjacent audiences, while traditional media remains important for reaching broader, non-startup buyers.
- •Newsletter/podcast coverage boosts reputation and hiring
- •These channels skew toward tech founders and the tech ecosystem
- •Ramp’s customer base is largely non-startup; broader reach still matters
- •Traditional PR targets different (often larger) customer audiences
- •Best strategy blends channels rather than treating them as substitutes
- 30:50 – 40:26
Building a repeatable growth engine: culture, rituals, and metric translation layers
Sri argues team structure matters less than operating system: culture, cadence, and shared metrics. He explains how large growth orgs can translate many local metrics into a single “common currency” North Star for planning, prioritization, and resourcing.
- •Growth engine success depends on culture, rituals, and execution cadence
- •Keep North Star metrics simple (often one, at most two)
- •Teams use local metrics day-to-day, but planning uses a common currency
- •Instacart example: map team-level inputs (e.g., app speed) to monthly active orderers
- •Use regression and/or long-term holdouts to measure cumulative impact
- 40:26 – 46:49
Ramp’s North Star (recently): dollars of SQL pipeline + activation ‘escape velocity’
Sri shares Ramp’s recent growth North Star metric and how translation factors guide prioritization. They also discuss activation thresholds (“escape velocity”) and a detour into why Ramp blocks personal email signups, plus how exceptions are handled.
- •Ramp North Star (recent past): dollars of SQL (sales-qualified lead) pipeline
- •Translation factors convert local improvements (e.g., web conversion) into SQL pipeline impact
- •Activation focus: a small set of key actions in first ~30 days predicts success
- •Personal email signups blocked due to typically low intent; workaround via outreach
- •Emphasis on choosing metrics that are intuitive and tightly linked to value creation
- 46:49 – 49:51
Choosing ROI metrics: why payback period beats CAC (and even LTV:CAC)
Sri explains why CAC can lead teams to optimize for cheaper but lower-quality customers. He argues payback period—built on contribution margin—anchors ROI in more observable, near-term economics and reduces reliance on fragile long-range LTV assumptions.
- •CAC alone over-optimizes for cost and can degrade customer quality
- •LTV:CAC is better in theory but highly assumption-laden for young companies
- •Payback period uses more recent, testable economics
- •Use contribution margin (profit after variable costs), not just revenue/gross margin
- •Leadership sets acceptable payback targets; teams orient around improving blended payback
- 49:51 – 58:05
Experimentation that ‘fails conclusively’: maximizing treatment effect in B2B
Sri outlines an experimentation philosophy where the goal isn’t merely to fail fast, but to learn decisively. In B2B, small sample sizes make it hard to get statistical clarity—so teams should increase treatment strength and run bigger, more definitive tests for costly initiatives.
- •Celebrate failure only if it produces learning; “failure is not learning”
- •B2B constraint: small N makes tests slow and ambiguous
- •Two paths to power: large N or big treatment; B2B often needs bigger treatment
- •Run “best version” tests first, then cost-optimize after proving lift
- •Example: account-based marketing tested as a strategy with multiple coordinated touches
- 58:05 – 1:00:25
Ramp’s tool stack and build-vs-buy philosophy (move fast by not building everything)
They touch on practical tooling choices that support sprint planning and website experimentation. Sri also describes Ramp’s discipline around buying commodity tools while building proprietary automation where it creates durable advantage.
- •Sprint planning/scoring system implemented in Airtable (template-driven)
- •Mutiny used for website personalization tied to third-party data
- •Ramp is deliberate about build vs. buy to preserve velocity
- •Build in-house where strategic (e.g., prospecting, lead scoring, sales automation)
- •Compared to Instacart/Opendoor, Ramp relies more on off-the-shelf experimentation tooling
- 1:00:25 – 1:17:17
Hiring, compensation, MECE, and lightning round takeaways
Sri shares tactical hiring approaches (network mapping and data-driven sourcing), strong views on paying top performers, and why retention/performance management drives talent density as much as recruiting. He closes with a MECE problem-solving framework and a lightning round on books, products, and operating tips.
- •Two hiring modes: network-driven “best person” mapping and data-driven sourcing (e.g., Similarweb signals)
- •Target hires from companies 1–2 stages ahead with strong craft in the function
- •Compensation philosophy: enable outsized rewards for 10x operators (small teams outperform)
- •Talent density = hiring + retention + performance management (avoid bar dilution)
- •MECE framework for comprehensive problem decomposition; lightning round on books, media, products, and negotiation tips
