Fixed price isn't a policy. It's a promise.

Hourly billing is not neutral. It transfers every unknown in a project onto the person paying the bill.

What hourly billing actually means

When a studio charges by the hour, their incentive and yours are pointing in opposite directions. A build that takes longer earns them more. A build that goes smoothly earns them less. Nobody sets out to drag a project — but the structure rewards it, quietly, and most clients don't notice until the invoice arrives.

Fixed price flips that. If we scope a project at €1,500 and it takes longer than we planned, that's our problem to solve. We absorb it. The number you agreed to is the number you pay.

Where the risk actually lives

Every project has unknowns. A third-party integration behaves differently than the documentation says. A feature turns out to need two components instead of one. A revision round surfaces a change that touches five pages, not one.

With hourly billing, every one of those unknowns is your cost. With a fixed price, they're ours. That's not charity — it's what we're being paid to manage. Working out what a thing will take before we start is the job. If we get it wrong, the penalty lands on us, not you.

That's the point.

What makes fixed price possible

Fixed price only works if the scope is written down before work begins. A quote without a scope list is not a fixed price — it's a number that will move.

This is why we spend two days on design before anything is built. We work out exactly what the project contains: which pages, which features, which integrations, who edits what after launch. That becomes the written agreement. The price is attached to a specific list of things, not to a vague description.

When someone comes back mid-project with a new requirement, we have a straight conversation: is this in the original scope? If yes, it's covered. If no, we quote it separately, in writing, before touching it. There's no ambiguity because there's a document.

That document also protects us. A client who remembers the project differently from how it was scoped doesn't have much room to move when everything is written down.

What it means in practice

You pay 30% upfront. The remaining 70% comes on completion — when the site is live, everything works, and you're happy with it. Nothing more, nothing collected in pieces as hours accumulate.

If you decide to cancel mid-project, the 30% is forfeited and that's the end of it. No exit fees, no invoice for hours worked, no argument about what was done. The 30% is what you're risking; we've already absorbed the design work.

Most projects between €700 and €3,500 are live within ten days of the design period finishing. The timeline is in the agreement. If we miss it for a reason on our side, that's on us — not priced back to you in extra hours.

The comparison most people don't make

A studio quoting hourly at €60/hour sounds cheaper than a fixed €1,500. It isn't, once the project runs 30 hours instead of 20. The fixed price was actually the lower number — but you only know that at the end of an hourly engagement, not the beginning.

We'd rather you know the number at the start. That's the entire reason we work this way.

If you want to know where your project lands, the pricing page shows the tiers and what each one includes. If you want a number for something specific, the 30-minute intro call is where we work it out — no obligation, and you leave with a real figure. Book one here.