59. Discovery Calls

A discovery call is not a demo slot.

It is the conversation where you learn whether the prospect has a painful problem, whether that problem matters now, who owns the decision, what they use today, and what would make a solution worth buying.

Founders often rush to show the product because demoing feels safer than asking hard questions. But if there is no real pain, a demo will not create it. Discovery protects both sides from wasting time.

The core discovery question is: can the founder uncover the buyer’s real pain, impact, decision path, and urgency before trying to sell the solution?

What It Covers

This chapter covers:

• Discovery goals
• Discovery frameworks
• Discovery mistakes

The founder’s job is to leave the call with more truth, not merely more hope.

Discovery Is A Truth-Seeking Conversation

A discovery call should answer four commercial questions:

1. Is the problem real?
2. Is the problem expensive or urgent enough?
3. Can this person influence or make a purchase?
4. Is there a next step that moves toward a decision?

If the answer to these is no, the call can still be useful research, but it is not pipeline.

Founders often confuse friendliness with qualification. A prospect may like you, like the product, and still have no budget, no authority, no urgency, and no reason to change. Discovery separates human warmth from commercial reality.

Discovery Goals

A good discovery call should clarify eight things.

Pain

What problem exists? How does it show up? Who feels it? Is it annoying or expensive?

Ask for stories:

• “Walk me through the last time this happened.”
• “What triggered it?”
• “Who noticed first?”
• “What did you do next?”

Stories reveal reality better than opinions.

Impact

Pain matters when it creates cost: time, money, risk, lost revenue, customer dissatisfaction, employee frustration, compliance exposure, or management attention.

Ask:

• “What happens if this is not solved?”
• “How often does this happen?”
• “How much time does it take?”
• “Who gets affected?”
• “What does this block?”

If the impact is unclear, the deal will drift.

Current Workflow

Understand what they do today. The current workflow may be a competitor, spreadsheet, agency, internal tool, WhatsApp group, manual process, or one employee holding everything together.

Current behavior is stronger evidence than stated interest. If they are already spending time or money, the pain is more real.

Decision Process

Many early founders sell to friendly non-buyers. The person likes the product but cannot approve it.

Ask:

• “Who else would be involved in deciding?”
• “How do you usually buy tools like this?”
• “Would finance, IT, procurement, legal, or the founder need to review?”
• “What would the next step look like if this is useful?”

Do this gently, but do it.

Budget

Budget questions feel uncomfortable, especially for founders new to sales. Avoiding them creates fake pipeline.

Ask:

• “Do you already spend money solving this?”
• “Is there budget for this category?”
• “What would make this worth paying for?”
• “If this saved [specific cost], how would you evaluate price?”

You are not begging for money. You are checking whether the problem is commercial.

Stakeholders

The user, buyer, approver, blocker, finance owner, IT reviewer, and implementation owner may be different people.

Map them early. A deal with hidden stakeholders is not a deal; it is a surprise waiting to happen.

Timeline

Urgency matters. A prospect may agree the problem exists but have no reason to act now.

Ask:

• “Why look at this now?”
• “Is there a deadline?”
• “What happens if this waits three months?”
• “What other priorities compete with this?”

Success Criteria

Before demo or pilot, understand what success means. Otherwise the customer can always say, “Interesting, but not enough.”

Success may be time saved, errors reduced, revenue recovered, faster onboarding, better reporting, fewer escalations, or improved customer experience.

The Real Next Step

The next step should follow the discovery truth.

Discovery result	Better next step
Pain is strong, buyer is present, urgency exists	Demo or proposal
Pain is strong, buyer is absent	Meeting with buyer or approver
Pain is unclear	More discovery with user or workflow owner
Value is clear, proof is missing	Bounded pilot with success criteria
Budget is unclear	Commercial conversation before heavy implementation
Not a fit	Close politely and record why

Do not drag every prospect into a demo. The right next step may be disqualification.

Discovery Frameworks

Frameworks are memory aids, not scripts.

BANT

Budget, authority, need, timeline. Useful for quick qualification, but too shallow if used mechanically.

SPIN

Situation, problem, implication, need-payoff. Useful because it moves from facts to consequences.

MEDDICC

