· 7 min read
Fixed price vs hourly: how to pay for a software build
Fixed price vs hourly software development: when each model fits, how scope changes are handled, and what a fixed quote should include before you sign.
Updated

Fixed price vs hourly is the first commercial question in almost every software project, and founders often hear it framed as a choice between a safe option and a flexible one. Neither label is quite right. Each model moves a different risk onto a different person, and each works well for a different kind of project. The useful question is not which model is better, but which risks you can afford to carry.
In short: choose a fixed price when the scope can be written down clearly enough to agree what "finished" means, which is true of most first versions. Choose hourly when nobody can yet say what the work is: research, an unfamiliar codebase, or small ongoing requests after launch. Many projects use both, with a short paid discovery, a fixed-price build, then hourly or monthly work after launch.
This guide explains how the two models work, when each one fits, how changes are handled under each, and what to ask for before you sign either kind of deal.
How fixed price and hourly billing work
With hourly billing, often called time and materials, you pay for the hours people actually work, usually at a rate per role. You get an estimate at the start, but the estimate is not a promise. If the work takes longer, you pay for the extra time.
With a fixed price, the developer agrees to deliver a written scope for an agreed amount. If the work takes longer than they expected, they absorb the cost. If you want something that is not in the written scope, it is priced separately.
| Hourly | Fixed price | |
|---|---|---|
| Who carries the risk of overruns | You | The developer |
| How changes are handled | Absorbed as more hours | Swapped, deferred or priced as a change |
| What you need before starting | A rough idea and a budget | A written feature list and screen map |
| Cost certainty | Low until the end | High, for what is written down |
| Flexibility mid-build | High | Lower, by design |
When hourly billing fits
Hourly billing is the honest choice when nobody can yet say what the work is. That includes:
- Research and prototypes where the point is to find out whether something is possible, such as a new algorithm or an unfamiliar piece of hardware.
- Ongoing work after launch, where small requests arrive every week and none of them is worth quoting on its own.
- Joining an existing codebase that nobody on the new team has seen, where the first weeks are spent reading and repairing.
- A team that works closely with yours, with your own product lead setting priorities day by day.
The risk with hourly work is not dishonesty. It is drift. Small decisions add hours, nobody owns the total, and the estimate quietly becomes a floor. If you choose hourly, protect yourself with a weekly cap, a timesheet you can read, and a short report each week of what the hours produced.
When a fixed price fits
A fixed price works when the scope can be written down clearly enough for two people to agree on what "finished" means. A first version of a product usually can be, because a good MVP is small on purpose: one kind of user, one main job, a short list of screens.
It suits founders who are spending their own money or a fixed round, who need to know what launch will cost, and who would rather make trade-offs than receive a larger invoice. It also changes the developer's incentive. On a fixed price, a team gains nothing from slow work, and a lot from clear decisions early.
The catch is the word "written". A fixed price is only as good as the scope behind it. A number quoted after a single sales call is a guess, and the gap between the guess and the real work comes back later as change requests. Our guide on how to scope an MVP shows how to get a scope tight enough to price.
Fixed price vs hourly when the scope changes
Every product changes during the build. Users react to a prototype, a competitor launches, a payment provider turns out to be harder than expected. The two models handle this differently.
Under hourly billing, a change simply adds hours. That is easy in the moment, and it is exactly why hourly projects drift. The only control is your own discipline about what to say yes to.
Under a fixed price, a change needs a decision. A good team will offer three options:
- Swap it. Replace a feature of similar size that has not been built yet. The price and date stay the same.
- Defer it. Put it on a version-two list and keep going. Many ideas look less urgent once real users arrive.
- Price it. A short written change with its own cost and its effect on the launch date, which you approve before work starts.
Be wary of anyone who promises unlimited changes for a fixed price. Either the changes are priced in somewhere, or the date will move. Agile teams have long put "responding to change over following a plan" in their manifesto, and a good fixed-price process does respond to change. It just makes each change a visible choice rather than a surprise on the final invoice.
What to ask for in a fixed quote
A fixed quote should be a short document, not a single number in an email. It is easier to get one if you start from a written software project brief. Before you sign, check that it covers:
- The feature list, with each feature described in a sentence or two.
- A screen map, showing every screen for every kind of user, including the admin panel. On CreditIQ, an education portal we worked on, that meant four main pages and an admin panel.
- Platforms. Web, iOS, Android, or which combination.
- Integrations. Payments, maps, email, accounting, sign-in providers, each named.
- What is not included. A good quote lists exclusions as clearly as inclusions.
- What "done" means. How each feature will be checked, and on which devices. Where a number fits, write it down: on Heartopsy, a PDF reports service we built, the budget for rendering a report was under three seconds.
- The timeline, with the dates that depend on you, such as content, feedback and store accounts.
- Running costs. Hosting, app store fees and paid services are usually yours. Know roughly what they are before launch.
- The change process, written down in the terms above.
- Ownership. The code, the designs and every account should be in your name.
- Support after launch, how long it lasts and what it covers.
If an agency cannot answer these, the price is not really fixed. We cover more of these questions in how to choose an MVP development agency.
What to ask for in an hourly deal
If hourly suits your project better, ask for:
- A rate card for each role, and who will fill each role.
- An estimate as a range, with the assumptions behind the low and high ends.
- A weekly or monthly cap that cannot be passed without your approval.
- Timesheets broken down by task, not just total hours.
- Working software you can open every week, so hours turn into something you can see.
- A notice period, so you can stop cleanly if priorities change.
The hybrid most founders end up with
In practice, many good projects combine the two. A short, separately priced discovery period produces a written scope, the build is then quoted at a fixed price, and ongoing work after launch moves to an hourly or monthly arrangement.
That is the shape of our own process. The first week is a blueprint: a feature list, a map of every screen and a fixed quote. Design and build follow at that price, with a preview link every week so you can see what you are paying for. After launch we fix bugs for 30 days, and the code and every account are already yours if you take the product elsewhere. The details are on our MVP development page.
Fixed price vs hourly: a quick way to decide
- If you cannot yet describe the screens, start hourly, or pay for a short discovery first.
- If you can describe the screens and need to know the cost, ask for a fixed price.
- If the work is small and continuous, pay by the hour with a cap.
- Whichever you choose, insist on weekly working software and ownership from day one.
If you would like a fixed quote for your own product, send us a short description and we will tell you what we would need to price it.
- Pricing
- Startups
- Hiring
Building a first version of your product?
We scope it in a week and launch it in 8–12, for a fixed price. Tell us what you want to build.
Keep reading

· 8 min read
How to hire MVP developers: where to look and what to ask
How to hire MVP developers for a startup: the skills a first version needs, where to find developers, what to ask, a paid trial task and what to put in writing.
Read the guide
· 8 min read
MVP development for non-technical founders: a plain guide
MVP development for non-technical founders: what you decide, what to leave to the team, how to check progress without reading code, and what to own from day 1.
Read the guide
· 7 min read
Agency, freelancer or in-house team: who should build your MVP?
Agency vs freelancer vs in-house for your MVP: cost, speed, risk and who manages the work, with a side-by-side table and a simple way to decide.
Read the guide