20. Running Customer Interviews

Running customer interviews is a craft. A good interview reveals how the customer’s world works. A bad interview flatters the founder and creates false confidence.

The interview is not a pitch meeting. It is not a product demo. It is not a debate. It is a careful attempt to understand recent behavior, current workarounds, decision-making, cost, urgency, and trust.

If you do interviews well, you will often leave with fewer assumptions and better questions. That is progress.

The core interview question is: can we get the customer to describe recent behavior, current workaround, cost, people involved, buying path, and trust requirements without leading them toward our preferred answer?

Interview setup

Segment hypothesis

Before the call, write who you think this person represents.

Example:

• “Indian D2C founder doing Rs 50 lakh to Rs 5 crore annual revenue”
• “Finance manager in a 100-500 employee B2B SaaS company”
• “School owner in tier-2 city managing admissions offline”
• “Sales head at an industrial distributor”

Do not mix segments casually. Pattern recognition depends on knowing which segment the conversation belongs to.

Problem hypothesis

Write the problem you think exists.

Use this format:

I believe [segment] struggles with [problem] when [trigger], causing [cost or pain], and today they solve it using [current workaround].

You are not trying to prove this sentence. You are trying to test it.

Target list

Maintain a simple target list:

• Name
• Segment
• Role
• Source
• Why they qualify
• Outreach status
• Interview status
• Notes link
• Follow-up action

This prevents discovery from becoming random networking.

Outreach script

Your outreach should be honest.

Do not pretend to ask for advice when you plan to pitch. Do not hide the startup context. But also do not lead with your product.

Good outreach says:

• Why this person is relevant
• What you are trying to learn
• That you are not selling on the call
• How long it will take
• What topic you will ask about

Conversation goal

Every interview should have one learning goal.

Examples:

• Understand current invoice follow-up workflow
• Learn how school owners choose admissions software
• Understand how sales teams qualify distributors
• Learn why users abandon onboarding
• Understand who approves a new compliance tool

If you try to learn everything, you will learn little.

Note-taking format

Write notes in a consistent structure:

• Interviewee profile
• Context
• Last occurrence
• Current workaround
• Cost
• People involved
• Buyer/approver
• Budget
• Trust criteria
• Exact phrases
• Surprises
• Follow-up
• Signal strength

Exact phrases matter. Customers often give you positioning language.

Consent

Ask before recording. If the topic is sensitive, do not record. Tell the person how you will use the notes.

For enterprise, health, finance, education, or employee-related topics, be careful with confidential information. You need learning, not secrets.

How to run the interview

Start with context

Open with:

Thanks for taking the time. I am trying to understand how people like you handle [problem area] today. I am not here to pitch. I may ask about recent examples, current process, and what makes this painful or not painful.

This relaxes the conversation and reduces performative feedback.

Use a simple interview flow

Do not turn the call into an interrogation. Use a calm flow:

1. Context: why you are speaking and what you are trying to learn.
2. Role: what the person does and how they relate to the workflow.
3. Last occurrence: the most recent time the problem happened.
4. Current workaround: what they did, with which tools and people.
5. Cost and stakes: time, money, risk, stress, customer impact.
6. Buying path: who owns change, budget, approval, and blockers.
7. Trust: what proof or support would make a new solution credible.
8. Next step: intro, second call, workflow review, prototype review, or pilot.

This flow keeps the conversation anchored in reality. You can still follow interesting branches, but you always return to behavior.

Ask about the last time

The most useful phrase in discovery is:

Tell me about the last time this happened.

Recent behavior is more reliable than opinions.

Follow up:

• When was it?
• What triggered it?
• Who was involved?
• What did you do first?
• What happened next?
• How long did it take?
• What made it difficult?
• What happened if it was not solved?

Study the current workaround

Current workaround reveals pain and budget.

Ask:

• What tools do you use today?
• Is there a spreadsheet?
• Is there a person doing manual work?
• Is there an agency or vendor?
• Is there a WhatsApp group?
• What breaks?
• Why have you not changed it?
• What have you already tried?

