146. Customer Discovery Templates

Use these templates to make customer discovery disciplined. The aim is to capture real behavior, not polite opinions.

Use these in this order: prospect list, interview script, conversation notes, pain scoring, pattern review, then the continue/change/stop decision. Do not jump to the final decision before collecting comparable notes.

Interview script

Opening:

Thanks for speaking with me. I am trying to understand how [customer type] handles [problem/workflow] today. I am not here to sell on this call. I want to learn from your real experience.

Questions:

1. Can you walk me through the last time this happened?
2. What triggered it?
3. Who was involved?
4. What did you do first?
5. What tools, people, or workarounds did you use?
6. What was frustrating, slow, risky, or expensive?
7. What happens if this is not solved?
8. Have you tried to solve it before?
9. Who owns the budget or decision?
10. What would make you take a next step?

Closing:

Is there anyone else who faces this problem often and would be useful for me to speak with?

Interviewer rule: ask for stories, not opinions. “Would you use this?” is weak. “Can you walk me through the last time this happened?” is strong.

Prospect list

Name	Company	Segment fit	Role	Source	Ask	Status	Notes
		Exact / adjacent / weak	Buyer / user / influencer	Intro / LinkedIn / community / customer	Interview / workflow review / pilot

Prioritize exact segment fit over famous logos.

Add at least 30 names before concluding that a market is hard to reach. If you cannot name 30 plausible prospects, the first problem may be segmentation, not demand.

Outreach tracker

Use this when discovery is not happening because the founder is “waiting for intros.”

Prospect	Segment	Source	Message angle	Sent	Reply	Call date	Outcome	Next ask
		Warm intro / LinkedIn / community / event / customer					Interview / artifact / referral / no fit

Review the tracker twice a week. If replies are low, improve the segment or message. If replies are good but calls are weak, improve the script. If calls are good but no one commits to anything, the problem, buyer, or urgency may be weak.

Outreach message variants

Use short messages. The purpose is to earn a conversation, not explain the whole company.

Warm intro message:

Hi [name], [introducer] suggested I speak with you. I am trying to understand how [specific customer type] handles [specific workflow/problem]. I am not selling anything yet. Could I ask you 20 minutes about how this works today?

Cold LinkedIn/email message:

Hi [name], I am speaking with [role/company type] about [specific painful workflow]. I noticed [relevant context]. If you handle this, could I ask you a few questions about how it works today? Happy to keep it short.

Community/group message:

I am researching how [customer type] manages [workflow]. If anyone has dealt with this recently and is open to a 15 minute conversation, I would be grateful. I am looking for real workflow stories, not pitching a product.

Bad message pattern:

We are building an AI-powered platform to revolutionize [industry]. Would you like to try it?

That asks the prospect to evaluate your solution before you have earned the right to propose one.

Interview anti-script

Avoid these questions unless you already have strong context.

Weak question	Better question
Would you use this?	What did you do the last time this problem happened?
How much would you pay?	What does this problem cost today in time, money, risk, or lost revenue?
Is this a big problem?	What happens if it is not solved this month?
Do you like this idea?	What would need to be true for you to change your current process?
Should we build feature X?	Where does the current workflow break most often?
Who is the decision maker?	Who gets annoyed, who approves budget, and who has to use the tool?

Discovery is strongest when the customer forgets your idea and talks about their life.

Conversation notes

Field	Notes
Person and role
Segment
Last real example
Trigger
Current workaround
Cost of problem	Time, money, risk, frustration, lost revenue
Existing alternatives
Budget owner
Exact customer words
Follow-up promised
Signal strength	Strong / medium / weak

Artifact request

Whenever trust allows, ask for an artifact from the current workflow.

Artifact	What it reveals
Spreadsheet	Fields, process, manual work, owner, frequency.
WhatsApp thread	Coordination pain, reminders, informal process, urgency.
Invoice or report	Budget, buyer, output expected, compliance pressure.
Screenshot	Current tool, friction, missing workflow, data shape.
Email chain	Stakeholders, approval path, delays, handoffs.
SOP/checklist	Formal process and where it breaks.

