Early founders resist basic financial or HR controls as 'big company stuff.' However, these systems prevent avoidable, costly mistakes, much like car brakes don't just slow it down but enable it to safely travel at higher speeds, as illustrated by a former CFO.
Related Insights
Accountants often create overly granular charts of accounts (150+ categories), which slows startups down. If you can't categorize an expense in five seconds, your system is too complex. Stick to 15-20 high-level categories. Simplicity in finance translates directly to operational speed and better decision-making.
As startups hire and add structure, they create a natural pull towards slower, more organized processes—a 'slowness gravity'. This is the default state. Founders must consciously and continuously fight this tendency to maintain the high-velocity iteration that led to their initial success.
After nearly failing, OpenGov adopted a frugal culture and discovered it grew faster. Less spending reduces system noise and inefficiency. A leaner, more focused sales team, for instance, can become more motivated and effective, leading to better results.
Counterintuitively, implementing formal processes like documented decision-making (e.g., a RAPID framework) early on increases a startup's velocity. It creates a clear, universally understood system for making decisions, preventing delays caused by ambiguity or passive-aggressive managers.
Founder failure is often attributed to running out of money, but the real issue is a lack of financial awareness. They don't track cash flow closely enough to see the impending crisis. Financial discipline is as critical as product, team, and market, a lesson learned from WeWork's high-profile collapse despite raising billions.
Retrofitting systems and standardizing incentive plans across a 1,400-person organization is immensely difficult. The key lesson is to implement enterprise-grade systems (like an ERP) and standardized processes when your company is still tiny. It's exponentially harder and more expensive to fix these issues at scale.