If the workaround is expensive and still tolerated, the problem may be important. If there is no workaround, the pain may be weak or hidden.

Ask about cost

Cost can be money, time, risk, stress, lost revenue, poor customer experience, compliance exposure, or employee frustration.

Ask:

• What does this cost you?
• How do you measure that?
• Who notices when it goes wrong?
• What happens if this remains unsolved for six months?
• Is there a budget connected to this?

Do not force a number if the customer does not have one. But look for stakes.

Map people involved

Most important problems involve multiple people.

Ask:

• Who does the work?
• Who requests it?
• Who approves it?
• Who pays for tools?
• Who complains when it fails?
• Who would need to agree to change?
• Who could block a new solution?

This separates user discovery from buyer discovery.

Understand decision process

Ask:

• How do you choose a new vendor or tool?
• Who must approve it?
• What budget threshold changes the process?
• How long does approval take?
• What documents are needed?
• Do you need security, legal, finance, or procurement review?
• What would make you say no?

Decision process is often where promising products die.

Explore trust criteria

Ask:

• What makes you trust a new vendor?
• Do you need references?
• Does local support matter?
• Does founder credibility matter?
• Does brand matter?
• Does data security matter?
• What would make you nervous?

Trust is a product requirement, sales requirement, and positioning requirement.

Question bank

Use these as prompts, not a script.

Problem questions

• When did this last happen?
• How often does it happen?
• What triggered it?
• What makes it painful?
• What happens if you do nothing?
• Who cares most when it goes wrong?

Workflow questions

• Walk me through the process.
• What tools are involved?
• Where does the handoff happen?
• What is manual?
• What takes the most time?
• Where do errors happen?

Budget questions

• Do you spend money on this today?
• Which budget pays for it?
• What alternatives have you tried?
• What would justify spending more?
• What approval is needed?

Trust questions

• What would make you trust a new solution?
• What proof would you need?
• Who else would need to be convinced?
• What risks would stop you?

Next-step questions

• Who else should I speak to?
• Would you be open to reviewing a prototype later?
• Would this be worth a paid pilot if we solve the issue?
• What would need to be true for you to try it?

What to avoid

Leading questions

Bad: “Would it save you time if this was automated?”

Better: “How much time does this take today?”

Pitching too early

Once you pitch, the customer starts reacting to your idea instead of describing their world. Save the pitch until you understand the context.

Hypothetical questions

Bad: “Would you pay Rs 5,000 per month?”

Better: “What do you spend today to solve this, including people and tools?”

Selling to polite friends

Friends often encourage you. Treat friend interviews as practice unless they match the target segment and can speak honestly.

Ignoring contradictions

If a customer says the problem is painful but has never tried to solve it, do not ignore that contradiction. It may reveal low urgency, lack of budget, or hidden constraints.

Overvaluing praise

Praise is pleasant. Commitment is evidence.

Better signals:

• Follow-up booked
• Introduction made
• Data shared
• Prototype reviewed
• Pilot agreed
• Payment discussed
• Budget owner introduced

After the interview

Immediately write:

• What surprised you?
• What exact words did they use?
• What repeated from previous calls?
• What contradicted your hypothesis?
• What segment does this support or weaken?
• What is the next action?

Discovery value decays quickly if notes are delayed.

A useful note format

Use one consistent note structure:

Field	What to capture
Segment	Which customer type this person represents.
Role	User, buyer, approver, operator, blocker, advisor.
Last occurrence	The most recent concrete story.
Current workaround	Tools, people, spreadsheets, WhatsApp, vendors, manual steps.
Cost	Time, money, risk, delay, customer pain, compliance exposure.
Buyer path	Who pays, approves, blocks, and influences.
Trust hurdle	What proof, support, or credibility is needed.
Exact phrases	Customer words that should not be paraphrased too early.
Signal strength	Weak, medium, strong, with reason.
Next action	What happens next, if anything.

