When verbal estimates happen
Verbal estimates are not lazy by default; they are a normal part of how jobs start. A customer at the door asks 'roughly what are we talking about?' You are mid-job and they point at one more thing. A longtime client wants to know if a project is a two-hundred-dollar conversation or a two-thousand-dollar one before they commit to a visit.
In those moments a spoken range is honest and useful. It answers the only question being asked: is this worth pursuing? The trouble starts when the ballpark quietly becomes the price.
The risks of staying verbal
A spoken number has no scope attached, and memory edits aggressively. What you said as 'somewhere around eight hundred depending on the parts' is remembered as 'he said eight hundred.' Every assumption each side made stays invisible until the invoice arrives.
- No record of what was included, so 'I thought that was covered' becomes a fight
- No validity date, so a months-old ballpark gets treated as today's price
- No line items, so the customer cannot see what changed when the number moves
- Nothing to forward to a spouse, landlord, or insurance adjuster, so the decision stalls
- Nothing to point to if a friendly disagreement stops being friendly
What writing it down fixes
A written estimate converts all of that fog into a document: scope in plain language, itemized prices, terms, and a date. The customer gets something they can decide on and share; you get a record of exactly what was priced. What is a written estimate covers what makes one count.
Written estimates also change how you are perceived. Two contractors give similar numbers; the one who follows up with a clean, itemized document looks like the one who will run the job the same way. Fair or not, that is how customers read it.
The ten minutes a written estimate costs is cheaper than the hour a misunderstood verbal one does.
Turning a ballpark into a written estimate gracefully
The awkward moment is the transition: you gave a range out loud, and now you need it on paper without seeming to walk it back. The script is simple. Give the range with the caveat built in — 'roughly six to eight hundred, but let me send you the real number in writing tonight' — then actually send it.
When the written number lands inside the range, no explanation is needed. When it lands outside it, the document does the talking: the line items show the part or the hour the ballpark missed. Customers accept revised numbers far better from an itemized page than from a phone call. If you need the writing process, how to write an estimate is the full walkthrough.
A rule you can apply today
Use this test: if the customer will make a decision from this number, write it down. Comparing contractors, budgeting, getting approval from anyone else, scheduling work — all decisions, all written. Sizing up whether a project is even worth a visit — conversation, verbal is fine.
And make the writing cheap enough that you always do it. EstimateBook drafts itemized estimates from a voice, text, or photo description on iOS and Android and shares them as PDFs, so 'let me put that in writing' takes minutes from the driveway. The draft is a starting point: you review every line before it goes out.