# Fixed price vs hourly: which fits your project? > Choose a fixed price when you can describe the result clearly, and hourly when the work is open-ended or the scope will keep changing. Many clients get the best of both by fixing the price per milestone, so each step has a clear result and a limited cost. Canonical: https://erdibuilds.app/guides/fixed-price-vs-hourly Last updated: 2026-11-06 (November 6, 2026) ## The two models in one minute With a fixed price, the developer agrees to deliver a defined result for an agreed amount. With hourly pay, you pay for the time spent, usually with a report of what was done. The difference is who carries the uncertainty. **Fixed price compared with hourly** | | Fixed price | Hourly | | --- | --- | --- | | Cost certainty | High. You know the amount up front. | Lower. The total depends on the time needed. | | Who carries the risk | Mostly the developer, if the work takes longer. | Mostly the client, if the work takes longer. | | Flexibility | Changes need an agreement on scope. | Changes are easy, the plan can shift every week. | | Best for | Clear scopes, first versions, defined features. | Research, rescue work, ongoing improvement. | | Main watch-out | Unclear scope leads to disputes about what was included. | Without limits, cost can grow quietly. | ## When fixed price works well - You have a written brief and know what done looks like. - The work is similar to things the developer has built before. - You want a budget you can plan around. - You prefer to judge the result, not the hours. The key is a good description. A [project brief](https://erdibuilds.app/guides/how-to-write-a-project-brief) with a done-list for each step turns a fixed price into a fair deal for both sides. ## When hourly works well - You are exploring and cannot say yet what the product should do. - You need a developer to dig into an existing codebase and find out what is wrong, as in a [rescue](https://erdibuilds.app/help/rescue-project). - The job is a stream of small tasks with no clear end. - You want to steer day by day and are happy to review time reports. If you go hourly, set a weekly cap and ask for short updates. A cap turns an open bill into a limited one. ## Milestones: a middle path A milestone is a fixed-price piece of a bigger project. You do not need to price the whole product on day one. You agree on the next step, fund it, review it and move on. If the direction changes, only the next milestone changes. That is how ErdiBuilds works. Each milestone is funded before work starts and runs 1, 2, 3, 4, 6 or 8 weeks. Milestones are from 50 to 2,000 each in your project currency. You approve the delivery before funds are released, and you can ask for changes first. See [how milestones are planned](https://erdibuilds.app/guides/how-to-split-a-project-into-milestones) for a method. > Rule of thumb: if you can write the done-list today, fix the price. If you cannot, explore first in a small, fixed step, then fix the rest. ## Questions to settle with the developer - What exactly is included, and what counts as a new request? - How are small changes handled inside a milestone? - What happens if the work takes longer than planned? - How will progress be shown during the milestone? More ideas for the conversation are in [questions to ask before hiring a developer](https://erdibuilds.app/guides/questions-to-ask-before-hiring-a-developer). ## How the choice feels day to day With a fixed price, your attention goes to the result: does it do what we agreed? Meetings are about scope and quality. With hourly work, attention goes to time: what was done this week, and what comes next? Neither is wrong. Pick the one that matches how you like to manage, and how clear your goal is today. Some clients also worry that fixed price makes developers cut corners. The best protection is a precise done-list and a review after every step. Small milestones keep that review easy. ## Frequently asked questions ### Is fixed price or hourly cheaper? Neither is always cheaper. Fixed price protects you from overruns on clear work. Hourly can cost less on small or uncertain tasks. What matters most is how well the work is described. ### What if my scope grows during a fixed-price project? Treat new ideas as a new milestone or a change to the next one. Agree on the result before the work starts, so the price and the finish line stay clear. ### Can I mix both? Yes. Some clients start with a small fixed-price discovery step, then plan the rest. Others use fixed milestones for features and a separate agreement for ongoing support. ### How are payments handled on ErdiBuilds? Per milestone. Each milestone is funded before work starts and runs 1, 2, 3, 4, 6 or 8 weeks. Funds are released after you approve the delivery and a short holding period. ### How do I keep hourly work under control? Set a weekly cap, ask for a short written update each week and review the result often. If the end is unclear, pick a fixed milestone for the next step. ## Related - [How to Split a Project Into Milestones](https://erdibuilds.app/guides/how-to-split-a-project-into-milestones): Split a software project into milestones that each deliver something you can see and approve. Rules, an example plan and a free planner tool. - [How to Write a Project Brief for a Developer](https://erdibuilds.app/guides/how-to-write-a-project-brief): A good project brief fits on one page: goal, users, must-have features, examples and limits. Here is what to include and a free tool to draft it. - [How it works](https://erdibuilds.app/how-it-works): From idea to finished project, step by step. - [Pricing](https://erdibuilds.app/pricing): What ErdiBuilds costs for clients and developers. - [How to Hire a Developer Safely](https://erdibuilds.app/guides/how-to-hire-a-developer-safely): Hire a developer with confidence: pay per milestone, fund before work starts, keep payments on one platform, and get access to your code as you go.