The freelancer's guide to setting rates when you're terrified of charging too much

There's a specific moment that catches most new freelancers off guard, and it isn't the first client conversation or the first invoice. It's the moment right before you say a number out loud, when your entire nervous system seems to organise itself around the fear that you're about to ask for too much.

This fear is worth taking seriously rather than talking yourself out of, because it isn't irrational. Naming a price is a genuinely different act from negotiating a salary, where a range was set by someone else and your job was to push toward the top of it. Here, you're the one setting the number, in public, with your name attached to it. But the fear of charging too much is doing more damage to most freelance careers than the thing it's protecting against ever would. Here's how to think about rates in a way that accounts for the fear without letting it set the number.

Why underpricing feels safe and isn't

The logic behind a low starting rate is intuitive: you're new to this, you haven't proven yourself as an independent, and a lower number reduces the risk of rejection. If a client says yes to a modest rate, the yes feels safer to interpret than a yes to a rate that would have felt bold to name. This is the reasoning almost everyone uses, and it is almost always wrong, for reasons that only become visible after a few months of working at the rate you set out of fear rather than out of a clear-eyed read of your value.

The first problem is that underpricing doesn't just cost you money on the current engagement — it sets a reference point. Clients anchor to the first number they pay you. Raising a rate with an existing client requires a specific, often uncomfortable conversation that your original lowball price made necessary and that a fair starting price would have avoided. You're not just choosing a rate for one project. You're choosing the number every future conversation with that client will be measured against.

The second problem is less obvious and more corrosive: underpricing changes how you show up in the work itself. When the rate feels too low relative to what you know you're capable of, resentment accumulates quietly, project by project, in a way that's hard to name and easy to misattribute to the client, the work, or freelancing itself, when the actual cause is a number you set out of fear six months ago and never examined again. Financial anxiety about being underpaid does not stay contained to the invoice. It leaks into the work.

The number to start from — and why it isn't your old salary

A useful starting calculation: take your most recent annual salary, divide it by roughly 220 working days, and double the result. That's a rough day rate. The doubling isn't padding or nerve — it's the cost of things your employer used to absorb without you noticing: the unpaid gaps between engagements, your own pension contribution, holiday and sick pay that no longer exists, self-employment tax, an accountant, software, professional insurance some clients will require before they'll sign anything. A salary was never just your take-home pay. It came with a whole invisible support structure, and your rate now has to fund that structure itself.

If you take that number and it still feels frightening to say out loud, that's useful information, but not in the direction most people take it. It doesn't mean the number is wrong. It means you haven't yet separated "this number is uncomfortable to say" from "this number is inaccurate." Those are different signals, and conflating them is the single most expensive mistake in freelance pricing. The discomfort is about you saying a number in public for the first time. The accuracy is about whether the number reflects what the work is actually worth to the person paying for it. Most people solve for the discomfort by lowering the number, when the discomfort was never really about the number at all.

Worth naming directly: a client who has a real budget for the outcome you provide is not comparing your rate to what you used to earn as an employee. They're comparing it to what the problem costs them if it stays unsolved, and to what an agency or a full-time hire would cost to get the same result. Against that comparison, a rate that feels enormous to you is often still a bargain to them. You're not pricing against your own salary history. You're pricing against the value of the outcome, which is a completely different number and is usually a larger one.

What it actually means when a client says you're too expensive

This is the moment the fear is really about, and it deserves to be examined directly rather than avoided by pricing low enough that it never comes up. When a client pushes back on a rate, it rarely means what the fear tells you it means.

Sometimes "too expensive" means the budget genuinely isn't there — the client likes what you'd do but the money for it doesn't exist in their current plan. That's not a verdict on your worth. It's a mismatch between your rate and a specific constraint, and it says nothing about whether the rate is fair. Sometimes it means the value hasn't been made concrete enough — the client is pricing against a vague sense of the work rather than a specific articulation of the outcome, and the fix is a clearer conversation about what changes for them, not a lower number. And sometimes, less often than the fear suggests, it genuinely is a signal to adjust — but even then, it's a data point about one client's budget in one moment, not a referendum on your value as a freelancer.