Notes should separate observation from interpretation. “Customer spends 6 hours every Friday reconciling orders” is observation. “This is a big market” is interpretation. Keep both, but label them.

When to show the product

In early discovery, avoid demoing too soon. But there is a time to show something.

Show a concept, prototype, or workflow only after you understand:

• The customer’s current process.
• The pain and cost.
• Who would need to approve change.
• What would make the solution trustworthy.

When you show it, do not ask, “Do you like it?” Ask:

• What part would you use first?
• What would not fit your workflow?
• Who else would need to see this?
• What would stop you from trying this next week?
• What would make this worth paying for?

The goal is still learning, not applause.

A 30-Minute Interview Script

Use this as a starting point, then adapt.

Time	Focus	Example prompts
0-3 min	Set context	”I am learning how teams like yours handle this today. I am not here to pitch.”
3-7 min	Role and context	”What do you own?” “How does this workflow connect to your goals?“
7-15 min	Last occurrence	”Tell me about the last time this happened.” “What triggered it?“
15-20 min	Current workaround	”Walk me through what you did.” “Which tools, people, and files were involved?“
20-24 min	Cost and stakes	”What did this cost?” “Who noticed?” “What if nothing changed?“
24-27 min	Buying and trust	”Who would approve a change?” “What proof would you need?“
27-30 min	Next step	”Who else should I speak to?” “Would reviewing a mock workflow be useful?”

The script is not a questionnaire. Follow the customer’s story. But make sure you leave with behavior, workaround, cost, buyer, trust, and next step.

The Ladder Technique

When a customer gives a vague answer, ladder down to reality.

Customer: “This is a big problem.”

Founder:

1. “When did it last happen?”
2. “What exactly happened?”
3. “Who was involved?”
4. “What did you do next?”
5. “How long did that take?”
6. “What happened because of it?”
7. “What have you tried to fix it?”
8. “Why did that not solve it?”

Do not argue with vague answers. Make them concrete.

Handling Money Conversations

Founders often avoid budget questions because they feel awkward. But price, approval, and payment are part of reality.

Ask softly but directly:

• “Do you spend money on this today?”
• “Is this handled by people, software, agencies, or internal time?”
• “Which budget would a solution come from?”
• “At what price does approval become harder?”
• “Would a paid pilot make sense if the scope were clear?”

You are not forcing a sale. You are learning whether the problem can become a business.

After-Call Follow-Up

Send a short follow-up within 24 hours:

• Thank them.
• Reflect one or two things you heard.
• Ask for the promised intro, document, or next step.
• Offer to share a summary later if useful.

Example:

Thanks again. I heard that the painful part is not invoice creation itself, but chasing missing documents before the deadline and knowing which clients are at risk. If you are comfortable, an intro to the person who handles the follow-up would help me understand the workflow better.

The follow-up tests seriousness. People who were warm on the call but never reply may have been polite, not committed.

Interview Debugging Guide

If discovery calls feel pleasant but do not produce decisions, debug the interview.

Symptom	Likely issue	Fix
Customers keep saying “interesting.”	You are asking for opinions.	Ask about the last time the problem happened.
Everyone is positive, but no one follows up.	Politeness is being mistaken for signal.	Ask for a concrete next step during the call.
Notes are full of feature ideas.	You are letting the customer design the product.	Go back to workflow, pain, cost, and constraints.
You cannot identify the buyer.	You stayed with the user only.	Ask who owns the outcome and budget.
The problem sounds real but vague.	You did not ladder down.	Ask for timing, people, tools, cost, and consequence.
Calls are too short.	The interviewee is weakly qualified or the ask is unclear.	Improve targeting and context-setting.
Calls become sales demos.	You are anxious to validate the solution.	Separate discovery calls from demo calls.
Customers avoid budget questions.	Trust or timing is weak.	Ask about current spend, approval process, or comparable tools instead of price first.

The interviewer should improve every week. If the fifth call sounds exactly like the first call, the founder is not learning how to learn.

