Quick answer: Choose a fixed price when your scope is clear and unlikely to change, hourly billing when the work is uncertain or exploratory, and a retainer when you need steady ongoing work such as maintenance and improvements. Many projects combine two models.
When you ask an agency for a quote, the pricing model matters as much as the number. It decides who carries the risk, how changes are handled and how much control you keep. This guide is general information to help you compare options, not legal or financial advice.
The three models at a glance
| Model | You pay for | Best when | Main risk |
|---|---|---|---|
| Fixed price | A defined scope and deliverables | Requirements are clear and stable | Changes are priced separately and can cause friction |
| Hourly (time and materials) | Time actually spent | Scope is unclear or likely to evolve | The total is harder to predict |
| Retainer | A reserved block of time or an agreed service each month | You need ongoing support and improvements | Unused capacity if you do not plan the work |
Fixed price
A fixed price suits projects you can describe in detail: a list of screens, features, integrations and what "done" means. The agency estimates the work and commits to the agreed deliverables. Your budget is easier to plan, but only if the scope is written down. A short brief leads to disputes later, so see our guide to writing a project brief for a software quote.
- Ask what is included and what counts as a change request.
- Ask how many revision rounds are covered.
- Ask for milestones and what you receive at each one.
Hourly or time and materials
With hourly billing you pay for the time spent, usually with regular reports. It gives flexibility when you are still learning what you need, for example when exploring an integration or fixing problems in an existing app. The trade-off is less certainty about the final total, so agree a cap or a review point after a set amount of work.
- Ask how time is tracked and how often you see reports.
- Ask whether you can set a budget limit that needs your approval to exceed.
- Ask who works on the project and what each person does.
Retainer
A retainer is an ongoing arrangement, typically monthly, for support, fixes and small improvements. It fits after launch, when apps need updates for new store and platform releases. Our mobile app maintenance checklist shows what that work usually involves. Agree what the retainer covers, how requests are prioritised and how quickly you can expect a response.
How to choose
- How clear is your scope? If you can list every feature, lean fixed price. If not, start hourly or begin with a small paid discovery phase.
- How likely is change? New ideas are normal. If you expect many, hourly or a phased approach avoids repeated change-request negotiations.
- How much budget certainty do you need? Fixed price gives the most. Hourly with a cap gives some.
- What happens after launch? Plan support from the start rather than as an afterthought.
Combining models
A common approach is a fixed price for a well-defined first phase, hourly for exploratory or changing work, and a retainer after launch. Whatever you pick, write down the deliverables, the payment schedule and who owns the code at handover. Read who owns the source code when you hire an app developer before you sign.
Questions to ask any agency
- What exactly is included in the quoted price?
- How are changes requested, estimated and approved?
- What are the payment milestones?
- What support is included after launch, and for how long?
- Will I receive the full source code and my store accounts?
Next step
If you are comparing providers, our guide on how to choose an ecommerce app development agency is a good companion. To discuss your project, see our Flutter ecommerce app development service or request a quote.
Frequently asked questions
Is a fixed price or hourly rate better for an app project?
A fixed price works best when scope is clear and unlikely to change, because the budget is predictable. Hourly billing suits uncertain or evolving work, ideally with a cap. A retainer fits ongoing maintenance after launch. Many projects combine them.