Hourly billing punishes you for getting faster and leaves clients guessing. Here is the fixed-price system I use instead, and how to move to it without scaring anyone off.
For my first year of freelancing I charged by the hour, because that is what every platform nudges you towards. It felt safe. Then I noticed something uncomfortable: every time I got better at my job, I earned less for the same result. A site that took me forty hours in year one took twenty in year two, and my invoice halved.
Hourly billing also makes clients nervous in a way they rarely say out loud. They do not know what the final number will be, so they hesitate to ask for things, and the project gets worse because of it. Fixed pricing fixed both problems. Here is how I do it now.
Start from what the site has to do, not how long it takes
A price should reflect the outcome for the client, not my speed. So before I quote anything I want to know three things: what the business sells, what the website needs to make happen (enquiries, bookings, sales, credibility), and what a good result is worth to them. A five-page site for a consultancy that lands one new client a quarter is worth a lot more than five pages for a hobby project, even if the build is identical.
That conversation happens on a discovery call. I do not send prices before it, and I say so politely when people ask. The call is where I find out whether they need a starter site or something with bookings, a shop and three languages.
How to price a website project: three tiers, then a firm number
I publish starting points rather than a menu: a small site from one figure, a business site from another, larger builds from a third. Public starting points do two useful things. They let people rule themselves in or out before they book a call, and they make the eventual quote feel like a refinement rather than a surprise.
After the call, the quote itself is a single fixed price with a written scope attached. The scope is the important half. It lists pages, features, what I need from the client and by when, how many rounds of design changes are included, and what is not included: copywriting, photography, hosting fees, plugin licences. Naming exclusions up front is not being difficult. It is how you avoid the awkward email in week four.
What actually moves the number
People assume page count is the main driver. It is one of about seven things I weigh:
- How many pages, and how many are genuinely different layouts rather than copies
- Custom design versus adapting a proven structure
- Selling products or taking bookings
- Connecting to tools the client already uses
- Moving content across from an existing site
- More than one language
- How quickly it needs to be live
Anything that adds risk or unknowns adds to the price. That is not padding; it is the honest cost of taking the uncertainty off the client’s plate.
Payment terms that protect both sides
Half up front books the time in my calendar. Half on launch. For larger builds I split across milestones instead, usually design sign-off and launch. I invoice in US dollars because most of my clients are overseas and it saves everyone a currency conversation. Nothing starts until the first payment lands, and nothing goes live until the last one does. Every client I have worked with has found that fair.
Making the switch without losing clients
If you currently charge hourly, do not flip everything overnight. Quote your next new enquiry as a fixed price built from your honest estimate plus a buffer for the unknowns, and keep existing hourly clients on their current terms. After three or four fixed-price projects you will have a feel for where your buffer should sit. Mine started at 30 percent and has settled at around 15, because scoping well removes most of the surprises.
The result, a couple of years in, is that clients know exactly what they are getting for exactly what price, and I get paid for being good at this rather than for being slow. That trade is worth making.
