Why designers find it so hard to name a price

We talk about value with a good deal of fluency. Why a product decision saves months, why a well resolved interface reduces support load, why research costs less than building blind. And then the moment comes to turn all of that into a number, and the voice drops.

It has happened to me and I have seen it in plenty of people who came from design. I do not think that is a coincidence, and I do not think it is a market problem or a matter of clients not valuing the work. It is more uncomfortable than that.

A price makes you say what you are worth

A quote is the one part of the job where you cannot hide behind process. You can defend a design decision with arguments, with data, with references. A number does not allow that: either you say it or you do not, and the moment you say it you are asserting something about yourself that you cannot qualify afterwards.

That is where the hedging comes from. The phased quote so the large figure never appears at once. The discount offered before anybody asks for one. The line saying we can talk about it if it seems like a lot, written into the same email as the proposal. None of that is commercial flexibility. It is apologising in advance.

Looking at what others charge is not research

The usual reaction to not knowing what to charge is to go looking for references. You check what comparable people charge, work out an average, and place yourself slightly below it, because you do not yet feel like you belong at that average.

That is not market research. It is fear wearing the clothes of a method. And it has a deeper problem: the prices you can see published belong to the people willing to publish them, which is not a representative sample of anything. You are averaging a self selected group and treating the result as data.

Placing yourself below it does not make you more likely to be chosen either. In professional services a price works as a signal, and a number well under everybody else raises an awkward question in the mind of whoever reads it.

The signal that actually matters

There is one signal worth more than any comparison, and it is simpler: somebody asking what it costs without you having raised the subject.

That question means the person has already decided internally that they want it and is working out whether they can afford it. It is a completely different point in the conversation from the one where you introduce the price yourself, because there you are still persuading.

When the question arrives on its own, whatever number you say gets measured against value that person has already recognised. When you say it first, it gets measured against nothing.

The first number is always wrong

This took me a while to understand and it saved me a lot of anxiety once I did: a price is far easier to correct than it is to introduce.

Raising a price for new clients needs nobody permission. Lowering it needs nobody permission either. The only genuinely expensive one is the first, because it is the one that breaks the deadlock, and waiting until a number feels completely right is an elegant way of never deciding.

If you name it and nobody walks away, you were cheap. That is useful information, even if it takes a while to sound like it. And if somebody does walk away, that is useful too: you have just found where your ceiling is without having to ask anyone.

What I do now

I write the number before the conversation, not during it. In the moment I always go lower, because the pressure of somebody waiting in front of you for an answer beats any conviction you arrived with.

And I send it in writing, with no ornament and no pre emptive justification. A proposal that spends three paragraphs explaining why it costs what it costs has already conceded that it costs too much.

Questions people ask about this

How do I price a digital product with no references to go on?

Start with a number you can say out loud without justifying it, and test it. The useful reference is not what other people charge, it is what happens when you say yours: if nobody leaves, it was low. That is faster and more reliable than any comparison table.

Is it better to charge hourly or by project?

By project, almost always. Charging by the hour penalises you for exactly what you have learned: the better you get, the less time it takes and the less you earn. It also turns every conversation into a negotiation about your speed rather than about the outcome.

What do I do when a client says it is expensive?

Ask compared to what. Most of the time the answer reveals they were comparing against something other than what you proposed, and that conversation is more useful than a discount. If the budget genuinely is not there, lowering the price does not fix it either: the thing to adjust is the scope.

Should I publish my prices on my site?

If your work is repeatable, yes, because it filters out conversations that were never going anywhere. If every project is different, an indicative range does the same job without committing you to a number you cannot stand behind.