How Much Should You Charge as a Freelancer? Hourly vs. Flat-Rate Pricing

You've decided to start freelancing. Maybe you've even found your first potential client.

And then comes the big question:

How much should I charge?

€20 an hour? €50? €120?

Should you tell the client your hourly rate, or would it be better to offer one fixed price for the entire project?

The internet is full of advice about freelancer pricing. Some people say you should always charge by the hour. Others insist you should never sell your time and should charge for results instead.

I think both approaches have their place.

I've used hourly rates, flat project prices, and combinations of the two in my own freelance work.

And I've learned that the most important thing isn't necessarily which pricing method you choose.

It's understanding what your time is worth, how much of it a project actually consumes, and whether the final amount makes sense for you.

Let's start there.

1. Find out what people in your industry charge

Before setting your prices, it's worth understanding the market you're entering.

A freelance graphic designer, software developer, CAD engineer, and management consultant might all have very different hourly rates.

Even within the same profession, prices can vary enormously.

A beginner offering straightforward tasks might charge a fraction of what an experienced specialist charges for complex technical work.

Start researching.

Look at freelancers offering services similar to yours. Check freelance marketplaces, independent portfolios, professional communities, and publicly available rate information.

Try to understand the range rather than searching for one magical average.

And don't forget geography.

Someone working with local small businesses may encounter very different budgets from someone serving international technology companies.

The market tells you what clients might be willing to pay. It doesn't automatically tell you what you should charge.

That's the next step.

2. Set your minimum hourly rate

Forget the market for a moment.

Ask yourself a simple question:

What's the absolute minimum I would be willing to work for?

Not the amount you'd be thrilled to earn.

The minimum amount that would make the job worth accepting.

Consider your living expenses, business expenses, taxes, equipment, and the time you'll spend finding clients and managing your business.

Most importantly, remember that being a freelancer doesn't mean you'll spend 40 hours every week doing paid client work.

You'll also spend time answering inquiries, preparing quotations, learning, handling administration, and sometimes waiting for the next project.

Let's imagine you need your business to generate €3,000 a month before personal taxes.

And you realistically expect to have 60 billable hours per month.

Your starting calculation is:

€3,000 ÷ 60 hours = €50/hour

That's your basic revenue requirement, not necessarily your final selling price. It doesn't yet include every financial contingency, profit buffer, or the effect of months with less work.

But it's a useful reality check.

If you're charging €25/hour when your business needs €50/hour just to meet its financial requirements, something has to change.

You either need more billable hours, lower costs, or a higher rate.

Knowing your minimum makes it much easier to recognize projects that simply aren't worth accepting.

3. Set your ideal hourly rate

Now for the more interesting question:

How much would you actually LIKE to earn per hour?

Let's say your minimum acceptable rate is €40/hour.

But ideally, you'd like to make €60/hour.

Great. Now you have two useful numbers.

Minimum: €40/hour

Target: €60/hour

Your minimum is a business constraint. Your target is what you're aiming for.

Having these two figures helps when evaluating projects and negotiating prices.

Perhaps you encounter an interesting project with a limited budget. It might still make sense at a lower rate if it gives you valuable experience, opens doors, or helps build a relationship.

Or perhaps a project is complicated, urgent, and requires specialized knowledge. In that case, charging above your usual target might make perfect sense.

The point is to decide deliberately rather than accepting whatever amount the client suggests.

And remember: your target hourly rate isn't necessarily the same as the hourly rate you advertise.

It can also be an internal benchmark for judging whether fixed-price projects are profitable.

4. Charging by the hour: my preferred approach

For most of my freelance product-development work, I prefer hourly pricing.

Why?

Because it's flexible.

I have a rate that reflects how I value my time, and it's within the market range for the services I provide.

When a client approaches me, we discuss the project, agree on the hourly rate and estimate how much work will be involved.

For example:

Hourly rate: €60

Estimated work: 20 hours

Estimated budget: €1,200

Then I do the work and track my time.

Simple.

But here's where it becomes important.

A project is rarely just the hours spent creating the final deliverable.

There can also be research, client meetings, documentation, unexpected technical problems, revisions, and changes to the original requirements.

I track all of these activities.

