What Discovery Calls Actually Reveal (Beyond the Pitch)

Published

10 Jun 2026

Author

Akash Shakya

A discovery call is not a sales conversation. It is a diagnostic conversation. The best discovery calls reveal more about the founder's readiness than about the agency's capability.

Editorial note: Founder quotes throughout this article are composites drawn from multiple EB Pearls engagements. The numbers and decisions are real. Identifying details have been changed.

Why We Wrote This

Most founders approach discovery calls as interviews where they evaluate the agency. That is half the equation. A well-run discovery call is bidirectional: the agency is evaluating whether the project is one they can deliver successfully, and the founder is evaluating whether the agency understands their problem deeply enough to solve it.

This article reveals what experienced agencies look for on discovery calls, what the best founders share, and how to extract maximum signal from a 60-minute conversation.

Introduction: The Discovery Call as Diagnostic

At EB Pearls, we have conducted over 2,000 discovery calls across 20 years. The pattern is consistent: the quality of the discovery call predicts the quality of the engagement with 80% accuracy. Not because discovery calls are magic. Because discovery calls reveal the three things that determine project success: problem clarity, constraint honesty, and decision-making readiness. For more, see the questions great founders answer before building.

Industry surveys consistently find that a majority of business and IT executives anticipate their software projects will fail from the outset. The discovery call is the first opportunity to break that pattern. If the founder cannot articulate the problem, the constraints, and the decision criteria in 60 minutes, the project is not ready for development, regardless of budget.

"We had a discovery call with a founder who opened with: 'I want to build the Uber of pet care.' I asked five basic questions about the customer, the problem, and the evidence. The founder could not answer any of them with data. The idea was 48 hours old. We recommended 4 weeks of customer discovery before a Discovery Workshop. The founder went to another agency, spent AU$95K on an MVP, and shut it down after 90 days with 23 users. The discovery call had revealed everything."

What Experienced Agencies Listen For

Signal 1: Problem Specificity

"I want to build an app" is not a problem. "Service businesses in Sydney with 5 to 20 employees waste 6 hours per week on manual scheduling because existing tools are designed for enterprises, not SMBs" is a problem. The specificity tells the agency whether the founder has done customer discovery or is working from an assumption. For more, see the true cost of waiting.

Problem specificity predicts scope accuracy. Founders with specific problems produce specific scope documents. Founders with vague problems produce vague scope documents, which produce scope creep.

Signal 2: Constraint Honesty

Founders who withhold their budget range ("I do not want to anchor you") create a problem for both parties. The agency produces a proposal that may be 3x the budget, wasting both parties' time. Or the agency lowballs to win the engagement and makes up the difference with scope reduction or change requests. For more, see why work with EB Pearls.

The honest answer: "My total budget is AU$80K to $120K, and I need something usable by September." That answer lets the agency scope the project to fit reality. Budget honesty is not weakness. It is efficiency.

Signal 3: Decision-Making Authority

Who is on the call? If the decision-maker is not present, the discovery call is a screening call, not a discovery call. Screening calls are fine, but they should be labelled accurately. The real discovery happens when the person who can say yes is in the room.

At EB Pearls, we ask early: "Who will approve the Locked Scope Document, the budget, and the timeline?" If that person is not on the call, we schedule a follow-up with them before proceeding.

"The most revealing moment in any discovery call is when we ask: 'What happens if the MVP data tells you the core assumption is wrong? Do you have budget to pivot, or is this a one-shot build?' Founders who have thought about this answer quickly and specifically. Founders who have not thought about it pause, and that pause tells us the project needs more Phase 1 work before it is ready for Phase 2."

Non-Obvious Truth: The Best Discovery Calls End with 'Not Yet'

The most valuable outcome of a discovery call is sometimes the recommendation to delay. A founder who needs 4 more weeks of customer discovery, or 2 weeks of competitive analysis, or a co-founder conversation about budget is better served by delay than by a premature engagement. At EB Pearls, roughly 20% of discovery calls result in a 'not yet' recommendation. Those founders, when they return, produce the best projects.

What Founders Should Ask (And What the Answers Reveal)