Do not publish or share customer artifacts without permission. Use them to understand workflow reality.

Workflow map

Use this after each strong interview. It turns a conversation into product and sales insight.

Workflow step	Who does it?	Tool/channel	Time/cost	Pain	Opportunity
Trigger
Intake
Processing
Approval
Follow-up
Reporting/output

For Indian B2B workflows, pay attention to informal channels. A company may officially use ERP, email, or a ticketing tool, while the real decision path runs through WhatsApp, phone calls, a trusted admin, or the founder’s personal approval.

Buyer-user-influencer map

Many discovery mistakes happen because the founder interviews the user and assumes the buyer agrees.

Role	Person	Cares about	Objections	Evidence needed
User		Ease, speed, less manual work	Learning curve, extra reporting	Demo, workflow fit, support
Buyer		ROI, risk reduction, revenue, cost control	Budget, trust, switching cost	Business case, pilot result, reference
Influencer		Team impact, compliance, customer experience	Internal politics, ownership	Clarity, credibility, low-risk trial
Blocker		Control, workload, existing vendor	Loss of power, migration effort	Involvement, training, migration plan

If the user loves the product but the buyer does not care, sales stalls. If the buyer likes the promise but the user resists, adoption fails.

Pain scoring table

Score 1 to 5.

Customer	Frequency	Intensity	Current spend	Urgency	Access to buyer	Notes

Interpretation:

• High frequency + high intensity = strong problem candidate
• High intensity + low frequency = may need enterprise or high-ticket model
• High frequency + low intensity = may need automation, bundling, or different buyer
• Low frequency + low intensity = usually weak startup problem

Signal grading

Use this to avoid over-counting polite conversations.

Signal	Grade
Customer says the idea is interesting	Weak
Customer describes a recent painful incident	Medium
Customer shows the workaround or data	Strong
Customer introduces the buyer or another affected person	Strong
Customer asks for a pilot, price, or implementation step	Very strong
Customer pays or commits resources	Strongest

If most evidence is weak, do not call the idea validated. Change the segment, script, or channel.

Commitment ladder

Discovery should gradually ask for stronger commitment.

Ask	What it tests
20 minute interview	Access and relevance.
Follow-up call with a colleague	Organizational pain.
Artifact share	Trust and workflow reality.
Pilot problem statement	Whether they will define success with you.
Data/sample workflow access	Implementation seriousness.
Paid diagnostic or paid pilot	Budget, urgency, and buyer ownership.
Internal championing	Whether someone will spend reputation on the problem.

Do not jump to paid pilots before trust exists, but also do not stay forever at “great conversation.” Every few conversations, ask for a slightly stronger next step.

Pattern review table

Pattern	Evidence	Count	Confidence
Same customer type			High / medium / low
Same trigger			High / medium / low
Same workaround			High / medium / low
Same buyer			High / medium / low
Same willingness to act			High / medium / low
Same objection			High / medium / low

Continue/change/stop decision sheet

Decision	Use when	Your notes
Continue	Strong repeated pattern in a reachable segment
Narrow	Pain is real but only for a smaller segment
Change problem	Customer exists but pain is different
Change customer	Pain exists but current segment is weak
Stop	No urgency, no access, no willingness to act

Final decision:

We will [decision] because [evidence]. The next test is [test] by [date].

Discovery decision memo

After every 10 to 15 useful conversations, write a short memo.

Section	Notes
Segment tested
Number of useful conversations
Strongest repeated pain
Current workaround
Buyer/user distinction
Willingness-to-act evidence
Main objection or blocker
What surprised us
Decision	Continue / narrow / change customer / change problem / stop
Next 7-day test

This memo prevents discovery from becoming a pile of notes. The output of discovery is not a transcript; it is a sharper decision.

Discovery dashboard

Track the process like a founder, not like a researcher.

Metric	Why it matters
Prospects identified	Shows whether the segment is real and reachable.
Outreach sent	Prevents fake progress through planning.
Reply rate	Tests message and access.
Useful calls completed	Counts real learning conversations, not all meetings.
Strong pain calls	Shows whether pain repeats.
Artifacts collected	Shows workflow depth.
Buyer conversations	Separates user interest from purchase path.
Concrete next steps	Measures willingness to act.

