How to use customer interviews to build better products

Executive overview

Most founders know they should talk to customers but find it overwhelming, time-consuming, or irrelevant to their stage. Deploy Empathy is a practical guide to customer interviews written by a bootstrapped SaaS founder for indie makers — not enterprise UX teams.

The core insight: you don't need a research budget or dedicated time blocks. Interviews integrate into what you're already doing, starting with feature requests.

Listening to customers — and letting that guide decisions — is the single biggest lever behind GeoCodeo reaching seven figures.

About the book and its audience

• Most user research books assume teams, budgets, and travel — alienating solo founders before they start
• The Mom Test covers early-stage validation; Deploy Empathy covers the full lifecycle: churn, activation, retention, feature decisions
• Written by a practitioner, not a consultant — examples match indie SaaS reality
• Structured for skimming: theory is minimal and woven in; cheat sheets at the back let you start immediately
• Influenced heavily by jobs to be done (Clayton Christensen, Bob Moesta) — focuses on what people are trying to accomplish, not what they say they want

The title and framing

• "Deploy" is a deliberate wink at developers — empathy is the thing being shipped, embedded in the product
• Empathy here means entering the other person's world and treating their decisions as valid from their perspective
• The book itself models empathy for the reader — directly acknowledging fears so founders don't spiral into anxiety before they start

Feature requests as customer research

• Feature requests are a built-in recruiting pipeline — customers come to you
• Don't immediately ask "can we build this?" — ask what's leading them to want it and what they're currently using instead
• If they're patching four tools together, there's real pain and money there; if it's a once-a-year thought, probably not
• Useful follow-up questions: "Can you walk me through the context?" / "What do you currently use for this?" / "Do you pay for those tools?"
• A phone call can follow — but the feature request itself is often enough to get the context you need

Getting to the real problem

• Customers express problems as solutions — a checkbox request often hides a workflow problem
• The job of the interview is to find the problem beneath the proposed solution
• Patterns across multiple similar requests signal a shared underlying problem worth solving structurally
• Example: repeated "if/then" requests in a campaign builder eventually revealed the need for a visual workflow builder — not a checkbox

Learning to interview

• Interviewing is a learned skill, not a natural one — mirroring, leaving silence, follow-up phrasing all require practice
• Michele learned under a PhD researcher and design leader, sitting in on interviews for months before leading them
• The book teaches these techniques in a way that acknowledges anxiety rather than dismissing it
• You don't need to stop building for a month — integrate interviews into existing workflows