Geoff Charles · Lenny's Knowledge Sketch

Core Concept

Velocity Is the Operating System

"Velocity is everything at Ramp. It's how we design our product development process, how we incentivize teams, who we hire, who we promote, and how we make every decision."

$100M ARR in 2 years with fewer than 50 in R&D
3 engineers + 1 designer + 1 PM built a Bill.com competitor in 3 months
1,000 new users join Ramp every single day
Velocity de-risks decisions, low cost of being wrong = faster iteration

Framework

The Ramp Velocity Recipe

$10B+

transaction volume

50

people at $100M ARR

8.5M

hours saved for customers

Single-Threaded Teams

One goal, one focus. Remove everything else, production bugs, cross-team asks, even internal visibility, until they hit traction. Give them a room, shield them, then add resources after gravitational pull builds.

Context Over Control

Align on goals, hypothesis, and data, then step back. Debate interpretation upstream, not solutions downstream. Teams closest to the ground make the best calls when given the right context.

The PM Contract

The contract is the strategy doc and roadmap, not tickets, not OKRs. PMs own vision + priority + high-level spec. Engineers own the breakdown. Never write a ticket.

Deep Dive

How Ramp Operationalizes Speed

No bug backlog: Every bug gets fixed as it surfaces. Engineers on rotation shield core teams from production issues so builders stay in flow
No status meetings, ever: Status is async, in the systems where work happens. Meetings are reserved only for collaboration, ideation, and real decisions
Quality as a control metric: If support ticket confusion spikes, you stop shipping features until UX is fixed. Quality is a guardrail on velocity, not separate from it
Voice of customer loop: Every negative review routed monthly to the PM, tech lead, and designer. NPS + CSAT + operational overhead tracked per team
Biannual planning over quarterly OKRs: Dropped expensive quarterly cycles (33% of the year was planning) for a lean biannual one-pager on company priorities

"Any second you spend planning is a second you don't spend doing. Increase the accuracy of planning only for the things that truly have high value of that accuracy."

The Strategy Doc (per pod)

Each pod writes their own one-pager covering:

1.What is the goal?
2.Why do we believe this will work?
3.Why are we uniquely positioned to win?
4.What metrics prove success?
5.What are the key risks and initiatives?

Support Reports to Product

First principle: every support ticket is a product failure. Support reports into product. 400K+ users, under 30 agents, because the goal is eliminating tickets, not resolving them.

Writing = Thinking

Shut the laptop. Take paper. Write the question at the top. Think before Googling. If you can write it clearly, you can think it clearly, and clarity compounds into velocity.

Tactics

How Ramp Hires & Runs PMs

Look for hunger over experience, candidates leaving because things got "too slow, too bureaucratic" are the signal
Favorite interview question: "What's the hardest thing you've ever done?", reveals their definition of difficulty and personal agency in overcoming it
Go deep on one decision, scratch until you hit bedrock on how they think through tradeoffs and why
Spot A+ engineers by: do they ask business questions? Do they set the pace for the PM? Do they jump into Slack proactively to help?
PM ratio: 1 PM to 8–15 engineers, possible because engineers, designers, and product ops all think like PMs
Never write a ticket, high-level spec + priority is the PM's output; engineers own the breakdown in Linear

The Real PM Job at Ramp Team culture, strategic alignment, stakeholder shielding, surfacing one-way decisions. Everything else gets pushed down. PMs are force multipliers, not ticket writers.

Contrarian

Velocity Myths That Slow You Down

✗ More goals = faster execution INSTEAD → ✓ Four focused bets ship faster than eight scattered ones. Present tradeoffs to leadership and force the choice. Saying no to half the list is how you double velocity.

✗ Moving fast means lower quality INSTEAD → ✓ Research shows quality goes UP with velocity. Fast teams fix fast. Large release batches waiting for review accumulate more bugs, not fewer.

✗ High velocity causes burnout INSTEAD → ✓ Burnout comes from effort without progress. Geoff burned out most when velocity was lowest. Flow state, where work feels thrilling, is the antidote, not fewer hours.

✗ Velocity culture can be bolted on INSTEAD → ✓ Ramp's velocity came from engineering quality first, not slogans. Hire A+ engineers, radically empower them, and kill status meetings. The culture follows the talent, not the other way around.