The first question most clients ask is the wrong one.

Almost every new project enquiry starts the same way. Someone reaches out, explains what they need, and somewhere in the first message asks: how much does this cost?

It is a completely reasonable question. I understand why it is the first one. Budget matters and people do not want to waste time if the numbers are nowhere near aligned.

But it is also the wrong first question. And answering it too early causes problems for both sides.

When a client leads with budget, one of two things tends to happen.

The first is that the number they give is too low for what they actually need. They say they have five thousand, the project clearly needs fifteen. Now there is a gap that is awkward to close. The client feels like the goalposts moved. The provider feels like they are being asked to justify a price that should have been obvious from the start.

The second is that the client gives a number that is higher than necessary. The scope quietly expands to meet it. Things get added that do not need to be there. The project gets more complicated and no better.

Both outcomes happen because price was established before scope was understood.

Scope is the only honest basis for price

What I need to know before I can give an accurate number is not what someone wants to spend. It is what they actually need.

How many pages? What kind of content? Is there existing branding or does that need to be created? Is there copy or does that need to be written? Is there a Figma file or does design start from scratch? What integrations are needed? What is the timeline?

Each of those questions has a real effect on the price. Answering them honestly takes maybe twenty minutes in a conversation. But those twenty minutes are the difference between an accurate quote and a guess.

A guess is bad for everyone. It leads to either an underpriced project that creates resentment halfway through, or an overpriced one that the client pays for things they did not need.

What the discovery call is actually for

I call the first conversation a discovery call but it is really a scoping session. The goal is not to pitch or to sell. It is to understand the project well enough to give an honest answer about whether I can help, what that would involve and what it would cost.

By the end of a good discovery call both sides know three things. Whether this is the right fit. What the actual scope of the work is. And roughly what that scope costs.

That is enough to decide whether to move forward. Everything else can be handled in the proposal.

When budget does matter

I am not saying budget is irrelevant. It matters. It is just not the first thing.

Once I understand the scope I always ask about budget. Not to work backwards from it but to check alignment. If someone needs a twelve-page multilingual SaaS site with custom animations and their budget is two thousand, it is better for both of us to know that upfront than to go through a full proposal process that was never going to lead anywhere.

Budget sets the boundary. Scope defines what happens inside it. Get scope first, then check if the boundary fits.

The one question that changes everything

Instead of asking how much is your budget, I ask: what does success look like for this project in six months?

That question tells me more than any budget number. It tells me what the project actually needs to do, what the client actually values and whether we are thinking about this the same way.

From there, everything else follows naturally. Including the price.

If you are thinking about a project and not sure what it would cost, the best thing to do is just reach out and describe what you are trying to achieve. We will figure out the rest from there.