Metrics, economic buyer, decision criteria, decision process, identify pain, champion, competition. Useful for enterprise sales where deals have many stakeholders.

Jobs-To-Be-Done

Useful for product-oriented founders. It asks what progress the customer is trying to make and why current solutions fail.

Problem-Impact-Outcome

For early founders, the simplest structure is:

1. What is happening today?
2. Why does it matter?
3. What would a better outcome look like?
4. Who decides whether to change?
5. What is the next step?

Use Frameworks Lightly

Frameworks become harmful when the call feels like an interrogation. The buyer should feel heard, not processed.

A founder can keep a simple note open with headings:

Pain:
Current workflow:
Impact:
Buyer:
Budget:
Timeline:
Success criteria:
Objections:
Next step:
Disqualification:

Use the headings to guide the conversation, not to force it.

Call Flow

A practical 30-minute flow:

1. Set context: “I would like to understand how you handle this today and then, if useful, share where we may help.”
2. Ask why they agreed: Their answer reveals perceived relevance.
3. Explore workflow: Get the actual process.
4. Quantify impact: Time, cost, risk, frequency.
5. Map decision: Buyer, approver, stakeholders.
6. Test urgency: Why now?
7. Share only relevant product context: Do not feature-tour.
8. Agree next step: Date, owner, purpose.

Opening The Call

Set the frame early:

Thanks for taking the time. I would like to understand how you handle [workflow] today, what is painful or not painful about it, and then I can share where we may or may not help. If it is not a fit, I will say that directly.

This lowers defensiveness. You are not pretending every call must become a sale.

Pre-Call Research Brief

Before a discovery call, write a quick research brief. It should take five to ten minutes, not an hour.

Field	What to look for
Company context	Size, industry, geography, product, customer type.
Trigger	Hiring, funding, expansion, compliance deadline, new market, new role, visible growth.
Role context	What this person likely owns and what they may not control.
Current tool guess	Competitor, spreadsheet, agency, internal system, manual process, or no tool.
Pain hypothesis	The specific workflow pain you suspect.
Trust path	Why they might believe you enough to talk.
Must-learn question	The one question the call must answer.

The brief is not a script. It is a way to avoid lazy discovery. If your first question could be answered by reading their website for two minutes, you are wasting buyer patience.

Good discovery feels informed but not presumptuous. You can say:

I noticed you are hiring implementation managers, so I wondered if onboarding load is increasing. I may be wrong. How are you handling customer onboarding today?

This gives the buyer room to correct you while showing that the call is not generic.

Questions That Work

Use questions that reveal behavior:

• “Walk me through the last time this happened.”
• “What did you do before this tool/process existed?”
• “Who gets pulled in when it breaks?”
• “How do you measure whether this is working?”
• “What makes this painful enough to solve now?”
• “What have you tried already?”
• “Why did that not work?”
• “Who would need to agree before you change this?”
• “What would make you say this is worth paying for?”

Avoid asking only opinion questions:

• “Would you use this?”
• “Do you like this?”
• “Is this interesting?”

People are polite. Behavior is more reliable.

When To Demo During Discovery

Sometimes a short product glimpse helps the buyer understand the category. That is fine, but keep it controlled.

Say:

I can show one relevant workflow for two minutes, but I do not want to turn this into a feature tour before I understand your process.

Then return to discovery. If the founder cannot resist demoing, the call becomes performance instead of learning.

India Angle

Indian B2B discovery often involves informal decision paths. The user may influence but not approve. Budget may be verbal. Payment may require founder approval, finance, procurement, GST vendor setup, or a trusted reference.

For SMBs, the owner may not describe process formally. Ask for stories, screenshots, files, WhatsApp examples, invoices, or reports. The real workflow may live in Excel, Tally, WhatsApp, phone calls, and one trusted employee.

For enterprises, discovery should include procurement, security, legal, implementation, support expectations, and internal champion strength.

Questions that are especially useful in India:

• “Who signs vendor payments for this category?”
• “Will GST invoicing or vendor onboarding be needed?”
• “Does finance approve this before or after pilot?”
• “Would your founder/CFO/CTO need to see this?”
• “Is there an existing vendor we would replace or sit beside?”
• “Do you usually pay monthly, annual, or after implementation?”
• “What would make your team trust a new vendor?”

