I gravitate to origin stories where product strategy meets real human pain. Tomer London is the co-founder and Chief Product Officer at Gusto, the payroll and people platform used by over 400,000 businesses. He grew up helping run his dad’s clothing store in Israel — an experience that sparked his mission to build better tools for small business owners. After moving to the US for a PhD at Stanford, he met his co-founders and started Gusto. That founding context matters: it rooted the company in empathy for SMBs and created the “burning problem” lens that still defines their roadmap.
What stands out most to me is the insistence on “emotional urgency.” In product discovery, polite feedback is noise; urgency is signal. I use a simple heuristic—the tug-of-war test for product-market fit: are customers fighting to pull the product into their workflow today, or gently praising it while doing nothing? Why founders should actively seek rejection is the companion lesson. Rejection exposes the edges of the problem, clarifies the job-to-be-done, and forces focus. When prospects say no with conviction, they’re actually giving you a prioritized backlog.
Gusto’s scrappy customer research: cold calling from a walk-in closet is the type of hustle I expect from great product teams. It’s a reminder that qualitative discovery doesn’t require a lab—just proximity to customers. I’ve seen forward-deployed conversations beat large-scale surveys every time, especially in SMB markets where workflows are idiosyncratic and switching costs are emotional as much as economic. Those early calls transformed abstract hypotheses into concrete user journeys, error states, and trust moments.
Reinventing payroll without any prior experience can be an advantage when you pair first-principles thinking with domain humility. The discipline is to ship with credibility from day one. “It’s not an MVP, it’s something that wows people” captures this perfectly. For regulated, high-stakes workflows like payroll and taxes, a minimum lovable product must feel complete at the edges that matter—accuracy, compliance, and support—while still being opinionated and simple. Competing with incumbents like ADP, Intuit, and Paychex required that Gusto’s default experience be both safer and easier.
Hiring for humility, not just talent is another keystone. In complex categories, humility accelerates learning loops, reduces coordination drag, and keeps teams close to customers. I’ve applied a similar bar in co-founder and executive selection: values alignment over resume prestige. The weekly co-founder ritual that built trust is a practice I recommend—structured, recurring time to surface concerns, decide faster, and avoid silent drift. Teams that maintain this cadence sustain velocity even as they scale.
Betting on SMBs – and ignoring investor advice is a familiar crossroads. Serving SMBs vs. startups demands different GTM mechanics, pricing psychology, and onboarding pathways. Gusto’s “start small” GTM playbook—narrow ICP, land with a high-urgency job, then earn the right to expand—de-risks complexity while proving unit economics. The shift from payroll to a multi-product platform only works when the initial wedge earns trust. That’s how switching costs became Gusto’s moat: not through lock-in tactics, but by becoming the source of truth for money-in, money-out, and people ops.
I also appreciate the candor around The two lucky breaks that gave Gusto an edge. Timing, regulatory tailwinds, or partner enablement often look like luck from the outside and like relentless preparation on the inside. Programs like Y Combinator can sharpen that preparation, but the compounding advantage still comes from daily execution—shipping, learning, and iterating. Along the way, names like Wells Fargo matter because financial infrastructure choices affect reliability and trust, which in turn affect retention.
A throughline here is craftsmanship anchored in real-world retail empathy. What Tomer learned about customers from his dad’s clothing store mirrors what I’ve seen across SMB product-market fit lessons: respect the owner’s time, remove ambiguity, and solve the whole problem, not just the shiny part. Building products customers actually love is the result of pairing opinionated design with verifiable outcomes—on-time payroll, fewer errors, less admin stress, and clearer cash flow.
If you’re a product creator tackling a workflow as critical as payroll, take these as your operating principles: measure emotional urgency, welcome rejection, over-index on discovery, hire for humility, and aim for wow, not just MVP. Whether you’re up against ADP, Intuit, Paychex, or building a new wedge entirely, this is a repeatable path from wedge to platform. For inspiration that shaped many builders in our field, revisit Steve Jobs’ “Secrets to Life” clip and Steve Jobs’ Stanford Commencement Speech—both reminders to question defaults and start from first principles.
Finally, a note on leadership. Product management leadership isn’t about grand roadmaps; it’s about creating the conditions for truth to surface quickly—through customer conversations, team rituals, and clear success metrics. Do that well, and like Gusto, you’ll earn the right to expand your product surface area without losing the trust that made customers choose you in the first place.
What concept is essential in high-stakes workflows?
Emotional urgency is the signal in product discovery. A minimum lovable product must feel complete at the edges that matter—accuracy, compliance, and support—while staying simple and opinionated.
What is the tug-of-war test?
It’s a heuristic to determine product-market fit: are customers fighting to pull the product into their workflow today, or are they only praising it and doing nothing? The pull indicates a strong signal; if they don’t pull, the problem needs reevaluation.
How did Gusto conduct early customer research?
Gusto conducted scrappy customer research, including cold calling from a walk-in closet. Proximity to customers made qualitative discovery more effective than large-scale surveys, and those early conversations shaped user journeys, error states, and trust moments.
Why is humility important in building Gusto's approach?
Humility accelerates learning loops and reduces coordination drag, keeping teams close to customers. The weekly co-founder ritual builds trust, and values alignment can matter more than resumes.
What is the GTM approach Gusto used?
Start small GTM narrows the ICP, lands with a high-urgency job, and then earns the right to expand. This approach de-risks complexity while proving unit economics.
How does Gusto's initial wedge relate to its moat?
The initial wedge earns trust, which allows switching costs to become the moat. Gusto becomes the source of truth for money-in, money-out, and people ops.
Leave a Reply