The Five-Minute Debrief

Immediately after every call, write a short debrief before memory becomes narrative:

Prompt	Answer
Was this person qualified?
What was the strongest behavior-based evidence?
What was only opinion?
What surprised us?
What did we avoid asking?
What follow-up did they agree to?
What should we ask differently next time?

Do not wait until the end of the week to synthesize everything. Good discovery improves call by call.

Handling Sensitive Topics

Some discovery topics involve money, failure, health, compliance, employees, family, or confidential workflows. Treat these carefully.

Use softer entry points:

• “Roughly, how do teams usually handle this?”
• “What tends to happen in companies like yours?”
• “Without sharing anything confidential, what makes this painful?”
• “Is there a safe example you can describe?”
• “Who normally gets involved when this becomes serious?”

Never pressure a person to disclose sensitive data. You need insight, not secrets. If the product requires sensitive access later, trust must be earned deliberately.

Remote Interview Hygiene

For video or phone calls:

• Keep the ask short and punctual.
• Ask permission before recording.
• Turn off distractions.
• Use a shared note only if it helps the interviewee think.
• Send the calendar invite with context.
• Follow up with one clear request.

For in-person interviews:

• Do not overstay.
• Observe workflow when appropriate.
• Ask before taking photos.
• Respect staff and customers around the interviewee.
• Pay attention to artifacts: registers, spreadsheets, WhatsApp groups, invoices, dashboards, checklists, physical movement.

Observation often reveals what conversation hides.

Question Rewrite Table

The quality of discovery often comes down to question wording. Weak questions invite opinions. Strong questions invite stories and behavior.

Weak Question	Better Question
Would you use this?	When did you last try to solve this problem?
Is this a problem?	What happened the last time this caused trouble?
How much would you pay?	What do you spend today in money, time, people, or risk?
Do you like this feature?	Where would this fit in your current workflow?
Would your company buy this?	Who would need to approve a change like this?
Should we build X?	What is the hardest part of the current workaround?
Is this urgent?	What happens if this is not fixed this month or quarter?
Can I send you updates?	What specific next step would be useful from here?

Before every interview, rewrite your top questions. If the question can be answered with politeness, it is probably too weak.

Commitment Ladder During Interviews

Do not pressure people, but do observe whether the conversation creates action.

Possible next steps, from weak to strong:

Commitment	Signal Strength
”Keep me posted.”	Weak; polite interest.
Replies to follow-up.	Better; small time commitment.
Introduces another user or buyer.	Strong; spends social capital.
Shares an artifact, workflow, or data sample.	Strong; opens real context.
Reviews a prototype or workflow mock.	Strong; invests attention.
Discusses pilot scope and success criteria.	Very strong.
Pays for a pilot, audit, setup, or early access.	Strongest early signal.

Ask for the next appropriate step at the end of the call. If every call ends with appreciation and no action, the founder has not yet found enough urgency, trust, or buyer clarity.

Interview Opening Contract

The first two minutes set the quality of the conversation. Founders often accidentally make the customer feel they are supposed to validate the idea. Instead, set a learning contract.

Use a simple opening:

Thanks for taking the time. I am not here to pitch or convince you. I am trying to understand how this workflow actually works today, where it is painful, and what would make change hard. Honest negatives are more useful than polite positives.

Then add:

• “I may ask about the last time this happened rather than general opinions.”
• “If a question does not apply, please say so.”
• “I will keep the conversation practical and respect anything confidential.”

This gives the interviewee permission to be honest. It also reminds the founder not to sell too early.

Live Signal Capture

During the call, mark signals in real time. Do not wait until later when memory becomes generous.

Use these tags in notes:

Tag	Meaning
STORY	A recent concrete event.
WORKAROUND	Current tool, manual process, person, agency, or spreadsheet.
COST	Time, money, risk, lost revenue, delay, reputation, stress.
OWNER	Person accountable for the outcome.
BUYER	Person or function that controls budget or approval.
TRUST	Proof, support, security, reference, brand, or relationship needed.
BLOCKER	Reason adoption may fail.
ACTION	Follow-up, intro, data share, prototype review, pilot, payment.

