Why we quote fixed price for the first stage

When someone asks us to build them a data pipeline or an internal ops tool, the first stage we quote is a fixed price. Not a day rate with an estimate attached. A number, a defined piece of work, and a date. Clients sometimes expect us to prefer the open-ended arrangement, since on paper it pays us for every hour we spend. We do it the other way round on purpose, and it is worth explaining why.

What fixed price forces us to do

To put a fixed number on a piece of work, we have to actually understand it first. That sounds obvious. It is also the step most projects skip, and skipping it is where budgets die.

Before we quote, we sit with the problem. We look at the real data, not the tidy sample. We ask what the tool is replacing and why the last attempt did not stick. We find the parts that look simple and usually are not: the supplier feed with three different date formats, the approval step that lives in someone's inbox, the edge case everyone forgot to mention. A fixed price is a promise, and you cannot make an honest promise about work you have not examined. The discipline is the point.

An open-ended contract lets you start building before you understand the problem. A fixed price makes you understand it first, because your own margin depends on it.

Where it protects the client

With time-and-materials from day one, the person carrying the risk of a bad estimate is you. If we misjudge the work, the clock keeps running and you keep paying. That is a strange deal to offer someone who cannot yet see inside the code to know whether the hours are well spent.

Fixed price moves that risk to us, which is where it belongs at the start. If we underestimated, that is our problem to absorb, and we absorb it. You know the number before you commit. You can compare it against what the thing is worth to you and decide with real information. And because our margin now depends on being right about the scope, we are motivated to say no to the vague feature and yes to the sharp one. The incentive points the same way yours does.

There is a second protection that matters more than the money. A fixed first stage is small and defined by design. At the end of it you have a working slice you can judge: a pilot that runs against your real data, or a scoped piece you can put in front of your team. If you do not like how we work, you find out cheaply, and you can walk. Nobody is locked into a long build on the strength of a sales call.

The honest tradeoffs

Fixed price is not free of downsides, and pretending otherwise would be the kind of thing we are trying to avoid.

• It takes real work up front, so there is a gap between "yes, let's talk" and a number on the page.
• We build a buffer into the price to cover the unknowns, so a fixed quote can look higher than the optimistic hourly math.
• It only works when the scope can be pinned down. If the problem itself is genuinely undefined, a fixed price is just a guess wearing a suit.

That last point is the real limit, and it is why we only fix the first stage.

Where fixed price stops making sense

Once the pilot works and we move into ongoing development, the shape of the relationship changes. Now the work is a stream of decisions: which feature next, how far to push on performance, whether to handle the odd case now or later. You want to be able to change your mind next week without renegotiating a contract. Trying to fix-price that is how you get an agency that argues about whether your new request is "in scope" instead of building the right thing.

So for the long haul we move to a rolling arrangement, usually a monthly block of capacity, where you can steer week to week. By then the trust has been earned in the only way that counts, which is by shipping something real. The fixed first stage is what makes that later flexibility safe. You are not handing over an open-ended budget to strangers. You are extending it to a team that already put a number on the table, hit it, and gave you something that runs.