Fixed price or hourly rate: which model is fair in a web project

What a fixed price really is

A fixed price is not a price quote but a transfer of risk. The service provider commits to delivering a described result for a fixed sum, no matter how long it takes.

This necessarily means a surcharge. If someone calculates that a project needs 80 hours, they can't offer 80 hours. They have to plan for it becoming 100. 15 to 30 percent is common, depending on how clear the description is.

That is not a trick but the condition for someone taking on the risk. If you want a fixed price, you are buying planning certainty, and that costs money.

The second effect is less obvious: a fixed price makes changes expensive. Every deviation from the described scope becomes a change order, because otherwise the calculation doesn't add up. What would be half an hour in the hourly model turns into a quote for 250 euros.

The price of certainty

A fixed price is not a price quote but a transfer of risk. The service provider commits to delivering a described result for a fixed sum, no matter how long it takes.

This necessarily means a surcharge. If someone calculates that a project needs 80 hours, they can't offer 80 hours. They have to plan for it becoming 100. 15 to 30 percent is common, depending on how clear the description is.

That is not a trick but the condition for someone taking on the risk. If you want a fixed price, you are buying planning certainty, and that costs money.

The second effect is less obvious: a fixed price makes changes expensive. Every deviation from the described scope becomes a change order, because otherwise the calculation doesn't add up. What would be half an hour in the hourly model turns into a quote for 250 euros.

When a fixed price is the right model

Three conditions have to come together.

The scope can be described. Twelve pages, a contact form, one language, copy comes from the client. That can be calculated.

The decisions have been made. If you don't know yet whether a blog will be added or whether there will be two languages, you are buying a fixed price for a project you don't know yet.

There is a fixed deadline or a fixed budget. That is exactly what the model is built for.

Typical projects that suit a fixed price: a relaunch with a clear page scope, a landing page, a corporate design, a migration from one system to another.

What matters then is that the scope of services is really in the quote, not as a heading, but as a list. Website as agreed is not a fixed price, it is a dispute with a date.

When the hourly rate is fairer

The hourly rate has a bad reputation because it leaves open what you end up with. For certain projects, it is still the more honest model.

When the scope only becomes clear while working. For consulting, for ongoing optimization, for anything where the result of the first week determines what makes sense in the second.

When a lot of coordination is needed. Several decision-makers, changing requirements, a project that is still shifting internally.

When you contribute parts yourselves. Then you only pay for what was actually done, instead of a flat fee for services you take on yourselves.

For ongoing support. A fixed monthly amount without an allowance means: in quiet months you pay too much, in busy ones you get too little.

To keep it fair, three things are needed: an estimate with a range, a cap at which you talk, and a transparent breakdown of the hours.

The hybrid model

In practice, the most sensible option is usually a combination.

Fixed price for the defined core. The twelve pages, the structure, the design, the technical build. Everything that can be described in advance.

Hourly rate for everything beyond that. Additional pages, change requests after approval, special features, consulting.

An allowance for the time after. For example, ten hours that can be used in the first six months, for the small things that always come up once a site is live.

That has advantages for both sides. You know what the core costs. The service provider doesn't have to add a surcharge for the unknown, because the unknown is billed by effort.

Only one thing is important: it has to be settled in advance what belongs to the fixed price part and what doesn't. Otherwise, this line shifts during the project, and then it is not a hybrid model but a point of contention.

What should be in the contract in both models

Regardless of the model, five points decide whether it runs fairly.

The scope of services as a list. Not website creation, but exactly what it includes.

The number of revision rounds. Two to three per stage is common. Without a number, every additional round is a conflict.

Who delivers what and by when. Copy, images, access, approvals. Delays on the client side are the most common reason for postponed deadlines.

What happens with extra effort. Is it discussed beforehand? From what threshold?

What is handed over at the end. Access, source files, documentation, usage rights.

A quote that contains these five points is solid in both models. One without them is risky in both models. The fixed price just hides that better.

The question that determines the model

Instead of deciding on a model, one question helps: How confidently can you describe today what should be there at the end?

If you can write it on one page and the same thing would be there in three months: fixed price. You are buying certainty and paying a surcharge for it that is worth it.

If you notice that every answer starts with it depends: hourly rate with an estimate and a cap. A fixed price on an unclear basis is either too expensive or gets renegotiated during the project, usually both.

And if the answer is somewhere in between, which is usually the case: hybrid model.

One last note: a service provider who immediately names a fixed price for an unclear project has either added a generous surcharge or will ask for more later. You can recognize both by the fact that no follow-up questions came.