At the end of the call, you should be able to scan the notes and see whether the conversation had substance. If the notes have many opinions but no STORY, WORKAROUND, COST, or ACTION, the call was probably weak.

Interview Debrief Protocol

After each call, spend five minutes writing the debrief before the next meeting.

Answer:

• What did we hear, not infer?
• What exact phrase should we preserve?
• What evidence became stronger?
• What evidence became weaker?
• What question did we fail to ask?
• What next action did the customer agree to, if any?
• Should this person count as qualified evidence?

Then assign one of three labels:

Label	Meaning
Evidence	This call should influence the product, segment, pricing, or sales motion.
Practice	Useful for learning how to ask, but not strong market evidence.
Noise	Polite, off-segment, vague, or misleading.

Founders often keep every conversation because every conversation took effort. That is understandable, but dangerous. Bad evidence should not get voting rights.

Conversation Repair Moves

Even good founders run weak interviews. The skill is to notice drift and repair the conversation while there is still time.

Problem During Call	What It Sounds Like	Repair Move
Too abstract	”Usually this is a challenge."	"Can you walk me through the last time it happened?”
Too polite	”Yes, that sounds useful."	"What would make this not worth adopting?”
Too senior	”My team handles that."	"Who on the team does this weekly, and could I speak with them?”
Too solution-focused	”You should build a dashboard."	"What decision would that dashboard help you make?”
Too future-focused	”We may need this next year."	"What is happening this quarter that would force action?”
No buyer clarity	”Someone would approve it."	"Who approved the last similar purchase?”
No cost clarity	”It wastes time."	"How much time, whose time, and what happens because of the delay?”
No next action	”Keep me posted."	"Would reviewing a workflow mock or introducing the buyer be useful?”

The repair move should feel curious, not aggressive. You are not cross-examining the customer. You are helping both sides escape vague language.

Artifact-Led Interviews

The best interviews often move from memory to artifacts. People describe workflows vaguely, but artifacts reveal the real process: spreadsheets, invoices, WhatsApp messages, dashboards, forms, screenshots, call logs, support tickets, SOPs, reports, job descriptions, purchase orders, or review comments.

Ask gently:

Would it be possible to show me an example with anything sensitive hidden?

Or:

Could you walk me through the spreadsheet, message, report, or tool you use today?

Artifacts help because they reveal:

Artifact	What It Can Reveal
Spreadsheet	Workflow steps, owners, data fields, errors, manual effort.
WhatsApp thread	Informal coordination, urgency, repeated questions, trust behavior.
Invoice or PO	Buyer, payment terms, tax/admin process, procurement reality.
Support ticket	Customer pain, internal handoff, resolution time, language.
Dashboard	Current metrics, gaps, decision flow, reporting burden.
Job posting	The problem a company is hiring people to solve manually.
Review or complaint	Trigger, emotion, competitor weakness, unmet expectation.

Artifact Safety Rules

Respect confidentiality. Never pressure someone to reveal private information. Tell them to hide names, amounts, customer details, patient/student/employee data, or anything sensitive.

Use these rules:

• Ask permission before recording or screenshotting.
• Accept a verbal walkthrough if the artifact is sensitive.
• Do not store sensitive files casually.
• Do not share artifacts outside the team without explicit permission.
• Summarize the workflow rather than copying private data.
• Mark notes as sensitive when needed.

Artifact Questions

When looking at an artifact, ask:

• Who created this?
• Who updates it?
• How often does it change?
• What happens if it is wrong?
• Which field or step creates the most pain?
• Who reads it before making a decision?
• What workaround exists outside this artifact?
• What would make this unnecessary?

Artifact-led interviews are especially useful in India because many real workflows live outside formal software: WhatsApp groups, Excel sheets, shared drives, phone calls, field staff, family businesses, accountants, and local vendors. If you only ask abstract questions, you miss the operating reality.

