Founders - Company Survives 30-Day Founder Absence

I stepped away from my companies for 30 days. No daily check-ins. No executive decisions. No safety net. When I came back, nothing had broken. Revenue continued. Problems got solved. The team didn't miss a beat. That result exposed something I hadn't been willing to see: I hadn't built a business. I'd built a dependency on myself. Here's what actually happened on that trip: I went to the Maldives with my wife. For the first 8 days I was physically present but mentally still running the companies. My nervous system was so wired from years of fight-or-flight leadership that I didn't know how to exist without a problem to solve. Somewhere around day 9, I stopped reaching for the phone. Not from discipline — from exhaustion. And in that stillness, something I hadn't expected happened: the businesses kept moving without me. Deals closed. Issues got resolved. My team made decisions I would have made — sometimes better ones. By day 30, I wasn't just rested. I was restructured. The lesson wasn't about travel. It was about systems and trust. Most founders I talk to are the single point of failure in their own company. They've built something that can't survive their absence — and they've mistaken that dependency for value. It isn't. It's a liability. If your business can't run for 30 days without you, you don't have a business. You have a job with a logo. The question worth asking isn't "can I afford to step away?" It's "what does it say about my company if I can't?" I'm writing about this at length in my upcoming book Permission to Unplug — for founders who've built something real but forgotten how to live outside of it. What's the longest you've stepped away from your business? And what did it teach you about what you'd actually built? Life's About Experiences