When they're part of our agreed billable scope, I charge for them too.

This works particularly well for larger projects because the scope often evolves as the work progresses.

What happens when the client changes their mind?

Imagine you're designing a product for a client.

You've already spent ten hours developing the agreed design.

Then the client has a new idea and wants to change something important.

That's another six hours of work.

With hourly pricing, this is relatively straightforward.

You discuss the change, update the budget estimate, complete the additional work, and bill for the time.

You're not automatically absorbing the cost of every new idea.

Of course, expectations must be agreed in advance. A client shouldn't be surprised by charges they never knew were possible.

This is why I like combining an agreed hourly rate with an estimated budget and regular communication.

The rate is clear, the client understands roughly what to expect, and you have flexibility when the scope changes.

Just make sure you distinguish a budget estimate from a hard spending cap. If the client has approved a maximum budget, agree on an increase before exceeding it.

The downside of hourly pricing

Hourly work isn't perfect.

Some clients want to know exactly how much a project will cost before they commit.

They don't want an estimate that could change.

And there's another interesting problem:

The better and faster you become at your work, the fewer hours you might be able to bill.

Something that took you ten hours a few years ago might now take only three.

Should becoming more skilled mean earning less for delivering the same valuable result?

Not necessarily.

That's where flat-rate pricing becomes interesting.

5. Flat-rate pricing: charging for the result

With a flat fee, you agree on one price for a defined project or deliverable.

Let's imagine a client needs a product designed and you agree on a fixed price of €600.

You deliver the agreed result, and the client pays €600.

Whether you complete it in six hours or fifteen hours, the project price stays the same unless you've agreed to change it.

Now compare what happens to your effective hourly earnings.

The project price hasn't changed.

But what you're earning for every hour of your time has changed dramatically.

And this is exactly why I think tracking time on flat-rate projects is just as important as tracking billable hours.

Know when your flat-rate project stops being profitable enough

Remember the target rate we established earlier?

Let's say you want to earn €60/hour.

You've agreed on €600 for a project.

That means your target time budget is:

€600 ÷ €60/hour = 10 hours

If you've spent eight hours, you're doing well.

If you've spent twelve, your effective rate has already dropped to €50/hour.

And if you're approaching twenty hours, you're now earning just €30/hour before expenses and taxes.

This doesn't mean you can simply abandon the project when you hit ten hours.

You still need to deliver what you promised.

But those numbers are telling you something important.

Maybe the scope is growing.

Maybe the client is requesting work outside the original agreement.

Maybe you've underestimated how complicated the project would be.

Or maybe you're spending far too much time perfecting something that doesn't need further work.

Tracking your time gives you an early warning before a good project turns into a bad deal.

If you're approaching your target time budget, review what's left to deliver. Finish the agreed scope efficiently, and negotiate a separately paid next phase if the client wants additional work.

6. Flat-rate pricing can also be value-based

Here's another way to look at pricing.

Imagine you're a web designer.

Two clients approach you.

One owns a small local bakery.

The other represents a large international brand.

Both need a website redesign, and for the sake of the example, let's assume the actual design work and deliverables require the same amount of time and effort.

Should both clients necessarily pay the same price?

Not always.

For the bakery, an improved website might make it easier for local customers to find the menu, check opening hours, or place orders.

For the international brand, the redesign could affect a much larger number of customers and potentially have a significantly greater commercial impact.

The technical work might be similar, but the business value of the outcome could be very different.

This creates an opportunity for value-based pricing.

Rather than calculating your price only from the hours required, you consider what the result is worth to the client.

Of course, being a big company doesn't automatically mean someone should pay more. You need to understand the actual value you're delivering, the scope, the expectations, and the risks involved.

But if your work can create meaningful business value, a fixed price can allow you to capture more of that value.

And if you've become highly efficient through years of experience, you can benefit from delivering an excellent result in less time.

The client pays for the agreed outcome. You benefit from the expertise that allows you to deliver it efficiently.

That's one of the strongest arguments for flat-rate pricing.

7. The biggest risk of fixed prices: scope creep

There's a catch.

And it's a big one.

Scope creep.

You agree to design something for €1,000.

The client approves the direction.

Then they request a small adjustment.

Then another.

