Fixed price vs hourly vs retainer: how to pay a software developer
How you pay a developer shapes the whole project: who carries the risk, how changes are handled and how predictable your budget is. There are three common models. None is always best; each fits a different kind of work.
By Ahsan Mehmood · · 6 min read
Fixed price: best for a defined scope
You agree what will be built, by when and for how much before work starts. The developer carries the risk of underestimating, so expect a careful scoping step first and a written change process for anything new.
Fixed price works best for an MVP, a website or a clearly defined feature. It works poorly when you are still discovering what the product should do.
Hourly: best for small or uncertain work
You pay for the time actually spent. It is the simplest model for bug fixes, small automations and exploratory work where nobody can honestly estimate the outcome up front.
The risk sits with you, so ask for a time estimate per task, a weekly cap and a log of hours with what was done in each.
Monthly retainer: best for ongoing product work
You reserve a developer for a set number of hours or days each month. It suits a product after launch: a steady stream of features, fixes and improvements with a predictable monthly cost and someone who already knows your code.
Check what happens to unused hours, how priorities are set each week and how much notice either side needs to end the arrangement.
Milestones make any model safer
Split the work into milestones with a written definition of done.
Pay each milestone after you have reviewed working software, not slides.
Keep the code in your own repository from day one, so you own every milestone you pay for.
Agree in writing how change requests are priced before the first one comes up.
A simple way to choose
Many projects use more than one: a fixed-price MVP, then a retainer once customers are using it. See the pricing options I offer, or book a free call to decide which fits your project.
If you can describe the result in one page, ask for a fixed price per milestone.
If the work is small or hard to estimate, pay hourly with a weekly cap.
If you need a developer every week after launch, use a monthly retainer.
Frequently asked questions
Is fixed price more expensive than hourly?
Sometimes, because the developer prices in the risk of underestimating. In exchange you get a predictable budget and the developer, not you, absorbs overruns on the agreed scope.
What should a fixed-price quote include?
The scope, milestones with a definition of done, a timeline, the price per milestone, who owns the code and accounts, and how change requests are handled.