DependMap

The ability to ingest standard ERP exports without cleaning data first makes onboarding very convenient. It delivers clear impact assessments quickly without requiring deep configuration expertise from the user.

Starting with a simple spreadsheet export is a huge convenience compared to six-month IT projects. It feels slightly cumbersome to manually manage updates, but the speed of getting a costed impact brief is undeniable for quick decision-making during supplier failures.

I am genuinely thrilled by the concept of mapping multi-tier dependencies automatically rather than doing it by hand; the idea of having a live model that detects disruptions and produces plain-English briefs is exactly what my team has been dreaming of for years. However, I must voice a concern regarding the advertised terms because the website states it starts from a spreadsheet export, yet also mentions scheduled connectors for SAP, Oracle, and Infor as a natural next step. This ambiguity about whether those connectors are included in the base price or constitute a separate enterprise upgrade feels slightly misleading for small to mid-sized businesses who might assume the spreadsheet method is the only path. Furthermore, the proof of concept section highlights a blind test against the Renesas fire, which is fantastic, but it does not clarify if the data validation includes real-time contract parsing or just static exports. I really want to love this, but the lack of explicit pricing tiers alongside the mention of 'six-month IT projects' for deep integration makes me wonder if we are looking at a simple tool or a heavy platform in disguise. I hope the onboarding is truly as low-friction as claimed.

The impact briefs look impressive for quantifying tier-two risks, but the pricing structure remains unclear from the current website details, leaving some uncertainty on total cost of ownership.