How to Price Your Services (Without Underselling)

Pricing is the part of freelancing that keeps people awake at night. You can be good at the actual work, land a client who wants to hire you, and then freeze the second they ask the only question that matters: "So what do you charge?" Say a number too low and you resent the job for weeks. Say a number too high and you worry you just talked yourself out of the money. Most people guess, feel sick about it, and move on. That guess is usually too small, and it tends to stay too small for years.

This guide is about pricing services with a clear head. Freelancing, an agency, coaching, done-for-you work of any kind. We will walk through the three ways people charge, why beginners almost always underprice, and the mindset shift that changes everything: you are not selling your time, you are selling a result.

The short version#

There are three common ways to price a service. You can charge by the hour, charge a flat fee for the whole project, or charge based on the value the result creates for the client. They are not equally good. Hourly pricing is the easiest to explain and the worst for your income, because it caps what you can earn and punishes you for getting faster. Project pricing is a big step up. Value-based pricing is where experienced people end up, because it ties your fee to what the work is actually worth to the buyer rather than how long it took you.

Beginners underprice for reasons that have almost nothing to do with skill. They price from fear, they price by copying the lowest number they see online, and they quietly assume the client is comparing them to the cheapest option available. Usually the client is not. The fastest raise you will ever give yourself is learning to talk about outcomes instead of hours.

Where does the money actually come from?#

A client does not pay you for your time. They pay you because the work you do is worth more to them than the fee they hand over. That gap is the entire business.

Client has a problem that costs them money or time
  ↓
You deliver a result that fixes it
  ↓
The result is worth $X to the client's business
  ↓
You charge some fraction of $X as your fee
  ↓
Client keeps the difference and is happy to pay
  ↓
You keep the fee minus your small costs

Look at the third line. That is where pricing lives. If the result you deliver is worth a lot to the client, you can charge a lot and they will still come out ahead. If the result is worth very little, no amount of confidence will let you charge a premium. This is why the same skill, say writing sales emails, can pay wildly different amounts depending on who you write them for. A hobby blogger and a company doing serious revenue by email are buying the same words, but the value on their end is not remotely the same.

Hourly pricing hides this completely. When you bill by the hour, you are pricing your time instead of the client's outcome, and your time has a hard ceiling: there are only so many billable hours in a week. We break down why that ceiling exists and how the whole model works in how freelancing actually makes money. The rest of this guide is about climbing off that ceiling.

The three ways to charge#

Hourly#

You track your hours and bill a rate for each one. Simple, transparent, and the client feels safe because they only pay for time spent.

The problem is that hourly pricing quietly works against you. The better and faster you get, the less you earn for the same result, which is backwards. It also caps your income at a hard wall. If you charge $50 an hour and can realistically bill 25 hours a week after admin, sales, and life, your ceiling is around $1,250 a week no matter how good you are. And it invites the client to watch the clock and question every hour instead of judging the result.

Hourly is fine when the scope genuinely cannot be defined up front, such as ongoing ad-hoc help where nobody knows how much work will show up. For most defined work, it is the weakest option.

Per project#

You quote one flat fee for a clearly defined piece of work. "A five-page website for $2,500." "A set of ten sales emails for $1,200." The client knows the total before they commit, and you get rewarded for being efficient, because finishing early does not cut your pay.

Project pricing is a large improvement for one reason: it breaks the link between your income and the clock. If you get faster, your effective hourly rate goes up and nobody notices or cares, because they bought a result, not a timesheet. The risk is scope creep, the client asking for "just one more small thing" until the project balloons past what you quoted. The fix is a written scope that says exactly what is included and what counts as extra. This model pairs naturally with packaging your work into fixed, repeatable offers, which we cover in productized services explained.

Value-based#

You price against what the result is worth to the client, not what it costs you to produce. If a project is realistically going to help a client earn or save a meaningful amount, your fee is a fraction of that number rather than a multiple of your hours.

This is the highest-earning model and the one that makes beginners nervous, because it feels like charging "too much" for something that did not take you long. But the client is not buying your effort. They are buying the outcome, and the outcome is worth what it is worth regardless of how fast you delivered it. Value-based pricing requires two things beginners usually skip: a real conversation about what the result is worth to the client, and enough confidence in your work to stand behind the number. You do not get there on your first job. You get there by delivering results, tracking what they were worth, and using that as evidence.

A worked example: the same job, three ways#

Let me put numbers on this. These figures are hypothetical, chosen to show the logic, not real client data or a promise of what you will earn.

Say a small online store hires you to rewrite the product pages and checkout flow for their best-selling item. The work takes you about 20 hours. Here is how each pricing model plays out.

Hourly. You charge $60 an hour. Twenty hours means you invoice $1,200. Clean and simple. But notice what happens if you are experienced and knock it out in 12 hours instead of 20: now you only earn $720 for the exact same finished pages. You got punished for being good. And the client, watching hours accumulate, may push back on any hour that looks long.

Per project. You quote a flat $1,800 for the rewrite, scope written down, two rounds of revisions included. The client knows the total up front and says yes. If it takes you 20 hours, your effective rate is $90 an hour. If your experience lets you finish in 12, your effective rate jumps to $150 an hour, and the client is just as happy because they got exactly what they paid for. Same work, more money, less clock-watching.

