Should I pay hourly or fixed price for a build?

Hourly versus fixed price is really a question about who carries the risk of the unknown, and the right answer depends on how well the work can be defined before it starts. Both models are honest in the right situation and dangerous in the wrong one. Here is how each really works, so you can choose the one that protects you rather than the one that sounds cheaper.

What each model really is

The two models differ in one thing: who bears the risk that the work takes longer than expected. Under a fixed price, you agree a number for a defined scope, and if it takes the builder longer than they thought, that is their problem, not your bill. Under hourly, also called time and materials, you pay for the hours actually spent, so if the work runs long, the cost runs up, and that risk sits with you. Neither is inherently fairer; they simply place the uncertainty in different hands. The whole decision comes down to how confidently the work can be defined in advance, because that is what decides whether fixing a price is even possible without someone getting hurt.

When fixed price is the right protection

Fixed price is the safer choice when you can define what you want clearly, which is the case for most people turning a prototype into a product, because the thing already exists and the gap to production, while invisible, is knowable. With a clear scope, a fixed price gives you certainty and predictability: you know the number, you can budget for it, and the pressure to be efficient sits with the builder rather than with your wallet. The condition is a genuinely clear scope, which is why a good fixed-price arrangement always rests on a detailed proposal that spells out exactly what is included, what is excluded, and how change is handled. Fixed price without a clear scope is not protection; it is a fight waiting to happen.

When hourly is honest rather than a trap

Hourly is not a trick, and there are situations where it is the honest choice. Genuinely exploratory work, where nobody can yet say what the finished thing should be, cannot be fixed-priced without either padding the number heavily or guessing and arguing later. Small, open-ended tasks, ongoing support, and work where you want the flexibility to change direction often suit hourly well. The risk with hourly is not dishonesty but drift: without a clear scope and regular check-ins, the hours can accumulate faster than the value. If you choose hourly, protect yourself with a cap or a regular review, so you are never far from a decision point. Used with those guardrails, hourly is a reasonable model, not a blank cheque.

How to choose, and the questions to ask

Choose by asking how well the work can be defined. If you can describe what you want clearly enough to write it down, prefer a fixed price on that written scope, because it gives you predictability and puts the overrun risk where it belongs. If the work is genuinely open-ended, prefer hourly, but with a cap and regular reviews so it cannot quietly run away. Whichever you pick, the protective questions are the same: what exactly is included, what is excluded, what happens when I want a change, and what do I own at the end. A model matters far less than a clear scope and honest terms. A fixed price on a vague scope and an uncapped hourly with no reviews are both ways to lose money; a clear agreement under either model is a way to keep control.