A great discovery call covers five areas — the real problem, the desired outcome, the budget, the decision process, and the working relationship — with about three questions each. Get those fifteen answers and the proposal practically writes itself, because you are describing their project back to them instead of guessing.

Why discovery quality decides proposal quality

Weak proposals are not a writing problem; they are an information problem. A freelancer who leaves the call knowing only "they want a new website" has to pad the proposal with generalities. A freelancer who knows the site exists to stop losing leads to a competitor, that success means twenty inquiries a month, and that the founder decides alone by Friday — that freelancer writes two specific paragraphs and wins. Here are the fifteen questions, grouped by what they unlock.

Understand the real problem (questions 1–3)

  • 1. "What prompted you to reach out now?" — The word now is the lever. Projects have triggers: a lost deal, a launch, a competitor move. The trigger is the real brief.
  • 2. "What have you already tried?" — Reveals dead ends to avoid, budget already burned, and how they think about solutions.
  • 3. "What happens if this does not get fixed?" — Surfaces the cost of inaction, which is the number your price will quietly be compared against.

Define the outcome (questions 4–6)

  • 4. "What does success look like six months after launch?" — Moves the conversation from deliverables to results, where your value lives.
  • 5. "How will you measure whether this worked?" — If they have a metric, build the proposal around it. If they do not, helping them pick one makes you the most strategic vendor they have talked to.
  • 6. "Is there an example — anyone's — of what great looks like to you?" — Calibrates taste cheaply and prevents an entire round of revisions later.

Surface the budget (questions 7–9)

  • 7. "What range have you set aside for this?" — Ask plainly. A proposal should confirm a number, never reveal one for the first time.
  • 8. "Is that budget for this project, or for everything this year?" — Distinguishes the project pot from the annual pot, and often uncovers phase-two money.
  • 9. "If the ideal version costs more than the range, do you want to see it anyway?" — Permission to propose the better option. Clients say yes to this question surprisingly often.

Map the decision process (questions 10–12)

  • 10. "Who besides you weighs in on this decision?" — Finds the hidden committee before it finds your proposal.
  • 11. "When do you want to make a decision?" — Creates a shared deadline and tells you exactly when to follow up.
  • 12. "What would make this an easy yes for you?" — The most underused question in freelancing. Clients will literally tell you what to put in the proposal.

Test the working relationship (questions 13–15)

  • 13. "Have you worked with a freelancer on something like this before? How did it go?" — Screens for red flags and reveals expectations shaped by past experiences.
  • 14. "Who will give feedback, and how quickly can you usually turn it around?" — Sets up your timeline dependencies before they become excuses.
  • 15. "Is there anything that worries you about this project?" — Invites the unspoken objection into the room, where you can answer it instead of losing to it silently.

From answers to proposal, fast

The call is only half the system; speed is the other half. Enthusiasm decays daily, so the proposal should land within 24 hours while the conversation is still warm. This is where structured discovery pays off twice: because you already know the problem, the outcome, the budget, and the decision path, the proposal is assembly rather than authorship. Tendrly is built for exactly this handoff — answer five questions with what you learned on the call and it produces a branded proposal with one clear price and a one-click Stripe payment link, so the client can go from reading to paid in a single step.

FAQ

How long should a discovery call be?

Thirty minutes covers all fifteen questions for most projects. Under twenty minutes, you are probably hearing symptoms rather than causes; over an hour, you have drifted into free consulting.

Should I share pricing on the discovery call?

Share a range once you understand the scope: "Projects like this usually land between $X and $Y." It filters mismatches immediately and makes the exact number in the proposal a confirmation, not a shock.

What if the client cannot answer the outcome questions?

That is useful data, not a dead end. Help them define success on the call — clients remember the freelancer who brought clarity, and fuzzy goals discovered late are the leading cause of "this is not what I expected."