Velocity over everything: How Ramp became the fastest-growing SaaS startup ever | Geoff Charles
Summary
Highlights
Geoff Charles introduces Ramp as a finance automation platform and corporate card solution for businesses. He highlights Ramp's unprecedented growth, reaching over $100 million in annual run rate in two years, making it the fastest-growing SaaS business in history. He attributes this success to a culture of velocity, which is ingrained in every aspect of Ramp's operations, from product development to hiring.
Geoff shares examples of Ramp's rapid development, such as building competitors to MX and Expensify within months, and launching an accounts payable product that moves billions of dollars annually. Key elements enabling this velocity include small, single-threaded teams with focused goals, providing necessary resources, setting tight timelines, and shielding teams from external chaos.
Ramp fosters empowerment by providing teams with context rather than micromanaging. Geoff emphasizes aligning on goals, hypotheses, and data allows teams closer to the ground to derive better solutions. He highlights the importance of leaders acting as 'repeaters in chief,' constantly sharing context to enable informed decision-making and prevent burnout by ensuring work feels impactful.
Geoff explains that quality at Ramp increases with velocity because rapid iteration allows for quick fixes and improvements. Control mechanisms like voice-of-customer processes, NPS/CSAT tracking, and monitoring operational overhead ensure quality is maintained. Teams are incentivized to keep metrics healthy; if they falter, new feature development is paused to address issues, ensuring ongoing quality.
Geoff reframes burnout, suggesting it's often linked to a lack of impact rather than simply long hours. He argues that high velocity can actually prevent burnout by keeping individuals engaged in a 'flow state.' The key is for management to ensure team members feel their work is meaningful and aligned with their personal goals, fostering a sense of ownership and dedication.
Ramp minimizes extensive upfront planning, prioritizing doing over deliberating, except for critical market moments. Geoff describes a 'contract' with teams that outlines goals, hypotheses, metrics, initiatives, risks, and long-term outcomes to ensure alignment. The company's unique blend of credit card, payments, and software business models necessitates original, 'first principles' thinking rather than pattern matching from past experiences.
Geoff highlights writing as a crucial tool for clear thinking and problem-solving, especially when tackling novel challenges. He advises starting with a simple question and dedicating time to deep thought before seeking external answers. This approach not only aids individual clarity but also facilitates effective communication and knowledge sharing within the organization, crucial for scaling a rapidly growing company.
To manage the overwhelming amount of information and tasks, Geoff employs a robust, yet simple task management system. He meticulously records tasks and their deadlines, grouping similar items and externalizing reminders to free up mental space. His philosophy is to optimize for 'processing, not memory,' using tools and systems to quickly retrieve information and focus on problem-solving rather than recall.
Ramp maintains a lean PM team (13 PMs for over 100 engineers) by encouraging everyone to 'think like a PM.' Product operations handle many traditional PM tasks, freeing PMs to focus on strategy and vision. When hiring, Ramp prioritizes candidates with a strong desire for impact and deep thinking abilities over extensive prior experience, seeking individuals who are proactive, curious, and accountable.
Geoff advises aspiring product managers to gain experience in roles adjacent to product, such as product operations, business operations, or sales engineering. The key is to deeply understand customer needs and the product itself, demonstrating impact in these areas. Ramp often offers internal candidates a trial period, with feedback from engineers and designers determining their fit for a PM role.