Just as real is process debt. A review added because of a launch gone wrong. A new legal check to guard against possible litigation. A section added to a document template. Layers accumulate over the years until you end up unable to release a new feature for months after it's ready because it's stuck between reviews, with an unclear path out.
This is one of the scariest things about scaling. Every process you add is a response to a real problem, but nobody goes back to ask whether the problem still exists or whether the fix is proportional. As a founder, I want to build a culture where process is treated like code: it should be reviewed, refactored, and sometimes deleted. The instinct to add a check after every failure is natural, but the discipline to remove checks that no longer serve you is what separates fast companies from bureaucratic ones. I keep thinking about Ramp's culture of velocity; they seem to guard against this almost religiously.
https://www.natural.co/blog/why-devan-joined-natural
Natural cares about the small things in ways that make me challenge my perception of what that means in a company setting.
Turns out someone called beforehand to arrange a 10am check-in time for me.
It is Mason from Equinox. He says Natural has created a 3 day pass for me at any of their locations.
Charger is already plugged in and through the wire hole. Two monitors — both Studio Displays – lined up perfectly.
This story hit me because it reframes “the small things” as indicators of deeper values, not superficial perks. Anyone can claim to care about people, but the extra step to care enough about thoughtful details and anticipate needs without being asked is what is important.
It makes me think about the kind of company I want to build: one where care isn’t a line in a values document but something you can feel in every interaction. One where culture shows up in the tiny, almost invisible actions, the ones easy to overlook yet impossible to fake.
As a founder, I want to design an environment where these small acts of consideration are the default, not the exception. Because those small things accumulate. They create momentum, trust, and a sense that people matter.
Ramp's CPO Geoff Charles talks about engaging customers early in the development process through beta testing before public launch — not as a QA step, but as a product strategy. At Ramp, they've given teams three-month mandates to build MVPs and go to market with them, treating the beta itself as the product experience. The philosophy is that doing is better than planning, and shipping something real to a small group of users generates more learning than any amount of internal debate. Their approach to beta is inseparable from their broader culture of velocity — they'd rather put something imperfect in front of real users than spend months polishing something nobody's validated.