How to run a discovery call before sending a price
A practical discovery call guide for founders: understand the buying problem, decision process and scope before preparing a useful proposal.
Muntaser Bin KamalPublished 
Before quoting, establish what triggered the request, what the buyer has tried, which deliverables matter, and who must approve the work. Summarize confirmed facts and unresolved assumptions, then agree on one next step. A discovery call succeeds when both sides can judge whether a proposal is appropriate.
- Ask about a recent situation before suggesting a solution.
- Separate confirmed requirements from assumptions that affect price or timing.
- Finish with a written recap and an agreed next step.
The request is the beginning of the conversation
A founder asks, “How much does a brand identity cost?” You could send a price immediately, but the request leaves important questions unanswered. Is this a new business, an existing brand expanding into retail, or a team struggling with inconsistent materials? Each situation may require different work.
You can still share an indicative range when your service has one. Explain the assumptions behind it and what would change the estimate. Discovery should help someone make a decision, not become a gate that prevents them from understanding affordability.
HubSpot’s discovery guide treats the conversation as a way to assess needs and fit before proposing work. The worksheet and scripts below are our practical recommendations, rather than a required sales framework.
Prepare a short agenda, not a presentation
Review the buyer’s public website, current offer and relevant materials. Record what you can observe separately from what you think those observations mean. A dated product page is visible evidence; assuming that it causes poor sales is an untested interpretation.
Open with a useful agreement: “I’d like to understand what prompted this, what needs to be ready, and how you’ll decide. Then we can see whether I can help and what information a proposal needs. Is there anything else you want to cover?”
Ask permission before recording. Written notes are often enough. Do not collect sensitive customer information when a description of the situation will answer your question. Leave room for the buyer’s questions about your process, availability and pricing.
Ask about the last real situation
Start with an event: “What happened recently that made you look for help?” Follow with, “Can you walk me through the last time this caused a problem?” These questions help distinguish an active need from a general wish.
Strategyzer’s customer interview guidance recommends learning from facts and listening before introducing solutions. Apply that principle without turning the call into an interrogation. Follow the answer that matters.
Useful prompts include:
- What were you trying to accomplish when the problem appeared?
- What did you do instead, and what happened next?
- Which part is manageable today, and which part keeps blocking progress?
- What would you need to observe to consider the work useful?
Avoid leading questions such as “Would a premium identity make customers trust you?” They invite agreement with your solution before the underlying problem is understood.
Turn the conversation into a decision map
Discuss consequences without exaggerating them. Ask what remains difficult if nothing changes, then confirm whether the buyer actually wants to address it now. A problem can be real without being the current priority.
Next, identify the practical constraints: launch dependencies, required files, languages, existing assets, internal responsibilities and approval process. Ask who will use the deliverables as well as who authorizes spending. A procurement contact and a day-to-day project owner may need different information.
| What you hear | What to clarify | Useful next move |
|---|---|---|
| “We launch soon” | Which date is fixed, and what depends on it? | Build a dependency list |
| “The partners need to agree” | What criteria will they use? | Include their requirements in the recap |
| “We need everything” | What must work on launch day? | Separate essential and later work |
| “We don’t know the budget” | Is there an affordability boundary or approval threshold? | Explain options and their assumptions |
This is an editorial decision aid. It is not a scoring system that predicts whether someone will buy.
Talk about money without making it a test
Explain why you are asking: “To avoid proposing something that cannot work financially, is there a range you have allocated, or a ceiling we should respect?” Let the buyer decline to answer. You can then explain your minimum engagement or the variables that determine cost.
Do not treat a small budget as evidence that someone is unserious. It may mean that the work needs phasing, that a simpler service fits, or that another provider is a better match. Equally, do not promise the full outcome before knowing whether the constraints allow it.
If the buyer asks for an exact figure now, name what you can price reliably and what remains conditional. Our guide to identity costs can help prepare that discussion. A clear boundary is more useful than an artificially precise quote.
Worked example: a launch in six weeks
Consider a hypothetical food brand planning its first retail launch in six weeks. The founder requests a new logo and packaging. This example does not represent a client result or a recommended delivery promise.
During discovery, you learn that the printer needs approved artwork in three weeks, product information is incomplete, and a distributor must review the pack. The important constraint is not simply “six weeks.” It is the earlier artwork deadline and the missing inputs.
A helpful recap would say: “The immediate need is an approved pack for one product. The printer deadline is confirmed; ingredient copy and distributor feedback remain outstanding. We need to check production specifications before committing to delivery.”
Possible next steps include a narrower launch scope, a revised schedule, or a paid consultation to resolve uncertainty. None should be presented as guaranteed feasible until the relevant dependencies are checked. Use the first brief checklist to organize those inputs.
Close with a recap the buyer can correct
Use three headings in your notes: confirmed, assumed and unresolved. Under confirmed, record statements the buyer actually made. Under assumed, list interpretations awaiting agreement. Under unresolved, identify information needed and who will provide it.
Finish with: “Here is what I understood. Your priority is X, success would look like Y, and Z still needs checking. What have I misunderstood?” Then agree on a deliverable, its owner and the next contact. That may be a proposal review, an introduction to another decision maker, or a decision to pause.
Send a concise summary through the channel the buyer agreed to use. Do not describe politeness, interest or verbal enthusiasm as an accepted proposal. The proposal follow-up guide covers what happens after a suitable offer is sent.
Use the next call to improve your process
Before your next conversation, write five questions that address your actual uncertainties. During it, notice when you start presenting before understanding the answer. Afterwards, check whether your notes could support a scoped proposal without inventing missing facts.
Common errors are asking every question mechanically, treating budget as the only qualification, diagnosing commercial problems without evidence, and ending with “I’ll send something” when neither side knows what happens next.
If the scope remains unclear, build a clear offer around one agreed problem before adding deliverables. If the founder needs help deciding what branding work to prioritize, a brand consultation can provide a focused next step. The purpose of discovery is a better decision for both sides, including a respectful decision not to proceed.
How this guide was prepared
Prepared with AI assistance for research, structure and drafting. Linked sources support the documented principles. Worksheets and suggested tests are editorial recommendations; numerical examples are hypothetical, not client results. No external review or measured business outcome is claimed.