Suggested weekly target for early discovery: 30 targeted prospects added, 20 messages sent, 5-10 useful conversations, 2-3 artifact requests, and one sharper decision. Adjust by segment, but keep a visible cadence.

B2C discovery notes

If the customer is a consumer, student, parent, creator, patient, trader, job seeker, or professional, discovery needs behavior evidence.

Signal	Useful question
Habit	When did you last do this? How often?
Spend	What have you paid for already?
Switching	What would make you stop using the current option?
Trust	What would make you believe a new product is safe?
Distribution	Where do you already discover solutions like this?
Retention	What would make you come back next week?

For consumer ideas, compliments are especially cheap. Look for repeated use, referrals, payment, sharing, saved time, status, income, or emotional relief.

Interview quality check

Score the interview process, not just the idea.

Question	Good sign
Did we ask about a recent real example?	The customer described a specific incident, not a hypothetical.
Did we map the current workflow?	We know people, tools, handoffs, timing, and failure points.
Did we identify the buyer or decision path?	We know who can approve money, time, data, or process change.
Did we capture exact language?	The notes include phrases we can reuse in positioning and sales.
Did we ask for an artifact, referral, or next step?	The conversation produced more than opinion.

If interview quality is weak, run better discovery before judging the market.

India field notes

Discovery in India often works better through trust networks than broad surveys. Track the source because it affects distribution later.

Source	What to learn
Warm intro	Which trust path opened the door?
Founder/community group	Is this a real buyer or another founder giving advice?
Trade association/event	Does the problem repeat across similar businesses?
CA/CS/lawyer/consultant	Which compliance or operating pain do they see repeatedly?
WhatsApp group	What language do customers use when they complain informally?

When the buyer is a promoter, owner, principal, doctor, shopkeeper, or family decision maker, the formal org chart may matter less than trust, cash flow, and timing.

Discovery packet by week

Discovery works best as a weekly operating habit. The goal is not to collect endless notes. The goal is to make the idea sharper every week.

Week stage	Packet	Founder action
Monday setup	Segment, prospect list, outreach tracker, message variants.	Choose one segment and send the first batch of asks.
Midweek learning	Interview notes, artifact requests, workflow maps.	Run calls, ask for real examples, collect workflow evidence.
Friday review	Pain scores, signal grading, pattern review, commitment ladder.	Compare conversations and identify repeated signals.
Weekly decision	Continue/change/stop sheet, discovery decision memo.	Decide what changes next week: segment, message, problem, ask, or product angle.

Suggested weekly operating targets:

Metric	Healthy early target
New prospects added	30 targeted names
Outreach sent	20 thoughtful messages
Useful conversations	5 to 10
Artifacts requested	2 to 3
Buyer/user maps updated	For every strong account
Decision memo	One per 10 to 15 useful conversations

Targets are not the point. They are a forcing function. If you cannot hit them, investigate why: poor segment definition, weak access, low trust, unclear message, or not enough founder discipline.

Discovery evidence gate

Use this gate before declaring an idea validated.

Evidence	Pass	Fail
Recent pain	Customers describe specific recent incidents.	They talk in hypotheticals.
Current workaround	They use people, spreadsheets, tools, agencies, money, or personal effort.	They agree it is a problem but do nothing.
Urgency	Delay has cost, risk, lost revenue, customer pain, or status loss.	They might care someday.
Buyer path	You know who approves money, data, process change, or adoption.	You only know the end user.
Trust	They share artifacts, referrals, internal context, or next steps.	They only give compliments.
Pattern	The same pain repeats in a reachable segment.	Every conversation points in a different direction.
Commitment	Someone agrees to a pilot, paid diagnostic, intro, data share, or concrete follow-up.	Nobody will spend time, money, data, or reputation.

Decision rule:

