Aug 6, 2023 · 1h 16m · lennys-podcast
Velocity over everything: How Ramp became the fastest-growing SaaS startup ever | Geoff Charles
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Geoff Charles, VP of Product at Ramp, breaks down the operational frameworks, lean organizational structures, and high-agency culture that propelled Ramp to become the fastest SaaS company to reach $100 million in ARR. He provides actionable insights on deploying single-threaded teams, replacing bureaucratic OKRs with high-context strategy contracts, and hiring elite talent to sustain extreme product velocity.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 31% of the talking time here. How this is scored →
Lenny as informed peer 3.4 Guest teaching 4.0 Guest disagreement 0.5 Lenny pushing back 0.7
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 29:38 Contrarian reframe of burnout as lack of velocity
Geoff directly challenges the standard tech narrative around long working hours causing burnout, asserting that burnout actually peaks during periods of low velocity and bureaucracy.
Hardest push from Lenny ▶ 43:30 Lenny challenges the modern meaning of OKRsLenny refuses to accept the standard jargon around OKRs, pressing Geoff on why tech teams obsess over metric frameworks when basic goal alignment is all that matters.
Biggest teaching moment ▶ 47:00 Integrating support directly under product ownershipGeoff surprises Lenny by revealing Ramp treats every customer support ticket as an explicit product failure, completely defying industry organizational patterns.
Lenny holds their own ▶ 21:07 Lenny cites developer velocity researchLenny brings empirical authority to the conversation by citing Dr. Nicole Forsgren's research demonstrating that shipping faster directly improves engineering quality.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Defining Ramp: Product Suite and Unprecedented Financial Milestones | 3 | 3 | 0 | 0 | Lenny sets the stage by highlighting Ramp's historic velocity and growth metrics. Geoff details Ramp's multi-product expansion and core thesis on velocity. | |
| Operationalizing Single-Threaded Teams and Shielding Core Builders | 3 | 4 | 0 | 1 | Lenny drills into how single-threaded teams operate without getting derailed by bugs or ad-hoc requests. Geoff outlines the structural buffers like rotational production engineering and product ops. | |
| Setting Lofty Ambitions and Visualizing Vision Through Design | 4 | 4 | 0 | 1 | Lenny brings in his Airbnb experience regarding lofty goals and asks how to prevent unrealistic burnout. Geoff explains aligning upstream on hypotheses and data rather than micromanaging solutions. | |
| Strategy Contracts, Asynchronous Cadences, and Scaled Product Reviews | 3 | 4 | 0 | 1 | Lenny asks how leadership oversees product quality without creating bottlenecks. Geoff outlines the strategy contract and explains that high-stakes reviews occur primarily between beta and general availability. | |
| Maintaining Product Quality and Guardrail Metrics at High Speed | 5 | 3 | 0 | 0 | Lenny brings in developer productivity research from Dr. Nicole Forsgren demonstrating that speed increases quality. Geoff reinforces this by outlining guardrail metrics including operational burden and zero bug backlogs. | |
| Advice for Product Managers Under Pressure to Accelerate Velocity | 4 | 4 | 1 | 1 | Lenny raises concern over startup founders demanding Ramp-like velocity without providing proper support. Geoff offers tactical pushback guidance for PMs to eliminate status meetings and present explicit trade-offs. | |
| Reframing Burnout: Flow State and True Ownership Over Speed | 3 | 5 | 2 | 1 | Lenny questions the sustainability of continuous shipping. Geoff contrarily reframes burnout, arguing it stems from stagnation and lack of agency rather than hard work in a flow state. | |
| Action Over Planning: Embracing Constructive Startup Chaos | 4 | 4 | 1 | 2 | Lenny questions Geoff's quote about minimizing planning, noting it can cause extreme chaos, and cites Sheryl Sandberg. Geoff clarifies that planning accuracy is only dialed up for critical company-wide market moments. | |
| Sponsor Spotlight: Attio Next-Generation CRM for Startups | 2 | 4 | 1 | 1 | Following the sponsor read, Lenny asks how strategy docs are formatted and how planning cycles run. Geoff explains abandoning heavyweight quarterly OKR planning in favor of biannual one-pagers. | |
| Identifying the Right to Win and Product Roadmap Accountability | 4 | 4 | 1 | 2 | Lenny pushes back skeptically on the definition and utility of OKRs across tech. Geoff illustrates Ramp's 'right to win' framework and explains why roadmaps serve as the sole execution contract. | |
| First-Principles Problem Solving and Integrating Support into Product | 2 | 6 | 1 | 0 | Geoff explains first-principles thinking by rejecting past playbooks and revealing that customer support reports directly into product because tickets represent product flaws. Lenny is visibly stunned by this structure. | |
| Writing as a Thinking Tool and Protecting Deep Work Blocks | 5 | 4 | 0 | 0 | Lenny and Geoff discuss writing as an essential medium for rigorous thinking. Lenny elaborates on calendar blocking and aggressive meeting protection practices. | |
| High-Efficiency Task Management and Freeing Cognitive Headspace | 5 | 3 | 0 | 0 | Lenny recognizes Geoff's personal organization methodology as closely paralleling David Allen's Getting Things Done. Geoff describes his daily note-grooming system designed to offload memory. | |
| Lean PM Ratios, Product Operations, and Distributed Product Ownership | 3 | 5 | 0 | 1 | Lenny asks how Ramp operates with an unusually lean ratio of 13 PMs to over 100 engineers. Geoff explains how engineers and designers are empowered to own scoping, ticketing, and specs. | |
| Identifying and Fostering A+ Engineering Talent in Startups | 3 | 5 | 1 | 0 | Lenny asks how PMs can gauge if their engineers are truly elite. Geoff breaks down specific indicators, such as engineers proactively resolving customer blockers and driving the product roadmap. | |
| Ramp's Product Manager Hiring Criteria and Interview Philosophy | 2 | 4 | 0 | 0 | Lenny asks about Ramp's unique interview filters and transition paths into product. Geoff outlines prioritizing decision depth and velocity appetite over domain experience. | |
| Lightning Round: Influential Media, Daily Routines, and Tool Mastery | 2 | 2 | 0 | 0 | Lenny runs through the standard lightning round covering media recommendations, interview prompts, health monitoring, and tool hygiene. Geoff closes with growth mindset advice. |
Statements from this episode (35)
Ramp reached $100M annual revenue in its first two years
“I mean, we were one of the fastest growing fintech and maybe SAS companies of all time. I think we've hit a hundred million in annual for first two years.”
Ramp has surpassed $10 billion in annualized transaction volume
“In terms of just raw transaction volume, you know, we have crossed ten billion in analyze spending on the platform and just getting started.”
Ramp built competitors to American Express and Expensify in months
“In three months, we built a competitor to Amex. Six months after that, we built a competitor to expensify, you know, both publicly traded companies.”
Ramp built a Bill.com competitor in three months with five people
“We basically gave a team, you know, goal of building a competitor to build.com. It was three engineers, one designer, one PM, three months, and they hit it out of the park and that product is, is, is moving in billions of dollars a year.”
Shield new product teams from organizational chaos until product-market fit
“Small teams have a single threaded focus give them the resources they need to execute, big lofty goals, very tight timelines, and then like shield them from the chaos that is the rest of the organization. Basically don't bother them and don't even tell the res…”
Very few individual contributors execute well across multiple simultaneous priorities
“There are very few people who are able to execute extremely well and more than one thing. And it's especially true for individual contributors.”
Ramp uses engineering rotations and product operators to shield core builders
“So, you know, we have a rotational program on production engineering, for example, where our engineers are protecting the core team from escalations, from bugs, from issues. We have product operators that are protecting the PM from the chaos that is, you know,…”
Incumbent market comparables de-risk business decisions for startup product teams
“When you look at, you know, bill.com, right, they're a publicly traded company, Expensify Public and Traded or Concur or Coupa. These are all like large players that are actually very motivating and largely de-risk some of the business decisions you're making.”
Anchoring on revenue targets and design prototypes drives extreme product velocity
“You're able to move super, super fast. If you have those two things in mind, the market and the revenue goal, because we're very revenue driven as a company and the designs that, that can really keep you anchored on, on what this could look like.”
Product leaders should debate data and hypotheses rather than potential solutions
“Oftentimes, you know, more junior leaders, and I was certainly in that camp earlier on, kept focusing on, on the solutions and debating the right solution when in fact you should really be debating upstream of that. You should be debating the interpretation of…”
Charles requires public weekly goals and uses 1-on-1s only to unblock reports
“I basically have teams, all my directs post their goals every week. First thing Monday, the goal there is to also have them review each other's goals. I have a one-on-one template that I basically use to keep on track of how progress is being made. But I certa…”
Fast-moving teams should stress-test product decisions at GA, not pre-beta
“It's the difference between a beta and the GA that that's where we really get plugged in when we make the decision to go live. To the rest of the customer base and asking sales to start selling. That's where I'll really come in and stress test the hypotheses a…”
Forsgren's research shows software quality increases as engineering velocity rises
“Actually, I just had a chat with Nicole Forsgren, who's world expert on developer productivity and developer experience, and they've done all this research on quality and speed of engineering and the engineering team, and they find that quality goes up as your…”
Ramp maintains zero bug backlog and fixes bugs as they surface
“We don't have a bug backlog. We fix every bug once they're surfaced almost.”
Ramp freezes new features if teams breach quality and confusion metrics
“And if that number is a slightly elevated, we're basically saying you can't ship any new features. You need to fix these things. And so, yeah, there's just these types of controls, but basically trying to standardize across the teams. This is your percentage o…”
Ramp's velocity is driven primarily by elite engineering and design talent
“Behind ramps velocity is a lot less like the culture that, that I try to amplify a lot more, the quality of the engineering and design talent candidly.”
Geoff Charles has never scheduled or run a status meeting at Ramp
“I've never had a status meeting. I've never scheduled a status meeting. Statuses are done async.”
High product velocity and core focus helps teams avoid workplace burnout
“And so I actually think velocity is a way to potentially avoid burnout. I'm not asking people to work, you know, unless hours a week, I'm asking people to get out of their own way and to focus on, on what truly matters, which is building great products for our…”
Teams should only invest in planning accuracy where precision delivers high value
“Because accuracy has cost, make sure that you're only increasing the accuracy of planning for the things that have high value of that accuracy.”
Ramp replaced quarterly OKRs with a biannual one-pager of company priorities
“We moved from like quarterly, very expensive quarterly planning, which took one month every three months. So basically, 33% of the time was planning to a biannual one pager on these are the company priorities. And it's much more smooth and much faster.”
Ramp avoids OKRs for product teams to prioritize direct roadmap velocity
“I stay away from them from a product perspective, because again, I want to focus on velocity, which is just output, which is your roadmap. But they could, they're pretty strong at more of the cross-functional side of things as well as the financial side of thi…”
Ramp considers support tickets product failures and has support report to product
“Our support reports into me, and the first principle there was saying, well, every support ticket is a failure of our product. We literally have that as, you know, a quote just posted on, on, on all those channels. It's a failure. And our, if the product works…”
Ramp supports over 400,000 users with fewer than 30 customer support agents
“We have an extremely low contact rate. We have, you know, over 400,000 users on our platform and a team of agents that's under, under 30.”
Writing rather than reading is the best way to improve clear thinking
“You could read things and that's helpful, but I don't think that reading makes you necessarily think better. It makes you more wise. But the best way to increase your capacity to think is to actually do the thinking. And so that's where I see writing. If you'r…”
Rachitsky: Product managers often lack unique skills beyond having free time
“I always think that PMs often don't really have any special unique skills. They just have the time to do the things that nobody else Wants to do or can't, or yeah, doesn't have the time to do or doesn't want to do.”
Offload memory into written notes to free cognitive headspace for processing
“I try to create or free up headspace for processing, not memory, and so I just basically spend very little time memorizing anything, and I write everything down.”
Ramp employs roughly 13 product managers for over 100 engineers
“We have about 13 PMs at RAMP, probably over a hundred engineers.”
Empowering engineers and designers to think like product managers creates leverage
“Making everyone feel like a PM is a great way to get leverage as a PM. And that means basically empowering the designer to think about the actual specs and priorities and scopes more than you or empower the engineer to take something that's. Fairly lightweight…”
Ramp product managers never write tickets or manage Linear tasks
“We never write a ticket. We don't spend much time in, in, you know, linear, which is our ticket management system. We basically, our contract is the vision and the priority and a very high level spec and everything else is kind of Pushed on the engineering tea…”
Engineers should have full autonomy beyond meeting their core product commitments
“Your job is to make sure that they're aligned with the long-term vision and that they can deliver what they've committed to. But on top of that, they can do whatever the hell they want. And if they're taking on something that puts the things that they committe…”
Radically empowered, opinionated engineers outperform passive teams that accept instructions
“And look like there, there's drawbacks to that culture, right? Where you get to like a radically empowered engineering team that thinks that they know the product better than the designer or the PM and they push back on the designs or they disagree with the PM…”
Ramp engineers and designers decide if trial product managers keep their jobs
“And what we typically do is we give those PMs a shot or those folks a shot. So we'd give them like six months to go into a new area and try it out. And then we basically have the engineers they work with and designers they work with actually make the call as t…”
Ramp's CTO focused solely on hiring elite talent in year one
“I mean, early, early on for the first year at ramp, Kareem our CTO was only focused on that. It was hiring the best talent. He was a lot less interested or focused on our product strategy or product market fit, or even our revenue. It was all about bringing in…”
Interactive visionary prototypes shared via video walkthroughs dramatically increase product velocity
“Having designers spend more time creating more visionary prototypes and then sharing those out in videos. It just has just huge impact on, on how exciting work is and how excited the team are. And so just providing that clarity is massive. And I think just aga…”
To protect deep work, check email once daily and Slack hourly
“Turn off notifications. Quit Slack. When you're doing deep work, check your emails once a day and just like literally go through them in like five minutes. They're off the times. Most of them are useless. Check Slack only at the top of the hour.”