Freelance Developer: Why Clients Don't Pay What You're Worth

I am Dejan Dozet, an independent software developer. I make a living from work I get the hard way — without an agency behind me, without a team finding clients for me, and without a guaranteed month. I have to find, assess, and bill every job myself.

That is why I do not think about pricing theoretically. I think about it every month.

A few days ago, I told a long-term client that my hourly rate was going up by twenty percent. He declined. There was no anger and no negotiation, just a short, “That won't work.” That same month, he was building a vacation house in the mountains.

It is not about that difference in price — how could it be?

Two types of clients

Some clients see you as an opportunity. They calculate: if this person builds a system that cuts my work from three hours to ten minutes, I will be ahead within a month. Price is not irrelevant to them, but it is always weighed against what they receive.

Others see you as a cost. To them, your invoice sits in the same column as electricity and office supplies. By definition, a cost should be reduced. No result can change the category they have put you in.

With the first group, a conversation about price takes five minutes. With the second, it lasts for months and never truly ends.

It is not always inability — sometimes it is ranking

For a long time, I thought clients who haggled simply had no money. For some, that is true, and there is nothing to hold against them — many small businesses are genuinely fighting to survive.

But then you notice a pattern. The same client who cannot pay twenty percent more is building a house. Another says your quote is expensive while sending messages from a trip through Switzerland.

These people have money. They simply do not spend it on you.

It is important to understand this without bitterness because it explains why negotiations always end in the same place. No one pushes builders on a construction site to lower their price. No one haggles with the materials supplier. Resistance is applied where someone gives in — and that is almost always the person working alone, for whom that one job matters.

The paradox I ignored for too long

The worst projects of my career were with the clients who paid the least.

The client who pays the least asks for the most changes, the fastest response, and the most explanations. They call you on weekends and keep you on the phone for hours. They change requirements as they go. They are never completely satisfied.

The reason is simpler than it looks. When the price is low, the client does not feel they are risking anything. And when they risk nothing, they have no incentive to be precise in their requirements, respect the agreement, or value your time. None of it costs them anything.

What it looks like when things go wrong

I built a website for a doctor who works abroad: the site, design, copy, an appointment-booking add-on, video-call integration, and custom payment on the website.

We agreed on EUR 700. Near the end, when I asked for the second instalment (EUR 350), he said he would not pay until the job was finished. I finished it and let him know. Then I waited two months for a response. When he finally replied, he sent me an AI-generated design proposal that was completely different from what we had agreed.

I spent 140 hours on that job. That comes to about EUR 5 per hour for work worth several thousand on the market.

I was not foolish. I was unprotected, which is something entirely different. I lacked three elements that I now always require: an advance payment, phased payments, and a written limit on scope. If I had had them, the overrun would have been visible after thirty hours, not at the end.

The sentence that should warn you

“I will reward you generously.”

I heard that from a client before I sent the quote. When the quote arrived, he said the price was high.

For a long time, I could not tell what bothered me about it, because the man has money — he travels, builds, and does not lack anything. Then I understood that the problem was not money but the relationship.

A reward is not a price. A reward is given by someone above to someone below. It implies that you will do the work cheaply or as a favour, and then receive something extra out of goodwill. That is probably what he is used to — people accommodate him and he returns the favour.

The problem is that such a relationship has no quote, no scope, and no deadline. There is only his assessment of what you deserved, made after you have already done everything.

That is why I now read that sentence as a warning. Not that there is no money, but that the two of us are not talking about the same kind of work.

What I concluded needs to change

1. Lowering your price does not bring better clients. It brings more of the same. A lower price is a signal, and it attracts precisely the buyer who chooses solely by price — the only quality such a client looks for, and the only one by which they can replace you tomorrow.
2. A published range always collapses to the lower bound. If you write “thirty to forty,” everyone reads thirty and negotiates from there.
3. Hourly billing has become a poor model. This is newer, and I think many people have not calculated it yet. If artificial intelligence lets you finish a job three times faster at the same quality, work that used to bring in one hundred now brings in thirty. To stay even, your hourly rate would have to triple — and no client will accept that, however justified it may be. With a fixed price, that problem does not exist: you charge for the result, and speed is your advantage, not the client's discount.
4. Terms must be the same for everyone, in advance. This is the most important one to me. If you require an advance, phases, and a defined scope from every client, you do not have to judge who will value you and who will not. The system does it for you. Whoever agrees has agreed. Whoever does not has selected themselves out.

Leaving without conflict

One client owed me a small amount for a year while regularly calling and keeping me on the phone for hours.

I did not tell him I could no longer work with him. I showed him how to use artificial intelligence for what he needed. Now he works on his own, he is satisfied, and I am at peace.

That was the best possible outcome with someone who could not pay anyway. It taught me something: you do not have to reject people — it is enough to offer them an alternative that genuinely helps. Those who accept it were not your clients in the first place.

What a price list cannot fix

For a long time, I thought my problem was how I positioned myself. It was not.

The problem was that I depended on channels that brought me the wrong people. Referrals carry a personal relationship that makes negotiation harder. Freelance platforms bring bidding wars with agencies that have people watching listings day and night. In both channels, someone else controls the terms.

No price list fixes that. It changes when you build something that makes you discoverable to the people looking for you. It is slow work and does not produce an immediate result, but it is the only thing that changes who knocks on your door.

Until that happens, there is nothing shameful about working for less than you are worth. Just do not declare that price to be your own.

If you are in a similar situation or have an experience different from mine, write to me — I would like to hear how you resolved it.