| Composite fit | 42 | — | 0.5 |
| Why: Modest technical alignment with a web/GIS database modernization effort is heavily discounted by a stalled solicitation with no release date, zero federal past performance, and a GIS capability gap that is central to this requirement. |
| Technical fit | 58 | pass | 0.3 |
| Why: Cloud-native web stack (React, TypeScript, Postgres, AWS/Azure GovCloud) maps reasonably to an AMLDB web application update, but the vendor shows no demonstrated GIS or geospatial capability, which is explicitly required for the AML GIS system components. |
| Financial fit | 50 | pass | 0.2 |
| Why: Contract size is unknown and the solicitation is indefinitely delayed, making financial workability impossible to assess; the vendor's commercial-scale platform experience suggests adequate capacity if the award is mid-tier, but there is no anchoring data. |