Value-based. Before quoting, you ask a few questions. The store tells you this product does roughly $10,000 a month in sales (their number, hypothetical here). A rewritten page that lifts conversion even modestly could be worth a few thousand dollars a year to them, possibly more. Against that, a fee of $3,500 is easy to justify, because if the work does what it is supposed to, they earn the fee back and then keep earning. You are not charging "$175 an hour." You are charging a fraction of the value you are creating. The client evaluates it against the payoff, not against your effort.

Same 20 hours of work. $1,200, $1,800, or $3,500 depending only on how you framed the price. Nothing about your skill changed between those three numbers. What changed was what you chose to charge for.

What you need and what it costs#

The good news about pricing better is that it is nearly free. You do not need to buy anything to raise your rates. Here is the honest split.

Required (and mostly free):

• A clear, written scope for each offer, so "the project" means the same thing to you and the client.
• A simple way to send an invoice. A free invoicing tool or even a clean PDF is enough to start.
• The willingness to say a number out loud without immediately discounting it.
• A few questions you ask every client about what the result is worth to them. This is the raw material for value-based pricing.

Optional (add later if they earn their keep):

• A contract template for larger projects, worth it once deals get big enough that a handshake feels risky.
• Proposal software that makes your quotes look polished. Nice, not necessary.
• An accountant once your income is large enough that tax gets complicated.

Do not let anyone talk you into a stack of paid tools before you have clients. The thing holding your income back is almost never software. Resist the shiny toolset early, a trap we describe in productized services explained and elsewhere on the site.

How long it takes to get pricing right#

Pricing is a skill you improve on every job, not a number you set once. Expect it to move in stages.

Your first few clients, you will probably charge too little. That is normal and, honestly, fine. Early low prices buy you something valuable: reps, testimonials, and proof that you can deliver. The mistake is staying there. Getting that first paying client is its own hurdle, and we cover it in how to get your first client.

Within your first several projects you should move from hourly to project pricing, because by then you can estimate scope well enough to quote a flat fee. Somewhere after that, once you have delivered results you can point to, you can start having value conversations and pricing against outcomes. There is no fixed calendar for this. A person doing steady work will get there faster than someone taking one job every couple of months, simply because they accumulate evidence and confidence quicker.

What beginners get wrong#

They price from fear instead of value. The internal question becomes "what is the most I can charge before they say no?" when it should be "what is this result worth to them?" Fear pricing always lands low.

They copy the cheapest number online. Marketplaces are full of people racing to the bottom. Pricing yourself against the cheapest listing you can find assumes your client is shopping purely on price. Serious clients usually are not, and the ones who are will be a headache anyway.

They undercharge to win the deal, then resent it. A price low enough to guarantee a yes is often low enough to make you hate the work by week two. A client who says yes instantly to your first number may be a sign you went too low.

They apologize for the price. Naming your fee and then immediately softening it, "but I can be flexible," "I know that might be a lot," teaches the client to negotiate down before they have even reacted. Say the number. Then stop talking.

They confuse being busy with being paid. Twenty low-rate hourly clients feel like success because you are slammed. But busy is not the goal. Profit per hour of your life is. Raising rates and taking fewer, better clients almost always beats stacking cheap ones.

They never raise rates on existing clients. The rate you set two years ago is not the rate you should be charging today. Good clients expect increases over time. Silence is not loyalty, it is just leaving money behind.

How I would start#

If I were pricing services from scratch, here is the path I would take.

I would pick project pricing as my default from day one and skip hourly entirely unless the scope was genuinely impossible to define. Even as a beginner, quoting a flat fee for a defined piece of work trains the right habit: pricing the result, not the clock.

I would package my work into two or three fixed offers with clear scopes and set prices, so I was not reinventing a quote every conversation. That packaging is the bridge from trading hours to selling a repeatable outcome, and it also makes recurring income easier to build later. The natural next step, turning one-off projects into monthly income, is covered in retainers explained.

I would ask every prospect one simple question before quoting: "If this works the way we both want, what is it worth to you?" Even when I could not price purely on the answer yet, it would tell me whether I was aiming too low, and it would slowly build my instinct for value.

And I would raise my rates deliberately. A simple rule: whenever I have more demand than I can comfortably take, the next new client gets a higher number. Demand is the signal that your price is too low, so I would let it push my rate up instead of just working more hours.

What I would not do#

I would not compete on being the cheapest. It attracts the worst clients and there is always someone willing to go lower. I would not bill hourly for defined work and then quietly punish myself for getting faster. I would not discount the second a client paused, silence is not rejection, it is thinking. I would not set one price and leave it untouched for years. And I would not wait for perfect confidence before charging a real rate, because confidence comes from delivering at a fair price, not from a mindset you finally achieve one morning.

The real shift#

Everything in this guide comes down to a single change in how you see the transaction. When you charge by the hour, you are selling pieces of your life, and there is a fixed number of them. When you charge for the outcome, you are selling something the client wanted anyway, and the price is tied to how much they wanted it. That is not a trick or a mindset hack. It is just a more honest description of what a service actually is. The client never wanted your hours. They wanted the thing your hours produce.

Get that straight and pricing stops being the scary part. It becomes a conversation about value, which is a much easier conversation to have than defending a timesheet. If you want the bigger picture of how service income fits alongside every other way people earn online, start with how freelancing actually makes money, and when you are ready to map out your own path, our free blueprint walks you through it step by step.