Velocity over everything: How Ramp became the fastest-growing SaaS startup of all time | Geoff Charles (VP of Product)

Episode Summary

Executive Summary: Jeff Charles explains how Ramp scaled to extreme growth by prioritizing velocity, small empowered teams, first-principles thinking, and tight strategic focus. He argues that speed comes from talent density, minimal process, strong context-sharing, and clear tradeoffs—not from more meetings or planning. The episode offers a detailed look at Ramp’s operating system for product development, hiring, and burnout avoidance.

Main Topics: Velocity as the core operating principle (Priority: 5/5): Ramp optimizes for shipping fast in every part of the organization—hiring, product development, decision-making, and promotion. Velocity is treated as both a competitive advantage and a filter for talent. Small, single-threaded teams and shielding from chaos (Priority: 5/5): Jeff describes how Ramp gives tiny teams big goals, tight timelines, and protection from distractions so they can focus on one objective at a time and ship quickly. Context over control and empowered product teams (Priority: 5/5): Leadership provides goals, hypotheses, and data, while teams own solutions and roadmaps. The company relies on context-sharing instead of micromanagement to scale decision-making. Strategy, planning, and tradeoffs (Priority: 4/5): Ramp uses a lightweight strategy process centered on goals, hypotheses, metrics, initiatives, and risks. The company favors biannual planning and financial alignment over heavy quarterly OKR processes. First-principles thinking and right-to-win (Priority: 4/5): Because Ramp spans cards, payments, software, SME and enterprise motions, it avoids copy-pasting playbooks. Teams reason from fundamentals, especially when launching new products or building support and operations models. Quality, operational controls, and burnout avoidance (Priority: 4/5): Ramp maintains quality by tracking customer pain signals, support load, CSAT/NPS, and bugs, while Jeff argues that velocity can reduce burnout by increasing flow, meaning, and ownership. Hiring, team composition, and PM role design (Priority: 4/5): Ramp hires for impact, deep thinking, and high agency. PMs are few, and much of the traditional PM work is distributed across product ops, design, engineering, and other team members.

Key Arguments: Velocity matters because it compounds over time, attracts strong talent, and lowers the cost of decisions by enabling fast iteration. Small teams with one clear goal outperform larger teams because they reduce coordination overhead and maintain focus. Leaders should provide context, not solutions; teams closer to the work will usually produce better answers when aligned on goals and data. Planning should be minimized unless accuracy truly matters; excessive planning and OKRs can create politics and slow execution. Ramp’s strategy works because it focuses on where the company has a unique right to win, reusing existing assets like money movement, risk, and accounting integrations. High velocity does not have to lower quality if there are strong feedback loops for bugs, customer confusion, NPS, and operational burden. Burnout is often caused more by low impact and distraction than by hard work; meaningful, fast-moving work can actually be energizing. A-plus engineers and designers are essential; to sustain Ramp’s model, the company must invest heavily in top-tier R&D talent and give them real autonomy.

Data Points: Ramp annual revenue: $100 million ARR in roughly two years - Used to illustrate the company’s extraordinary growth trajectory Ramp team size at early scale: ~50 total in R&D, with less than 40 engineers and 3 PMs - Jeff described the company reaching $100M annual revenue with a very small product org Initial company size when Jeff joined: About 10 people, including about 8 engineers - Shows how small the team was when major products were built Amex competitor build time: 3 months - A small Ramp team built a competitor to Amex in a short timeframe Expensify competitor build time: 6 months after the Amex competitor - Ramp built another major product quickly after the first AP product team size and timing: 3 engineers, 1 designer, 1 PM, 3 months - Used as an example of single-threaded team execution AP product scale: Billions of dollars a year - Jeff says the accounts payable product is now moving massive volume Businesses served: 15,000 businesses - Ramp helps small/mid-sized companies automate finance operations Daily user growth: About 1,000 users join per day - Indicates ongoing platform growth Savings delivered: $600 million in savings - Ramp claims savings generated for customers Time saved for customers: 8.5 million hours saved - Reported as the operational benefit to customers Transaction volume: Over $10 billion annual spending on platform - Shows the scale of payments flowing through Ramp PM count: About 13 PMs - Current product management team size at Ramp Engineer-to-PM ratio: Roughly 1:8 to 1:15 - Jeff says the ratio varies by team

Pivotal Quotes: "Velocity is everything at RAMP." — Jeff Charles: He explains that velocity shapes hiring, incentives, organization, and product development "Any second you spend planning is a second you don't spend doing." — Jeff Charles: His philosophy on minimizing planning and maximizing execution "Every support ticket is a failure of our product." — Jeff Charles: Used to explain why support reports into product and why product teams are accountable for reducing issues

Implications: For product leaders, Ramp’s model suggests that speed comes from talent density, fewer priorities, strong context, and ruthless elimination of process. Teams that want similar results must redesign operating norms, not just demand faster execution.