When a client changes the request after you send the quote

Published on September 1, 2026

You send a quote. Then the client replies with one small change.

Can you also include the extra room? Could you deliver it next week instead? What if we added two more people? It may sound like a minor adjustment, but the answer can change the work, the timing or the price.

The difficult part is not saying yes or no. It is making sure both sides understand what changed before the original quote quietly becomes a different job.

Start by naming the change

Do not answer the new request from memory. Write down what is different from the version you quoted.

The change might affect:

• the number of items, people or locations;
• the result the client expects;
• the materials or information required;
• the delivery date;
• the number of review rounds;
• who needs to approve the work.

A short reply can make the difference visible:

I understand that you would now like to include [change]. The original quote covered [original scope]. Let me check what this does to the timing and price before I confirm it.

This is clearer than treating the request as an ordinary follow-up message.

Separate clarification from a real scope change

Not every new message requires a new quote. Sometimes the client is asking you to explain something that was already included.

Ask three questions:

1. Was this part of the original request?
2. Was it included in the quote, even if the wording was not obvious?
3. Does fulfilling it require more work, time or responsibility?

If the answer to the third question is no, a clear explanation may be enough. If the answer is yes, the request deserves a new decision.

Keep the original quote easy to reference

Many scope problems begin because there is no simple record of what the quote included.

Keep one short reference for each quote:

• the problem or result being addressed;
• what is included;
• what is not included;
• the agreed timing;
• assumptions that the price depends on;
• the next decision.

This does not need to be a long contract. It can be a short summary that both sides can read quickly.

For example:

This quote covers the setup of the booking flow for one location, using the information supplied by the team, with delivery by 15 September. It does not include ongoing message management or changes to the existing payment system.

The more specific the original boundary, the easier it is to discuss a later request without sounding defensive.

Give the client a clear path

When the request changes, there are usually three useful paths:

Keep the original scope

The new request can wait. Continue with what was agreed and record the additional idea for later.

Adjust the quote

The change matters now. Explain what it adds, what it moves and what needs to be approved before work continues.

Change the plan

The new request replaces the original one. Stop treating it as an addition and restate the new result, timing and price.

The client should not have to guess which of these paths you are following.

A message that keeps the conversation useful

Try this structure:

Thanks — I can look at that. It changes [scope/timing/assumption] from the quote we discussed. I see two options: we can keep the current plan and review this next, or I can update the quote to include it. Which direction works better for you?

The wording leaves room to help without promising the change before you understand it.

Watch for the quiet costs

Some changes do not add a visible task but still create work. A faster date may require rearranging other commitments. An additional decision-maker may add review time. A new system may require access or testing that was not part of the original plan.

Before agreeing, ask:

• What work appears because of this change?
• What work moves or disappears?
• Who needs to provide information or approval?
• What happens to the date?
• What needs to be recorded so the team does not work from two versions?

If you cannot answer these questions, you are not ready to confirm the change.

What to automate later

A simple system can flag when a request mentions a new item, date or deliverable. It can compare the current note with the original scope and prepare a review checklist.

It should not decide whether the business can absorb the change or promise a new price by itself. That decision depends on context, capacity and the relationship with the client.

Review the last few projects where the scope changed. Look for the moment when the original quote stopped matching the work. That is usually the part worth making clearer.

If you want to find repeated decisions like this in your business, use the AI Opportunity Map.

A small change is easier to handle when everyone can see what it changes.