Unforeseen work is normal in service businesses. Websites have legacy issues. Consulting projects uncover missing data. Renovations reveal hidden conditions. Creative projects expand when more stakeholders get involved. The problem is not that unknowns exist. The problem is quoting them in a way that makes the client feel like you already expect trouble.

The best language is calm, specific, and fair. You are not accusing the client. You are defining how the project will stay organized if reality changes. A quote should protect the business while still feeling approachable.

Start with assumptions, not warnings

Assumptions are friendlier than threats. Instead of saying, “Extra work will be billed if you delay the project,” say, “This quote assumes feedback is provided within three business days so the agreed timeline can be maintained.” The meaning is similar, but the tone is completely different.

Good assumptions explain what the price is based on. They help the client understand how to keep the project on track.

  • “This quote assumes final copy and approved brand assets are supplied before design begins.”
  • “This quote assumes access to the existing system is available within two business days of approval.”
  • “This quote assumes up to two revision rounds are included for each deliverable.”
  • “This quote assumes existing site conditions match what was visible during the initial walkthrough.”

Use exclusions to define the edge of the quote

Exclusions do not need to sound defensive. They simply define what is not included. This is especially important when clients might assume that “website,” “consulting,” “installation,” or “brand package” includes everything they can imagine.

Try this structure: “This quote does not include X. If X is needed, we will confirm scope and pricing before proceeding.” That sentence is firm without sounding combative.

  • “This quote does not include custom integrations beyond the systems listed above. If additional integrations are required, we will confirm scope and pricing before proceeding.”
  • “This quote does not include permit fees or third-party inspection costs unless specifically listed.”
  • “This quote does not include additional stakeholder interviews beyond the sessions described in the scope.”

Explain change requests before they happen

A change request process should feel like a professional workflow, not a punishment. The client should know that new requests are welcome, but they may affect price, timeline, or both.

Sample wording: “If new requirements come up during the project, we will outline the requested change, confirm any price or timeline impact, and ask for approval before additional work begins.”

This is also where negotiation discipline matters. If a client asks for more while trying to hold the same price, the answer is usually to trade scope rather than margin. The practical scripts in Quote Negotiation Strategy: Trade Scope, Not Margin are useful for that moment.

When to use a contingency

Some uncertainty is likely enough to price in advance. For example, a contractor may know that hidden damage is possible, or a developer may know that an old plugin stack could create extra QA work. In those cases, you can use a contingency reserve or define a clear allowance.

For a deeper pricing approach, read Risk Reserves in Client Quotes. You can also compare formal project reserve concepts with resources like Project Management Academy’s guide to contingency and schedule reserve.

Client-friendly clauses you can adapt

Discovery dependency

“This quote is based on the information available at the time of writing. If discovery reveals requirements that materially change the scope, we will document the change and confirm next steps before proceeding.”

Material price changes

“Material pricing is valid for 14 days. If supplier pricing changes before approval, we will update the affected items and confirm the revised total before work begins.”

Client delays

“The project timeline depends on timely feedback, approvals, and access. Delays in these items may shift delivery dates. If delays create additional work, we will confirm any impact before continuing.”

Unknown technical conditions

“This quote assumes the existing system can support the requested work without major remediation. If technical issues are discovered, we will provide options before additional work is performed.”

Do not overlegalize the quote

There is a place for terms and legal review, but the quote itself should still be readable. If every sentence sounds like a lawsuit waiting to happen, the buyer may feel uneasy. Keep language plain. Be specific. Avoid blame. Use professional boundaries without turning the quote into a defensive contract.

Negotiation resources often emphasize preparation and clear boundaries. For broader context, Timify’s article on contract negotiation strategies is a useful reminder that clarity before approval prevents tension later.

A simple wording formula

Use this formula when writing assumptions or exclusions: “This quote assumes/includes X. If Y changes, we will confirm Z before proceeding.”

  • X is the planned scope.
  • Y is the possible change or unknown.
  • Z is the process for approval, pricing, or timeline adjustment.

In ququ, you can save these clauses inside templates, add payment terms and conditions, and keep your quote clean while still protecting the business. The goal is not to sound suspicious. The goal is to make uncertainty manageable before it becomes conflict.