• If pain and workaround pass but buyer path fails, continue discovery with buyers.
• If user love passes but urgency fails, look for a higher-stakes workflow.
• If trust fails, improve access and credibility before judging demand.
• If pattern fails after enough good interviews, narrow the segment or change the problem.
• If commitment fails repeatedly, do not call the idea validated.

The most dangerous discovery result is a folder full of friendly conversations. Useful discovery should leave the founder with sharper language, a narrower segment, stronger proof, and a more uncomfortable but clearer decision.

Copy-paste discovery CRM

Use this as a simple spreadsheet before buying any CRM. Each row is one prospect or interview.

Field	Value
Name
Company / context
Segment
Role
Source	Warm intro / cold outreach / community / event / referral
Status	To contact / contacted / scheduled / interviewed / no response / not fit
Problem hypothesis
Recent pain example
Current workaround
Cost of problem	Time / money / risk / revenue / stress / customer pain
Buyer path
Artifact requested	Screenshot / spreadsheet / process doc / invoice / message / none
Commitment	Intro / data share / pilot interest / paid diagnostic / none
Exact customer language
Interview quality score	1-5
Next action
Decision impact	Continue / narrow / change / stop

After every 10 useful conversations, create this summary:

Segment tested:

Repeated pain:

Strongest evidence:

Weakest evidence:

Current workaround:

Buyer/user distinction:

Words customers used:

What surprised us:

What we should stop assuming:

Next experiment:

This gives discovery a memory. Without a CRM-like evidence log, founders remember the most emotional conversations, not necessarily the most useful ones.

Copy-paste interview debrief

Fill this immediately after each useful conversation, before the founder memory starts rewriting it.

Interview:
Segment:
Role:
Date:

One-line summary:

Recent real example:

Current workaround:

Pain cost:

Buyer / approver:

Exact words worth reusing:

Artifact or proof seen:

Commitment asked:

Commitment received:

What this confirms:

What this weakens:

Follow-up:

Debrief quality check:

Weak debrief	Strong debrief
”Good call, they liked it."	"Ops head spends 6 hours every Friday reconciling vendor invoices in Excel and asked for a paid diagnostic."
"They need automation."	"They copy data from WhatsApp, email, and Tally because no one trusts the ERP export."
"Potential customer."	"User is interested, but finance head owns approval and has not been reached.”

Good discovery notes are useful to product, sales, positioning, and fundraising. If the note is only useful to the founder who took the call, it is not structured enough.

Segment evidence board

Use this after 10 to 15 conversations in one segment.

Evidence area	Strong signal	Weak signal	Notes
Pain repeats	Same painful workflow appears in multiple conversations.	Every prospect has a different problem.
Trigger repeats	Same event creates urgency.	No clear trigger.
Workaround exists	Customers spend time, money, people, or tools today.	Customers only complain casually.
Buyer is reachable	Founder can identify and reach approver.	Only users are accessible.
Trust path exists	Warm intros, advisors, community, or proof opens doors.	Customers do not respond or share context.
Willingness to act	Prospects accept follow-up, share artifacts, introduce others, or discuss payment.	Compliments but no next step.
Founder fit	Founder has credibility, access, domain insight, or speed in this segment.	Segment is attractive but inaccessible.

Decision:

Segment:
Evidence strength: strong / mixed / weak
Primary risk:
Next 7-day test:
Decision: continue / narrow / change / stop

Discovery false-positive log

Track signals that felt good but did not convert into useful evidence.

False positive	Why it misled us	How we will test better next time
Compliment	Customer liked the idea but had no urgency.	Ask for recent incident, cost, and next step.
Famous logo	Company looked impressive but was not the buyer segment.	Prioritize segment fit over brand.
Warm intro	Intro created access but not pain.	Qualify problem before counting it as signal.
Feature request	Customer asked for a feature but would not commit.	Ask whether it solves a repeated paid problem.
Survey agreement	People clicked yes but did not spend time or money.	Ask for behavior, artifact, or commitment.

False positives are not embarrassing. They are part of learning. The mistake is letting them inflate confidence.

Related chapters

• 18. Customer Discovery Fundamentals
• 19. Running Customer Interviews
• 132. 7-Day Customer Discovery Playbook