Most typical phrasing
“Actually, let’s also include the landing page... and maybe email too. We’re still figuring it out.”
Optional analytics
FlowDockr only loads optional analytics and third-party tools after you allow them. Read the Privacy Policy.
You are still in the quoting stage, but each new message changes the deliverables, priorities, or timeline. Get a professional reply you can adapt and send.
Start with 2 free drafts. No subscription required.
Typical client message
“Actually, let’s also include the landing page... and maybe email too. We’re still figuring it out.”
Situation snapshot
You are still in the quoting stage, but each new message changes the deliverables, priorities, or timeline.
Reply goal
Slow the process down enough to define a stable brief.
Client message generator
Slow the process down enough to define a stable brief.
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
Slow the process down enough to define a stable brief.
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
Guide the client toward a clearer scope checkpoint instead of guessing at a moving target.
These are the real wording patterns this scenario is built to handle.
Most typical phrasing
“Actually, let’s also include the landing page... and maybe email too. We’re still figuring it out.”
Other ways this shows up
“The scope is still moving a bit, but can you quote it now anyway?”
“We keep adding things as we think through it. Can you still price this up?”
Reply playbook
Use this when the search intent is "client brief keeps changing before quote" and the client message matches this negotiation stage. It also covers searches like "changing brief before quote client reply".
Step 1
You are still in the quoting stage, but each new message changes the deliverables, priorities, or timeline.
Step 2
Pause the quoting motion long enough to confirm a stable brief and the assumptions a quote would be based on.
Step 3
Guide the client toward a clearer scope checkpoint instead of guessing at a moving target.
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
Pause the quoting motion long enough to confirm a stable brief and the assumptions a quote would be based on. 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.
Pause the quoting motion long enough to confirm a stable brief and the assumptions a quote would be based on.
Use a softer tone when the client is still collaborative and the pressure looks like uncertainty rather than bad faith.
Slow the process down enough to define a stable brief.
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 says they need help figuring out the scope
A lead is interested but does not have a stable brief yet and wants you to help shape what the project should include.
Client wants a fixed price for an unclear project
The client wants a fixed quote before the scope is stable enough to price accurately, which creates real delivery risk.
More client replies for rate objections, discount requests, and budget pushback.
More client replies for rate objections, discount requests, and budget pushback.
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 says they need help figuring out the scope
A lead is interested but does not have a stable brief yet and wants you to help shape what the project should include.
Client wants a fixed price for an unclear project
The client wants a fixed quote before the scope is stable enough to price accurately, which creates real delivery risk.