Fixed price or milestone billing: which is right for your project?

When you commission a website, an app or custom software, one of the first questions is how you will pay for it. Two approaches come up again and again: a single fixed price for the whole project, or payment in stages tied to milestones.

Neither is better in every case. Each suits a different kind of project, and understanding the difference helps you choose the one that gives you the right balance of certainty and flexibility.

What a fixed price means

With a fixed price, you agree the total cost up front for a clearly defined piece of work. The quote sets out exactly what you are getting, and the price does not change unless the scope does. Payment may still be split, for example a deposit at the start and the balance on delivery, but the total is known from day one.

The main advantage is certainty. You know what you will spend, which makes budgeting simple. It also puts the focus on delivering the agreed outcome.

When fixed price works well

• The requirements are clear and unlikely to change much, such as a brochure website or a well-understood feature.
• You have a firm budget that cannot be exceeded.
• You want to agree everything before work starts and then leave the developer to get on with it.

Where fixed price can struggle

A fixed price depends on the scope being understood. If the requirements are uncertain, one of two things tends to happen. Either the quote includes a generous allowance for the unknowns, so you pay for risk that may never materialise, or the scope is tied down so tightly that every new idea becomes a formal change request.

That is not a flaw, just a trade-off. A fixed price gives you certainty about cost in exchange for less freedom to change direction along the way.

What milestone billing means

With milestone billing, the project is divided into stages, and each stage is agreed and paid for as it is completed. A milestone might be an approved design, a working first version, or a launch-ready build. You agree what each stage involves and what it costs before it begins.

The main advantage is flexibility. You see real progress at each stage, you can adjust what comes next based on what you have learned, and you are never committed to the whole project at once.

When milestone billing works well

• The project is large or complex, and it makes sense to build it in phases.
• You expect to learn things along the way, perhaps from user feedback, that will change what you need.
• You want to start with a smaller first release and add to it as the business grows.

Where milestone billing can struggle

The total cost is less certain at the outset, because later stages are defined as you go. That makes it easier for a project to grow beyond what you first imagined. It also needs more involvement from you, since each stage needs a decision. The remedy is to agree an overall budget range and to be clear about the cost of each stage before it starts.

Questions to help you decide

1. How clearly can I describe what I need today?
2. How likely is it that the requirements will change?
3. Do I have a fixed budget, or can it flex if the project grows?
4. How much time can I give to reviewing and deciding at each stage?
5. Would I rather launch something small soon, or one complete product later?

What to look for in either approach

Whichever model you choose, a good quote should be in writing and should describe clearly what is included. It should explain how and when payments are due, what happens if the scope changes, and how any extra work will be agreed before it is carried out. There should be no hidden fees, and nothing that surprises you on an invoice.

It is also perfectly sensible to combine the two. You might fix the price of a clearly defined first phase, then agree later phases as milestones once you know more. If you are not sure which suits your project, describe it to us and we will recommend an approach and set it out in your written quote.