Discovery calls that close

A client has replied to your pitch with "Can we jump on a call?" You have 30 minutes to find out if this is real work, at a price you can live with, and to leave them wanting your proposal.

A discovery call has two jobs. You decide whether the project is worth doing, and the client decides whether you are the person to do it. Anything that does not serve one of those can wait for the kickoff.

Before the call: ten minutes of homework

Look at the client's website, their LinkedIn page and the LinkedIn profile of the person you are meeting. If they have hired freelancers before (an Upwork history, a "work with us" page, an old agency credit), note it. The playbook on researching a client's budget has quicker ways to estimate what they can spend.

Write down three or four questions specific to them. "I saw you launched in Pune last quarter. Is this project tied to that?" tells the client you did the reading, and it gets better answers than a generic opener.

Check the boring things too: your link works, your camera is on, and you are in a quiet room. Join two minutes early.

The 30-minute agenda

Share this in the calendar invite so the client knows the call has a shape.

1. 1

   Step 1: Context

   5 minutes

   Who you are in two sentences, then ask what they are working on and why now. Keep the small talk short and real; one question about their launch beats a minute on the weather.

2. 2

   Step 2: Their side of the story

   15 minutes

   The problem, who it affects, what they have tried, what done looks like and when they need it. You mostly listen and take notes. Ask "what else?" before moving on.

3. 3

   Step 3: Your questions

   7 minutes

   Budget range, who decides, who else is involved, how they will judge the result. This is where most freelancers go quiet; do not.

4. 4

   Step 4: Next steps

   3 minutes

   Agree what happens next and by when: "proposal by Thursday, 30-minute walkthrough on Friday", or "not a fit, and here is why".

If the client runs over in part two, cut your pitch, not your questions. They can read about your work later; you cannot quote without the answers.

Questions that surface budget and the decision-maker

Budget is the question people skip, and then they spend a weekend on a proposal for ₹2 lakh when the client had ₹40,000. Ask it plainly once you understand the problem.

• "Do you have a budget range in mind, or are we scoping to fit?"
• "What did you spend the last time you hired someone for something like this?"
• "If the proposal came in around ₹75,000, would that be in the right range, or should I plan a smaller first phase?"

The third one works when the client will not name a number. You anchor with a realistic figure based on the scope you just heard, and their reaction tells you most of what you need. The pricing playbook covers how to arrive at that number.

The decision-maker matters as much as the budget. The person on the call is often a manager who will forward your proposal to a founder or a finance head.

• "Who else will look at the proposal before you decide?"
• "Is there anyone whose sign-off we need, like finance or legal? And have you hired for this before, by comparing quotes or after one conversation?"

If the real decider is not on the call, ask for 15 minutes with them before you send the proposal, or offer to walk them through it. A proposal forwarded without you loses most of its context.

Two more questions are worth asking on almost every call: "What would make this project a success six months from now?" and "Is there a date this has to be live by, and what happens if it slips?" The first gives you the language for your proposal. The second tells you whether the deadline is real.

Things to name on the call, not later

Some problems are cheaper to raise now than to discover in week three.

If several people are involved and none of them is on the call, ask who decides, and ask to meet them.

If you hear "We'll know the budget once we see your proposal", either they lack budget authority or they are collecting quotes. Ask which, kindly: "Are you comparing a few options? That's fine, it helps me pitch the right scope."

If the deadline is two weeks for six weeks of work, say it out loud: "I can do the landing page in two weeks, or the full site in six. Which matters more?" Clients rarely resent this. They resent finding out on day ten.

If you hear more than one of these, read the client red flags playbook before you quote.

Closing questions that ask for the work

Many calls end with "Great, I'll send something over" and then drift. Close by asking for a commitment that fits where the client is.

When they are clearly keen, assume the yes and plan: "Shall I pencil in a kickoff for Monday the 14th, so you have the first draft before Diwali?"

When something is holding them back, bring it out: "Is there anything about the approach or the timeline you're unsure about?" If they say no, that is your cue to move to next steps. If they name something, you have found the real objection.

When there are two sensible options, offer a choice between them rather than a yes or no: "Would you rather start with the homepage only, or do the full five pages in one go?"

When the deal is close, spell out what starting looks like: "To start on the 14th I need the signed SOW and the 40% advance. I'll send both today."

Do not offer a discount to close. If price comes up, the price pushback playbook has scripts that trade scope instead of cutting your rate.

The recap email, sent the same day

Send this within a few hours, while the client still remembers the call. It is the document they will forward to the people who were not there.

Subject: Recap: {{project name}} call, {{date}}

Hi {{name}},

Thanks for the time today. Here is what I took away, so we are working from the same page:

What you need: {{one or two sentences in their words}}
Why now: {{the trigger they mentioned}}
What success looks like: {{their measure, e.g. "demo bookings from the site rather than traffic"}}
Timeline: {{live by date}}, with {{any fixed dates}}
Budget: you mentioned {{range}}; I'll scope the proposal to fit
Who decides: you and {{name/role}}

Next step: I'll send a proposal with two scope options by {{day, date}}. Could we take 20 minutes on {{day}} to go through it with {{decider}}?

If I've got anything wrong above, just reply and correct me.

{{your name}}
{{phone}}

If the client goes quiet after the proposal, use the sequence in following up after a proposal. The proposal playbook covers what to put in the proposal itself.

Walking away without burning the bridge

Sometimes the call tells you no. Say it the same day, give a specific reason, and leave the door open.

Hi {{name}},

Thanks for walking me through {{project}}. Based on what you described, I don't think I'm the right fit right now: {{specific reason, e.g. "you need daily on-site support in Gurugram and I work remotely from Kochi"}}.

If it helps, I can introduce you to {{name}}, who does exactly this. And if the scope changes, I'd be glad to talk again.

{{your name}}

A specific reason reads as honest. "Not a fit" on its own reads as if you are hiding something, and clients remember who was straight with them.

If you only do one thing after reading this, ask about budget and the decision-maker on your next call, before the last three minutes.