user interview guide for solopreneurs: templates and scripts (2026)
user interviews are the highest-leverage research method available to a solopreneur. five 30-minute conversations with the right people will teach you more about your market, your product, and your buyers than any survey, analytics dive, or competitor scrape. they will also produce the actual customer language you can drop directly into your headlines, your sales pages, and your product copy.
most solopreneurs never run them. and most who try run them poorly: they pitch instead of listen, they ask leading questions, they take notes in a way that loses the best quotes, and they end up with a vague sense of what was said but no clear takeaways.
this guide gives you the framework I have refined over years of running interviews for indie products and client work. you will get two complete scripts (one for problem discovery, one for product validation), a checklist for finding subjects, the rules for running the conversation without biasing it, and a synthesis workflow that turns 5 calls into a one-page brief in under 2 hours. by the end you will be able to run your first 5 interviews this week.
why interviews beat almost everything else
surveys produce shallow data at scale. analytics produce deep data on past behavior. interviews produce something neither can: rich context, actual language, and emotional signal.
a 30-minute user interview is the cheapest, fastest way to learn what your customers actually think. five interviews catch about 80 percent of major patterns in a defined audience. solopreneurs in 2026 should run 5 to 8 interviews before any product launch, pricing change, or major content pivot. the most expensive research mistake is skipping interviews and going straight to surveys.
the rest of this guide is the playbook for getting that signal cleanly.
when to run interviews vs other methods
| your question | use interviews? |
|---|---|
| why do customers buy what they buy? | yes, top choice |
| what should I build next? | yes, paired with analytics |
| what should I price this at? | qualitative first, then survey |
| what features are most used? | no, use analytics |
| what is the market size? | no, use desk research |
| would they pay $X? | partly, then validate with WTP survey |
interviews answer “why” and “how” questions best. they are not the right tool for sizing or comparing options at scale. for that combination, see qualitative vs quantitative research: which one when.
how to find subjects
the biggest blocker for new interviewers is finding people. here are the channels that work for solopreneurs, ranked by how well they convert.
channel 1: your existing customers (highest yield)
if you have any paying customers, even 5, ask them. an email like:
“I am working on improving [product] and would love 30 minutes to ask you about how you currently use it and what is missing. no pitch, no upsell, just learning. coffee on me (in the form of a $20 Amazon card).”
response rate from happy customers is typically 30 to 50 percent. compensation helps but is not always necessary.
channel 2: your email list (medium yield)
send to 100 to 200 people and ask for 30-minute calls. compensation matters more here.
channel 3: LinkedIn outreach (medium yield)
filter by your target persona. send personalized messages explaining who you are, what you are studying, and what they get out of the conversation (compensation or first access). expect 5 to 10 percent positive response rate.
channel 4: Reddit and niche communities (variable yield)
post in relevant subreddits asking for 30-minute calls. follow community rules. transparency about what you are doing matters.
channel 5: paid recruiting (when you cannot find them)
services like UserInterviews.com or Respondent.io let you specify the persona and pay for matched interviews. cost is typically $50 to $150 per interview. fast but expensive.
the two scripts
I keep two interview scripts as templates. one for problem discovery (when you do not yet have a product to test), one for product validation (when you have something to react to).
script 1: the problem discovery interview (30 minutes)
use this when you are exploring whether a problem is worth solving. no product needed.
opening (2 minutes)
“thanks for taking the time. quick context: I am [your name], working on [vague description of area]. this is a learning conversation, not a pitch. there is no product I am trying to sell you. I just want to understand how you currently handle [problem area]. I will record this for my own notes if that is okay with you. is now still a good time?”
warm-up (3 minutes)
- “tell me a bit about your role and what you do day-to-day.”
- “where does [problem area] fit in?”
the core questions (20 minutes, mostly listening)
these are the seven questions I rotate through, depending on where the conversation goes:
- “tell me about the last time you dealt with [the problem]. walk me through what happened.”
- “what did you do to solve it? what tools or workarounds did you use?”
- “how often does this happen? when was the most recent time?”
- “how much time or money does this cost you?”
- “what would make it easier?”
- “what have you tried that did not work? why didn’t it?”
- “if you could wave a magic wand and have anything happen, what would happen?”
the first question is the most important. you want a specific story, not a generality. if they answer in generalities, redirect: “can you give me a specific example, like the last time this happened?”
closing (5 minutes)
- “before we wrap up, is there anything I should have asked you that I did not?”
- “is there someone else you think I should talk to about this?”
- thank them, confirm any compensation, hang up.
script 2: the product validation interview (30 minutes)
use this when you have a product, prototype, or landing page and want to test reactions.
opening (2 minutes)
same as script 1, but add: “I will share something I am working on partway through and ask for your honest reactions, including the negative ones.”
warm-up (3 minutes)
- “tell me about your role and how you currently handle [problem area].”
- “what tools or processes do you use today?”
show the artifact (5 minutes)
share your screen with the landing page, prototype, or demo. give them about 60 seconds to read or click around.
reaction questions (15 minutes)
- “what do you think this does, just from looking at it?”
- “who do you think this is for?”
- “what is your gut reaction? (the goal is honest, even if it is bad)”
- “what is unclear or confusing?”
- “if this existed and worked perfectly, would you use it? when?”
- “what would stop you from using it?”
- “what would you expect to pay for it?”
closing (5 minutes)
same as script 1.
the rules of running the conversation
these rules are what separate interviews that produce signal from interviews that produce vapor.
rule 1: shut up
your job is to listen. when in doubt, stay quiet. counts: you should be talking less than 20 percent of the time.
rule 2: do not pitch
the second the interviewee senses you want them to like something, the data is contaminated. resist the urge to defend, explain, or sell.
rule 3: ask for stories, not opinions
opinions are cheap. stories are expensive. “what do you think of X” gets you opinions. “tell me about the last time you did X” gets you stories.
rule 4: probe with the five whys
when someone gives a generic answer, ask “why” or “tell me more about that”. do this up to five times. specifics live below the surface.
rule 5: do not lead
leading: “would you say the onboarding is confusing?”
not leading: “walk me through your first day with the tool.”
rule 6: capture verbatim
write down the exact words people use, not your paraphrase. the verbatim quotes are gold. paraphrases lose the power.
rule 7: be willing to hear bad news
if you only hear what you want to hear, you wasted the call. ask “what would stop you” and listen.
sample size and stop conditions
5 to 8 interviews per audience segment is the sweet spot for most solopreneur projects. by interview 5 you typically hear the same major themes repeating. by interview 8 you are confirming patterns rather than discovering new ones.
| number of interviews | what you typically learn |
|---|---|
| 1 to 3 | initial impressions, lots of variance |
| 4 to 5 | major themes start repeating |
| 6 to 8 | confirmation of patterns, edge cases |
| 9 to 12 | diminishing returns, segment splits |
| 13 plus | only useful if comparing 2+ segments |
stop when you hear the same major theme from 3 different interviewees. that is the threshold I use.
the synthesis workflow
5 interviews produce roughly 10 hours of audio (or 100+ pages of transcripts if you transcribe). raw notes are not insight. the synthesis is the work that turns raw material into a decision.
step 1: transcribe each interview (I use Otter.ai or Descript)
step 2: tag every quote in the transcript by theme. start with broad themes and let new ones emerge.
step 3: cluster quotes by theme into a single document.
step 4: count themes. how many of 5 interviewees mentioned theme X?
step 5: write a one-page brief: “5 interviewees said X. 3 said Y. 2 said Z. the strongest pattern was [X]. the most surprising was [Z]. the implication for our decision is [conclusion].”
this synthesis takes about 2 hours for 5 interviews. for the full workflow, see research synthesis methods for fast decisions.
tools I use
| tool | purpose | cost |
|---|---|---|
| Calendly | scheduling | free tier |
| Zoom or Google Meet | video calls | free tier |
| Otter.ai or Descript | transcription | free tier or $10/month |
| Notion or Google Docs | note-taking and synthesis | free |
| AI tools for tagging | thematic analysis at scale | varies |
for analyzing transcripts at scale with AI, see how to use AI to analyze survey responses, which covers the same workflow applied to interview transcripts.
handling specific interview situations
over time you will run into recurring situations that need their own playbook.
the over-explainer interviewee
some people answer a question with a 5-minute monologue that drifts off-topic. gently redirect: “that is helpful context, can I ask you about [specific part]?”. do not let one talkative interviewee burn 25 of your 30 minutes.
the silent interviewee
some people give one-sentence answers to every question. probe with “why” and “tell me more”. if it persists, the interview will likely produce thin data; finish politely and add another interview to compensate.
the pitch hijacker
some interviewees, especially other founders, will start pitching you on what you should build. politely redirect: “I appreciate the suggestions, can I take you back to your own experience for a minute?”.
the friend giving you “support”
friends and family are often the worst interviewees because they want to encourage you. they will say “yes I would totally pay for that” because they like you. be wary. either avoid friend interviews or explicitly tell them: “I am here to find weaknesses, please be honest, your support has already been registered.”
the angry customer
sometimes you get an interview with someone who is frustrated. let them vent for 5 minutes before steering to your questions. their anger contains real signal about gaps in your product.
screen-share vs no screen-share
for problem discovery interviews, no screen-share. you want them describing their situation, not showing you their tools. screen-sharing tends to focus on the tool rather than the underlying problem.
for product validation interviews, screen-share is essential. you want to see them react to a real artifact. think-aloud while they navigate is gold.
taking notes during the call
three approaches:
option A: write everything: tedious but highest fidelity. only works if you can type fast.
option B: write key quotes only: faster, but you will lose context by the time you synthesize.
option C: record + transcribe + take only structural notes during the call: my preferred method. let the recording capture words, take notes only on emerging themes (“seems frustrated about X”, “pricing comes up again”). transcripts handle the verbatim later.
option C is best for most solopreneurs. tools like Otter.ai, Descript, or Fathom Notetaker auto-transcribe and produce searchable archives.
ethical considerations
a few rules I follow:
- always tell the interviewee how I will use the recording
- always offer the option to be anonymized
- never share verbatim quotes outside the project without explicit permission
- if compensation was promised, send it within 24 hours
- if I learn something that should change the interviewee’s behavior (e.g., they are about to make a decision based on bad info), I tell them, even if it changes the interview dynamic
these rules cost almost nothing and build a reputation that makes future recruiting easier.
connecting interviews to your research design
interviews are one method inside a larger research design. use them inside the lean experiment, the diagnostic audit, or the JTBD framework from research design for small business: 5 frameworks. plan them with how to write a research brief. pair them with surveys built using survey question writing patterns.
for the broader free-research toolkit, see how to do market research for free and how to do competitor research for free.
conclusion
user interviews are the most underutilized research method in the solopreneur toolkit. they cost almost nothing, take about 5 hours of total time for a full round, and produce richer signal than any other research method available at this scale.
the trick is not technical. interviews are not hard to run mechanically. they are hard to run well because they require the discipline to listen instead of pitch, to ask for stories instead of opinions, and to hear bad news without flinching.
start this week. pick the most pressing question on your list. find 5 people who can answer it. send the email. run the calls using one of the two scripts. take notes verbatim. synthesize in under 2 hours.
the cumulative effect of running 5 interviews per quarter is enormous. you will start seeing your customers in a different resolution. your copy will sound like their voices. your product decisions will rest on real evidence instead of guesses. the gap between solopreneurs who interview and solopreneurs who do not is the largest research gap I see, and closing it is one of the highest-leverage moves available.
book your first interview today. you will have collected better signal in a week than most of your competitors collect in a year.