Ben Horowitz and Ali Ghodsi: How to Run a $100 Billion Business

Summary

• Databricks escaped the classic open-source trap by recognizing that Apache Spark’s popularity was not a business model. Downloads and Spark Summit proved demand, but customers could still ask, “Why can’t I just download the open source version?” After PLG stalled at roughly $3 million ARR, the company added proprietary differentiation, hired experienced commercial leadership and went all-in on enterprise sales.
• Ali Ghodsi’s operating system is aggressive self-education combined with direct access to ground truth. He advises founders to admit they are “zero,” interview the best practitioners, compare conflicting playbooks and hire people good enough to teach them. He and Ben Horowitz argue that CEOs must “fly low and fast,” because actual knowledge resides with customers and individual contributors—not neatly inside the executive staff or org chart.
• High intensity scales through leadership, organizational design and visible impact—not hours alone. Ali sets the tone by working nights and weekends and vets candidates through backchannel references, but explicitly rejects burnout as the objective. Ben’s sharper point: no motivational speech can overcome a “three-legged race” of dependencies where employees know extra effort will not change the outcome.
• The Microsoft partnership worked because a genuine product-for-distribution trade was reinforced by a painful commitment. Microsoft had a portfolio gap and roughly 60,000 sellers; Databricks had the product but would sacrifice “12 months of our roadmap” to integrate it. The team demanded a large pre-commit so someone inside Microsoft would care if it failed, then survived a deal that “died” around 10 times.
• Databricks evaluates acquisitions in the reverse order of conventional corporate development: people, product integration, then financials. Ali wants founders who will build for five years and code bases that can become one product; buying revenue first may create two years of growth but ultimately leaves “a bag of crap that doesn’t work together.” Ben argues the hidden casualty is sales efficiency, because every separate architecture creates more specialists, support systems and customer friction.
• A pivotal decision was rejecting an acquisition offer six times Databricks’ prior valuation. Ben acknowledged that selling would pay a16z handsomely, then framed the real cost as spending a lifetime wondering whether Ali had abandoned his “one shot.” The same ambition turned the seemingly absurd suggestion to add Databricks to FANG into a P95 engineering-compensation model—and preceded Ben’s 2019 prediction, at a $6 billion valuation, that the company would reach $100 billion.
• Even at Databricks’ scale, the AI talent market cannot be treated as a pure bidding contest. Ali believes many reported $100 million offers are exaggerated by CEOs with incentives to reset compensation expectations; his counterweight is mentorship, learning and real ownership. He contrasts smaller startups with Databricks’ scale, citing a $100 billion valuation and 10,000 employees. He also stresses luck: starting in 2012 might have been too early, 2014 too late, while the actual 2013 start barely survived a frozen Series C market—“there’s a lot of randomness.”

Deep dive

Not yet available upstream; scheduled sync will retry.