You knock out a logo in three hours that would've taken a junior designer three days. At $75 an hour, you earn $225 for the best work of your career. The slow beginner would have billed $1,800 for something worse. That's backwards. The thing making it backwards is the hourly model, and fixing it is the entire reason this argument exists.

Pricing isn't a personality test. The right model depends on the project, the client, and how well you can predict your own time. Most freelancers should understand all three and switch between them on purpose, not pick one and marry it. Here's how each actually behaves once money is on the line.

Hourly: simple, fair, and quietly limiting

You track your time and bill it. A web developer at $90/hour logs 22 hours and sends an invoice for $1,980. The math is honest, and nobody fights about scope, because the moment a client adds work, the clock just keeps running.

Hourly earns its keep in a few specific spots: open-ended work where the scope genuinely can't be pinned down, ongoing maintenance, "be available when I need you" retainers, and any client who changes direction every other week. In all of those, billing by the hour keeps you from working for free.

The ceiling is the problem, and it's structural. Your income maxes out at hours times rate, and a week holds only so many billable hours. You're also punished for getting good — the faster you finish, the less a task pays. And clients watch the meter. They'll question a 6-hour job that "felt like a 2-hour job" and start treating you like a taxi with the engine idling. Set your rate by working backward from what you actually need to clear after self-employment tax and all the hours nobody pays you for. Our hourly rate guide and the calculators walk through that math.

Project pricing: one number, one deliverable

You quote a flat fee for a defined outcome. "A five-page marketing site for $6,500." The client knows the damage upfront. You get paid for the result instead of the hours, so finishing early means the saved time is yours to keep.

For well-defined work, this is where most freelancers belong. A copywriter who's shipped 40 landing pages has a pretty good sense of how long number 41 takes. Quoting $2,500 flat instead of "roughly 18 hours at $120" pulls double duty: it kills the client's fear of a ballooning invoice, and it rewards your speed, because your real hourly rate creeps up every time you get sharper.

Scope creep is the trap. "Can you just tweak the homepage?" turns into ten unbilled revisions. Project pricing holds together only if you spell out what's included and — this part matters more — what isn't. A structure that survives contact with real clients:

  • Deliverables: exactly what they get, in plain terms.
  • Revision rounds: "two rounds included; further rounds billed at $X."
  • Out of scope: a short list of things that are explicitly extra.
  • Payment terms: a deposit (commonly 30–50%) before you start, balance on delivery.

To land on a number, estimate your realistic hours, multiply by your target rate, then tack on 20–30% because something always goes sideways. Call that a buffer, not padding. It's the cushion for the version of the project where the client ghosts for two weeks and then wants everything by Friday.

Value-based pricing: charging for the outcome

Now you price against what the work is worth to the client, not what it costs you to produce. Picture a consultant who builds an email sequence the client expects to throw off $200,000 in new revenue this year. Charging $40,000 isn't greedy — it's 20% of the value created, and the client signs happily because they pocket the other $160,000 they didn't have before.

Run the same job hourly: 50 hours at $150 is $7,500 for an identical result. The hourly version leaves more than $30,000 on the table, because the hours have nothing to do with what that sequence was worth.

Three things have to be true for this to work. The work has to move a number the client can measure in money — revenue, savings, time, risk dodged. You have to credibly tie your work to that number. And you need to be talking to someone who owns a budget and cares about the result, not a procurement desk lining up hourly rates on a spreadsheet.

It falls apart when the value is fuzzy or small. A $200 blog post doesn't unlock six figures, so don't jam it into that frame. Value pricing also demands actual conversations. You have to ask what the project is for, what a win is worth, and what it costs the business if nothing changes. Skip the discovery and there's no value price to quote.

A worked comparison

Say you're building a checkout flow meant to lift a store's conversions. Same work, three ways to price it:

  • Hourly: 40 hours x $100 = $4,000. Predictable for the client, capped for you.
  • Project: flat $6,500, scope defined, two revision rounds. You wrap in 35 hours, so your effective rate lands around $186/hour.
  • Value-based: the store does $2M a year online, and the new flow is projected to add 8% in sales — call it $160,000. You quote $20,000, roughly 12.5% of first-year value.

The work never changed. Only the framing did. That's the whole lesson in one example.

How experienced freelancers climb the ladder

Almost nobody starts at value-based pricing, and you shouldn't try. The path tends to run like this. You start hourly because you honestly can't tell how long things take yet. After you've done a type of project enough times, you flip that work to flat fees, which instantly pays you back for the speed you've built. Then, for high-stakes jobs with measurable upside, you start pinning price to outcomes.

What bridges project pricing and value pricing is one habit: asking sharper questions before you quote. Swap "how many pages do you need" for "what does this have to accomplish, and what's it worth if it works?" Even when you still send a flat project fee, those answers let you anchor the number to the client's stakes instead of your hours.

A useful halfway step is tiered proposals. Put up three options — lean, standard, premium — at three prices. Clients almost always pass on the cheapest and rarely grab the priciest, which quietly steers them to the middle and flips the question from "is this too much?" to "which one?"

Don't forget the tax math

Whatever you charge, the IRS treats you as a business. You owe self-employment tax (Social Security and Medicare, roughly 15.3% on net earnings) on top of income tax, and you'll generally make quarterly estimated payments. A $6,500 project is nowhere near $6,500 in your pocket, so carve off a real chunk for taxes from every invoice. Reading the IRS overview of the self-employment tax once will stop the numbers from blindsiding you. For the deeper version, see our quarterly estimated taxes guide.

So which one wins?

None of them, every time. Reach for hourly when scope is genuinely unknown or the work is open-ended support. Reach for project fees on anything you've done enough times to estimate with confidence — that's the default for most established freelancers. Reach for value-based when the outcome is measurable, large, clearly tied to your work, and you've earned the trust to have that conversation.

The freelancers who earn the most didn't pick the "best" model. They matched the model to the job, and they kept asking, on every project, what the thing was actually worth.

This article is general educational information, not personalized financial, tax, or legal advice. Confirm the specifics with a qualified professional or an official source like the IRS for your own situation.