Pricing Design Work Honestly

Pricing is the part of the job nobody teaches, so most of us learn it by accident. A number slips out in a call, the client says yes too quickly, and you spend the whole project quietly resenting it.

What follows is the approach I settled on after a few of those. It is not a formula. It is a way to make the number honest, to you and to the client, so that the project can start without anyone holding their breath.

Start with what the work actually costs

Before any proposal, I write down what a project takes, including the hours nobody sees. Early in my career I priced only the time spent in the design tool, and the projects always came out cheaper than they felt. The difference was everything around the screen.

• Time on the design itself, rounded up rather than down.

• Meetings, emails and the small revisions that never feel like work.

• Software, fonts and licences bought for this project.

• A share of the time you spend finding the next client.

If a figure is missing from that list, it ends up paid by you instead of by the project. The last item surprises people most. Finding work is part of doing work, and a fair price carries a small piece of it.

Hourly, daily or per project

Each model hides a different risk, and none of them is wrong on its own. The mistake is picking one by habit instead of by the shape of the job.

I use per-project pricing for most work and keep a day rate for anything open-ended. Whichever you choose, say plainly why. A client who understands the reasoning is far less likely to bargain against it.

Say what is included

A price without a scope is only half a price. My proposals list three things in plain sentences: what I will deliver, how many rounds of revision are included, and what counts as new work. I keep the list short enough to read in one minute.

A clear scope is not a defence against the client. It is a promise to both sides.

The revision limit is the line people hesitate to write down. I say it kindly and I say it early: two rounds are included, and further rounds are quoted. Nobody has ever walked away over it, and it quietly protects the quality of the work.

When the scope changes

It will. A client sees the first layout and realises they also need a second language, or a print version, or a different audience. That is normal and it is not an attack on you. When it happens, I name the change, give the cost, and ask if they want to go ahead. It takes two minutes and avoids the awkward invoice at the end.

A short script

“That’s a new direction, which is outside what we agreed. I can do it for an extra amount, or we can keep the current plan. Which do you prefer?”

Notice that the question gives the client a real choice. They stay in control of the budget, and you stay in control of the workload.

Talk about money early

I raise budget in the first conversation, not the third. It sounds blunt, but it saves both sides from a week of work on a project that was never going to fit. A range is enough: “projects like this usually land between X and Y. Does that work for you?”

If you want to see how I read a brief before quoting, From Brief to First Sketch covers it. A good quote is mostly a good understanding of the problem.

Don’t discount out of fear

When a client pushes back, my first reply is a question: what part of the price worries you? Often it is the scope, not the number, and scope can change without touching what you are worth.

If I do lower the price, I lower the work with it. Fewer revisions, a smaller deliverable, a later date. Cutting the price while keeping everything else teaches the client that the first number was never real.

Send the invoice kindly and on time

The last part of pricing is getting paid. I invoice the day a milestone is approved, with payment terms stated in the proposal, and I follow up once, politely, when it is late. Being calm and consistent about money is a professional habit, and clients tend to match it.