The artifact does not need to be beautiful. In fact, messy artifacts are often more valuable. They show where the current system is bending under pressure.

Interview Question Bank

Founders often ask either too broadly or too directly. A useful question bank keeps the conversation grounded in behavior while still letting the customer tell the story in their own words.

Use the bank like a menu. Do not ask every question. Pick the few that match your learning goal.

Learning goal	Questions to ask
Understand trigger	”What usually causes this problem to appear?” “When did it happen last?” “What changed before it became painful?”
Understand workflow	”Walk me through what happens from start to finish.” “Who touches this before it is done?” “Where does the work slow down?”
Understand workaround	”How do you handle it today?” “What tools, people, spreadsheets, vendors, or WhatsApp groups are involved?” “What have you tried before?”
Understand cost	”What does this cost in time, money, delay, risk, customer anger, or management attention?” “Who feels the cost most?”
Understand priority	”Where does this sit compared with other problems?” “What happens if this remains unsolved for six months?”
Understand buyer	”Who owns this problem?” “Who would approve a change?” “Who could block it?”
Understand trust	”What would make you trust a new vendor or tool?” “What proof would you need before trying it?”
Understand urgency	”Why solve this now?” “What deadline, growth, audit, churn, customer complaint, or cost increase makes this active?”

Good discovery questions are usually short. The follow-up is where the value comes from.

Customer: We waste a lot of time on this.
Founder: When did that last happen?
Customer: Last Friday.
Founder: What exactly happened last Friday?
Customer: The sales report did not match the invoice data.
Founder: Who noticed it?
Customer: Our finance manager.
Founder: What did she do next?

That sequence is more useful than asking, “Would you use software to solve this?” The customer may say yes, but the founder still learns nothing about the workflow, cost, urgency, or buyer.

Interview Signal Score

After each interview, score the signal before your memory turns the conversation into optimism.

Dimension	0	1	2
Recent behavior	No recent example.	Example exists but is vague.	Clear recent example with timeline and steps.
Workaround	No workaround.	Informal workaround exists.	Costly workaround with people, tools, money, or repeated effort.
Pain cost	No cost named.	Cost described emotionally.	Cost visible in time, money, risk, churn, errors, delay, or lost revenue.
Buyer clarity	Buyer unknown.	Possible buyer identified.	Buyer, approver, user, and blocker are mapped.
Urgency	Nice-to-have.	Important but not urgent.	Active trigger or deadline exists.
Trust path	No path.	Some proof might help.	Clear proof needed: reference, demo, pilot, compliance, support, ROI, or founder credibility.
Next action	No follow-up.	Soft interest.	Dated next step, intro, artifact review, pilot discussion, or buyer meeting.

Add the score out of 14. Then classify the conversation:

Score	Meaning	Founder response
0-4	Weak signal	Do not build from this interview. Improve segment or questions.
5-8	Learning signal	Keep interviewing, look for repeated patterns.
9-11	Strong problem signal	Test willingness to pay, buyer path, and product promise.
12-14	Commercial signal	Move toward pilot, paid test, design partner, or sales process.

Do not turn the score into fake precision. It is a forcing function. It makes the founder explain why an interview was strong instead of saying, “The call went well.”

The 24-Hour Synthesis Ritual

Discovery loses value when notes sit untouched. Within 24 hours of every interview, write a short synthesis.

Interview:
Segment:
Role:
Strongest evidence:
Weakest evidence:
Exact phrase worth remembering:
Current workaround:
Buyer or approver:
Trust requirement:
What surprised me:
What I should ask next:
Signal score:
Decision:

The decision should be one of four:

Decision	Meaning
Continue	Interview more people in this same segment because the pattern is promising.
Narrow	The segment is too broad; define a tighter profile.
Change question	The interview did not produce behavior; improve the script.
Advance	Move this person toward artifact review, prototype review, buyer intro, pilot, or sales call.