For SMBs and owner-led businesses, the real decision path may be a conversation with the owner, not a formal process. For enterprises, the opposite is true: a user may be enthusiastic, but procurement, security, legal, and finance can still take weeks or months.

For global buyers, assume trust is lower until proven otherwise. Crisp notes, calendar discipline, clear follow-up, security posture, and product proof matter more when the buyer has no local context for you.

Discovery Notes

Write notes immediately after the call while memory is fresh.

Use a simple structure:

Field	Good note
Pain	”Finance spends 2 days/month matching settlement reports from 3 marketplaces.”
Impact	”Month-end close delayed; founder reviews exceptions manually.”
Current workflow	”Excel + downloads from seller dashboards + bank statement checks.”
Buyer	”Finance head recommends; founder approves; CA checks GST treatment.”
Budget	”Currently pays agency 25k/month for finance ops support.”
Urgency	”New marketplace launch next month increases volume.”
Success criteria	”Cut reconciliation time by 50 percent and produce clean report.”
Objection	”Worried about integration effort.”
Next step	”Demo with finance head and founder Friday 11am.”

Bad notes are vague:

“Good call. Interested. Send deck.”

That is not pipeline intelligence. It is memory theater.

Discovery Debrief

After every serious call, take three minutes to debrief before moving to the next task.

Use this format:

Debrief question	Answer
What did we learn that we did not know before?
Is this real pipeline or research?
What was the strongest buying signal?
What was the strongest risk?
Which question did we avoid?
What should change in ICP, message, demo, product, or pricing?
What is the next step and date?

This habit is small but powerful. It turns sales calls into company learning. Without a debrief, founders often remember the emotional tone of a call, not the commercial truth.

Discovery Call Scorecard

After every discovery call, score the opportunity. The score is not for the investor update. It is for founder honesty.

Use a 0-2 score for each dimension:

Dimension	0	1	2
ICP fit	Outside target segment.	Adjacent fit.	Clear target segment.
Pain	Vague interest.	Recognized pain.	Repeated, specific, costly pain.
Current workaround	No current behavior.	Light workaround.	Active workaround with time, money, or risk cost.
Buyer access	Non-buyer only.	Influencer.	Economic buyer or clear path to buyer.
Urgency	No timing.	Some interest this quarter.	Trigger or deadline creates urgency.
Budget path	No budget owner.	Possible budget owner.	Clear budget owner or paid current alternative.
Trust path	No proof or relationship.	Some credibility.	Reference, strong proof, or trusted intro.
Next step	Vague follow-up.	Next step exists but weak.	Dated next step with purpose and owner.

Interpretation:

Score	Meaning	Action
0-5	Research, not pipeline.	Learn, then disqualify or nurture.
6-10	Possible opportunity.	Clarify missing buyer, pain, or timing.
11-16	Qualified opportunity.	Move to demo, pilot, proposal, or stakeholder meeting.

The score is a forcing function. If the founder cannot score the call, the call was probably too vague.

The Missing Question

At the end of every weak discovery call, ask yourself:

“What question did I avoid because I was afraid of the answer?”

Common avoided questions:

• “Who signs off on this?”
• “Is there budget for this?”
• “What happens if you do nothing?”
• “Why solve this now?”
• “Would you pay for a pilot?”
• “Who would block this?”
• “What would make you say no?”

The avoided question is often the question that would have saved the founder three weeks.

Disqualification

Disqualification is a sales skill.

Disqualify when:

• The company is outside the ICP.
• The pain is not painful enough.
• The buyer cannot identify a decision process.
• No one will commit time, data, or money.
• The prospect wants custom work unrelated to the product direction.
• The required trust or compliance bar is far beyond your current ability.

Be respectful:

Based on what you described, I do not think we are the right fit right now. The pain seems real, but it sounds like you need a custom services partner more than software. Happy to reconnect if that changes.

A clean no creates room for a better yes.

Qualification Exit Criteria

At the end of discovery, every opportunity should exit into one of four states.

State	Criteria	Next step
Qualified	Pain, buyer, urgency, budget path, and next step are clear.	Demo, pilot, proposal, or stakeholder meeting.
Research	Pain exists but buyer, urgency, or workflow is unclear.	More discovery with the right role.
Nurture	Fit exists but timing is weak.	Follow-up when trigger appears.
Disqualified	Pain, fit, budget, trust, or scope is not right.	Close politely and record reason.

