Lenny's PodcastVelocity over everything: How Ramp became the fastest-growing SaaS startup ever | Geoff Charles
CHAPTERS
- 0:00 – 0:31
Ramp’s early “ship impossible things fast” track record
Geoff opens with concrete examples of Ramp’s extreme execution speed: building competing products with very small teams and hitting major revenue milestones early. The framing sets up the central theme of the episode—velocity as the core competitive advantage.
- •Built major product lines in months with ~10 people early on
- •Reached ~$100M annual revenue run rate with a very small R&D org
- •Launched accounts payable with a tiny pod that scaled to billions in volume
- •Teaser of the “recipe”: small teams, focus, lofty goals, shielding from chaos
- 0:31 – 4:54
Geoff’s background and why this conversation matters
Lenny introduces Geoff (VP Product at Ramp) and explains why Ramp is a must-study example for product teams. The episode is positioned as an inside look at operationalizing velocity, first-principles thinking, and empowered teams.
- •Ramp described as fastest-growing SaaS business in history (per Lenny)
- •Episode focus: velocity, empowerment, first principles, avoiding burnout
- •Promise of practical systems: planning, strategy, feedback loops, hiring
- •Context: how Ramp achieved scale with unusually lean headcount
- 4:54 – 7:05
What Ramp is and what makes its growth so unusual
Geoff gives a clear overview of Ramp as a finance automation platform and corporate card for SMBs, spanning expenses, bills, and accounting automation. Then he shares standout metrics that establish Ramp’s scale and momentum.
- •Ramp automates expense management, card payments, bill payments, accounting
- •Customer base scale and daily user growth
- •Savings and time saved as customer value metrics
- •Transaction volume growth as a signal of platform scale
- 7:05 – 9:12
Velocity as a company operating system (not a slogan)
Geoff explains how velocity permeates hiring, promotions, decision-making, incentives, and process design. He argues velocity compounds into impact, improves talent attraction, and lowers the cost of decisions through fast iteration.
- •Velocity influences process, incentives, hiring, promotion, and decisions
- •High-velocity teams iterate into impact over time
- •Fast shipping is a strong talent magnet
- •Lower decision cost simplifies decision-making and reduces risk
- 9:12 – 10:47
How Ramp achieves speed: small pods, single-threaded goals, and shielding
Specific examples illustrate how Ramp ships category-level products rapidly with tiny teams. Geoff details the operating model: single-threaded focus, ambitious goals, tight timelines, and strong protection from organizational noise.
- •Examples: competitor-level products built in 3–6 months
- •Accounts payable built by a 3-engineer pod in ~3 months
- •Operating recipe: small team + one goal + tight timeline
- •Shield teams from distractions; expand only after early traction
- 10:47 – 13:15
Keeping teams single-threaded: removing distractions and operational “protective layers”
Geoff defines “single-threaded” as waking up to one core goal and removing everything else. He describes operational mechanisms—rotations and roles—that keep pods from getting pulled into bugs, escalations, and enablement work.
- •Single-threaded = one primary goal; eliminate other asks
- •Physical and organizational isolation to maintain focus
- •Production engineering rotations handle escalations and bugs
- •Product operations shields PMs from documentation, releases, enablement, requests
- 13:15 – 15:11
Lofty goals without losing the plot: markets, revenue focus, and motivating prototypes
Lofty goals are grounded in market comparables and reinforced through design-led vision. Geoff explains how Ramp uses revenue-driven clarity and compelling prototype walkthroughs to keep teams motivated and aligned while moving fast.
- •Market comparables (Bill.com, Expensify, etc.) help de-risk ambition
- •Revenue-driven goals keep focus concrete
- •Design prototypes (Figma + Loom walkthroughs) anchor “future state”
- •Ambition balanced by market clarity and a compelling product vision
- 15:11 – 19:52
Context over control: empowerment via upstream alignment (goals → hypothesis → data)
Geoff outlines how Ramp empowers teams by aligning on goals and hypotheses rather than prescribing solutions. He shares how his own management evolved—less solution micromanagement, more context sharing and coaching.
- •Hands-off leadership works when goals are tightly aligned
- •Debate upstream (goals/hypotheses/data) instead of downstream (solutions)
- •Leader’s job becomes “repeater-in-chief” of context and priorities
- •Empowerment breaks when leaders dictate solutions without shared context
- 19:52 – 22:55
Product reviews, feedback loops, and quality controls that make speed sustainable
Ramp keeps quality high by structuring when and how leadership engages (especially near GA) and by instrumenting customer feedback and operational burden. Geoff details rigorous feedback loops and hard stops when customer confusion rises.
- •Scaled product reviews for “large rocks”; structured asks and trade-offs
- •Leadership more engaged at GA decisions than early beta iterations
- •Voice-of-customer: negative reviews routed to PM/design/tech leads monthly
- •Controls: NPS/CSAT, operational burden, on-call assignment, confusion-driven ticket tracking
- 22:55 – 24:03
Bug philosophy and support as a product accountability mechanism
Geoff explains Ramp’s aggressive approach to bugs—essentially no long-lived bug backlog—and ties it to on-call ownership and operational metrics. He also reframes support as a product failure and uses that first-principles view to keep contact rates low.
- •“No bug backlog” mindset; fix quickly once surfaced
- •Production engineering/on-call feels the pain and resolves issues fast
- •If confusion-driven tickets rise, feature shipping pauses until fixed
- •Support reports into product; support incentives reduce ticket volume over time
- 24:03 – 29:17
Advice to PMs pressured to ‘move faster’: empowerment, fewer meetings, and sharper trade-offs
Geoff responds to the ‘copy Ramp’ impulse by emphasizing prerequisites: elite R&D talent, true empowerment, and ruthless removal of low-value process. He argues velocity requires trade-offs and clear menus of what will and won’t be done.
- •Velocity depends heavily on engineering/design talent and empowerment
- •Reduce meetings and status updates; do status async in real-time systems
- •CEOs can’t demand speed and also demand “everything”
- •PMs should present explicit trade-offs and force prioritization decisions
- 29:17 – 37:33
Burnout, chaos, and planning vs. doing: making velocity feel energizing
Geoff reframes burnout as often caused by low movement and low impact rather than high effort. He also explains where Ramp plans deeply (big coordinated moments) and where it stays intentionally loose to preserve speed.
- •Burnout correlates with low progress/low impact more than hard work
- •Velocity can prevent burnout by enabling flow state and visible wins
- •Plan deeply for high-value accuracy moments (e.g., major launches)
- •Accept local pod chaos while keeping strategy/vision stable
- 37:33 – 42:12
Strategy documents and why Ramp is ‘uniquely positioned’ to win (right to win)
Geoff defines strategy as the bridge between vision and roadmap, then describes a consistent doc structure used by pods. He highlights the “right to win” concept with a concrete example of why bill pay was a natural expansion from cards/expenses.
- •Strategy = how to achieve goals; distinct from vision and roadmap
- •Doc elements: goals, hypotheses, unique advantage, metrics, initiatives, risks, outcomes
- •Pods write strategy docs; Geoff aligns them to product + financial strategy
- •Right-to-win example: bill pay reuses money movement, liabilities, accounting integrations, and existing users
- 42:12 – 57:02
OKRs, first-principles thinking, and writing for clarity (plus deep work habits)
Geoff explains why Ramp largely avoids OKRs for product execution, preferring roadmap contracts, while using OKRs selectively for cross-functional goals. He then connects first-principles thinking to writing as a method for solving hard scaling problems and shares how he protects deep work time.
- •OKRs can become political and slow; roadmap is the product ‘contract’
- •Biannual priorities replaced expensive quarterly OKR planning cycles
- •First principles required because Ramp spans credit, payments, software, PLG + enterprise sales
- •Writing on paper to answer a clear question builds thinking capacity; block time in calendar and minimize interruptions
- 57:02 – 1:16:56
How Ramp scales product with few PMs: distributing PM work, product ops, and a high talent bar
Geoff details Ramp’s lean PM-to-engineer ratio and how the company gets leverage by pushing PM responsibilities into the whole product org. He covers the core PM role at Ramp, how to recognize A+ engineering, hiring signals, breaking into PM, and ends with a lightning round and closing advice.
- •~13 PMs with 100+ engineers; leverage comes from designers/engineers thinking like PMs
- •Product operations handles operational load (releases, enablement, research, issue mgmt)
- •Core PM job: strategy/vision, team culture, stakeholder shielding, focus protection
- •A+ talent signals: business curiosity, ownership, proactivity, pace-setting, accountability; hiring prioritizes hunger for impact + deep thinking; breaking into PM via adjacent roles
