Pricing

Why freelancers undercharge (and what actually fixes it)

The confidence explanation is wrong and the structural explanation is incomplete. The real problem is that nobody in this trade has a reliable reference point, and a person without one anchors on whatever number they heard last.

N

North

2026-06-02 · 4 min read

Why freelancers undercharge (and what actually fixes it)

Ask why freelancers undercharge and you will get two answers. The popular one is confidence: know your worth, value yourself, charge what you are worth. The better one, which has been displacing it for a few years now, is structural: hourly billing hides value, scope creep eats margin, marketplaces rank on price.

The second answer is a real improvement and it is still not the whole thing, because it does not explain the freelancer who has read all of that, switched to project pricing, written a scope line, left the marketplaces, and is still quoting low. There are a lot of those. I think the missing piece is simpler and less flattering to everyone, including the people who write pricing advice.

Nobody in this trade has a reliable reference point, and a person without a reference point anchors on the last number they heard.

We went looking for one. Last year North ran about seventy published freelance-pricing claims through adversarial verification: rate tables, project-cost brackets, the confident percentages that show up in every pricing article. Sixteen survived. Nine were refuted outright. No fixed-fee project range for logos, identities, websites, illustration or photography made the survivor list — not one, in any currency. The confident-looking tables are, as far as we could establish, made up.

That absence is the actual mechanism. In most trades a price has a shape you can feel: you know roughly what a plumber costs because you have paid one, and so has everyone you know. A branding project has no such shape. So when you sit down to quote, the only numbers available to you are the last thing you charged, the number a peer mentioned once at a meetup, and whatever the client hinted at. All three are anchors, none is evidence, and two of the three are biased downward — your last price because you were less experienced when you set it, the client's hint because it is in their interest.

Underneath that sits a second problem, which is that freelancers are unreliable narrators of their own finances. There is an exchange on Hacker News I keep returning to, where someone volunteers that they bill around fourteen thousand a month and, after taxes, walk away with about seven. The figure is trusted precisely because it gives away the deflating half. Most rate conversations do not. They quote the top-line number and skip tax, unpaid admin, the invoice that arrived nine weeks late, the two weeks between projects. You are not benchmarking against your peers' income. You are benchmarking against their invoices, which are a much bigger number.

And billed is not banked. Another developer, in a Hacker News thread in 2014 about clients who vanish, described one who skipped town without paying any of his developers and summed up his own position as being out like five thousand, question mark. That shrug is the right register for how most freelancers hold this information. The money you did not collect does not appear in anybody's rate conversation, including your own, and it should, because a year with two of those in it is a different year from the one your invoices describe.

So what actually fixes it.

Not a pep talk, and not only the structural fixes, though you should do those. The fix is to build the reference point the market refuses to give you, per project, from the only source that has one: the client. What is the thing worth to them? Not in general — in this business, this year, in a number they will say out loud. That figure is available surprisingly often and almost nobody asks for it. It gives your price something to be proportionate to, which is the thing you have been missing, and it is durable in a way that a benchmark never was, because it belongs to the job in front of you rather than to an average of strangers. The questions that get it out of a client are the closest thing this trade has to a pricing method.

The second fix is to write your floor down before the conversation, not during it. Hours you expect to spend, times the rate you need to survive. Not to quote it, and not to defend it. Just so that when the anchoring starts you have one number in the room that came from you. A calculator that does the floor arithmetic takes about two minutes and removes the excuse.

The third is to stop treating a lost job as a verdict. You quote a handful of projects a quarter. That is not a sample size, and reading your own win rate as a signal about your prices is how a run of bad luck turns into a permanent discount. Do the arithmetic on the year, not the month.

The version of this advice you will read elsewhere ends by telling you to value yourself. Mine ends by telling you that the reason this is hard is not a personal failing and not entirely fixable: you are pricing in a market that has deliberately never published a price. Get the number from the client, keep your floor in your pocket, and stop comparing yourself to invoices you have never seen.

Share this post

Frequently asked questions

How do I know if I am undercharging?
The old tell — that you win nearly every job you quote — is weaker than it sounds, because a solo freelancer quotes too few jobs a year for the ratio to mean anything. A better check is whether you can say out loud what the last project was worth to the client who bought it. If you cannot, you were not pricing, you were guessing, and guesses drift downward under pressure.
Does raising my rate mean losing clients?
Some, yes, and the arithmetic still usually favours it. What the encouraging version leaves out is that the departures are not evenly distributed: price-sensitive clients leave first, which is the intended effect, but so do a few good ones whose budgets are genuinely fixed. Budget for a lean quarter rather than expecting a clean swap.

From the blog

Plain-spoken guidance on the business side of your craft.

View all posts