Eric Migicovsky

Eric Migicovsky explains why founders should keep direct contact with users and how to conduct interviews that produce useful evidence. He recommends asking about specific past problems, listening more than talking, and avoiding pitches, hypotheticals, and vague compliments. He outlines five interview questions and practical ways to find early users, then offers a framework for evaluating potential first customers by problem cost, frequency, and budget. For teams iterating toward product-market fit, he discusses measuring user attachment and using interviews to guide product decisions.

Eric Migicovsky shares lessons from moving Pebble from Waterloo to Silicon Valley after joining YC in 2011. He argues that moving makes sense when your early customers are there, when you need access to the region’s dense startup network, or when the surrounding pace helps your company move faster. Silicon Valley’s high costs and recruiting challenges can outweigh those benefits, especially if your customers or a strong hiring or research advantage are elsewhere. For founders who stay elsewhere but plan to build a high-growth company, he recommends spending time in the Bay Area to build a network.

Eric Migicovsky explains how startup founders can build a useful network of advisors and mentors. He recommends finding some advisors who are a few years ahead in the same domain, since their experience is recent enough to offer practical examples and introductions. A broader group can provide strategic feedback, but founders should combine advice from multiple people and make their own decisions. He also describes typical advisor equity grants and suggests setting a regular cadence with advisors who receive equity.

Eric Migicovsky explains what to look for when hiring at an early-stage startup. He recommends hiring people who can adapt as the company changes direction, and prioritizing trust so teammates can work independently. He also values people with a multidisciplinary skill set, since early hires often need to handle work across several areas. His three priorities are trust, creative flexibility, and multidisciplinary skills.

Eric Migicovsky uses Pebble’s history to explain how hardware startups can learn quickly before committing to expensive production. He recommends small early tests, close customer contact, frugality, and flexible teams, while treating crowdfunding as either an early validation tool or a later sales channel. For hard tech, he emphasizes shortening iteration cycles, demonstrating customer demand alongside technical progress, and choosing a business model that fits the product. He also discusses practical ways to reduce risk from custom hardware, inventory, hiring, and fundraising.