What is the worst project you have delivered?
This question tests self-awareness. Agencies that claim 100% success are either lying or not taking on challenging work. The best answer describes a specific failure, the root cause, and what changed. For more, see the Discovery Workshop.
How do you handle scope changes mid-project?
This question reveals process maturity. Good answer: written change request, 3D estimate, trade-off decision. Bad answer: 'We are flexible.'
Who from your team will I interact with daily?
This question reveals team stability. If the answer is a project manager you will never meet the developers, that is a relay model, not an embedded model.
What do you need from me to succeed?
This question reveals partnership orientation. Good answer: 'Your time for 2 to 3 hours per week, fast decisions, and honest feedback.' Bad answer: 'Just the requirements.'
Can I speak to a client whose project went over budget?
This question reveals transparency. Every agency has projects that went over. The question is whether they let you hear the story from the client's perspective.

The Discovery Call to Discovery Workshop Pipeline

A well-run discovery call naturally leads to one of three outcomes:

Outcome 1: Discovery Workshop proposal. The problem is validated, constraints are clear, and the decision-maker is ready. The workshop is the next step. For more, see the first build mistake.

Outcome 2: Not yet. The problem needs more validation, the constraints are unclear, or the decision-maker is not aligned. The recommendation is specific pre-work with a timeline to revisit.

Outcome 3: Not a fit. The project needs a different type of partner (industry specialist, in-house team, different technology stack). A transparent decline is more valuable than a forced fit.

Red Flag: Agencies That Quote on the First Call

If an agency provides a budget estimate on the discovery call without a Discovery Workshop, scope document, or detailed requirements, the estimate is a guess. Guesses become change orders. Ask: 'What is this estimate based on?' If the answer is 'similar projects,' ask: 'What makes my project similar to those projects?'

Problem articulated with specificity: who, what, current workaround, market size
Budget range shared honestly (not withheld to avoid anchoring)
Decision-maker present on the call
Timeline and constraints communicated
Founder asked about failures, not just successes
Next step is clear: Discovery Workshop, pre-work, or decline

Frequently Asked Questions

What is the purpose of a discovery call?

To determine fit, not to sell. A good discovery call surfaces the founder's real constraints, timeline, budget, risk tolerance, and decision-making patterns. Both parties should leave knowing whether to proceed.

How long should a discovery call last?

45 to 60 minutes. Shorter calls lack depth. Longer calls indicate either poor structure or that the call has become a free consulting session.

How long does each phase take?

Your customer evidence (who has the problem, how many, willingness to pay). Your constraints (budget range, timeline, technical). Your decision criteria (what matters beyond cost). Your questions (ask about their failure rate, not their success rate).

What are red flags on a discovery call?

The agency talks more than they listen. They quote before understanding scope. They guarantee outcomes. They do not ask about your users. They skip questions about budget (they will surprise you later).

Should I do multiple discovery calls with different agencies?

Yes. 3 to 5 calls gives you calibration. You will recognise quality questions from weak ones, and you will see which teams genuinely try to understand your problem versus which are running a sales script.

Free Founder Resources

Discovery Call Preparation Checklist (PDF)
Everything to prepare before a discovery call: problem statement, customer evidence, constraints, decision criteria, and questions to ask.
Agency Evaluation Scorecard (Google Sheets)
Score agencies across 10 dimensions after discovery calls: problem understanding, process maturity, team structure, transparency, and fit.
Red Flag Reference Card (PDF)
One-page list of discovery call red flags with explanations and alternative questions to ask.

Final Thought

A discovery call is the cheapest diagnostic in software development. 60 minutes that reveal whether the project is ready, the team is right, and the fit is genuine. The founders who treat discovery calls as evaluations instead of pitches build better products with better partners.

The most important thing a discovery call can reveal is that you are not ready yet. That revelation, at minute 45, saves you six figures at month 6.

Akash Shakya Chief Operating Officer and Co-Founder

Discover app development insights and AI trends with Akash Shakya, COO of EB Pearls. Learn how we build successful digital products.

Start your project with the right foundations

Book a Free Consultation

5.0

Most of the decisions that determine long-term product success are made in the first few weeks. Book a discovery call and we'll show you exactly what Built to Last™ looks like applied to your project.