Do not let “maybe” become a hidden fifth state. Maybe is expensive because it clutters the pipeline and drains founder attention.

Objection Library

Keep an objection library from discovery calls.

Objection	What to capture
Value	What outcome did they not believe?
Trust	What proof, reference, or security concern appeared?
Timing	What competing priority blocks action?
Budget	Which budget owner or threshold is missing?
Product	Which workflow gap blocks use?
Authority	Who else needs to be involved?
Implementation	What setup, data, integration, or training burden worries them?

Review the library every two weeks. Repeated objections should change the product, pitch, proof, ICP, or pricing. If the same objection appears for months and nothing changes, the sales process is not learning.

Decision Process Map

For qualified B2B opportunities, draw the decision process:

1. Problem owner recognizes pain.
2. Champion evaluates solution.
3. Buyer approves value and budget.
4. Risk owners review security, finance, legal, or operations.
5. Pilot or proposal is accepted.
6. Commercial terms are agreed.
7. Contract, PO, invoice, or payment process starts.
8. Implementation begins.

Even if the company is small, write the map. A deal slips when the founder discovers step 6 after celebrating step 2.

Mutual Action Plan

For qualified opportunities, create a mutual action plan. This is a simple shared plan that shows how both sides will reach a decision.

Use it when:

• The buyer says the problem matters.
• More than one stakeholder is involved.
• A pilot, security review, procurement step, or proposal is needed.
• The deal has a real commercial path.

Plan format:

Step	Owner	Date	Output
Discovery recap	Founder		Written summary of pain, impact, and goals.
Workflow demo	Founder + user		Confirm product fit and gaps.
Buyer review	Customer champion		Economic buyer sees value and risk.
Pilot scope	Both		Objective, timeline, success criteria, price.
Security/procurement	Customer owner		Approval path and blockers.
Commercial decision	Buyer		Yes, no, or specific next step.

The mutual action plan should not feel bureaucratic. It should feel like clarity. Serious buyers often appreciate it because it helps them manage internal stakeholders. If a prospect refuses every concrete step, the deal may not be real.

Champion Building

In many B2B deals, the person who likes the product is not the person who can buy it. The founder’s job is to help a real champion make the internal case.

A champion is not someone who says “interesting.” A champion:

• Owns or strongly feels the pain.
• Has credibility inside the company.
• Can explain the value in their own words.
• Will introduce you to the buyer or approver.
• Will tell you the truth about blockers.
• Has something to gain if the problem is solved.

Use discovery to test whether a champion exists.

Ask:

• “If this worked, who else would care?”
• “Who would need to approve it?”
• “How would you explain the value internally?”
• “What objection would your finance or leadership team raise?”
• “Would you be comfortable introducing me to the person who owns that decision?”

If the prospect refuses to introduce you after several useful conversations, they may be interested but not a champion. Record that honestly.

Common Mistakes

• Pitching immediately.
• Asking questions only to set up your pitch.
• Accepting “interesting” as buying intent.
• Ignoring budget.
• Not asking who decides.
• Selling to non-buyers.
• Ending without a dated next step.
• Not writing notes right after the call.
• Turning frameworks into interrogation.
• Avoiding budget and authority because it feels impolite.
• Believing a demo request means the opportunity is qualified.
• Accepting vague success criteria for a pilot.
• Not asking what happens if the problem remains unsolved.

Reader Action

Before your next five calls, write three must-learn questions:

• One about current workflow.
• One about impact.
• One about decision process.

After each call, record:

• Pain.
• Current behavior.
• Impact.
• Buyer.
• Timeline.
• Next step.
• Disqualification reason, if any.

Your pipeline quality will improve faster than your pitch.

After five calls, review patterns:

• Which pain repeated?
• Which segment had the strongest impact?
• Which role understood the problem fastest?
• Which objection appeared most often?
• Which calls had real next steps?
• Which calls should have been disqualified earlier?

Update your ICP, outreach, demo, and pricing based on the answers. Discovery is where your sales system learns.

Discovery Call Exit Memo

After every serious discovery call, write a short exit memo before memory fades.

Field	Notes
Customer situation	What is happening in their business now?
Pain	What problem did they describe in their own words?
Impact	What does the problem cost in time, money, risk, or lost growth?
Current workaround	How do they solve it today?
Buyer map	User, champion, economic buyer, approver, blocker.
Urgency	Why now, or why not now?
Budget path	Existing budget, new budget, founder approval, finance, procurement.
Success criteria	What would make them say the solution worked?
Next step	Dated action owned by a person.
Sales learning	What should change in ICP, message, demo, product, or price?

This memo should be short enough to complete in five minutes. If the founder cannot fill it, the discovery call was too vague.

Discovery Red Flags

Watch for:

• Prospect cannot describe current behavior.
• Pain is interesting but not costly.
• No one owns the problem.
• Buyer will not join future conversations.
• Timeline is “sometime this year.”
• Success criteria stay vague.
• Prospect wants a demo before sharing context.
• Every next step depends on “internal discussion” with no owner.

Red flags do not always mean stop. They mean slow down, qualify harder, and avoid treating the opportunity as real pipeline.

Qualification Score

After discovery, score the opportunity before moving to demo or proposal.

Dimension	0	1	2
ICP fit	Poor fit	Adjacent fit	Clear fit
Pain	Vague	Real but not costly	Recent, repeated, costly
Buyer	Unknown	Influencer/user	Budget owner or clear path
Urgency	No timing	Possible future timing	Trigger or deadline exists
Current workaround	Unknown	Described loosely	Specific workflow/artifacts seen
Success criteria	Vague	Partly defined	Measurable and agreed
Next step	None	Soft follow-up	Dated action with owner

Interpretation:

Score	Meaning	Action
0-5	Weak opportunity.	Disqualify or continue discovery only if learning value is high.
6-9	Possible opportunity.	Clarify buyer, urgency, and success criteria before demoing.
10-14	Strong opportunity.	Move to demo, pilot, proposal, or buyer meeting.

This score is not bureaucracy. It keeps the founder from demoing to everyone who is polite.

Stakeholder Map

Many Indian B2B sales conversations start with one friendly person but close through several people.

Map stakeholders:

Role	Person	What they care about	Risk/blocker	Next action
User		Workflow, usability, time saved.	Adoption effort.
Champion		Internal win, problem solved.	Political risk.
Economic buyer		ROI, cost, priority.	Budget and timing.
Technical approver		Security, integrations, data.	Implementation risk.
Finance/procurement		Price, terms, vendor process.	Payment and compliance.
Founder/owner		Business outcome, trust, speed.	Confidence in vendor.

If the map has only one name, the deal is fragile. Ask who else needs to be involved before the customer can say yes.

Discovery-To-Demo Gate

Move to demo only when these are true:

• You can state the pain in the customer’s words.
• You know the current workaround.
• You know who decides or who must be involved.
• You know what outcome the demo should prove.
• There is a reason the prospect should act now.
• There is a next step you can ask for after the demo.

If these are missing, say:

Before I show the product, I want to understand one more thing so I do not waste your time. How is this handled today, and who would need to be involved if you wanted to change it?

That sentence often saves founders from beautiful but useless demos.

Discovery Truth Table

After discovery, classify the opportunity honestly. This prevents the founder from treating every friendly call as a deal.

Discovery truth	Meaning	Next move
Strong pain, buyer path, urgency, success criteria	Real opportunity.	Demo, pilot, proposal, or buyer meeting.
Strong pain, no buyer path	Useful but incomplete.	Ask for buyer/approver meeting before heavy work.
Strong user pain, weak business impact	Product learning, not yet sales pipeline.	Continue discovery or nurture.
Interest but no current workaround	Curiosity may be higher than urgency.	Ask what happens if nothing changes.
Budget unclear but value clear	Commercial path needs discovery.	Discuss budget category and approval process.
Success criteria vague	Pilot or demo may drift.	Define success before next step.
Wrong segment but interesting problem	Research signal.	Record learning, avoid roadmap distraction.
No pain, no urgency, no owner	Not pipeline.	Disqualify cleanly.

Discovery Close

End the call with one of four closes:

