Recall Sessions: Tomer London on Building Gusto from ZenPayroll to 400,000 Customers

What It Covers

Tomer London, cofounder and CPO of Gusto, traces the company's growth from ZenPayroll's first 100 beta customers in 2012 to 400,000 businesses served today, covering early customer acquisition tactics, pricing mistakes, product focus principles, hiring philosophy, and AI's current role in transforming small business operations.

Key Questions Answered

• •Early Customer Acquisition: Target a hyper-narrow initial market to validate product-market fit before expanding. Gusto's first version served only California-based companies with under five salaried employees that had never run payroll — deliberately shrinking the addressable market to achieve excellence in one slice before scaling geographically and by feature set.
• •Pricing as Market Signal: Charging $2 per employee per month — roughly one-tenth of competitors — sent an unintended message of low value and raised questions about company viability. London's standing advice to founders is to raise prices, not primarily to optimize revenue, but to signal product quality and build market confidence in the solution.
• •Kill Product Criteria: Use two simultaneous signals — quantitative conversion data and qualitative customer sentiment — to decide whether to kill a product. Only discontinue when both metrics are clearly negative. If numbers are strong but satisfaction is low, improve the product. If satisfaction is high but adoption is low, fix onboarding and go-to-market.
• •SMB Go-to-Market Reality: Building software for businesses under 50 employees is "startup in hard mode." Gusto's first 1,000 customers came entirely through word-of-mouth, not paid ads or outbound sales. This only works when the problem is acutely painful — London's benchmark is customers actively cursing their current solution and expressing urgency to replace it immediately.
• •AI Productivity Multiplier: Engineers using tools like Claude Code with multiple simultaneous agents running are achieving 10–20x productivity gains on greenfield projects. London personally returned to coding after years away, shipping a full internal dashboard in roughly 24 hours — work he estimates would have previously required weeks from a professional engineering team.