An enquiry lands: "We need a new website, can you share a quote?" That could be a ₹15,000 job for a local clinic or a ₹5 lakh job for a funded D2C brand. Quote too low and you are stuck doing a big project for a small fee. Quote too high and you never hear back, without knowing why.
You will not always get the exact figure, but you can nearly always find out which range you are in before you send a number. Do it in two passes: research before you talk, and one well-timed question when you do.
Fifteen minutes of research before the call
Most clients leave plenty of public signals about how much they can spend. You are not trying to guess their bank balance, only to work out whether they are a ₹20,000 client or a ₹2 lakh one.
Before the first call
0 of 8 done
A few of these need a word of explanation.
Open job posts are one of the best signals. If a startup is trying to hire a full-time designer at ₹10 lakh a year and has not filled the role, a freelancer covering the gap for three months at a fair day rate costs them less than the hire would. You can say so.
Salary data gives you the client's alternative. A content writer on ₹6 lakh a year in Bengaluru costs a company about ₹2,400 a working day before PF and office costs. If your quote for a month of writing comes close to that, you are competitive; if it is half, you are probably underpricing.
Platform history is blunt and reliable. On Upwork, the client's profile shows what they have spent and the average hourly rate they paid. Someone with fifty hires at a low average is shopping on price. The Upwork, Behance and Dribbble guide covers reading profiles in more detail.
Funding news cuts both ways. A company that raised a Series A last month usually has budget and urgency. A company that raised three years ago and has gone quiet may be watching every rupee.
Read the brief for clues
The enquiry itself tells you a lot, if you read it twice.
Urgency usually means flexibility. "We need this before the Diwali sale" or "our launch is in three weeks" signals a client who will pay to have it done properly and on time.
Who is writing matters too. A founder decides quickly and can move money. A marketing manager has a set budget and needs to justify it to someone else, so give them a proposal they can forward. A procurement team will compare you on price against two other quotes.
Phrases like "looking for someone affordable", "small budget for now, more work later" or "simple job, should not take long" are not always warning signs, but they are worth noting. The client red flags playbook has the ones that should stop you quoting at all.
When and how to ask
You will hear both "never ask the budget, it hands them control" and "always ask it first, it saves time". Our view sits in between: ask, but not first. Ask after the client has told you what the work is for and what a good result looks like. By then you have both talked about value, and a budget question sounds like you are fitting the solution to their goal rather than sizing them up.
On a call, it can sound like this:
"That's really helpful, thank you. Based on what you've described, I can see a couple of ways to do this, and they're quite different in effort. Do you have a range set aside for it? It helps me suggest the version that fits, rather than sending you something you'll need to cut down." If they hesitate: "No problem. For context, projects like this usually run from about ₹40,000 for a focused version, which would be the homepage and two inner pages, to ₹1 lakh or more for the full build with the booking flow. Which end feels closer to what you had in mind?"
The second part is a price range, and it does two jobs. It anchors the conversation on your numbers instead of theirs, and the client's reaction tells you where they sit. A pause at ₹40,000 tells you one thing; "that's fine, what does the full version include?" tells you another. The anchoring playbook explains how to set those ranges, and discovery calls that close covers the rest of the call.
If there is no call and everything is happening over email, put the same question in writing:
Hi Meera, Thanks for the details on the new site. Before I put a proposal together, two quick questions: 1. Is the booking flow needed at launch, or could it come in a second phase? 2. Do you have a budget range in mind? Projects like this usually fall between ₹40,000 and ₹1 lakh depending on the features, and knowing your range lets me suggest the right version instead of the most expensive one. Happy to jump on a 15-minute call if that's easier. Arjun
Work out what the result is worth to them
Budget is what the client has set aside. Value is what the work will earn or save them, and it is often much larger. Knowing it helps you judge whether your quote is reasonable from their side.
Take a coach selling a ₹6,000 online course who wants a new landing page. If the page brings in 30 extra sales a month, that is ₹1.8 lakh a month. A ₹50,000 quote looks very different against that number than against "a single web page". You do not have to put this maths in the proposal, but you can ask the questions that reveal it: "How many sales a month does the current page bring in? What would a good month look like after the change?"
When the budget is below your floor
Sometimes the research and the question both point to a budget smaller than your floor rate allows. You have a few honest options.
- Cut the scope to fit the money. "For ₹30,000 I can do the homepage and contact page; the blog and booking flow can follow when you are ready."
- Split the work into phases, with the first phase priced to fit this quarter's budget.
- Refer them to someone earlier in their career who would welcome the job, and keep in touch.
What you should not do is quote the full scope at the lower price. Clients rarely remember the discount; they remember the price, and the next project starts from it. If they push back after you quote, the price pushback playbook has scripts for trading scope instead of rate.
If you only do one thing differently, stop quoting from the enquiry alone. Fifteen minutes of research and one question at the right moment will change the number you write.
Common questions
Is it rude to ask a client what their budget is?
No, as long as you ask at the right point. Opening with "What's your budget?" can sound like you are sizing up their wallet. Asking after they have explained the goal sounds like you are trying to fit the solution to it. Most clients who have bought freelance work before expect the question and are relieved not to waste time on a quote they cannot afford.
What if the client says they have no budget in mind?
Often it means they have not bought this kind of work before. Offer ranges: "A basic version usually runs ₹40,000 to ₹60,000, a fuller one ₹90,000 to ₹1.2 lakh." Their reaction tells you more than a direct answer would. If they balk at the lowest range, they may not be ready to hire, and that is worth knowing early.
How do I check a client's budget on Upwork?
Open the client's profile from the job post. It shows how much they have spent on the platform, how many freelancers they have hired, and the average hourly rate they have paid. A client who has paid an average of a few dollars an hour across many hires is unlikely to accept a rate several times higher, whatever you write in the cover letter.
Should I quote Indian and foreign clients differently?
Budgets differ, so the quote often will too. What should not change is your floor, the least you will accept for a day's work. Quote each client what the work is worth to them and what their market pays, as long as it sits at or above that floor. Many funded Indian startups pay rates close to foreign clients, so do not assume a lower number because the client is local.
