Why I Build Systems Before They're Needed
As someone who's spent over two decades building operations from the ground up, I've learned that the most important systems are the ones you put in place before you need them. It's a principle that's guided every role I've taken, from my early days in consulting to leading operations at companies like Veracross and now at Ramp. Too many leaders wait until they're drowning to think about process. By then, it's too late.
This belief crystallized for me during my time at Veracross. When I joined as COO, we were a solid company serving independent schools with our student information system. But I could see the growth trajectory ahead of us. We had the product-market fit, the team was hungry, and the market opportunity was massive. The question wasn't whether we'd scale. It was whether we'd scale gracefully or chaotically.
I spent my first 90 days building what I called "infrastructure for tomorrow." While the team focused on immediate customer needs and product development, I was designing hiring frameworks we wouldn't use for six months, documenting processes for departments that didn't exist yet, and establishing metrics we weren't quite ready to track. Some people thought I was getting ahead of myself. They weren't wrong, but that was exactly the point.
The payoff came 18 months later when we hit a growth spurt that would have broken most companies. Instead of scrambling to hire, we had clear job descriptions, interview processes, and onboarding workflows ready to deploy. When customer volume spiked, our support team had escalation procedures and knowledge bases that let them handle three times the load without missing a beat. We didn't just grow. We grew without losing what made us good in the first place.
This approach requires a specific mindset. You have to be comfortable investing time and energy in systems that might feel unnecessary in the moment. You need to think around corners and anticipate problems that haven't happened yet. Most importantly, you have to resist the urge to build everything perfectly from day one. The goal isn't to create rigid processes, but flexible frameworks that can evolve as the company does.
At Ramp, I'm applying this same philosophy to our international expansion. We're not just opening offices and hiring people. We're building the operational backbone that will let us scale across multiple markets simultaneously. That means establishing legal frameworks, financial controls, and communication protocols before we have teams in place to use them. It means thinking through compliance requirements for markets we haven't entered yet.
The companies that struggle with growth are usually the ones that treat operations as an afterthought. They hire brilliant people, build great products, and find strong market demand. But they don't invest in the unsexy work of building systems that can handle success. When growth comes, they're not ready for it.
I've seen this pattern enough times to know that preparation isn't just about avoiding problems. It's about creating the conditions for excellence. When your systems are ready before you need them, your team can focus on what they do best instead of fighting fires. That's how you turn rapid growth from a crisis into an opportunity.