How Do You Tell a Customer Their Final Price May Change?

You tell a customer their price may change at the estimate, before they sign anything, not after the job is done. Name the specific conditions that could cause the price to move, write them into the estimate as exclusions or allowances, and tell the customer exactly how and when you'll contact them if one of those conditions happens. A surprise at invoice time is what creates disputes. A condition they agreed to in writing is just a line item.

Most contractors know this in their gut but still botch it in practice. They say something vague like "it might cost a little more if there are surprises" and move on. The customer hears that as filler, not a warning. Then three weeks later there's rot behind the drywall, the price goes up $800, and the customer feels blindsided even though you technically mentioned it. The fix isn't saying it louder. It's saying it specifically, in writing, at the right moment.

Say it at the estimate, never at the invoice

The only time a price change lands well is when the customer already expected it. That expectation gets built during the estimate conversation and gets locked in on the estimate document itself, not verbally and not as an afterthought. If the first time a customer hears "this could cost more" is in a text message mid-job, you've already lost the trust battle, even if you're completely in the right.

This means you need to identify the risk before you ever price the job. Walk the kitchen remodel, the roof, the fence line, whatever it is, specifically looking for the things that tend to blow up pricing in that trade: subfloor rot, old wiring behind a wall you're opening, a septic line you can't see, soil conditions, HOA requirements you haven't confirmed. If you're not sure what to look for before you even get to the house, a site visit checklist built around your trade's usual surprises will save you from a lot of these conversations later.

Name the specific conditions, don't speak in generalities

"Price subject to change" is a legal CYA phrase, not a communication tool. It protects you in a dispute but does nothing to prepare the customer. What actually prepares them is a short, specific list of the conditions that would trigger a change, written directly into the estimate.

For a kitchen remodel, that might look like:

• Subfloor: estimate assumes no rot or water damage under existing flooring. If damage is found once flooring is removed, repair is billed at $X per square foot.
• Electrical: estimate assumes existing wiring meets code. If wiring needs to be brought up to code once walls are opened, that work is quoted separately.
• Plumbing: if galvanized pipe is found behind the wall being removed, replacement is an additional cost, quoted once exposed.

Each line does three things at once: it tells the customer what you assumed when you priced the job, it tells them what would change that assumption, and it gives them a rough sense of what the change would cost. That's the difference between an exclusion that protects you on paper and one that actually prepares the customer emotionally. For bigger remodels specifically, pricing a kitchen job without missing the hidden costs covers the categories that most often get missed at this stage.

Allowances work the same way for anything with a selection the customer hasn't made yet — tile, fixtures, countertop material. "Tile allowance: $4/sq ft. Customer selections above this amount are billed at actual cost." That's not a hedge, it's a number the customer can plan around.

The exact wording to use

In person or over the phone, keep it short and specific rather than apologetic. Something like:

"The number I'm giving you today assumes what we can see. If we open this wall and find rotted subfloor or wiring that's not up to code, that's not included in this price — I'll stop, show you exactly what we found, and get your OK on the cost before any of that work happens."

That sentence does the job because it names the trigger (opening the wall), names what's excluded (rot, non-code wiring), and commits to a process (show you, get your OK, then proceed). Compare that to "there might be some surprises" — same intent, completely different level of trust built.

On the written estimate, pair that verbal explanation with a line near the total that says something like: "This estimate is based on visible conditions as of [date]. Conditions noted under Exclusions are not included and will be priced separately if encountered." That sentence alone, sitting above your signature line, has saved more contractors from invoice disputes than any amount of verbal reassurance.

Agree on how you'll notify them, before it happens

The condition itself isn't what upsets customers — the lack of notice is. So the estimate conversation should also cover the mechanism: will you call, text, or send a change order through whatever software you use? Will you wait for their approval before continuing, or only pause if the number crosses some threshold they set?

Most contractors do fine with a simple rule: anything under $150 extra, you'll just mention it when they're home; anything over that, you stop and get written approval before proceeding. State that threshold out loud at the estimate. It gives the customer control without making every $40 surprise into a negotiation.

When the condition actually shows up mid-job, treat it exactly like a scope change: document it, price it, and get sign-off before the work continues. Change Orders 101 covers how to price and document that moment so it holds up if the customer questions it later — the short version is photo, written price, signature, before you touch it.

What happens when you skip this step

Skip the conditions-in-writing step and you end up negotiating the price increase after the fact, usually with a customer who's already annoyed and a crew that's already done the work. You're arguing from a weaker position every time. The invoice becomes the first place the customer hears bad news, and invoices are a terrible place to deliver news — there's no room to explain, just a number that's higher than they expected.

The contractors who get paid without a fight are the ones who moved the hard conversation earlier, to the estimate, when there's still time to explain, answer questions, and get a signature. It takes five extra minutes at the walkthrough. It saves hours of back-and-forth later.

Where this fits in your workflow

If you're building estimates by hand or from memory, it's easy to forget to write the exclusions down even when you mentioned them out loud. Trusso builds estimates against your own price book, so the categories that tend to carry conditions — demo, electrical, plumbing, drywall repair — are already there to prompt you, and exclusions or allowances sit right on the document the customer signs, not in a separate conversation you have to remember to have. It won't tell you what conditions apply to your job, but it makes sure the ones you decide on actually end up in writing in front of the customer.