Fixed price or hourly: how should I pay a developer?
Short answer: Pay a fixed price when you can describe what you want in writing and agree what done looks like. Pay by the hour, also called time and materials, when the scope is unclear or will change as you learn. If you are unsure which one you have, split the job: a small paid first phase to write the scope, then a fixed price for the build. That hybrid protects a small business from both the overrun risk of hourly billing and the padded price of a fixed quote on a vague brief.
You have a quote from a developer and need to know whether a fixed price or an hourly rate is the safer way to pay for it.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
How each model works
Fixed price means you and the developer agree on the work and one total price before it starts. If the job takes longer than planned, the developer absorbs the extra cost. If it takes less, the developer keeps the difference. Changes to the agreed work are priced separately. Who builds it matters as much as how you pay; see freelancer versus agency for custom software.
Hourly, also called time and materials, means you pay for the hours worked, plus any direct costs such as a software licence the developer buys for you. The total is not known in advance. You get an estimate, but the bill follows the actual hours.
The question is simply who carries the risk of the unknown. In a fixed price, the developer carries most of it, so they price it in. In hourly billing, you carry it. Everything else follows from that.
What a very large buyer does with the same choice
The US federal government buys software and services all the time, and its purchasing rules put this choice in plain words. The Federal Acquisition Regulation, the rulebook for government buying, says that for commercial products and services the buyer generally must use firm-fixed-price or fixed-price with price adjustment contracts, and that time-and-materials contracts are not fixed-price contracts. It also says time and materials may only be used when it is "not possible at the time of placing the contract to estimate accurately the extent or duration of the work," and warns that this type of contract provides no positive profit incentive for cost control, so the buyer must watch performance closely (see FAR 16.601). Even then it sets a ceiling price that the contractor exceeds at its own risk.
You do not have to follow government rules, but the logic is useful. Fixed price is the default when you can describe the work. Hourly is the exception for work you cannot yet describe, and when you use it you need a cap and close supervision.
A decision rule: how clear is the scope?
| Your situation | Better fit | Why |
|---|---|---|
| You can list every screen, report and rule, and nothing will change | Fixed price | The developer can estimate accurately, and you know your total |
| You know the goal but not the details | Phased: paid scoping, then fixed price | The first phase turns unknowns into a written scope |
| You will learn as you go, such as testing a new product with customers | Hourly with a monthly cap | The work will change, and a fixed price would fight every change |
| Ongoing small fixes and improvements to a live tool | Hourly block or monthly retainer | The tasks are small and arrive at random |
| Rebuilding something that already exists and works | Fixed price | The existing tool is the scope, so it is easy to compare |
If you tell me you "know what you want" but the only description is a conversation, you have the second row. The test is simple: could two different developers read your document and give you roughly the same price? If not, the scope is not clear enough for a fixed price. Timing is covered in how long custom software takes to build.
A worked example with made-up numbers
Say you want a customer portal where clients log in, see their job status and download invoices. A developer estimates 200 hours of work at $100 an hour. Both the rate and the hours are made up for this example. The base cost is $20,000. For a fixed price, the developer adds a cushion for unknowns. Say it is 25 percent, so the fixed quote is $25,000. Here is what you pay depending on how the job really goes.
| What actually happens | Hours | Hourly bill | Fixed bill |
|---|---|---|---|
| Scope was clear, no surprises | 200 | $20,000 | $25,000 |
| Some surprises, normal for software | 260 | $26,000 | $25,000 |
| Scope was vague, you changed your mind often | 320 | $32,000 | $25,000 plus priced changes |
Look at what this shows. When the scope is clear, fixed price costs you a $5,000 premium for protection you did not need. When surprises are normal, the two come out close. When the scope is vague, hourly can run 60 percent over the first estimate, but a fixed price on a vague brief does not save you either: you will pay for each change as an extra, and arguments about what was in scope will start. The fixed price only protects you if the scope document is good.
That is why the scope document matters more than the pricing model. A written scope tells the developer what is included, lists what is not, and defines what done means. My statement of work template with a free example gives you a structure to fill in.
Where fixed price goes wrong
- Vague scope. The developer prices the cheapest reading of your brief, then charges for everything you meant. Every change becomes a negotiation.
- Cut corners. If the job runs long, a developer on a fixed price has a reason to rush testing or skip the hard parts. Ask what testing is included.
- Padded price. The cushion for unknowns is paid by you whether or not the unknowns happen.
- Slow reaction to change. You learn something halfway through, and every change needs a quote and approval, which feels like a tax on learning.
Where hourly goes wrong
- No ceiling. The bill grows with the hours. A slow developer earns more than a fast one.
- Hard to compare. A $60 an hour developer who takes 400 hours costs more than a $120 an hour developer who takes 150. Rate alone tells you little.
- Weak reporting. If you only see an invoice with a total, you cannot tell whether the hours were well spent. Ask for a weekly note of what was done.
- Drift. Without a clear target, the project can wander. Hourly works best with a short list of goals for each week or two.
If you use hourly, set a monthly cap, ask for weekly summaries of hours and what was built, and stop at the end of any month where the progress does not match the bill. Good requirements are what make a fixed price possible; see how to write requirements for a software developer.
The hybrid: a paid first phase, then a fixed price
This is the option I recommend most for small businesses with a goal but not a full plan. It works in three steps.
- Phase one: scoping. You pay a small fixed amount, or a capped number of hours, for the developer to write the scope: screens, rules, data, what is out of scope, and a list of risks. You own this document and can take it to anyone.
- Phase two: a fixed price for the build based on that scope, with a payment tied to milestones you can see, such as a working login, a working form, a working report.
- Phase three: change requests are quoted as a small fixed price or a few hours, in writing, before work begins.
The Agile Manifesto, a widely cited set of principles written by software practitioners, says to welcome changing requirements, even late, and to deliver working software frequently, with a preference for the shorter timescale (see the principles). Milestones that deliver something working every few weeks give you both: a fixed price per piece, and a chance to change course between pieces.
Whatever you choose, get the ownership terms in writing. A transfer of copyright ownership is not valid unless it is in writing and signed by the owner, under 17 U.S.C. 204. Also, the legal term "work made for hire" is narrower than most owners assume. Under 17 U.S.C. 101, work by an independent contractor counts only if it falls in a short list of listed categories and both sides sign an agreement saying so, so a signed assignment of rights is the safer route. Ask a lawyer about the exact wording for your contract.
Red flags in any quote
- A fixed price with no written scope attached.
- An hourly estimate with no cap and no weekly reporting.
- No mention of testing, fixes after launch, or who owns the code.
- A price that is far below every other quote. Someone has misread the work, or plans to charge for changes later.
- Payment of the whole amount up front.
For what drives the total in the first place, see custom software development cost. To judge who you are hiring, read how to choose a custom software development company. If you only need a first working version, AI MVP development covers how small a first build can be. And if you are unsure you need a full agency at all, fractional CTO versus development agency explains the alternative.
Pick fixed price if, pick hourly if
- Pick fixed price if: you have a written scope, the work is a known type, and you care most about knowing the total. Pay in milestones.
- Pick hourly if: you are still learning what to build, or the work is small fixes arriving over time. Cap the hours and ask for weekly notes.
- Pick the hybrid if: you have a goal but no scope. This is the most common case.
Need something completely custom?
Everything above is a path to get it running quick and cheap. But sometimes none of these fit, and what you need is something custom that you own, built uniquely for your business from the ground up, with AI thoughtfully designed into the parts of it that your processes actually benefit from. An asset that grows in value, not a generic, one-size-fits-all boilerplate that's an expense with a lock-in. This is a complete bespoke build, and it's something I do very well. Get in touch to know more.
How I'd approach this
If I were hiring, I would not start by comparing rates. I would write down, in plain words, what the tool must do on day one and what can wait. Then I would ask for a scope and a fixed price for that first piece, paid in milestones, with the code and data owned by me. If the developer could not give a fixed price because the work is truly unclear, I would pay for a short scoping phase first.
I use fixed prices for my own work, agreed in writing before I start, because small business owners need to know the total. Fixes and finishes start around $1,500. For work that is still taking shape, I would rather scope it first than guess a number we would both regret.
Questions people ask
Is fixed price or hourly cheaper for software development?
Neither is always cheaper. Fixed price includes a cushion for unknowns, so it costs more when the job goes smoothly. Hourly costs less when the job is small and clear, and can cost far more when it is vague. The worked example above shows both outcomes.
What is time and materials?
It is a contract where you pay for the hours worked plus direct costs such as licences, instead of one agreed total. It suits work where the scope is not yet known, and it needs a cap and regular reporting.
Can I change my mind on a fixed price project?
Yes, but each change is usually priced on top of the agreed total. A good contract says how changes are requested and quoted. A statement of work is the place to set that up.
What hourly rate should I expect for a developer?
Rates vary widely by country, experience and type of company, so ask for several quotes and compare the total, not only the rate. A cheaper rate with slow work can cost more than a higher rate that finishes fast.
Who owns the code if I pay by the hour?
The payment model does not decide ownership. The contract does. Ownership transfers need to be in writing and signed, and you should ask a lawyer to check the wording. See custom software development cost for what else to ask a developer.
More in this topic: Problem solving: custom software (22 guides) →
Sources
- FAR 16.201, fixed-price contract types (acquisition.gov)
- FAR 16.601, time-and-materials contracts (acquisition.gov)
- Principles behind the Agile Manifesto (agilemanifesto.org)
- 17 U.S.C. 204, execution of transfers of copyright ownership (Cornell LII)
- 17 U.S.C. 101, definitions including work made for hire (Cornell LII)