What value-based pricing actually means for freelancers

Most proposals list chores and staple a number to the bottom

Picture your last proposal.

Five pages. Homepage, about page, contact form, three rounds of revisions. A tidy little grocery list of everything you're going to build.

And then, way down at the bottom, in slightly nervous font size... the price.

You know the feeling. You stared at that number for twenty minutes wondering if it was too high. It wasn't. It was just naked. Sitting there next to a chore list, begging to be compared against the next freelancer's chore list.

Here's the thing nobody told you.

A task list turns you into a vending machine. Client puts in coins, page comes out. And vending machines compete on one thing only... who charges less for the same can of Coke.

This is where value based pricing walks in. As Benek Lisefski, a designer with 17 years behind him, puts it, value based pricing is still a fixed fee like project pricing. The difference is in how you arrive at and justify that fee.

Same fee. Different reasoning.

And the reasoning is everything. In one practical guide for freelancers, the example is blunt: if you're rebuilding an e-commerce site and the client expects a 20% revenue increase, that outcome is worth more than the hours you invest.

The hours don't move the client. The 20% does.

So the whole game is swapping your list of chores for the client's desired result. That's it. That's the mutation. Everything else in this article is just showing you the exact sentences.

Clients don't buy the wrench turns. They buy the car starting.

Think about a mechanic.

Imagine one who hands you an invoice that reads: loosened 14 bolts, turned wrench 62 times, applied grease. And a price.

You'd laugh. You don't care how many times he turned the wrench. You care that your car starts when you turn the key.

That's your proposal right now. A list of wrench turns.

The client is standing in the parking lot going... but does it drive?

This is the myth that keeps freelancers broke: the belief that if you just prove you're skilled enough, list enough deliverables, show enough credentials, the client will happily pay. So you pile on the tasks. More pages, more features, more proof that you're worth it.

And the client still balks at the price.

Shannon Mattern, who runs the Web Designer Academy, nails why. When a client says it's out of their price range, the real reason is they can't see how parting with your fee today will help them create many times more than that later, not just in dollars but in time, capacity, and sanity.

Then she delivers the gut punch.

You assume they already know the value of a website, so you've been busy convincing them that you are worth it. But they're not looking for evidence that you're worth it.

They're looking for evidence that the result will be worth it.

Big difference. Your credentials answer a question the client isn't asking. The outcome answers the one they are.

So stop selling the wrench turns. Sell the car starting.

The web designer rewrite: one conversion line instead of a page count

Let's get concrete. Here's a designer's proposal before and after. Same project, same designer, two sentences apart.

Before, the scope line reads:

• "5-page website redesign: homepage, services, about, blog, contact. Mobile responsive. 3 rounds of revisions. Fee: $3,000."

Tidy. Also a vending machine.

Now the after. Same designer, one outcome line, price sitting right behind it:

• "Rebuild your product pages to lift checkout conversions from 1.8% to a target of 3%, which at your current traffic is roughly $60,000 more in annual revenue. Investment: $7,500."

Notice what changed. The tasks are still in there somewhere, buried in an appendix where they belong. But the headline is a number the client's CFO would recognize.

And the price went up, not down.

This isn't wishful thinking. In three pricing conversations coached last month, the freelancer who moved from an hourly rate to a value anchor raised their per-project income by roughly two and a half times... on work that actually took less time.

I've watched this same swap play out with freelancers I work with, and the pattern is boringly consistent: the moment the fee sits next to a revenue number instead of a page count, the price objection quietly disappears. Nobody argues about $7,500 when it's standing next to $60,000.

Use a real, specific number too. Not "increase conversions." Say 1.8% to 3%. Say $60,000. Specific numbers feel researched and rational. Round, vague ones feel like you pulled them out of the air, which makes the client suspicious you did the same with your fee.

The outcome doesn't have to be a promise you'll get sued over. It's a target you're pointing at together. But it has to be measurable, or you're back to selling wrench turns.