evelin.

Customer interview fundamentals for first time SaaS founders

Learn how to run simple, honest customer interviews that reveal real problems, workflows and what people might actually pay for.

What customer interviews are really for

A customer interview is a structured conversation that helps you see the world through your customer’s eyes. You explore their current workflow, pains and trade offs, instead of selling your idea or demo. The goal is to understand three things: how they work today, what feels painful or risky, and what outcomes they care about. When done well, interviews replace guesses with real language and concrete stories from the field. This signals which problems are worth solving and which are just minor annoyances. Think of each interview as a way to sharpen your problem definition, not as a chance to pitch your product vision.

What good interviews reveal
🧩
Real workflows
Step by step, in their words
🔥
Pain points
Moments of stress or waste
🎯
Desired outcomes
Results they truly care about
💸
Value hints
Where time or money is lost

How to pick the right people to interview

Interview people who clearly feel the problem you want to explore, not just anyone who fits a broad demographic. Look for signs of urgency such as spending money on a workaround, hacking together spreadsheets or complaining often about the issue. Start with 5 to 10 people in a tight niche, for example clinic owners with under 20 staff, or Shopify store owners who ship physical goods. It is better to go deep in one slice than to mix very different profiles. Warm introductions usually create more honest conversations than cold outreach, so ask friends, colleagues or online communities for connections.

Selecting interview candidates
  1. 🎯1
    Define slice
    Narrow niche and role
  2. 🔥2
    Spot urgency
    Look for clear pain signs
  3. 🤝3
    Use warm intros
    Ask networks and groups
  4. 📅4
    Schedule 5–10
    Aim for short calls first

Designing simple questions that uncover truth

Good interview questions stay close to real events in the recent past. Ask what they did last week, how they made a decision and what they tried before. Avoid asking what they would do in the future, people overpromise there. Use open questions that start with what, how or tell me about, and then stay quiet and listen. Aim for a loose script with 5 to 8 core questions, not a long survey. Start broad with their role and goals, then zoom into a specific workflow, then explore pain, frequency, existing tools and budget. Read your questions aloud and remove anything that sounds like a pitch.

Helpful vs misleading questions
Helpful questions
  • •When did this last happen
  • •Walk me through your process
  • •What have you tried so far
  • •How do you decide on tools
Misleading questions
  • ✓Would you use a tool that
  • ✓Do you like this idea
  • ✓Would you pay for this
  • ✓Is this a big problem
VS

Running the conversation without bias or pitching

At the start, thank them, share why you are curious about their work and set expectations for a short, honest chat. Make it clear that you are not selling anything on this call. During the interview, keep your camera on, maintain friendly eye contact and take light notes. Ask one question at a time. Reflect back what you heard in your own words and check if you understood correctly. If they mention a pain, dig deeper with questions like what makes that hard, how often does this happen and what happens if you do nothing. Keep your idea to yourself until the last few minutes, or skip it entirely in early rounds.

Flow of a strong interview
  1. 🧭1
    Open and align
    Purpose, time, no pitch
  2. 🔍2
    Explore context
    Role, goals, workflow
  3. 🩹3
    Dig into pain
    Frequency and impact
  4. ✅4
    Clarify & close
    Summarize, ask permission to follow up

Spotting willingness to pay without leading questions

Signals of willingness to pay usually show up before you ever say price. Look for signs like spending money on a workaround, paying staff many hours to fight the problem or losing deals due to this issue. Ask neutral questions such as what does this cost you today, how much time do you or your team spend here and have you paid for tools or consultants to help. When you do talk about pricing, anchor it in their costs and value, not your effort. If they quickly propose budget ranges, timeline or approval steps, you might be close to a monetizable problem.

Strength of payment signals
Complaints only25/100
Time wasted55/100
Money spent on hacks80/100
Lost revenue95/100

Common mistakes and how to avoid them

Many founders treat interviews as a chance to validate their idea instead of exploring the customer reality. They talk most of the time, ask leading questions and walk away with comforting but empty compliments. Another trap is mixing very different customer types in one batch of interviews, which blurs patterns. To avoid these mistakes, measure yourself on talk time, aim to speak less than 30 percent. Record or take detailed notes, then review them later for exact quotes and repeated themes. After every 3 to 5 interviews, pause, cluster what you heard and decide if you must refine your niche or questions.

Learning loop from interviews
📋Plan
🎧Interview
🧠Review
🛠️✂️Adjust

✂️ Stop after a few rounds if no strong pains emerge

Real-world examples

  • • You run an online yoga platform and talk to 8 freelance instructors about how they currently schedule classes, cancel sessions and get paid, to see if payment or scheduling is the real pain.
  • • You plan a SaaS for small clinics, so you interview 6 clinic managers about how they manage no show appointments, where delays happen and what it costs them each month.
  • • You want to build reporting tools for Shopify sellers, so you ask 7 store owners to share their exact weekly reporting routine and which numbers they already pay tools to track.

Useful links

  • Y Combinator — Talks and essays on startup idea validation and customer conversations
  • Intercom — Articles on customer research and product discovery

Keep learning

Related courses

More programs on evelin that fit this path. Each one adapts to you after a two minute quiz.

Guides from related courses

All courses on evelin →

Turn reading into real progress

A short quiz builds your personal learning path for How to Build a SaaS. Lessons adapt to you from day one.

Start the quiz

Created with AI assistance and reviewed before publishing.