An IT project comes up: move the mailboxes, clean up who has access to what, connect Odoo to the bank, automate a report. You ask for a price. Two answers come back: "it's this much, fixed price", or "budget this many hours, we'll take them off a pack". Both are defensible. They split the risk differently, and that split is what you are really choosing.
I have already compared an hour pack with hiring an in-house IT person in an earlier article. The question here is narrower: for a given project, should you pay for a result or for time?
What you are actually buying
With a fixed price, you buy a result described upfront. The provider carries the overrun risk: if the work takes twice as long as planned, that is their problem. In return, they price that risk in and stick to the signed text. Anything not written down becomes an extra.
With an hour pack, you buy time. You keep the overrun risk, but you also keep the freedom to change your mind along the way. Nobody negotiates a change order because you found a second server at the back of the cupboard.
Fixed price works when the result fits on one page
An honest fixed price needs a scope you can count and check. "Move twelve mailboxes to Microsoft 365, with calendars and contacts, without losing a single message": you know how many, you know what, you know how to check. Both sides can quote without bluffing.
Three questions before you sign:
- Is the deliverable described in a way you can verify, or with adjectives like "modern", "secure" or "optimised"?
- Who signs off the end of the project, and against which tests?
- How is a new request priced and approved before anyone does it?
If even one answer is missing, the fixed price is not safer. It just pushes the argument to the end of the project.
An hour pack fits when you find things out as you go
Many small IT projects start with an unknown. Nobody knows exactly who can reach the file server, which shares are still in use, or which Excel macro feeds the invoicing. Quoting that at a fixed price means asking the provider to guess. Either they pad the price to cover themselves, or they underestimate and rush the end.
An hour pack lets you look first and decide afterwards. It also suits work that arrives in small pieces: a laptop to set up, a permission to fix, a Peppol invoice that will not go through.
It does ask for discipline on your side: an up-to-date priority list, and a record of hours used, task by task. Without that record, you do not know what you paid for. Check how long the hours stay valid before you buy.
The mixed approach: scope in hours, deliver at a fixed price
For a mid-sized project, combining the two is often the healthiest option. A few hours go into taking stock and writing down the scope. That document belongs to you. The well-defined parts then move to a fixed price, and whatever is still fuzzy carries on in hours.
A good test: another provider should be able to quote a fixed price from that document. If they can, the scope is precise enough.
A quick decision grid
- You can count the work (laptops, mailboxes, users): a fixed price is an option.
- You don't yet know what is in the cupboard: hours first.
- The need comes back as small requests over several months: a pack.
- Your budget is fixed and will not move: a fixed price, with the scope cut to match.
- You want to be able to change priorities every week: a pack.
What matters either way
Fixed price or pack, ask for the same three things at the end: documentation of what was done, admin access in your own name, and a list of what is left to do. Without them, you depend on the provider, whatever the billing model. We covered this for domain names and admin accounts.
z80 sells hour packs; what they cover and their terms are on the IT expertise and hour packs page. If you are unsure which model suits a specific project, send three lines to info@z80.be: what you want to achieve, what exists today, and your deadline.