Brand Logo

Got a question? Chat with us.

Chat on WhatsApp › Book a Meeting ›
Chat with us
WhatsApp Icon
fixed price vs time and materials software

Fixed-Price vs Time & Materials for Modernization

Contents

  • Why most firms can’t quote fixed-price on legacy work
  • How a diagnostic makes fixed-price possible
  • What a walk-away clause actually protects
  • Milestone billing on a long program
  • Questions to ask any firm quoting fixed-price without a diagnostic
  • When time and materials is the right answer
  • FAQ
  • Next step

Here is the honest position, stated before the argument: nobody can quote a fixed price on a legacy system they haven’t read. Not us, not anyone. A fixed price offered on a discovery call is a guess wearing a suit, and you will pay for that guess later — in change orders, in padding, or in a firm quietly cutting quality to protect a margin it priced wrong.

That’s not an argument against fixed pricing. It’s an argument about sequence. This article explains why most firms genuinely can’t quote fixed on legacy work, what makes it possible, and the questions that distinguish a real fixed price from a number someone made up.

Why most firms can’t quote fixed-price on legacy work

Fixed pricing requires bounded uncertainty. On greenfield work you can bound it: the requirements are the requirements, the stack is chosen, and the unknowns are mostly about effort rather than existence.

Legacy work inverts that. The dominant uncertainty isn’t “how long will this take” — it’s “what is actually in there.” And that uncertainty has a specific, nasty shape.

The unknowns are unknown. Not risks you can price with a contingency, but things nobody knows exist. Undocumented business logic. A cron job that some downstream system depends on. A dependency nobody can upgrade because of a reason lost when someone left in 2019.

Discovery is the work. On a rebuild, a large share of the effort goes to determining what the current system actually does, because the answer to “what should the new one do” is mostly “what the old one does, including the parts nobody remembers.”

The blast radius is unbounded before you map it. A change that looks local can turn out to touch everything, and you cannot know which changes those are without reading the system.

Faced with that, a firm has three options. Refuse fixed pricing and work on time and materials — honest, and it puts all risk on you. Quote fixed with heavy padding — you overpay for risk that mostly doesn’t materialize, and the padding is invisible. Or quote fixed without padding and manage the overrun through change orders — which is how most fixed-price software disputes start.

There’s a fourth, and it’s just sequencing.

How a diagnostic makes fixed-price possible

You cannot price what you haven’t read. So read it first, as a separate, smaller, fixed-price engagement.

A Systems Audit — $18K–$35K, two to three weeks — produces an architecture map and a risk register. With those in hand, the uncertainty that made fixed pricing impossible has been converted into a document.

The build proposal that follows is priced against the map, not against a conversation. That’s the whole mechanism, and it’s why the audit is fixed-price too: its own scope is genuinely bounded, because reading a system is a defined amount of work in a way that changing one isn’t.

The arithmetic works in your favour. An audit at $18K–$35K that removes the padding from a $400K build proposal pays for itself several times over — and that’s before accounting for the change orders it prevents. The diagnostic isn’t an additional cost. It’s the thing that makes the larger number honest.

There’s a second effect that matters more over a long engagement. When the firm building the thing also produced the map, they can’t blame the scope. They wrote it. That alignment is worth more than the pricing mechanism itself.

our published price bands for each stage

What a walk-away clause actually protects

Our audits carry one: you own the architecture map, risk register, remediation plan and fixed-price build proposal whether or not you hire us afterward. Hand them to a competitor if you want.

What this protects, specifically:

Against a diagnostic designed to sell a rebuild. If the firm doing the assessment only profits when the answer is “rebuild,” you should discount the answer accordingly. A diagnostic you can take elsewhere has to be defensible to a rival firm reading it critically, which changes how it gets written.

Against sunk-cost lock-in. Without the clause, the money you spent on discovery is stranded if you choose a different firm. That’s an artificial switching cost, and it’s the point of not offering the clause.

Against a quote you can’t evaluate. With the map, you can take our build proposal to two other firms and get comparable quotes — comparable because they’re pricing against the same document. That’s genuine competition, and we’d rather win it than avoid it.

The commercial logic on our side is straightforward. A client who feels locked in negotiates like a hostage. A client who could walk and chooses to stay actually believes the plan. The second kind of engagement goes better, and over six to twelve months that difference is worth far more than the switching cost we gave up.

Milestone billing on a long program

A $250K–$750K modernization program running six to twelve months is not one fixed price. It’s a sequence of them.

Each milestone has its own scope, price and acceptance criteria. Written before the milestone starts, not negotiated after.

