Most typical phrasing
“Can you send a proposal and let us know what this would cost?”
Use this scenario when a potential client is interested but has not shared a budget and you need to qualify the opportunity before preparing a quote.
Start with 2 free drafts. No subscription required.
Typical client message
“Can you send a proposal and let us know what this would cost?”
Situation snapshot
The client wants pricing before you know whether their budget and expectations are compatible with a useful project scope.
Reply goal
Learn the budget range or constraints early enough to avoid wasted proposal work and a poorly anchored quote.
Client message generator
A direct, low-pressure budget question that connects the number to scope and options instead of making it feel like a test.
Review the diagnosis and next move first, then adapt the message draft before you send it.
Your guidance and message draft will appear here
Generate a result to see the situation diagnosis, recommended move, send-ready message, risks, and timed next action.
Why this works
What it protects
Learn the budget range or constraints early enough to avoid wasted proposal work and a poorly anchored quote.
How it sounds
To recommend the right scope, could you share the budget range you have set aside for this work? That will help me suggest an approach that is realistic for both the outcome and the timeline.
Next step
If the client will not share a range, offer a relevant starting range or two scoped options with explicit assumptions.
These are the real wording patterns this scenario is built to handle.
Most typical phrasing
“Can you send a proposal and let us know what this would cost?”
Other ways this shows up
“We do not have a fixed brief yet, but can you quote this?”
“What would you charge for a project like this?”
“Please send your pricing before our next call.”
Reply playbook
Use this when the search intent is "how to ask client about budget" and the client message matches this negotiation stage. It also covers searches like "ask client budget professionally freelancer".
Step 1
The client wants pricing before you know whether their budget and expectations are compatible with a useful project scope.
Step 2
Explain that budget helps you recommend a realistic scope, then ask for a range rather than demanding an exact number.
Step 3
If the client will not share a range, offer a relevant starting range or two scoped options with explicit assumptions.
Concise
Happy to give pricing context. Before I lock in a number, I'd want to confirm the scope, timeline, and what success looks like so the quote is actually useful.
Best for: Use when you need a short reply that keeps the thread moving.
Warm
I can share a starting range, but I would want to tie it to a few assumptions first so the number does not mislead either of us.
Best for: Use when you want to preserve trust while still keeping the boundary clear.
Firm
Explain that budget helps you recommend a realistic scope, then ask for a range rather than demanding an exact number. If the client wants a different path, make the tradeoff explicit before you continue.
Best for: Use when the client is repeating the pressure or treating the boundary as optional.
Explain that budget helps you recommend a realistic scope, then ask for a range rather than demanding an exact number.
Use a softer tone when the client is still collaborative and the pressure looks like uncertainty rather than bad faith.
Learn the budget range or constraints early enough to avoid wasted proposal work and a poorly anchored quote.
Client asks your rate before explaining the project
The lead asks for pricing before giving enough context to quote responsibly. You need to avoid locking yourself into a number too early while still being helpful.
Client wants a price before sharing the full scope
The client keeps pushing for a number before they have shared enough information to price the work responsibly.
Client message is too vague to quote the project properly
A lead asks for a quote but gives very little usable detail, making it risky to price or promise anything accurately.
More client replies for rate objections, discount requests, and budget pushback.
Close variants of this client conversation that need a similar kind of reply.
Client asks your rate before explaining the project
The lead asks for pricing before giving enough context to quote responsibly. You need to avoid locking yourself into a number too early while still being helpful.
Client message is too vague to quote the project properly
A lead asks for a quote but gives very little usable detail, making it risky to price or promise anything accurately.
Client wants a price before sharing the full scope
The client keeps pushing for a number before they have shared enough information to price the work responsibly.
If the client keeps pushing on price, these are the next pricing conversations likely to follow.
Client says your quote is too high
You sent a detailed proposal with scope, timeline, and price. The client replies saying the quote is higher than expected, but they have not given you a real budget yet.
Client asks for an immediate quote
The client wants a number immediately, but you do not yet understand the project well enough to quote cleanly. You need to slow the decision without sounding evasive.
Client says they don't have the budget
The client signals interest but says the budget cannot support the current proposal. You need to protect pricing integrity while finding out whether there is still a workable version of the deal.