20Growth: How Wiz Built a $30BN Brand in Enterprise | What Worked vs What Was a Mega Failure: Lessons Learned | Why Marketers Make the Worst CMOs & What To Look for in Growth with Raaz Herzberg

What It Covers

Raaz Herzberg, CMO at Wiz, reveals how the cloud security company scaled from zero to multibillion dollar ARR by starting upmarket with Fortune 10 customers, prioritizing brand over pipeline metrics, and building unconventional marketing strategies.

Key Questions Answered

• •Enterprise-first strategy: Wiz's first paying customer was a Fortune 10 company, enabled by founders' Microsoft Azure security background providing deep enterprise knowledge. Starting upmarket in security creates downstream momentum because buyers want solutions their bank uses, making the path to smaller customers easier than reverse.
• •Time-to-value as competitive advantage: Wiz delivers value in 15 minutes versus months-long enterprise deployments by designing for infinite scale from day one. This product philosophy eliminates technical debt, enables fast POVs without sales friction, and allowed the company to sell millions per hour before hiring salespeople through pure product pull.
• •Brand over attribution metrics: Pipeline numbers and marketing attribution are meaningless because every company measures differently and green dashboards don't prevent CMO firings. Focus instead on warm rooms—whether prospects already know your name when meetings start. Measure success through sales team feedback and customer awareness, not MQL counts.
• •Unconventional marketing execution: The Wizard of Oz booth at RSA conference generated 4x more leads than traditional approaches at identical cost. Marketing allows experimentation without permanent consequences unlike product decisions. Hire doers who understand the domain deeply rather than traditional marketers focused on pipeline metrics and complex attribution models.
• •Product decisions for scale: Build features asking "will this work at infinite scale?" from day one. Example: showing infrastructure graphs works for 100 machines but breaks at 50,000. This mindset prevents refactoring, eliminates technical debt accumulation, and enables velocity because teams avoid building wrong solutions that require later rebuilds.