A potential client calls about a branding project. Midway through the conversation, they ask: “Just ballpark, what would something like this run?” The freelancer, wanting to be helpful, says: “Probably around $4,000 to $5,000.” The call ends well. Two days later, the freelancer sends a proper scoped quote for $8,500 after understanding the full project. The client replies: “On the call you said $4,000–$5,000. Why has it nearly doubled?” The freelancer never quoted $8,500. They scoped it correctly. But the number they said on the call is now the anchor, and they’re negotiating down from their own casual estimate. The project closes at $6,200.
A verbal quote given without scope is almost always too low. You say a number based on what you heard in 60 seconds of project description. You haven’t asked about revision rounds, timeline constraints, the number of stakeholders, the specific deliverables, the legal requirements, or the ten other scope variables that determine the real price. Then you do all of that and the real number is higher, and you’re defending a change the client perceives as bait and switch.
Why verbal quotes create anchors you can’t escape
Anchoring is the cognitive bias where the first number someone hears disproportionately influences their evaluation of every subsequent number. If you say “$4,000–$5,000” on a call and then send an $8,500 quote, the client doesn’t evaluate your quote on its merits. They evaluate it as “$3,500–$4,500 more expensive than what you said.” The comparison is unfair, your quote is fully scoped and your ballpark wasn’t, but the anchoring effect doesn’t care about fairness.
The anchor is especially sticky because it was verbal. Verbal statements feel more trustworthy, more personal, and more committal than written documents with disclaimers. The client remembers “you said around $5,000” the way they remember a promise, not a rough guess.
The math on underbidding from anchors: If a freelancer does this twice a month, gives a ballpark on the call, then scopes correctly, and each time negotiates from the anchor to somewhere in between, they lose an average of $2,000–$4,000 per project. Over 12 months, that’s $48,000–$96,000 in revenue lost to a habit that took 10 seconds to form.
The redirect that works
When a client asks for a number on the call, this is the only response you need:
“I want to make sure I give you a number that’s actually accurate, can I follow up after this call once I’ve had a chance to think through the scope? That way I won’t over- or under-quote you, and you’ll have something concrete to work with rather than a rough guess.”
This redirect does three things. It frames not giving a number as a benefit to the client (they get accuracy instead of a guess). It signals that you take scoping seriously, which is a quality signal. And it buys you the 24 hours to quote properly.
If they push harder:
“Genuinely, for something like this, the range is wide, $5,000 to $20,000 depending on scope. I could give you a rough number now but it would be a wide enough range that it wouldn’t actually help you budget. After our call I’ll have a real number for you by tomorrow.”
The key is to make the range wide enough that it’s obviously not a quote. “$5,000 to $20,000” is not an anchor, it’s an acknowledgment that scope determines price. “$5,000 to $6,000” is an anchor.
The clients who refuse to wait 24 hours for a proper written quote, who insist on a number right now, on the call, before you’ve asked a single scoping question, are giving you important information about how they’ll behave throughout the project. A client who won’t let you scope properly will also not give you clear briefs, will change direction mid-project, and will dispute scope boundaries on the final invoice. You can say no to the shortcut and set the tone for a professional engagement. Or you can give the number and confirm their expectation that this is how you work.
When a verbal ballpark is acceptable
Two situations where giving a rough number on the call is the right call:
1. Returning clients with repeat work. If a client has hired you three times for the same type of project, they know your rate, you know your rate, and a verbal “this would probably run around $4,500, same as the last one” is fine. You have prior scoped work to reference. You’re not guessing.
2. Budget qualification, the “are we even in the same ballpark?” question. Sometimes a client is asking whether you’re in the same price range before investing time on both sides. This is legitimate. The answer: give a wide range, positioned honestly.
“For a project like this, clients typically invest anywhere from $8,000 to $30,000 depending on scope. If that’s in the right range for you, I’d love to do a proper scope call, if it’s way outside your budget, better to know now.”
This isn’t a quote. It’s a filter. You’re finding out if the conversation is worth having. If the client says “we were thinking $1,500,” you’ve saved both parties an hour of scoping. If they say “that sounds about right,” you schedule the proper call and quote after.
The written quote advantage
A written quote, properly formatted, does things a verbal number can never do:
- It defines scope, what’s included and what isn’t
- It has an expiry date, which creates appropriate urgency
- It’s referenceable, both parties can look at the same document
- It signals that you’re organized and professional
- It gives the client something to get internal approval on (a verbal number can’t go to their CFO)
- It protects you if there’s any dispute about what was agreed
A verbal quote is a number without context. A written quote is a commitment with boundaries. The second one is always better for the freelancer, and it’s usually better for the client too, they just don’t know to ask for it.
The rule: never give a number until you have enough scope information to attach it to something specific. On a call, that means asking questions first. After a call, that means writing a quote. Either way, context before number.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
