Run a Low-Cost Discovery Interview Before Building an App

Building an app is expensive and time-consuming. Too many early teams skip the simplest validation: talking to real potential users with non-leading questions, then interpreting a small sample responsibly. This guide gives a concrete, low-cost process you can run in a week, a worked hypothetical example, a reusable interview checklist and template, and realistic limitations so you can act without overconfidence. This is practical editorial guidance, not academic research.

Define the distinct reader problem

You have a feature idea (or an app concept) and want to know whether people will use it before you spend months and thousands of dollars building it. You need quick, low-cost interviews that uncover real jobs-to-be-done, avoid leading participants, and let you decide next steps from a sample of 10–20 conversations.

Why low-cost interviews work

Short, structured interviews are cheaper than prototypes and faster than surveys for exploring motivations and unmet needs. They work when you focus on open questions, observe behaviors, and use an explicit decision rule for what the small sample tells you. The goal is directional clarity—enough to choose build, iterate, or stop—not statistical proof.

Step-by-step process (actionable and realistic)

Clarify the single testable assumption. Example: “People who work in shared offices need a simple way to schedule quiet time and will prefer an app over email.”
Recruit 10–15 relevant people. Use your network, local coworking groups, Facebook groups, or paid ads with a $50 budget. Screen with one qualifying question: “Have you tried to schedule quiet time in a shared office in the past month?” Filter for yes/no.
Prepare a non-leading script (use the template below). Keep interviews to 20–30 minutes, remote or in-person.
Run interviews in pairs when possible: one interviewer, one note-taker who timestamps quotes and behaviors.
Synthesize with a simple rubric: count explicit pains, observed behaviors, and stated willingness to try a solution. Use a decision rule: if 6+ of 12 show clear pain and willingness, proceed to a low-fidelity prototype test; if 3 or fewer, stop or pivot.
Plan one cheap follow-up test (e.g., a clickable prototype, landing page, or calendar integration) based on the top three unmet needs.

Non-leading question set (use this template)

Start: “Tell me about the last time you tried to schedule quiet time at work.”

What happened? (Listen, don’t prompt)
What other ways did you try? (Probe for workarounds)
How did that feel? (emotional language, costs—time, annoyance)
What was the outcome? (success/failure, who was involved)
If you had a tool that solved this, what would success look like? (no product suggestions)
Have you paid or considered paying for a tool to solve this? If yes, how much would you consider reasonable? (get numbers)

Hypothetical worked example (detailed)

Assumption: Coworking members need a simple way to book quiet blocks and would prefer an app.

Recruitment: Post in two local coworking Facebook groups and message contacts; recruit 13 people in five days. Offer a $10 gift card per participant (cost: $130).

Interviews: 12 interviews, 20 minutes each (4 hours of interviewing total; 3 hours of prep and synthesis). Note-taker records exact quotes and timestamps (e.g., “I just put a sticky on my monitor” — participant 5, 04:12).

Findings (examples):

10/12 described the problem: unexpected noise during deep work.
7/12 used ad-hoc workarounds: sticky notes, calendar events, or asking a manager.
4/12 had previously tried scheduling tools but found them too heavyweight.
6/12 said they would try a simple app; 3 of those named a price under $3/month, 2 would only use a free tool.

Decision using the rubric: 6 of 12 show both pain and a willingness to try — proceed to a simple landing page test and a clickable prototype. Budget outlay so far: $130 incentives + ~8 hours of team time. Next step: build a 3-screen prototype and run a 20-person landing page test at $100 ad spend.

Checklist: Interview logistics and synthesis template

Define one testable assumption (write it in one sentence)
Recruit 10–15 qualified participants (note source and cost)
Send confirmation and consent note (5 mins)
Use the non-leading script; timebox to 20–30 minutes
Capture verbatim quotes and behaviors; timestamp them
After each interview, mark Yes/No for: problem present, workaround used, willingness to try
Synthesis: tally counts, list top 3 unmet needs, and decide: Stop / Prototype / Pivot

Two realistic limitations and simple adaptations

Limitation 1 — Sample bias: Small samples skew toward your network. Adaptation: recruit across two different channels (e.g., network + one public group) and note differences in answers.

Limitation 2 — Social desirability and leading cues: Interviewees sometimes tell you what they think you want. Adaptation: use behavior questions (past actions) over hypotheticals, and prioritize observed workarounds over stated intentions.

First 10-minute action

Write and record your single testable assumption and the one screening question. Example (10-minute script):

Assumption: Remote freelancers in shared offices struggle to block distraction and would use a simple scheduling tool.
Screen: "Have you tried to set aside uninterrupted work time in the past month? Yes/No"

Send that screening question to 5 contacts or post it in a relevant group. Track responses — that single quick step will tell you whether recruiting is feasible.

Sources and scope

This is practical editorial guidance drawn from experience running early user interviews and product discovery. It is not academic research and does not cite external studies. Use this when you need fast directional insight. For broader methods and templates, see our guides index: Better Lifestyle guides or the start page: Start here.

Three concise FAQs

Q: How many interviews are enough?
A: For directional validity, 10–15 well-targeted interviews are usually sufficient; use a clear decision rule for action.

Q: Should I pay participants?
A: Small incentives ($5–$20) increase response and show respect for time; choose what fits your budget.

Q: How do I avoid leading questions?
A: Ask about past behavior first, use neutral prompts, and never present your solution until after you understand the current workflow.

Use this guide to reduce wasted build time and to make better early product decisions. The template and checklist are reusable across ideas; update the screening question and assumption for each new test.