
Sign up to save your podcasts
Or


What if the infrastructure protecting you from scale is the reason you can't afford to reach it?
Basecamp's founder publicly abandoned the cloud after calculating they'd spent $3.2 million annually on AWS. Their discovery? Actual usage didn't match what they were paying for. Today we sit down with Vidar Hokstad, founder of Hokstad Consulting, who's spent twenty-five years helping startups stop overengineering their infrastructure. Vidar reveals the uncomfortable math behind startup cloud spending: sixty to seventy percent is pure waste. We explore why engineering teams build for Google's traffic while sales teams are still making cold calls, and how the communication breakdown between pitch decks and development teams creates expensive solutions nobody needs. Discover why Twitter's "crappy" early architecture was actually the right call, how a one-second cache fix can buy months of breathing room, and the three questions every founder should answer before approving infrastructure spend.
Keywords: cloud infrastructure, AWS costs, startup scaling, overengineering, Kubernetes, cloud optimization, infrastructure costs, startup runway, Vidar Hokstad, technical architecture
By Anthony FrancoWhat if the infrastructure protecting you from scale is the reason you can't afford to reach it?
Basecamp's founder publicly abandoned the cloud after calculating they'd spent $3.2 million annually on AWS. Their discovery? Actual usage didn't match what they were paying for. Today we sit down with Vidar Hokstad, founder of Hokstad Consulting, who's spent twenty-five years helping startups stop overengineering their infrastructure. Vidar reveals the uncomfortable math behind startup cloud spending: sixty to seventy percent is pure waste. We explore why engineering teams build for Google's traffic while sales teams are still making cold calls, and how the communication breakdown between pitch decks and development teams creates expensive solutions nobody needs. Discover why Twitter's "crappy" early architecture was actually the right call, how a one-second cache fix can buy months of breathing room, and the three questions every founder should answer before approving infrastructure spend.
Keywords: cloud infrastructure, AWS costs, startup scaling, overengineering, Kubernetes, cloud optimization, infrastructure costs, startup runway, Vidar Hokstad, technical architecture