Lenny's PodcastVelocity over everything: How Ramp became the fastest-growing SaaS startup ever | Geoff Charles
At a glance
WHAT IT’S REALLY ABOUT
Inside Ramp’s playbook: tiny empowered teams, extreme velocity, huge impact
- Ramp’s VP of Product, Geoff Charles, explains how Ramp became the fastest-growing SaaS and fintech company by aggressively prioritizing velocity, small empowered teams, and A+ talent. The company repeatedly built competitive products to incumbents like Amex, Expensify, and Bill.com in months with very lean teams, by focusing on single-threaded ownership, first-principles thinking, and minimal process. Strategy at Ramp centers on clear goals, strong financial targets, and a roadmap ‘contract’, while product teams are given wide autonomy and context instead of top-down control. Geoff also digs into how they avoid burnout, structure planning, organize support under product, hire and evaluate PMs, and why writing and deep work are core to good decision-making.
IDEAS WORTH REMEMBERING
5 ideasOptimize for velocity with small, single-threaded teams and big goals.
Ramp repeatedly shipped full competitors to large incumbents (Amex, Expensify, Bill.com) in ~3 months with 3–8 engineers by giving pods one clear objective, tight timelines, and shielding them from distractions or shared responsibilities.
Empower teams with context over control to scale decision-making.
Leaders align with teams on goals, hypotheses, and key data, then largely step back from dictating solutions; teams closer to the problem own the ‘how,’ while leaders act as ‘repeater-in-chief’ for strategy and context.
Use simple, lightweight strategy instead of heavy OKR machinery.
Ramp moved away from time-consuming quarterly OKRs toward biannual one-page company priorities, a strong financial plan with clear owners, and team-level strategy docs that define goals, hypotheses, metrics, risks, and why Ramp has a right to win.
Maintain quality at high speed through clear control metrics, not process.
They fix every surfaced bug, track NPS/CSAT, operational burden (ticket rate per user), and ‘confused’ tickets; when these go red, teams stop shipping new features and must improve quality before resuming.
Treat support as a product failure and put it under product.
Customer support reports into product, is incentivized to reduce contacts (not just resolve them), and feeds structured customer feedback directly into teams—resulting in a tiny support staff serving hundreds of thousands of users.
WORDS WORTH SAVING
5 quotesVelocity is everything at Ramp. It’s how we design our product development process, how we incentivize teams, who we hire, and who we promote.
— Geoff Charles
Every support ticket is a failure of our product.
— Geoff Charles
Any second you spend planning is a second you don’t spend doing.
— Geoff Charles
I actually think velocity is a way to potentially avoid burnout. When I felt burnout, it was when I had the lowest amount of velocity.
— Geoff Charles
Don’t take everything I’m saying at face value. Start from first principles for your own company.
— Geoff Charles
High quality AI-generated summary created from speaker-labeled transcript.
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome