Founder-led discovery calls are working sessions for learning whether a problem deserves product attention and whether a person has reason to act. Run them as diagnosis first: ask, listen, test the cost and urgency, then decide what the conversation earned. The useful surprise is that a call can succeed by changing your understanding of the market or product, even when it produces no near-term buyer. Guy Podjarny used early conversations to understand what it meant to build a developer-tooling company and how that differed from a cybersecurity company.1 That gives a founder a wider job than qualification.
Before the call
Start with what you need to learn, then decide who to call. A founder-led call works best when the learning target is clear before the conversation begins.
Customer discovery happens before you build anything significant and is intended to reduce the risk of investing time and money.2 Preparation before the call determines the quality of what you learn, so know the prospect's business beforehand and leave knowing their pain.3 With the default manual path, aim to speak with around 30 potential customers while looking for pain and pull.4
Write a short note for each call with the problem you want to test, the part of the workflow you need to understand, and the product decision the answer could change. Keep the note open during the conversation. At the end, you should be able to say what you learned, what remains unclear, and whether the opportunity deserves another conversation.
Open the call
Set a frame that gives the other person a reason to explain their situation. Keep the opening short enough that the call gets to the customer's world quickly.
Plan two minutes for the introduction and agenda.5 A discovery call is a diagnostic conversation. Your job is to ask questions, listen, and hold product talk until you understand the situation.6 Founders do not need to sound like stereotypical salespeople to become good at discovery.7
Say what you want to understand and check that the topic is relevant. Ask what prompted the conversation, what they hoped to cover, and whether it makes sense to spend the time on that problem. Then stop explaining and let them answer. Move on when they have accepted the frame and started describing their own situation.
Diagnose the problem
Make the prospect describe the problem in their own words before you test your explanation. You are looking for the event, process, or failure that creates enough friction to deserve action.
Every discovery call should uncover the real problem, its cost, and who decides to fix it.8 Ask where the problem appears, how the team handles it today, what happens when the current approach fails, and who feels the consequences. Follow an interesting answer with "Tell me more" or "What happens next?" so you learn the sequence instead of collecting a label.
Listen for concrete effects and ownership. If the answer stays at a general complaint, keep asking about the last time it happened. Move on when you can state the problem plainly, explain what it costs, and identify the person who can approve a change.
Test urgency and fit
Pain gives you a topic. Urgency tells you whether the topic can support a buying decision soon.
Customer interviews only work when you listen for urgency.9 Ask: "Is this buyer curious, or are they ready to change how their business operates?"10 Look for a recent trigger, a consequence they already feel, or a change they have committed to making. Curiosity can produce useful learning, while readiness gives the conversation a path to action.
A discovery call should establish whether the prospect has a problem the business can solve and whether the prospect is a good fit.11 Determine how close they are to investing so you can qualify out prospects and avoid wasting time.12 Disqualifying a bad prospect saves as much time as qualifying a good one.13
Ask what happens if they leave the problem alone, what they have tried, and what would need to change for action to become worthwhile. Move on when you know whether the issue is active, whether the person wants change, and whether the business can help with the problem they described.
Shape the product question
Use the conversation to learn what the product must do for this segment. Feature requests are useful when you connect them to the problem and the outcome the customer wants.
Alex Kracov used calls to ask which features needed to be built to get the customer excited about the product.14 Having a founder or product team member lead these conversations can shift the discussion toward what the product does and does not do for a market segment.15
Ask what a workable solution would change in their day, what it would need to handle, and what would make them willing to use it. Record the capability, the problem behind it, and the customer type attached to it. This keeps the call connected to product decisions without turning the conversation into a feature pitch.
Close with a decision
A useful conversation needs a deliberate ending. Give the other person a clear choice about what happens after the learning is complete.
Every discovery call should end with a clear next step agreed to by both parties.16 Name the action, the person responsible, and the reason for doing it. Ask whether the proposed step makes sense, then confirm what each person will do before the next conversation.
If the problem is weak, the urgency is absent, or the product cannot address it, close the loop cleanly. A clear decision protects your time and keeps weak opportunities from shaping the product.
What not to do
The mistakes below make you talk before you learn. Remove them from the call plan before you start.
- Do not use scripted, unnatural questions.17
- Do not position your product before uncovering real pain or buying dynamics.18
- Do not show up to talk; founders and salespeople who talk more than they listen close fewer deals and never understand why.19
- Do not spend forty-five minutes telling the prospect what your company does when the prospect wants someone to understand the problem.20
- Do not carry your pre-call assumptions into the conversation; let go of expectations and discover what is true there.21
After the call
Turn what you learned into a decision while the details are still fresh. The point of founder-led discovery is to improve both the opportunity judgment and the product judgment.
After the conversations, the Stytch founders started building and launched quickly.22 Use your notes to decide whether to continue learning, pursue the opportunity, change the product question, or stop. Keep the customer's wording beside the product implication so later decisions stay connected to the problem that created them.
Take the next call with a learning target, a short frame, and questions that move from problem to cost, urgency, and decision. Leave with either a clear next step or a clear reason to stop pursuing the opportunity, then feed the product implication into the next build decision.