Podcast
a16z Podcast | Embracing Sales
- GitHub's leadership initially resisted building a sales organization due to a cultural perception of salespeople as "dishonest pushers" and a belief that the product should sell itself through viral, community-driven adoption.
- The decision to establish a sales team was driven by direct customer feedback, specifically from individual developers within large enterprises who lacked the internal authority to deploy GitHub and requested assistance selling the tool to their CIOs and management.
- Peter Levine's background as a former engineer who transitioned to sales framed the function as educational and advisory rather than transactional, focusing on helping customers understand product value rather than "extracting the last dollar."
- Chris Wanstroth noted that the resistance to sales was most pronounced because the company had achieved significant early success and product-market fit without a dedicated sales force, creating a natural tendency to rely solely on engineering growth.
- GitHub's sales strategy prioritizes hiring individuals who value relationships, understand the open-source community, and can act as "teachers" to enterprise decision-makers rather than traditional closers.
- To prevent cultural friction between engineering and sales, GitHub implemented a rigorous onboarding process where new hires attend internal talks, Q&As, and sessions with "super fans" to learn the company's specific values and communication styles.
- The company utilizes a unified internal infrastructure to integrate functions, including a public GitHub repository named "GitHub Sales" where engineering, design, and sales teams collaborate on issues and feedback.
- GitHub maintains cultural cohesion by ensuring all internal updates, whether from engineering or sales, are communicated through the same channels (e.g., blogs, chat) and shared with the entire organization equally.
- Chris Wanstroth confirmed that while a sales team was not necessary for the first six years of the company, it is now deemed a "good decision" and a requirement to transition from a focus on startups to capturing the global enterprise developer market.
- Peter Levine stated that enterprise software companies generally must build a customer-facing sales organization eventually, as large organizations expect direct human interaction as part of the purchasing process, whereas consumer or small-business models may not require one.
- A current strategic focus for the organization is refining the feedback loop between the growing sales team and product/engineering groups to prioritize customer requests for feature development and product changes.
- The company aims to balance its relationship-focused sales model with its existing commitments to customer support, user testing, and product-led growth rather than viewing sales and product development as a zero-sum dichotomy.
- The "Iron Man" style $30 watch worn by Peter Levine was cited as a symbolic rejection of the stereotypical "Rolex" image of a high-pressure salesperson, reinforcing the culture of humility and engineering-led values within the sales team.