Velocity as Design Principle

Speed as the one edge incumbents cannot copy

Eric Glyman describes building Ramp around velocity as an architectural choice rather than a culture slogan: "We from early on designed the company explicitly around velocity."¹ His reasoning is a claim about incumbents. The companies Ramp competes with were founded, in his phrase, by people who actually wore top hats, J.P. Morgan, Henry Wells, the founders of Amex, Citi, and Chase, and their moats of brand, distribution, and underwriting expertise are real and enormous but slow-moving. He offers a test for how little has changed: if you had to use the phone your parents used at your age you could not function, but if you had to use their bank account or credit card you probably could, thirty to forty years of near-stagnation in the product while the rest of technology went from no phones to flip phones to computers that can think. On his account that gap is the opening, and speed is the only edge the incumbents structurally cannot copy, because their advantages are precisely the slow-moving kind.

Counting the days

Glyman describes tracking the company's age in days rather than quarters, at one point noting the company was 2,310 days old, and setting founding milestones the same way: approved by the card network within 45 days, by the bank within 60, and funding first transactions by 70.¹ He describes early growth targets of 10 percent per week and, at scale, 20 percent per month, which he acknowledges is intense. He presents the day counter less as a vanity metric than as a pacemaker: with a small team going up against companies of tens of thousands, the operative question becomes whether the last stretch of days moved the company forward more than the previous one, and which hours actually inflected the trajectory. He describes the counter as giving everyone permission to subtract, to step out of a meeting or decline an activity in order to say yes to the thing that matters.

Managing inputs, not outcomes

Glyman frames velocity as higher-leverage allocation of fixed hours rather than working more of them, and pairs it with a hiring model that favors people who find joy in their craft over those who simply absorb burnout, plus extreme focus on one or two functions.¹ The discipline of managing inputs rather than outcomes runs alongside the diagnostic in theory-of-constraints: identify the inputs predictive of the far-off goal and manage tightly to those. The habit of saying no to preserve tempo also connects to the-new-luxury-is-less, where subtraction is the premium good.

The engineering mechanics

Karim Atiyeh supplies the engineering tactics under the principle. He describes shortening the idea-to-customer cycle everywhere, asking how long it takes to get code to production and, inside that, how fast tests run and how quickly one can deploy.² He recounts pushing back when Ramp's first product manager, Geoff Charles, now the company's head of product, tried to size every task with story points, arguing you can have precision on how long things take or you can do them very fast but rarely both, because rewarding people for hitting estimates incentivizes padded estimates they can safely beat. He also argues that best-practice process moves a below-average team to average, while the people most extreme on speed tend to work in nonstandard ways, so velocity at the frontier is anti-standardizing. A broken arm early in his career at Paribus, when he was effectively the whole engineering team, forced him to maximize the output of others rather than his own, working through terse instructions and diagrams instead of doing the work himself, an early, literal lesson in the delegation velocity later requires at scale.² Both founders treat speed as a designed property of the company rather than an attitude.

Where the founders qualify it

Atiyeh states a blunt precondition: velocity depends far more on the quality of engineering and design talent than on culture, and he describes spending his first year almost entirely hiring. He argues a leader cannot ask for velocity while refusing to grant empowerment, eliminate process, and increase focus, the trade he says leaders from traditional industries decline to make.² The growth-side caveat is that velocity is only valuable if a team can still learn from it: running many sloppy experiments teaches nothing, so speed under deadline has to be repaid later with rigor.