a16z Podcast: Embracing Sales

Episode Summary

Executive Summary: GitHub’s co-founder/CEO and Andreessen Horowitz’s Peter Levine discuss why GitHub eventually built a sales organization despite early resistance. The core thesis: sales should be a customer-education and relationship function, not a manipulative one, and is especially necessary once enterprise users need help championing a product internally. The conversation focuses on preserving culture, aligning sales with engineering, and using sales to expand GitHub’s reach without losing its product-first ethos.

Main Topics: Why GitHub resisted sales initially (Priority: 5/5): Chris explains that GitHub’s early aversion to sales came from a stereotype of the salesperson as pushy, dishonest, and culture-corrupting, which conflicted with GitHub’s product-led, community-oriented identity. Sales as customer education and relationship-building (Priority: 5/5): Peter reframes sales as teaching customers, answering questions, and helping them reach their own conclusions, while Chris emphasizes long-term relationships with enterprise buyers and users. Customer demand as the trigger for a sales team (Priority: 5/5): GitHub’s users began asking for help selling the product internally to managers and CIOs, revealing a gap between developer enthusiasm and organizational adoption that product marketing alone could not solve. Preserving culture while scaling go-to-market (Priority: 5/5): Both speakers stress hiring, onboarding, and ongoing integration as the mechanisms that keep sales aligned with GitHub’s values and prevent an 'us versus them' dynamic. Engineering and sales collaboration through tools (Priority: 4/5): GitHub uses its own product and internal communication channels to keep engineering, product, and sales connected, including shared repositories, issue threads, chat, and internal blogs. When a company needs sales (Priority: 4/5): The discussion concludes that sales is not universally required, but enterprise software companies usually need it once customers expect human interaction and internal coordination support.

Key Arguments: Early reluctance to sales is common in engineering-led companies because 'sales' is often associated with manipulation rather than customer help. Peter Levine’s engineering-to-sales path illustrates that effective salespeople can function as teachers and product translators rather than quota-only sellers. GitHub’s viral product adoption worked well initially, but enterprise expansion created a new need: helping internal champions persuade decision-makers. A sales team can increase revenue by raising the value per customer, not merely by pushing more product. Culture risk is managed best through hiring for shared values and onboarding that teaches new sales hires GitHub’s norms and mission. The biggest organizational failure mode is an 'us versus them' split between engineering and sales; leadership must enforce one team, one objective, one customer. GitHub’s own tools and workflows help unify departments and enable direct feedback loops from customers to product and engineering. Enterprise customers often expect a human point of contact, so sales becomes part of the standard go-to-market model for enterprise software.

Data Points: Time before GitHub built sales: 6 years - Chris says GitHub went roughly six years before adding a sales team. Internal rollout scale: 10,000 developers - Chris uses this as an example of the size of enterprise deployments sales may help manage. Target audience expansion: Every developer in the entire world - Chris describes the company’s broader ambition beyond startups and open source users.

Pivotal Quotes: "The simple answer is our customers told us to." — Chris Wanstroth: Explaining why GitHub eventually built a sales organization. "I rationalized my life as being a teacher of our product as opposed to a seller of our product." — Peter Levine: Describing his philosophy of sales as education rather than extraction. "One team, one objective, one customer." — Peter Levine: Summarizing the cultural principle needed to align engineering and sales.

Implications: For product-led companies, sales is not a betrayal of culture if it is built as education, trust, and customer advocacy. As products move into enterprise environments, human help becomes a competitive advantage and a scaling necessity.