Blog / Fixed price or hourly: choosing project by project

Fixed price or hourly: choosing project by project

Fixed price vs hourly billing, side by side: who carries the risk, when each model works, how many hours a fixed bid can carry, and how to price one.

Money · · 8 min read

Fixed price or hourly is usually argued as a preference. It is not. It is a decision about who carries the risk of what nobody knows yet, and the honest answer changes from project to project.

What is a fixed-price project?

A fixed-price project is sold for one agreed total for a defined scope of work, whatever the hours turn out to be. The client knows the price on day one. The agency keeps the difference if the work takes fewer hours than estimated and pays for it if the work takes more. The alternative, hourly or time and materials, charges the hours actually worked at agreed rates.

A fixed price is also called a fixed fee, a fixed bid or a lump sum. In each case the price is tied to the scope, not to the time, which is why the written scope decides whether the project makes money.

The question under the question

On a fixed price, the agency carries the risk. If the work takes longer than estimated, the agency pays for the difference in margin. On time and materials, the client carries it: they pay for the hours the work actually takes, and they accept that the final figure is not known on day one.

Neither is generous or greedy. What matters is whether the risk sits with the party that can actually control it.

Fixed price and hourly side by side

Fixed priceHourly (time and materials)
Who pays for an overrunThe agencyThe client
What the client knows on day oneThe totalThe rate and an estimate
What you need before quotingWritten scope, past data, a change processA rate card and a way to report hours
Admin during the projectTracking hours against the estimateTimesheets the client can check
Typical failureMargin lost to extra roundsTrust lost to a surprising invoice

When a fixed price is the right call

  • You have done this shape of work before, and you can look up what the last three similar projects really took rather than what you remember.
  • The scope can be written down as deliverables, rounds of revision and an explicit list of what is out of scope.
  • There is a change process both sides accepted before the work started, so the first new request does not become an argument.
  • The client needs a number to approve a budget. Sometimes the fixed price is not about risk at all; it is about how their finance department works.

When hourly is the honest answer

  • Discovery. If the first phase exists to find out what the project is, no one can price the whole of it yet.
  • A moving target. A client in the middle of a rebrand, a funding round or a reorganisation will change direction, and a fixed price only hides that until the invoice.
  • Ongoing work. Support, maintenance and retainers are priced by capacity, not by a deliverable.
  • A first project with a new client. You do not yet know how many rounds of feedback they need. That is not a flaw, it is missing information.

The version most agencies end up with

A fixed price for a well-defined phase, then time and materials for what follows. Discovery hourly, build fixed. Or a fixed monthly capacity with a written rule for what happens when a month goes over. The point is that the pricing model matches how much is actually known at that moment, rather than being a company-wide rule applied to every project.

Pricing a fixed bid without guessing

  1. Estimate in hours by role, not in one number. Design, build and project management have different cost rates.
  2. Check the estimate against the past. What did the last similar project actually record? If you cannot answer that, the estimate is a wish, and the case for time and materials just got stronger.
  3. Add contingency openly. A percentage for the unknown, decided before the client sees the number, not discovered afterwards.
  4. Price against cost, then against value. Cost tells you the floor; value tells you whether the ceiling is higher.
  5. Write down what is out of scope. The out list protects the margin more than the in list does.

What the numbers do

Take a website quoted at 8,000. The estimate is 120 hours at a 35 cost rate, so 4,200 of effort, plus 1,000 of direct expenses. That leaves 2,800 before company overhead, a 35% margin.

Now the same project takes 160 hours because the client needed two more rounds: 5,600 of effort plus the same 1,000 leaves 1,400, or 17.5%. The price did not change. The risk did what risk does.

On time and materials the same 40 extra hours would have been invoiced, and the conversation would have happened while the work was in front of both parties instead of at the end.

How many hours a fixed price can carry

Turn the example around and ask how far the estimate can slip. With a price of 8,000, 1,000 of direct expenses and a cost rate of 35, the project breaks even at 200 hours: (8,000 − 1,000) ÷ 35. If you want at least a 20% margin, the limit is 154 hours: (8,000 × 0.8 − 1,000) ÷ 35. An estimate of 120 hours therefore has 34 hours of room before the margin drops below target, and 80 before the project loses money.

Write those two numbers into the project brief. When recorded hours pass the first one, it is time to talk to the client, not after the second.

What a fixed-price contract should include

  1. Deliverables, listed one by one, with what “done” means for each.
  2. What is out of scope, written down, so a new request is visibly new.
  3. Revision rounds: how many are included and what one more costs.
  4. Client inputs and dates: the content, approvals and access the client owes, and what happens to the deadline if any of them arrive late.
  5. Payment milestones: a deposit, then payments tied to delivered stages instead of one final invoice.
  6. Acceptance: how and when the client signs off each stage.
  7. The change process: how extra work is priced and approved before it starts.

The free scope of work template covers these sections and can be attached to a fixed-price proposal.

The change process matters more than the model

Whichever model you choose, extra work needs a route: a request with one owner, a decision that says included, extra or declined, and a record kept with the project. Without it a fixed price quietly loses margin and an hourly project quietly loses the client’s trust. There is more on that in scope creep and billing.

Where PLYNTUM fits

projects and tasks give every agreed change its own task, owner and date. time tracking records the hours against the project, which is what makes the next estimate better than the last one. finance and costs puts effort, expenses and revenue on one record, so you can see which model actually worked on which kind of project.

For a fixed bid, the profit margin calculator shows how many hours the price can carry, and the free invoice template covers billing once the work is agreed.

REAL SCREENS

How it looks in PLYNTUM.

Screens from a demo workspace with sample data, as the product looks today.

PLYNTUM Projects: contracted value, amount received and amount remaining across six projects, with payment status and work status per project
Projects: contracted value, what has been received and what is still to collect, per project, next to its work status.

Follow one project through the product

MONEY

Common questions

More articles

All articlesRSS

PLYNTUM

Start with the work that keeps getting stuck.

Bring one project into a connected workspace. See the work, the people and the cost together.