How to handle job-day surprises without bad blood
A job-day surprise only turns into an argument when it's raised as a demand instead of a choice. Lead with what you observed, not a number — show the photo, name the difference plainly, price it, and hand the decision back to the client: here's what changed, here's what it adds, your call. The process that makes this enforceable is covered separately; this is about how to actually say it.
Why does raising extra charges feel like a bait-and-switch?
Not because the extra charge is unreasonable — usually because of the order things happened in. The client heard a firm number first, then watched it grow, with no chance to weigh in before the growing started. That sequence reads as being sprung on, even when the underlying reason (a filthy oven, a room that wasn't mentioned) is completely legitimate. Fixing the feeling means fixing the sequence, not avoiding the conversation.
What should you actually say when you arrive to a bigger job?
Separate observation from price, in that order. "The oven's got heavy build-up that wasn't visible in the photos" is a fact the client can check. Following it immediately with a number, backed by a photo, turns a claim into evidence. Then hand back the decision explicitly — "I can include it for an extra amount, or clean to what was originally quoted, your call" — instead of implying it has to be done. Clients who feel like they chose rarely feel ambushed.
What kinds of job-day surprises come up?
It's rarely only the classic dirty-oven case. A room or area not mentioned in the original request, access or parking that eats into the booked time, or a task that turns out to need more than one person are all the same shape of problem: the job on arrival doesn't match the job that was priced. The response is the same regardless of which one it is — observe, photograph, price, confirm, then act.
How does QuoteX structure this conversation?
The mechanics — comparing the property to the original photos, pricing the difference, and getting written approval before starting — are covered in full in the oven problem: getting paid for extra work, and QuoteX's arrival-check flow builds that exact sequence into the job: flag the difference against the photos, batch it into one priced item, send it for approval, and only start once the client has responded. This post is about the conversation that flow is designed to replace — the doorstep negotiation — not the process itself.
Common questions
How do I tell a client a job costs more than quoted?
Lead with the observation, back it with a photo, then price it separately and let them decide — naming the difference before the number is what keeps it from sounding like a demand.
What if they refuse to pay the extra?
Clean to the originally quoted scope and say so plainly. Respecting a "no" is what makes a client trust your next "yes."
Is it okay to charge more without asking first?
No — that's the bait-and-switch clients react to. Price and confirm in writing before doing the extra work, every time.
Does a surprise mean my quote was wrong?
Not necessarily — a quote reflects the information available at the time. A surprise means the property didn't match it, not that the method failed.
Let the arrival check have this conversation for you
Photograph the difference, price it, and send one batched approval — QuoteX's arrival-check flow keeps job-day surprises in writing, before the work starts.
Start free — 10 quotes, no card