The practical shift that helps most: treat "that's more than we were expecting" as the opening of a negotiation, not the end of one. There's usually room to adjust scope, timeline, or payment structure before the rate itself needs to move. Reducing the rate should be the last lever you pull, not the first, and pulling it first is exactly what fear trains you to do by default.

Raising your rate without blowing up the relationship

At some point, usually somewhere between the third and sixth engagement, most freelancers realise their rate has fallen behind what the work is actually worth, and the question becomes how to raise it without damaging a relationship that's otherwise working well.

The direct approach works better than the indirect one. A message along the lines of "starting with our next engagement, my rate will be [new number] — I wanted to give you advance notice" is complete on its own. It doesn't need an apology, a lengthy justification, or a discount offered pre-emptively to soften the news. Clients who value your work expect rates to rise over time; it's a normal feature of a working relationship, not a rupture in it. The apologetic version — padded with qualifiers, offering to hold the old rate "just this once," explaining at length why the increase is warranted — signals uncertainty about whether the new number is deserved, and that uncertainty is what damages the relationship, not the increase itself.

Giving reasonable notice matters more than the size of the increase. A rate change announced with a full project cycle of lead time, rather than sprung on an invoice, gives the client room to plan and reads as professional rather than abrupt. Most clients who value the working relationship will simply adjust. The ones who leave over a fair, well-flagged increase were usually the ones getting the most value relative to what they were paying — which is useful information about your previous rate, not a loss worth mourning.

Day rate, project rate, or retainer — and when each protects you

The rate model you choose changes how much the fear of "too expensive" can affect you, independent of the number itself. A day rate is the easiest to reason about and the easiest for a client to compare against alternatives, which makes it a reasonable default while you're still calibrating what your work is worth. Its weakness is that it ties your income directly to hours logged, which caps what experience and efficiency can earn you — the better and faster you get, the less a day rate rewards it.

A project rate, priced against the outcome rather than the hours, is where experienced freelancers eventually migrate, because it lets your growing efficiency work in your favour instead of against it. The difficulty is pricing it accurately before you've done the work, which takes a few projects to get calibrated — early project-rate quotes tend to run low because it's hard to estimate effort you haven't yet learned to estimate. Padding the estimate more than feels comfortable, in the early going, is the correct move, not a dishonest one.

A retainer — a fixed monthly amount for ongoing availability or a defined scope of recurring work — is the most stable of the three and the one that does the most to quiet the underlying fear, because the pricing conversation happens once rather than at the start of every engagement. It's also the hardest to get a client to agree to before they've seen your work directly, which is why retainers tend to come later, from clients you've already delivered for under a day rate or project rate.

Sitting in the silence after you've named the number

Almost everything above is arithmetic and negotiation mechanics. The actual skill being built, underneath all of it, is the ability to say a number and then tolerate the silence that follows without rushing to fill it. That silence is where new freelancers lose the most value, not in the number itself.

The instinct to fill it comes from the same place as the instinct to underprice in the first place: a fear that the number, sitting there unexplained, will be judged and found excessive. But a price doesn't need active defending the moment it's spoken. It needs to be stated clearly and then left alone. If the client has a question or an objection, they'll raise it, and you can respond to what they actually say rather than to what you're afraid they're thinking. Responding to an imagined objection before it's been voiced is how freelancers negotiate against themselves without a client ever having to say a word.

This gets easier with repetition in a way that no amount of reading about it will substitute for. The first time you name a rate that feels too big and the client simply says "sounds good, let's do it," something recalibrates that no framework can talk you into on its own. It's worth engineering that first repetition deliberately — naming a fair number even when it's frightening — because the fear shrinks fastest through evidence, not through reassurance.

The piece on landing your first freelance client is the natural companion to this one if you're still working out where the client conversation even starts. The honest account of the first six months freelancing after burnout covers the underpricing mistake in more detail, including what it actually cost. And the first 90 days of going independent as a former PM has the real financial picture of a rate set correctly from the start, month by month.