Comparison

Fixed price vs hourly billing: which suits your software project?

The short answer: choose a fixed price when you can describe what the system has to do, and hourly billing when the task is pure exploration or nobody knows where it will end. For most SME projects a fixed price is the safer choice, because the risk of overruns sits with the supplier rather than with you.

8 min read · Updated 29 September 2026

The choice between a fixed price and hourly billing is really about one thing: who carries the risk if the project takes longer than expected? With hourly billing it is you. With a fixed price it is the supplier. Both models have their place, but they suit very different tasks, and choosing the wrong one is expensive.

What is the difference between fixed price and hourly billing?

Fixed price

  • You know the price before work starts
  • The supplier carries the risk of overruns
  • Needs a written scope with features and integrations
  • Changes are priced before they are built
  • The supplier profits from being efficient

Hourly billing

  • The price is known only when the work is done
  • You carry the risk of overruns
  • Can start without a finished scope
  • Changes are simply added to the timesheet
  • The supplier earns more the longer it takes
The two models side by side.

The last point is not an accusation. Most suppliers billing by the hour work honestly. But the incentive is skewed, and you feel it when the estimate slips and nobody is really responsible. With a fixed price the incentive is reversed: the supplier has a direct interest in building the right thing quickly and without detours.

When does a fixed price fit, and when does hourly billing?

Rules of thumb for choosing a model.

SituationBest modelWhy
New website, web app or app with a known purposeFixed priceThe features can be listed up front
MVP to test a business ideaFixed priceThe budget is limited and the scope must be sharp
Integration with known systems such as e-conomic or MobilePayFixed priceThe APIs are documented and the task is defined
Debugging an old, undocumented systemHourlyNobody knows what is hiding in the code
Research and experiments with new technologyHourly with a capThe goal is learning, not a specific deliverable
Ongoing development after launchFixed price per featureEach change is small and can be priced on its own

If you are building something new to test an idea, also read about MVP development. And to understand why the hourly rate on its own is a poor basis for comparison, see developer hourly rates.

How is a fixed-price scope written?

A good scope is not a thick document. It is a precise list that both you and the supplier can point to when doubts arise. A managing director should be able to read it in ten minutes, and it should still be concrete enough for a developer to know what to build.

  1. Purpose: what problem does the system solve, and how will you know it works?
  2. Users and roles: who logs in, and what may each role see and do?
  3. Features: a numbered list, one line per feature, such as "staff can create an order".
  4. Integrations: which systems must it talk to, and which way does data flow?
  5. Out of scope: what is deliberately left for later, written down.
  6. Acceptance: how you sign off that each feature has been delivered.
  7. Running: hosting, updates, support and backups after launch, and the monthly cost.

Point five is the one most people skip, and it is the one that most often causes conflict. When what is not included is written down, there is no doubt about what is. We have a ready-made requirements specification template you can start from. For the job portal Jobero we started from the first sketch and built the brand, the design and the full system, and there too a sharp boundary around the first version was what got the project off the ground.

How are changes handled in a fixed-price project?

1

New idea

You have an idea during the project or after launch and describe it briefly.

2

Within scope?

If it adjusts an existing feature, it is part of the work.

3

Fixed price for the new

If it is a new feature, it gets a fixed price per feature, stated up front.

4

You decide

You approve in writing and the feature is built. If you say no, nothing happens.

New ideas are welcome. They simply get a price before they are built.

Our packages are built on exactly that model: 12, 24 or 36 features and 1, 2 or 3 integrations at a fixed price from DKK 18,000 plus a fixed monthly plan. See them under pricing. For a concrete proposal, describe your project here and you will get a written fixed-price proposal within 24 hours.

Questions about fixed price and hourly billing

Is a fixed price more expensive than hourly billing?
Not necessarily. A supplier taking on the risk may add a buffer, but an hourly bill often has its own buffer in the form of meetings, rework and estimates that slip. What decides it is how well the scope is described. A precise scope gives a sharp fixed price. A vague scope gives either a high fixed price or an open-ended hourly bill.
What happens if we change our minds along the way?
Small adjustments within a feature already in scope are part of the work. If you want a new feature, it is priced on its own before it is built, so you can say yes or no. With us, extra features have a fixed price per feature. That way the project only grows when you have decided it should, and never behind your back.
When is hourly billing the right choice?
When the task cannot be described in advance. That covers debugging an old system, research and experiments with new technology, or a developer joining your own team for a longer period without fixed deliverables. Here hours give flexibility. In that case, insist on a cap or regular reporting so you can stop in time.
Do we need a requirements specification to get a fixed price?
Not a heavy one. What matters is that you can describe who uses the system, what they need to do and which systems it has to talk to. The supplier can help structure the rest. We have made a template you can use as a starting point, and we turn your description into a list of features and integrations in the proposal.
How fast can we get a fixed-price proposal?
With us, you get a written fixed-price proposal within 24 hours of receiving your description. The proposal lists features, integrations, the one-time price and the monthly plan, so you can compare it with other quotes line by line. Where something is unclear, we ask rather than guess, so the price holds.
Is there a middle ground between fixed price and hourly billing?
Yes. Many projects work best with a fixed price for the first version and a fixed price per feature afterwards. You get budget certainty on what you know, and flexibility for what you only discover once the system is in use. Another middle ground is a capped bank of hours, but that requires you to keep an eye on consumption yourselves.

Also read

Guide · 2026

Software requirements specification template: from idea to fixed price

→

Price guide · 2026

Developer hourly rate in Denmark: what a developer costs per hour

→

Solution · MVP

MVP development: build the smallest thing that proves something

→

Want us to build it for you?

You get a fixed-price proposal within 24 hours.

Get a fixed-price proposal in 24 hours
Dennis Nielsen

Dennis Nielsen

Head of Operations, Ceptiv

Free consultation

One free hour of advice before you start.

Describe your project and I will contact you as soon as possible, so we can schedule a no-obligation meeting. You leave with practical advice on how to get your project off to a good start.

  • Free
  • 1 hour
  • No obligation
Describe your project

Or call us on +45 81 98 32 71