Acceptance is defined in advance and is objective. “The new order service handles 100% of production traffic with error rates at or below current” — not “the client is satisfied.” Subjective acceptance is how milestone billing turns adversarial.

Each milestone ends at a decision point. You can stop. Not as a threat, as structure: a program you can exit at six defined points is a program you can govern, and it’s the version a board will approve. A program you can only exit by breaching a contract is one nobody wants to sign.

Re-scoping happens at milestone boundaries, in the open. Discovery during month three will change what month seven should be. Pretending otherwise produces either a bad month seven or a change order argument. Handling it at a boundary, with the map updated, keeps it a planning conversation.

Named architect, consistent across milestones. Continuity of the person who holds the model in their head is worth more than any contractual term. why continuity is the scarce resource

Questions to ask any firm quoting fixed-price without a diagnostic

If a firm gives you a fixed price on legacy work before reading the code, ask these. The answers are diagnostic regardless of who you’re talking to.

“What did you base this number on?” If the answer is a discovery call and a demo, they’re pricing risk they haven’t measured. That risk is in the number — you just can’t see it.

“What’s your change-order history on comparable projects?” A fixed price with a pattern of 40% change orders is a time-and-materials engagement with worse governance. Ask for the actual figures on their last three engagements of similar size.

“What happens when you find something you didn’t expect?” There is no wrong answer except “that won’t happen.” Listen for whether the mechanism is defined in advance or invented under pressure.

“What’s explicitly out of scope?” A fixed price with no documented exclusions isn’t fixed. The exclusions are where the change orders come from, and a firm that hasn’t written them down hasn’t thought about them.

“Who owns the estimate if it’s wrong?” On a genuine fixed price, the firm does. If the answer involves sharing overruns, you’re in a hybrid arrangement — which can be fine, but you should know.

“Can I take your scope document to another firm for a competing quote?” The answer tells you whether they’re competing on quality or on switching costs.

When time and materials is the right answer

Fixed pricing isn’t always better, and a firm that says it is should be discounted.

Genuine R&D. If nobody knows what should be built, fixed price forces a specification that will be wrong. You’ll get exactly what you asked for, which was the wrong thing.

Active emergencies. Stabilizing a failing system involves responding to what you find. Fixing scope during a fire means either scoping too narrowly to help or padding heavily for the unknown.

Ongoing capacity. An embedded pod running your roadmap is monthly, not fixed-price, because the roadmap changes. That’s the point of having one.

Very small work. Under a few weeks, the overhead of scoping and acceptance costs more than the risk it manages.

The pattern: fixed price where the scope can be known in advance, time and materials where it genuinely cannot. And a diagnostic is how you find out which situation you’re in.

FAQ

Is fixed-price or time and materials better for software development?

Neither universally. Fixed price is better where scope can be determined in advance — which on legacy work requires a diagnostic first. Time and materials is better for genuine R&D, active emergencies, and ongoing roadmap capacity. The mistake is treating it as a philosophical preference rather than a question about how knowable the scope is.

Can a firm quote fixed-price on a legacy system without reading the code?

Not honestly. A fixed price offered before anyone has read the system is a guess, and you pay for it later in change orders, padding, or quality cut to protect a mispriced margin. A real fixed price is produced from an architecture map.

Isn’t paying for a diagnostic just an extra cost?

It’s usually the opposite. An $18K–$35K audit removes the risk padding from a $400K build proposal and prevents the change orders that padding was hedging against. It also gives you a document three firms can quote against comparably.

What is a walk-away clause?

A clause under which you own the diagnostic deliverables regardless of whether you hire the firm that produced them. It protects against an assessment written to sell a rebuild, against sunk-cost lock-in, and against a quote you have no way to compare.

How should milestone billing work on a long program?

Each milestone gets its own scope, price and objective acceptance criteria written before it starts, and each ends at a genuine decision point where you can stop. Re-scoping happens at boundaries in the open. Subjective acceptance criteria are what turn milestone billing adversarial.

What should be out of scope in a fixed-price contract?

Whatever the firm has thought about and excluded — and the absence of a documented exclusions list is the warning sign. Exclusions are where change orders originate, so a contract without them isn’t actually fixed.

Next step

If you have a fixed-price quote in hand that wasn’t produced from an architecture map, ask the six questions above before signing. They cost nothing and the answers are informative whoever you’re buying from.

If you’d rather have the map first, that’s what the Systems Audit produces — $18K–$35K, two to three weeks, and you own all four artifacts whether you hire us or take them somewhere else.