Hourly rate or fixed project price? How to compare the cost of work

One supplier quotes for the entire project; another offers an hourly rate. You cannot compare those figures without knowing the scope and likely effort. Even two hourly rates say little if the teams understand the task differently.

Start with the result you need. Then examine how each model lets you control the cost of reaching it.

For a fixed price, check the boundaries

Establish the assumptions covered by the total, what you supply and how changes are priced. Ask what happens if an integration differs from its description or materials arrive later than expected.

A fixed price is useful when you know what it applies to. An unclear scope does not become precise simply because there is one number beside it.

For hourly work, check effort and control

Ask for estimated effort, team roles and reporting arrangements. Establish which activities are charged: meetings, testing, management and fixes. You also need a spending limit and a clear point at which you decide whether further work should proceed.

Here is an invented example to illustrate the arithmetic: 100 hours at 250 PLN equals 25,000 PLN excluding VAT. At 180 PLN, 160 hours costs 28,800 PLN excluding VAT. The lower rate alone does not identify the cheaper option. This does not prove anything about a particular supplier's productivity; it shows why both rate and effort matter.

Compare the same outcome

Ask for the result of each stage, its expected cost and how the supplier will flag a likely overrun. Agree what you receive if you stop after that stage.

The pricing model needs to suit the scope and purchasing arrangements. Whichever you use, look for visible progress, understandable billing and an agreed process for change decisions. Add post-launch costs when comparing the whole budget, so the delivery model does not distract from the cost of operating what you buy.