A fixed-price modernization proposal prices a defined obligation. When discovery is incomplete, the definition of that obligation becomes a central part of the comparison. A stable quoted number does not make unknown interfaces, business exceptions, or recovery requirements disappear.
The practical question is whether both parties can determine what the deliverable must do and how it will be accepted. Ambiguity in that boundary can reappear as excluded work, disputed acceptance, or a later change to scope.
Price stability and scope completeness differ
US FAR 16.202-1 defines a firm-fixed-price contract as one whose price does not change merely because the contractor’s performance costs differ from expectations. That is a specific US federal procurement definition.
It does not establish unlimited requirements or dictate the interpretation of a private contract. Applicable terms and modifications still matter. The distinction useful to this assessment is between the cost of performing agreed work and the discovery of work whose inclusion is unresolved.
A proposal should identify required inputs, interfaces, outputs, quality, exclusions, and acceptance evidence. A conversion count is insufficient when the buyer expects a working service with reconciled data and a maintainable deployment.
Unknown inventory must remain unknown
A CMDB can contain stale versions, missing relationships, or conflicting owners. AWS’s portfolio guidance calls for examining freshness and gaps before using such records as assessment evidence.
Normalize names while retaining source identifiers and aliases, then sample important records against deployed evidence. Conflicts should be resolved or explicitly retained as uncertainty.
Suppose an inventory lists one nightly export while discovery later finds a quarterly consumer with a different layout. The contract needs a stated treatment of that discovery. An assumed complete inventory cannot provide that decision after the fact.
Discovery can produce a priced boundary
A bounded discovery deliverable can establish representative workflows, dependency evidence, unsupported features, and acceptance examples before a larger commitment is defined. Its own scope and output should be inspectable.
Alternatively, a proposal can state assumptions and a change process for unresolved areas. The comparison should show how different assumptions affect the offered obligation rather than ranking quotations as if they covered identical work.
Unknown capability is neither demonstrated failure nor demonstrated success. Supplier evidence should distinguish an untested claim from a failed representative trial.
Milestones need dependencies and purpose
A milestone can represent delivered source, accepted data reconciliation, demonstrated recovery, or completed handover. These events should state their verification method and prerequisites.
US FAR performance-based financing distinguishes independent from cumulative events in its own financing context. That distinction illustrates why one event can depend on earlier accepted work without making every milestone a production-readiness decision.
Payment triggers and operational acceptance should therefore remain explicit. A paid conversion milestone can coexist with unresolved integration and cutover work; the record should not describe the service as complete merely because that payment event occurred.
Compare the whole transition obligation
Supplier comparison should use common requirements and evidence requests and record strengths, gaps, exclusions, and risks. The actual procurement rules depend on the buyer; the FAR example does not establish compliance elsewhere.
Include licenses, manual remediation, validation, coexistence, training, operations, warranty, handover, and exit over the same horizon. Retained customer duties can materially affect the effort required to realize the proposal.
Acceptance is concrete when both parties can inspect whether the delivered behavior satisfies the priced scope and identify the disposition of newly discovered work. The fixed price then applies to an understandable obligation rather than substituting for discovery.