Geoff Charles

Geoff Charles is VP of Product at Ramp, the fastest-growing SaaS business in history, which reached $100M in annual revenue in two years with under 50 people in R&D -- a ratio of output to headcount that makes the sustainability question empirically unavoidable. Their core argument: Extreme velocity does not require burnout if you keep teams small, single-threaded, and shielded from organizational chaos. The key is building layers of protective tissue around core teams so they can focus on one lofty goal without distraction. The evidence is specific: Ramp's 3-month sprint to build an Amex competitor with ~8 engineers. Furthermore, bill.com competitor built by 3 engineers, 1 designer, 1 PM in 3 months -- now moving billions/year. Rotational production engineering program that shields core teams from bugs and escalations. In Geoff Charles's own words: "When I joined, we were about 10-ish folks, about eight engineers, and in three months, we built a competitor to Amex. Six months after that, we built a competitor to Expensify, both publicly traded companies. We hit a hundred million in annual revenue. I think we were under at that point 50 total in the R&D department." (Ramp's extraordinary velocity metrics with a tiny team.)

As VP of Product at the fastest-growing SaaS company in history, Charles built the product organization from 10 people to a team that shipped multiple billion-dollar product lines--each created by small autonomous teams in months, not years. Their core argument: Empower people closest to the problem -- full autonomy with accountability. The evidence is specific: Ramp building a competitor to Amex in three months with eight engineers. Furthermore, a five-person team (3 engineers, 1 designer, 1 PM) building a Bill.com competitor in three months that now processes billions per year. Ramp's flex product for eCommerce companies built by a single-threaded team in one summer. In Geoff Charles's own words: "Empower the folks closest to the problem to own the decision. We give teams the resources they need to hit the goal, and we hold them accountable to hitting the goal. Simple as that." (Ramp's autonomy philosophy.)

Geoff Charles is VP of Product at Ramp, the fastest-growing SaaS startup in history, reaching $100M+ in annual run rate in two years. He joined when the company had about 10 people and built the product organization that scaled across expense management, card payments, bill payments, and accounting. Their core argument: Measure and reward impact per headcount -- ruthlessly cap headcount because every person you add inherently slows the rest of the organization. The evidence is specific: Built a competitor to Amex in 3 months with ~8 engineers. Furthermore, built a competitor to Expensify with under 50 total R&D, fewer than 4 engineers and 3 PMs. Built a competitor to Bill.com with 3 engineers, 1 designer, 1 PM in 3 months -- now moving billions/year. In Geoff Charles's own words: "We try to increase leverage as much as possible -- defined by impact divided by headcount. We reward teams that were able to get more done with very little. For the first two years at Ramp, we had fewer than five PMs and fewer than 50 engineers as we scaled to $100 million in ARR." (On Ramp's team sizing philosophy as published in Lenny's Newsletter.)

Charles built Ramp's product org from 10 people to the fastest-growing SaaS business in history, proving that velocity-first decision-making can produce billion-dollar product lines in months with tiny teams. Their core argument: Velocity is everything -- speed de-risks decisions by lowering the cost of being wrong. The evidence is specific: Ramp building a competitor to American Express in three months with eight engineers. Furthermore, a five-person team building a Bill.com competitor in three months that now processes billions per year. Ramp's flex product for eCommerce companies built by a single-threaded team in one summer. In Geoff Charles's own words: "Velocity is everything at Ramp. It's how we design our product development process. It's how we incentivize teams, it's who we want to hire, it's who we want to promote, and it's everything around how we make decisions and how we organize the organization." (How velocity permeates everything at Ramp.)

Charles built the product organization at the fastest-growing SaaS company in history, proving that velocity-first principles work even in financial technology where billions of dollars flow through the platform. Their core argument: Velocity over everything -- high-velocity decision-making and extreme focus. The evidence is specific: Ramp processing over $10 billion in spending on the platform while maintaining a velocity-first culture. Furthermore, a five-person team building a Bill.com competitor in three months that moves billions of dollars per year. Ramp's R&D department of fewer than 50 people reaching $100M ARR. In Geoff Charles's own words: "Everything we do is around velocity. This means high-velocity decision-making, keeping things simple, reducing team sizes and dependencies, maintaining extreme focus and work ethic." (On Ramp's velocity-first philosophy.)

Charles has turned Ramp's org design into a velocity machine, and his most contrarian claim is that pure platform teams are a trap almost all fast companies fall into too early. His logic: platform work exists to serve real product use cases, and the decisions about what to build are dominated by product context, not generic infrastructure elegance. When a platform team is removed from the product teams it serves, prioritization drifts toward the abstract. So Ramp deliberately embeds platform work inside the product team with the most acute need. Payments platform lived inside Bill Pay because the new use cases were B2B payments; data-science platform lived inside the risk team because underwriting was where the demand concentrated. Only after those teams rack up 'a few wins' does Ramp spin them out — specifically to force them to work across multiple teams. In Geoff's own words: "Our payments platform was embedded within our Bill Pay product because most of the new use cases were B2B payments. Our data-science platform was embedded within our risk team since most of our data-science needs were on underwriting. We spin teams out after they've had a few wins to force them to work across teams." (Concrete example of how Ramp decides when platform work earns its independence.)