Clients ask for ballparks because they don’t want to waste 45 minutes scoping a project that’s three times their budget. That’s reasonable. Your job is to give them a useful range without accidentally signing yourself into the low end of it forever.
Here’s how it goes wrong. You say “around 5K” on a discovery call. Three weeks later you send a 7,200 quote. The client emails back: “I thought you said 5K?” Now you’re either eating the difference or losing the deal. Both bad.
Why the one-number ballpark always backfires
When a client asks “roughly what does this cost?” the instinct is to give them a clean number. “Around 6K.” Easy to say, easy to remember, easy to be wrong about.
Single-number ballparks become anchors. The client hears 6K and stops listening. From that moment on, anything above 6K feels like a price hike and anything below feels like good news. You’ve boxed yourself into a number you guessed at in 4 seconds.
The fix is to never give a single number for a ballpark estimate freelance work. Always give a range, and make the range wide enough to cover what you don’t know yet.
The range formula
Early-conversation ballpark range: low end times 2 equals high end.
- “Somewhere between 4K and 8K”
- “Roughly 12K to 24K for the full build”
- “Probably 800 to 1,600 for the design piece”
That 2x range communicates “I have a rough idea, not a final number.” Clients with budgets that fit anywhere inside the range will keep talking. Clients with budgets way below the low end will say so, and you save the scoping call.
After a discovery call, narrow to roughly plus or minus 25 percent: “Looking like 6K to 9K now that I’ve heard the details, real quote tomorrow.” After you’ve seen the spec or wireframes, it’s a real quote.
The exact words to use
Some phrasing that gives a useful ballpark without locking you in:
- “Ballpark, not a quote: projects like this usually land between X and Y.”
- “Without the details I’d want to see, I’d estimate somewhere in the X to Y range.”
- “Similar work I’ve done has fallen between X and Y, depending on [the variable].”
- “Hard to say without knowing more, but most clients in your situation budget X to Y.”
Each of those has two parts: a number, and a hedge that explains why it’s a range. The hedge is what saves you later.
Words to avoid in a ballpark:
- “About”
- “Around”
- “Roughly” (without a range)
- “Probably”
Those single-modifier words feel like a real number with a tiny disclaimer. Clients hear the number and ignore the disclaimer. A real range with two endpoints can’t be misheard the same way.
What variables actually shift the price
A useful ballpark estimate freelance clients respect names the variables that move the number. Otherwise the range looks arbitrary.
For a website project:
- “5K if you bring the copy, 9K if I write it”
- “5K for 5 pages, 12K for 12 pages with custom modules”
- “5K if the brand exists, 11K if we’re doing identity work first”
Naming the variable does two things. It justifies the range (the client now sees why the high end is higher), and it prompts the client to volunteer the info that narrows it. “Oh, we have the copy already”, boom, the ballpark just tightened.
Putting it in writing without getting trapped
Sometimes the client asks for a ballpark by email. Don’t refuse. Just structure it carefully.
Template:
Hi [Name],
Quick ballpark before our call: projects like what you’re describing usually land between 6K and 12K, depending on whether [variable A] and [variable B] are in scope.
This is a ballpark only, not a quote, real number after we talk through the details. Tuesday at 2 still good?
[Your name]
That email gives a real range so the client can budget, names the variables that move the price, and labels the number clearly as “ballpark, not a quote.” If the client screenshots and forwards it to their boss, the boss sees a range and a disclaimer. No commitment, no surprise.
What to do when the ballpark and quote don’t match
You’ll have projects where the ballpark was 6K to 10K and the real quote lands at 11K. It happens, scope grew, you learned something on the call. Don’t pretend the gap doesn’t exist.
The line:
“Quick heads up, when I gave the 6K to 10K range, I hadn’t seen [the spec / the integration list / the timeline]. The real quote is 11K, broken down below. If 10K is the hard ceiling, here’s what we’d cut to land there.”
That email acknowledges the gap, explains why, and gives the client a path to land in the original range if budget is fixed. Most clients accept the higher number once they hear the reason. The ones who can’t, you’ve handed a real fallback.
When to refuse a ballpark
Sometimes the right answer is no number at all. Cases where refusing is correct:
- The client hasn’t described what they want in any concrete way
- They’re shopping 8 freelancers and clearly just collecting numbers
- The project type is too varied to have a meaningful range (“how much for a marketing strategy?”)
The line for refusing:
“Honestly, I’d be guessing if I gave you a number right now, projects in this space have ranged from 3K to 50K depending on scope. Can we do a 20-minute call so I can give you something useful instead of a number I’d regret?”
That refusal is fine because you’re offering a path forward. Refusing without offering a next step reads as rude. Refusing with a calendar link reads as professional.
The internal note that protects future-you
Every time you give a ballpark, write yourself a one-line note. Date, client, range you gave, assumptions.
May 23, Acme Corp, said 6K to 10K for the rebrand, assuming logo plus 5-page site, no copywriting
When the real quote conversation happens 3 weeks later, you have a record. You know what you said and why. You can re-anchor the conversation with confidence instead of trying to remember a casual conversation.
The shortest possible ballpark email
When you don’t have time to draft a paragraph:
“Ballpark 6K to 10K depending on scope, real quote after a call, Tuesday work?”
One sentence. A range. A disclaimer. A next step. That’s the whole formula.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
