A concrete contractor described his system on r/Contractor, and it is the system most advice recommends. He gives ballpark estimates over the phone specifically to filter out people who are not serious.
Then he described what happened anyway.
Story one. He told the homeowner the project would run $6,000 to $9,000 depending on conditions he could not assess remotely. They sounded fine with it. They booked a visit. He drove out, looked at the site, and gave the real figure: $7,000.
Their response: "we thought this would cost us at the most $3,000."
He pointed out they had discussed the range on the phone, more than once, and that materials and equipment alone came to roughly $3,000, which left his labour at nothing.
Story two. He explained his recent jobs ran $12 to $15 per square foot for the design they wanted. They liked the price per square foot. He visited, quoted $12, showed them their total area, and they had what he described as a meltdown.
He did everything the advice says to do, and lost both afternoons.
The short answer
Yes, give a range, and then make it consequential. The ballpark works as a filter; it just does not work as well as contractors expect, because there is no cost to a caller who agrees to it insincerely. Converting an acknowledgement into a stated budget is the difference between a filter that catches most people and one that catches almost everyone.
Why the ballpark works at all
Before the criticism, the case for it, because refusing to give numbers is worse.
It saves the visit. A contractor who will not discuss price until he has driven out has committed an hour or more before learning whether the enquiry was real. One contractor described spending 10 to 20 hours a week doing exactly this, unpaid.
It answers the question they actually asked. Someone ringing a contractor mostly wants to know whether this is a $3,000 problem or a $30,000 problem. Refusing to indicate which reads as evasive, and evasive reads as expensive.
It builds credibility. A tradesperson who can price a job approximately from a description sounds like someone who has done it many times. A tradesperson who cannot sounds like someone who has not.
It costs two minutes. Against an hour of driving, the arithmetic is not close.
So the ballpark is right. The question is why it fails as often as it does.
The specific way it fails
Here is the mechanism, and naming it is what lets you fix it.
Agreeing to a range on the phone costs the caller nothing.
No signature, no deposit, no commitment, no consequence. Saying "that sounds fine" is free. And for a homeowner who wants to see whether you might come in lower, or who has not really absorbed the number, or who simply finds it socially awkward to say "that is triple what I expected," agreeing is the path of least resistance.
Watch out
The concrete contractor's frustration was that the homeowner "remembered" the range when challenged. That is the tell. They had heard it, understood it, agreed to it and booked the visit anyway. The range was not misunderstood; it was acknowledged without being accepted, and those are different things.
There is a second version in his story two, and it is worth separating because it is a genuine communication failure rather than a filtering one.
A unit rate is not a price. Twelve dollars per square foot sounds modest. Most homeowners have no reliable sense of their patio's area, so they agree to a rate without ever having computed a total. The meltdown came at the multiplication, not at the rate.
If you quote per unit, do the multiplication out loud on the call. "Twelve to fifteen a square foot, and you said roughly four hundred square feet, so you're looking at five to six thousand." Now they have agreed to a number rather than a rate.
Making the range consequential
Four wording changes, none of which take longer than the version they replace.
Ask them to confirm it as a budget, not acknowledge it as a number.
Weak: "It'll be somewhere between six and nine thousand. Does that sound alright?"
Better: "It'll be somewhere between six and nine thousand. Is that a budget you're comfortable with, or is it more than you had in mind?"
The second explicitly offers them the exit. That matters, because most people will not volunteer that a number is too high; they will take the offered escape if you provide one, and they will agree if you do not.
Give the total, always. Even if you priced it per unit to get there.
State what the range assumes. "That's assuming reasonable access and nothing unusual under the surface. If the base has to come out, it goes up." A number attached to conditions is understood as conditional. A bare number is remembered as a promise.
Quote high. Set the range slightly above where you expect to land. It filters harder, and coming in under it reads as good news rather than as a discount you have been argued into.
The questions before the number
The range works better when it follows a short qualification, and these five take about ninety seconds.
"How did you find us?" A referral is almost always worth visiting. Someone who found you third on a list and is "looking for a price" is usually collecting numbers. A twenty-year general contractor described this as his first filter and it is the highest-signal question on the list.
"What are you trying to achieve?" Not what they want built. One contractor put the distinction well: a client wants a fence, but what they need is privacy from a nosy neighbour. Selling to the need changes both the conversation and the close rate, and it also surfaces scope you would otherwise miss.
"Roughly how big?" You need something to price against, and their answer also tells you how much they have thought about it.
"What's your timeline?" Vague timelines mean vague commitment.
"Have you got a figure in mind?" Some will not answer. The ones who do have just saved you an afternoon, and the ones who deflect have told you something too.
Reading the answer
The most useful signal is not what they say to your range. It is how they say it.
| Reaction | What it usually means |
|---|---|
| Engages with the number, asks what moves it | Real. Book the visit. |
| Goes quiet, changes the subject | Expectation is far below. Probe. |
| "That's fine, when can you come?" with no questions | Ambiguous. Ask the budget question directly. |
| Asks whether you can do better before you have visited | Price shopper. Proceed carefully. |
| "I've had a couple of others out already" | You are the comparison quote, not the first choice. |
The third row is the one that produced both of the concrete contractor's wasted afternoons. Enthusiastic agreement with no questions attached is not a good sign; it is an absence of engagement, and it should trigger the budget question rather than a diary entry.
That last row deserves a direct question in response: how many others are you speaking to? Most people answer honestly, and a prospect on their fourth quote is usually looking for a number to negotiate with rather than a contractor to hire.
Half of this happens before the phone rings. Our free check looks at what your site tells a prospect before they call, whether they can enquire without phoning at all, and where that enquiry lands. Ten checks, about fifteen seconds.
When not to give a number
Three situations where the range does more harm than good.
When you genuinely cannot estimate it. Structural work, anything behind a wall, old buildings. A range you invent to seem helpful becomes the number you are held to. "I'd be guessing, and a guess helps neither of us" is a legitimate answer, provided you follow it with what you can offer: a paid detailed assessment, or a visit priced as a call-out.
When the scope is undefined by the customer. If they do not know what they want, no range describes it. Ask what outcome they are after, and if the answer is still vague, the honest next step is a scoping conversation rather than a number.
Emergency work. Someone with no heat is not comparison shopping. The useful number is your call-out or diagnostic fee, not a job range. State it before you drive: residential service call fees commonly sit in the $99 to $159 range, and a fee disclosed on the phone is a normal business term while the same fee produced at the door is a dispute.
The version for small jobs
Worth separating, because applying this process to a $300 job is disproportionate and contractors do it constantly.
For repeatable small work, do not estimate at all. Publish a rate card and quote from it in thirty seconds. Tap replacements, standard call-outs, tune-ups, common repairs.
This removes the visit entirely, converts faster because the customer gets a number while still motivated, and filters honestly, since anyone who baulks at a published price was never going to accept a quoted one.
It requires knowing your real cost on repeatable work, which means tracked hours rather than assumptions, and that discipline is the subject of flat rate versus hourly pricing.
The threshold sits roughly where a site visit would take longer than the job. Below it, quote from the card. Above it, the range-then-visit process applies.
What the ballpark cannot fix
Being honest about the limits, because the phone call is one filter in a sequence and it will never catch everyone.
Some people will still waste your time. Both stories above involved homeowners who had heard the range and booked anyway. A better phone process reduces that; it does not eliminate it, because you cannot make someone tell you the truth about their budget.
Some of them are not doing it deliberately. A homeowner may genuinely have no idea what concrete costs, hear a number that sounds abstract, and only react when it becomes concrete on paper. That is not malice; it is unfamiliarity, and giving the total rather than a rate is what prevents it.
A price expectation of a third of the real cost is not negotiable. When someone expects $3,000 for a $7,000 job, there is no version of the conversation that closes it. Recognising that quickly and ending the call politely is the win, and it is worth more than the visit you avoided.
Building your own ranges
The advice assumes you can produce a credible number in ninety seconds. If you cannot, that is the thing to fix first, and it is a data problem rather than a confidence problem.
Pull your last twenty completed jobs and sort them by type. For each type, record the final invoiced total and the rough size or scope.
Take the middle 80%. Discard the cheapest and most expensive outliers, which are usually explained by something unusual you would spot on a call anyway.
That spread is your range. Not a guess, not a competitor's price, and not what you hope to charge. What you actually charged, for that kind of work, recently.
Write them down somewhere you can see during a call. A card by the phone or a note on a screen. Ranges recalled from memory drift downward under pressure, because the memorable jobs are the ones where price was contested.
Review twice a year. Material costs move, and a range built eighteen months ago is quietly quoting last year's prices.
Two things this exercise reliably surfaces. Contractors discover their spread is far wider than they assumed, which is itself useful, because a wide spread means the drivers of cost are not being asked about on the call. And they discover their instinctive verbal quotes sit near the bottom of their real range rather than the middle, which is a straightforward way of underpricing before a job even starts.
If you have not tracked completed jobs by type, that is the prerequisite, and it is the same discipline that underpins pricing generally. The method is in how to price a job as a contractor.
Handling the ones who quote your range back
It will happen. You said five to six thousand, the written estimate came in at six-five because of something you flagged as a variable, and the customer says you told them five.
Do not argue about what was said. Nobody wins that and it damages a relationship you may still convert.
Point at the condition, not the conversation. "The range assumed the existing base could stay. When I got out there it had to come out, which is the two thousand on line four. Happy to talk through options if that pushes it too far."
Have the options ready. A reduced scope, a phased approach, a cheaper specification. A customer whose objection is met with a genuine alternative frequently takes it, and one whose objection is met with a defence usually leaves.
Then note it. If several customers are quoting your ranges back to you, your ranges are too narrow or your conditions are not being stated clearly enough on the call. That is a fixable process problem rather than a run of difficult clients, and the signal only appears if you write down when it happens.
A workable script
Put together, the whole call is about two minutes.
Them: How much for a patio out back?
You: Happy to give you a rough idea. How did you come across us? … And what are you hoping to get out of it, is it mainly for seating or is it more about getting rid of the mud? … Roughly what size are we talking? … About four hundred square feet, right. For that, done properly with the prep, you're generally looking at five to six thousand, assuming decent access and nothing unexpected under the surface. Is that in the range you had in mind, or is it more than you were expecting?
Then stop talking and listen.
If the answer engages with the number, book the visit. If it deflects, ask once more directly. If the expectation is a third of the figure, thank them and end it warmly, because that is a good outcome and it took two minutes rather than an afternoon.
And if the visit does happen and the quote goes out and then nothing comes back, that is a separate problem with a separate fix, covered in why customers ghost after a quote and how to follow up on a quote without being pushy.