• Advance: “It sounds like this is active and worth a focused demo with [person] by [date].”
• Clarify: “Before I show the product, we need to understand who owns this decision.”
• Nurture: “This does not sound urgent now. What would make it worth revisiting?”
• Disqualify: “I do not think this is a fit right now, and I do not want to waste your time.”

Clear closes create trust. Vague closes create fake pipeline.

Commercial Qualification Layer

Discovery should understand the problem, but it must also uncover whether the problem can become a deal. Add a commercial layer after you understand pain.

Ask these questions naturally:

Area	Question	What it reveals
Current spend	”How do you handle this today, and what does that cost in tools, people, time, or errors?”	Whether budget or hidden spend exists.
Cost of inaction	”What happens if nothing changes for the next 6 months?”	Whether urgency is real.
Decision owner	”Who would need to be involved if you wanted to change this workflow?”	Buyer map.
Approval path	”How do you normally approve a new tool or vendor like this?”	Process and friction.
Budget category	”Would this come from operations, sales, finance, IT, founder budget, or another bucket?”	Where money lives.
Timing	”Is there a deadline, target, audit, hiring plan, launch, or customer pressure behind this?”	Trigger strength.
Proof	”What would you need to see before trusting a new company with this?”	Trust path.
Success	”What result would make you say this was worth paying for?”	Pilot or proposal criteria.

Do not interrogate. Earn the right to ask by first showing that you understand the workflow. Commercial questions land better after the prospect feels heard.

Deal Confidence Score

After each discovery call, score the opportunity from 0-2 on each dimension:

Dimension	0	1	2
Pain	Vague interest.	Specific pain.	Recent, costly, repeated pain.
Buyer	User only.	Buyer suspected.	Buyer identified or involved.
Urgency	No timeline.	Soft priority.	Active trigger or deadline.
Budget	Unknown.	Budget category likely.	Spend, approval, or paid pilot path visible.
Fit	Custom or unclear.	Some fit.	Strong ICP and repeatable workflow.
Trust	No proof path.	Some proof needed.	Clear proof path and willingness to engage.
Next step	Vague.	Possible follow-up.	Dated next step with owner.

Interpretation:

• 11-14: real opportunity, advance.
• 7-10: promising but incomplete, clarify before heavy work.
• 4-6: learning call, not pipeline yet.
• 0-3: disqualify or nurture.

This score is not perfect, but it protects the founder from emotional pipeline. If a deal cannot score well after discovery, the next step should be more discovery, not a proposal.

Multi-Stakeholder Discovery

For B2B deals, one call is rarely enough. Each stakeholder sees a different risk:

Stakeholder	What they care about
User	Daily effort, usability, speed, quality.
Manager	Output, visibility, team adoption, accountability.
Buyer	ROI, budget, urgency, risk, alternatives.
IT/security	Access, data, integration, reliability.
Finance/procurement	Price, terms, vendor process, payment.
Founder/owner	Trust, strategic importance, cash flow, control.

Your job is not to pitch the same story to everyone. Your job is to learn each person’s risk and connect the product to the shared business outcome.

Discovery Call Operating Script

A founder does not need a robotic script, but a clear structure prevents rambling.

Use this flow:

Stage	Purpose	Sample language
Open	Set context and earn permission.	”I would like to understand how this works today before I show anything. If it is not a fit, I will say so.”
Recent incident	Move from opinion to reality.	”Can you walk me through the last time this caused a problem?”
Workflow	Understand steps, people, tools, and handoffs.	”What happens before and after this step?”
Impact	Quantify pain without forcing fake numbers.	”Where does this show up as time, money, risk, delay, or customer impact?”
Current workaround	Learn competition.	”How do you handle it today?”
Ownership	Map decision path.	”Who owns improving this workflow?”
Timing	Find urgency.	”Why is this worth solving now rather than later?”
Proof	Learn trust requirements.	”What would you need to see before changing the current process?”
Close	Choose next step honestly.	”Based on this, I think the useful next step is…”

The founder should talk less as the call gets deeper. Early explanation is fine, but the value is in the customer’s story.

Discovery Notes Format

Good notes are short, factual, and reusable. After each call, write:

