Most typical phrasing
“Can you give me a rough price range?”
Optional analytics
FlowDockr only loads optional analytics and third-party tools after you allow them. Read the Privacy Policy.
The client is not asking for an exact quote yet. They want a quick range, and you need to answer without pretending the project has already been scoped. Get a professional reply you can adapt and send.
Start with 2 free drafts. No subscription required.
Typical client message
“Can you give me a rough price range?”
Situation snapshot
The client is not asking for an exact quote yet. They want a quick range, and you need to answer without pretending the project has already been scoped.
Reply goal
Give a range with assumptions so the client understands what would move the number up or down.
Client message generator
Generate a reply when a client asks for a rough price range. Give a useful range, explain the assumptions, and avoid overcommitting before scope is clear.
Review the suggested approach and choose the response that best fits your client conversation.
Your polished reply will appear here
Generate a result to see the send-ready message, the reasoning behind it, and follow-up guidance if the client keeps pushing.
Why this works
What it protects
Give a range with assumptions so the client understands what would move the number up or down.
How it sounds
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.
Next step
Tell them what details you still need before converting the range into a formal quote.
These are the real wording patterns this scenario is built to handle.
Most typical phrasing
“Can you give me a rough price range?”
Reply playbook
Use this when the search intent is "client asks for a price range" and the client message matches this negotiation stage. It also covers searches like "how to give a rough freelance price range".
Step 1
The client is not asking for an exact quote yet. They want a quick range, and you need to answer without pretending the project has already been scoped.
Step 2
Give a range with assumptions so the client understands what would move the number up or down.
Step 3
Tell them what details you still need before converting the range into a formal quote.
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
Give a range with assumptions so the client understands what would move the number up or down. 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.
Give a range with assumptions so the client understands what would move the number up or down.
Use a softer tone when the client is still collaborative and the pressure looks like uncertainty rather than bad faith.
Tell them what details you still need before converting the range into a formal quote.
More client replies for rate objections, discount requests, and budget pushback.
More client replies for rate objections, discount requests, and budget pushback.
Client asks for a timeline before sharing what you need
The client wants a delivery estimate but has not sent the assets, content, access, or dependencies required to judge timing.
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 asks if your rates are negotiable
The client is probing for flexibility before the real work discussion has even started. You need to answer clearly without sounding rigid or weak.