Why a fixed price per week beats a fixed-scope quote

A fixed-scope quote sounds safe. One number, one deliverable, signed up front. The problem is that nobody knows the real scope of a systems job until they're inside it. So either the builder pads the quote to cover what they can't see, or they quote lean and come back in week six with a change order. Owners who've been through it once recognise the second pattern immediately: the phase-two quote that arrives at three times phase one.

Price the week, not the project

The alternative is to fix the price of a unit of time instead of a unit of scope. One week costs one amount, agreed before Monday. Monday, you and the builder agree one goal for the week, written in a sentence. Friday, you see it working on your real data and decide whether to book the next week.

• The price can't creep, because there's nothing to creep. Next week is a new agreement.
• Scope can change freely, between weeks, without an argument about what was promised.
• You can stop after any Friday. Everything built so far is yours and keeps running.
• The builder has no reason to pad, because the work is paid as it's done.

What it asks of you

One named person on your side who can answer questions during the week, a short Monday conversation, and twenty minutes on Friday to check the work. That's the whole commitment. Owners who try it rarely go back to quotes, for the same reason nobody goes back to a mobile plan with a two-year lock-in once they've had month to month.