Fixed price or pay by the hour: which is better?
Quick answer
Choose a fixed price when the scope is clear and written down. Choose paying by the hour when the work is genuinely uncertain and you can watch it closely. Most business projects do best with a fixed price per part, which gives you a firm number for what is known and a clear process for what changes.
Vastavik Bajpai , Founder
· 2 min read
How you pay for software shapes how the project behaves. Each model rewards different behaviour from the supplier, so it is worth choosing on purpose.
Fixed price
You agree a scope and a price, and the supplier carries the risk of getting the estimate wrong. It works when the scope is written down in detail. It fails when the scope is vague, because every change becomes an argument about what was included.
Time and materials
You pay for the hours worked. It suits research, rescue work on an old system, and long-running product teams where the roadmap changes monthly. It fails when the buyer cannot see what the hours are producing, because the incentive to finish is weaker.
The middle path: a price per part
Break the project into parts, and give each part a fixed price. You get a firm total for what is known, you can remove parts to fit a budget, and a change is simply a new part with its own price. This is how we quote, because it keeps both sides honest.
Questions to ask whichever model you choose
- What exactly is included, in writing?
- How is a change requested, priced and approved?
- When do I see working software?
- What is the payment schedule, and what do I receive at each payment?
Read what moves the cost, or ask us for a quote that prices each part.
Questions people ask
Is fixed price always cheaper?
No. A fixed price includes a margin for the risk of being wrong. On a well-defined project it is usually the better deal; on a vague one you pay for the uncertainty either way.
What is a retainer?
A fixed monthly amount for a set number of hours or a set list of duties, usually for support and small improvements after launch.
Can we switch models during a project?
Yes, and it is common: a fixed price for the first version, then a monthly retainer for changes and support.
Related pages
Pages people read alongside this one.
The service this guide is about
More guides
Custom software or ready-made: which to buy?
Buy ready-made software when it does most of what you need and your process can bend to fit it. Build custom software when your process is the advantage, when several tools no longer talk to each other, or when subscription costs and workarounds are eating the savings.
How do you choose a software development company?
Judge a software company on how it works, not on its sales pitch. Ask who you will actually talk to, how it quotes, whether you own the code, what happens after launch, and ask to speak to a past client. The answers matter more than the size of the company or the length of its client list.
Who owns the source code in a software contract?
Unless the contract says otherwise, the company that writes the code usually keeps the copyright. Your contract should assign the code, designs and documents to you once the project is paid for, and should list any open-source or paid parts that keep their own licences.