Company/person:
Segment:
Role:
Recent incident:
Current workflow:
People involved:
Tools/workarounds:
Impact:
Trigger:
Buyer/approver:
Budget path:
Trust requirements:
Objections:
Exact customer language:
Next step:
Confidence score:

Keep exact customer language separate from founder interpretation. “We waste time reconciling invoices” is different from “they need finance automation.” The first is evidence. The second is a hypothesis.

Discovery Anti-Patterns

Anti-pattern	What it sounds like	Why it hurts
Pitch-first discovery	”Let me show you what we built.”	You bias the call before learning the problem.
Leading questions	”Wouldn’t this save your team time?”	You teach the customer the answer.
Future fantasy	”Would you use this if it existed?”	People are generous about imaginary behavior.
Feature polling	”Which features do you want?”	Customers describe symptoms, not always good products.
Avoiding money	”We will talk pricing later.”	You postpone the hardest truth.
Accepting vague next steps	”Let’s stay in touch.”	Pipeline becomes fiction.
Overstaying a bad fit	More calls with no owner or urgency.	Founder time gets diluted.

If a call is going nowhere, politely disqualify. Good sales discipline is also good product discipline.

India-Specific Discovery Realities

Discovery in India often mixes formal and informal signals:

• Buyers may not directly say “no”; they may slow down.
• WhatsApp follow-ups may be more effective than email for some SMB segments.
• The person who feels the pain may not control payment.
• Trust may come from founder reputation, mutual connections, references, or in-person meetings.
• Procurement may be informal until it suddenly becomes formal.
• Payment timing can reveal seriousness better than verbal enthusiasm.
• Family businesses may involve advisors, relatives, CAs, or long-time operators in decisions.

This does not mean the founder should become casual. It means the founder should be warm and precise at the same time: clear recap, clear next step, clear owner, clear date.

Discovery Call Control Points

A good sales discovery call has control points. These are moments where the founder checks whether the conversation is still moving toward truth and a real next step.

Moment	Control question
Opening	”Is it okay if I ask about your current workflow before showing anything?”
Pain	”When did this last happen?”
Impact	”What did that cost in time, money, risk, or missed revenue?”
Owner	”Who is responsible when this goes wrong?”
Current solution	”What do you use today, and what is not working?”
Decision process	”If this looked useful, what would happen next internally?”
Budget	”Is this a problem you would solve with software, service, hiring, or not at all?”
Close	”Based on this, should we move to a demo, involve someone else, or stop here?”

Control does not mean dominating the call. It means protecting both sides from vague enthusiasm.

Call-To-Next-Step Ladder

Do not end every discovery call with the same CTA. Match the next step to the evidence.

Evidence from call	Best next step
Pain is vague	Ask for another example or speak to a closer user.
Pain is real but buyer unknown	Ask for buyer or approver intro.
Buyer is present but impact unclear	Build a quick ROI or cost-of-pain estimate together.
Workflow is complex	Ask for artifact review or process walkthrough.
Trust barrier is high	Offer reference, security note, founder-led pilot, or small controlled test.
Problem and buyer are clear	Schedule focused demo or pilot design call.
Timing is weak	Agree on trigger-based follow-up.
Bad fit	Disqualify politely and ask one learning question.

The best next step should create more evidence or move the deal closer to a decision. “Let us stay in touch” does neither.

Mutual Next-Step Note

After a serious discovery call, send a short mutual next-step note. This tests whether the prospect agrees with your understanding and whether they are willing to move.

Use this format:

Thanks for the conversation. My understanding is:

Problem:
Current workflow:
Impact:
People involved:
Why now:
Proof needed:
Open questions:

Suggested next step:
Owner on your side:
Owner on our side:
Date:

The note does three things:

Benefit	Why it matters
Confirms pain	The prospect can correct your interpretation before you build or propose.
Reveals seriousness	Serious buyers engage with next steps; vague interest often fades.
Creates internal artifact	Champions can forward the note to buyers, finance, IT, or founders.

If the prospect does not respond, do not immediately assume rejection. Follow up once with a useful question. If there is still no movement, move the account to nurture or disqualify. Pipeline should not depend on silent hope.

Related Links

• 56. Founder-Led Sales
• 60. Demos and Pilots
• 18. Customer Discovery Fundamentals
• 138. Founder Sales Call Playbook