Pricing a project when the client asks “what’s your hourly?”

It usually comes up in the first call, before anyone has described the work: “And what’s your hourly rate?” It is a reasonable question. It is also the wrong one for a project, and if you answer it with a number the whole conversation becomes an argument about that number.

Why the hourly rate misleads everyone

An hourly rate punishes experience. The faster you get, the less you earn for the same result. It also makes the client the manager of your time: every hour becomes something to question. And it tells them nothing about what the project will cost, which is what they actually wanted to know. The one arrangement where selling hours does work is a retainer that sells availability, not output.

The answer that works

Give a straight answer, then move. “For small, open-ended work I bill at 110 an hour. For a project like this I would rather quote a fixed price for a defined scope, so you know the number before we start. Can I ask a few questions about what you need?” Clients rarely object to that, because it offers them certainty, which is the thing the hourly question was reaching for. Work that hourly figure out before the call; the freelance rate calculator gets you there from your income goal and costs.

• Answer the question in one sentence so you are not evasive.
• Name the fixed price as the better deal for them: no surprises.
• Move immediately to scoping questions.
• Send the fixed quote with the hourly rate listed only for change requests.

Where the hourly rate still belongs

It belongs in the proposal, in exactly one place: the change-request line that keeps scope creep priced. “Work outside this scope is estimated in advance at 110/h.” There it protects you and informs the client, and it never becomes the headline. Review that figure once a year like any other price, and when it goes up, a rate increase letter gives the clients you already work with notice before it applies.