# Discovery call

> The first conversation before any proposal — where scope, budget reality and fit get established instead of guessed.

The discovery call exists because written requirements lie by omission: the brief says 'a shop' and means 'a shop that syncs with the warehouse we forgot to mention'. Thirty minutes of questions surfaces what the document left out — the actual goal (usually not 'a website' but 'more orders'), the constraints, the budget range, the decision process, and whether the two sides can work together at all.

A good one ends with both sides knowing what happens next: the engineer knows what to price and what to warn about, the client knows the rough shape and cost of the path. A call that ends in a proposal for the wrong thing was not a discovery, it was a formality — the point is the questions, not the meeting.

## Related terms

- https://dfieldsolutions.com/en/glossary/mvp.md
- https://dfieldsolutions.com/en/glossary/retainer.md
- https://dfieldsolutions.com/en/glossary/social-proof.md

---

Source: https://dfieldsolutions.com/en/glossary/discovery-call
DField Solutions — Dunakeszi, Hungary — dezso@dfieldsolutions.com
Booking: see https://dfieldsolutions.com/en/contact