Then they reconsider an earlier decision.

Then someone else on their team wants a different version.

Suddenly, the project you expected to finish in twenty hours has consumed forty.

And you're still getting €1,000.

Your effective hourly earnings have been cut in half.

This is why I think the scope agreement is incredibly important for flat-rate projects.

Before starting, clarify what the fixed price includes.

For example, a website design package might include the agreed number of pages, specific deliverables, two rounds of revisions, and a defined handover.

Changes outside that scope can be quoted separately.

My favorite solution: fixed price plus hourly extras

You don't have to choose one pricing method forever.

You can combine them.

For example:

Website design: €1,500 flat fee

Includes the agreed pages, deliverables, and two revision rounds.

Additional revisions or scope changes: €60/hour

This gives the client confidence about the main project price while protecting you from unlimited additional work.

The key is to establish these terms before starting.

That's much easier than arguing about unexpected charges when the project is almost finished.

8. Don't be afraid to mix pricing methods

This is something I've become increasingly comfortable with in my own work.

I don't always treat my tracked hours as a strict billing formula.

Sometimes I'll finish a project, review the hours I've spent, consider the complexity, urgency, extra effort and value I've delivered, and decide what I think the work deserves to cost.

Four hours at my usual hourly rate might work out to €240.

But perhaps the job required working over the weekend, solving a particularly difficult problem, or delivering an unusually valuable result.

I might price that work at €400 instead, where the commercial arrangement allows it.

Other times, I might charge less because I don't think all the hours I spent should be passed on to the client.

Tracking time gives me information. It doesn't take away my freedom to make pricing decisions.

Of course, if you've already committed to a specific fixed price or binding hourly terms, those agreements still matter. Your pricing flexibility isn't a reason to ignore an agreed contract.

But when you're free to determine or negotiate the final fee, your tracked hours don't have to be the only factor.

I don't think freelancers need to be rigid about this.

A pricing method is a tool, not a religion.

Choose the one that suits the work and the client, and don't be afraid to use a different model for the next phase.

9. Whatever you charge, track your time

There's one principle that applies to everything we've discussed.

Whether you charge €25/hour, €100/hour, or €5,000 for a project:

Track how much time the work actually takes.

Not just the hours you invoice.

Track your research, revisions, documentation, communication, and any additional work associated with the project.

Why?

Because without that information, you're guessing.

You might believe a project was profitable because the invoice looked good.

But what if it quietly consumed twice as much time as expected?

Or perhaps you discover the opposite: a particular kind of project consistently pays well and takes you surprisingly little time.

That's valuable information too!

For years, I organized my freelance work with a simple weekly board and tracked the numbers separately.

That approach eventually inspired me to build StickyWeek.

It's a visual weekly planner and time tracker for freelancers that supports hourly, flat-rate, and non-billable work.

You can track time against your projects, review what you've earned, and see your effective hourly rate.

For flat-rate work, that's particularly useful because you can compare the agreed project revenue with all the time you've actually tracked on it.

You don't have to guess whether your €600 project took eight hours or eighteen.

You can see the numbers.

And that makes it easier to price your next project more confidently.

10. Your first pricing strategy doesn't have to be perfect

If you're just starting freelancing, don't let pricing become another reason to postpone taking on your first project.

Research your market.

Calculate a realistic minimum.

Set an ideal target.

Choose a pricing method that makes sense for the work.

And agree on how changes and additional work will be handled.

Then do the project, track your time, and compare the result with your expectations.

Maybe you charged too little.

Maybe the project took longer than expected.

Or maybe you discover that clients are happy to pay considerably more for your expertise.

That's how you learn.

Your rates will change as your experience, skills, clients, and understanding of the market develop.

The important thing is to make those changes based on what you've learned rather than just guessing.

So, hourly or flat-rate?

My answer is simple:

Use hourly pricing when flexibility and uncertain scope matter most.

Use flat-rate pricing when you can define the deliverables, understand the risks, and agree on a price that makes the outcome worthwhile.

And don't be afraid to combine the two.

But whatever you choose, know your minimum, aim for your target, and track the time you actually spend.

Because the most important number isn't necessarily the rate you put in your quotation.

It's what you really earned for the time you put into the project.