Assets discovered
Systems, containers, reports, datasets, packages, jobs, models, tables, and selected components.
Sample outputs
These examples show the kind of inventory, dependency evidence, warnings, confidence, scoring, and planning outputs a pilot assessment is intended to produce.
Systems, containers, reports, datasets, packages, jobs, models, tables, and selected components.
Direct, parsed, and inferred relationships across reports, jobs, packages, models, views, and tables.
Coverage gaps, unresolved references, redaction, circular patterns, and partial metadata signals.
Simple external scoring with the drivers and caveats visible.
Direct and parsed evidence separated from inferred links, missing access, and ambiguous names.
Unknowns are explicit follow-up questions, not hidden assumptions.
Deliverable types
A walkthrough should not only show counts. It should show how the inventory, dependency map, coverage report, complexity scorecard, recommendation signals, and readout pack work together.
Source systems, containers, assets, components, schedules, and selected raw artifacts.
Direct, parsed, and inferred relationships with evidence IDs, confidence, and caveats.
Partial scans, inaccessible surfaces, unsupported patterns, and reduced-confidence areas.
1-5 complexity and risk signals with explainable drivers rather than false precision.
Retain-and-investigate, phased modernization, priority planning, rationalization candidates, and open questions.
CSV exports, printable summaries, and review notes for stakeholders, partners, or planning workshops.
Asset levels
Dependency reality
A real estate may have tens or hundreds of reports, packages, datasets, tables, jobs, and models. Dependencies can be deep, repeated, ambiguous, or nearly circular. TangleMap is meant to expose that shape with caveats, not flatten it into a neat migration list.
Screenshot-style previews
These static previews show the kind of review surfaces a walkthrough should cover. Real client output should be redacted or synthetic before it becomes downloadable material.
A redacted output can support downstream planning or AI-assisted delivery frameworks with source systems, key assets, dependency edges, confidence, caveats, and follow-up questions.
A downloadable checklist or sample-output pack is a good lead-capture candidate, but the launch site currently uses a public checklist page. The gated download flow should be added once the form, consent copy, privacy wording, and follow-up process are decided.
Next step
Use a walkthrough to review sample deliverables, caveats, and interpretation before scoping a real pilot.