Every Friday, review the week’s interviews together. Look for repeated words, repeated workflows, repeated blockers, and repeated willingness to take the next step. If every interview produces a different story, the segment is probably too broad or the problem statement is still fuzzy.

Interview Anti-Patterns

These patterns create false confidence:

Anti-pattern	What it sounds like	Better move
Pitch disguised as discovery	”Would you use our product if it did X?"	"How do you solve this today?”
Compliment collection	”Everyone liked the idea."	"Who agreed to a specific next step?”
Future fantasy	”Would this be useful someday?"	"When did this problem last cost you something?”
Friend bias	”My network says this is needed."	"Interview people who can reject you honestly.”
Segment mixing	”SMBs said…"	"Which kind of SMB, with what trigger and buyer?”
Demo escape	”They understood after I showed the product."	"Could they describe the pain before the demo?”
No synthesis	”I remember the call."	"Write the evidence, score, and decision within 24 hours.”

The founder should leave discovery with sharper judgment, not just more notes.

Status And Politeness Filters

Many customer interviews sound positive because people want to be helpful, look smart, avoid conflict, or maintain relationship warmth. This is especially common when the founder is introduced by a mutual contact or when the interviewee is senior.

Use filters to separate politeness from evidence:

Polite answer	Better probe
”This is interesting."	"What part of this matches something that happened recently?"
"We should use something like this."	"What do you use today, and when did you last use it?"
"Send me details."	"What would you look for before deciding whether this is worth another conversation?"
"Budget should not be an issue."	"Who approves this category of spend and what was the last similar purchase?"
"My team will like it."	"Who on the team would resist it, and why?"
"This saves time."	"Whose time, how much, and what happens with that saved time?"
"We can try it."	"What would need to happen before a trial starts?”

Do not punish customers for being polite. Just do not treat politeness as proof.

Status Filter

Some answers are shaped by status:

• A senior person may understate operational chaos because it reflects badly on the team.
• An operator may exaggerate pain to get better tools.
• A buyer may talk strategically but not know daily workflow.
• A consultant may describe patterns but not direct urgency.
• A friend may encourage the founder to protect the relationship.

Ask for examples, artifacts, and sequence:

Can you walk me through the last time this happened?
What did you do first?
Who got involved next?
What was the consequence?
Can you show me a sanitized example?

The more the interview moves from opinion to sequence, the more useful it becomes.

Remote Interview Quality Checklist

Many discovery calls happen on Zoom, Google Meet, WhatsApp, or phone. Remote calls can work well if the founder designs for attention and artifacts.

Before the call:

• Confirm the role and segment.
• Send a short note that this is research, not a sales pitch.
• Ask whether they can keep a recent example ready.
• Prepare 5 core questions, not 25.
• Keep a note template open.

During the call:

• Start with context and permission to ask practical questions.
• Ask about the last real incident.
• Slow down when the customer mentions a workaround.
• Ask who else gets involved.
• Ask what happens if nothing changes.
• Ask for a concrete next step only if the signal is strong.

After the call:

• Send thanks and any promised summary.
• Write notes within 24 hours.
• Tag exact phrases.
• Record follow-through behavior.
• Decide whether this person should be advanced, archived, or referred.

Remote discovery fails when founders treat calls as casual chats. It works when every call is designed to capture behavior, artifacts, and follow-through.

India angle

In India, customer interviews may require context-building before direct questioning. Some customers may be polite, indirect, or hesitant to discuss money. Some may switch languages mid-conversation. Some workflows may involve family members, staff, accountants, vendors, or WhatsApp groups.

Be patient. Ask for stories. Ask to see examples. Do not mistake indirectness for lack of insight.

Reader action

Run three interviews this week using the same note format. After each interview, write the strongest evidence, weakest evidence, and one thing you should ask better next time.

Related links

• 18. Customer Discovery Fundamentals
• 19. Finding People to Interview
• 21. Interpreting Customer Discovery
• 132. 7-Day Customer Discovery Playbook
• 146. Customer Discovery Templates