"We've got about 3.000 for this."
I heard that sentence early in a call once, and I did what most freelancers do with a number: I built the project around it.
Trimmed the scope to fit. Skipped the second concept. Quoted 2.900 so it would feel like a comfortable yes.
It was a comfortable yes. And a project that should have been worth three times that came in at 2.900, because the client's first guess had become my final answer without either of us noticing.
Here's what I didn't understand back then. A client's budget is not information about the work. It's information about their expectations before they've talked to you. It's what they thought this would cost, on their own, without knowing what's possible.
The moment you hear it, two things can happen. You can treat it as a ceiling and shrink the project to fit under it. Or you can treat it as a starting point and show them what the project is actually worth.
Nearly every freelancer picks the ceiling, because the ceiling feels safe. Nobody says no to a quote under budget.
But that number was never the client's limit. It was their opening assumption. When you price to it, you're letting the least informed person in the conversation set the value of your work.
Now when a client names a budget, I say the same thing every time: "Good to know. Let me tell you what this would take to actually get the result you're after, and we'll see where it lands."
Sometimes it lands on their number. More often it lands well above it, and the client says yes anyway, because now the price is attached to an outcome instead of a guess.
Their budget is where the conversation starts.
It was never where it had to end.
– Moritz
Tiny tactical tip:
Next time a client names a budget before you've quoted, don't respond to the number at all.
Say "good to know," ask what the project needs to achieve, and quote from that. Then compare your quote to their number. The gap is money you were about to leave on the table.