Most typical phrasing
“How quickly can you get this done? We haven’t gathered everything yet, but roughly what would the timeline be?”
Optional analytics
FlowDockr only loads optional analytics and third-party tools after you allow them. Read the Privacy Policy.
The client wants a delivery estimate but has not sent the assets, content, access, or dependencies required to judge timing. Get a professional reply you can adapt and send.
Start with 2 free drafts. No subscription required.
Typical client message
“How quickly can you get this done? We haven’t gathered everything yet, but roughly what would the timeline be?”
Situation snapshot
The client wants a delivery estimate but has not sent the assets, content, access, or dependencies required to judge timing.
Reply goal
Clarify dependencies before committing to a timeline.
Client message generator
Clarify dependencies before committing to a timeline.
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
Clarify dependencies before committing to a timeline.
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
If you give any estimate, frame it as conditional on the missing inputs rather than as a fixed commitment.
These are the real wording patterns this scenario is built to handle.
Most typical phrasing
“How quickly can you get this done? We haven’t gathered everything yet, but roughly what would the timeline be?”
Other ways this shows up
“Can you give us a timeline before we pull everything together?”
“We do not have the assets yet, but how fast could this move on your side?”
Reply playbook
Use this when the search intent is "client asks for timeline before sharing assets" and the client message matches this negotiation stage. It also covers searches like "timeline estimate before assets client reply".
Step 1
The client wants a delivery estimate but has not sent the assets, content, access, or dependencies required to judge timing.
Step 2
Make the dependencies explicit so the client understands which inputs drive timing.
Step 3
If you give any estimate, frame it as conditional on the missing inputs rather than as a fixed commitment.
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
Make the dependencies explicit so the client understands which inputs drive timing. 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.
Make the dependencies explicit so the client understands which inputs drive timing.
Use a softer tone when the client is still collaborative and the pressure looks like uncertainty rather than bad faith.
Clarify dependencies before committing to a timeline.
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.
Client asks exactly what is included before approving
The client is close to moving forward but wants a tighter explanation of what is and is not included in the work.
More client replies for rate objections, discount requests, and budget pushback.
More client replies for rate objections, discount requests, and budget pushback.
Client asks exactly what is included before approving
The client is close to moving forward but wants a tighter explanation of what is and is not included in the work.
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.