From Visibility to Action. A webinar series on what it takes to turn scattered technical knowledge into context that teams and AI agents can actually see, understand, and act on. This is the second session, following the first webinar on making the IT ecosystem visible and actionable.
How many quarters has that SAP or Navision migration been waiting its turn? That legacy Java system nobody wants to touch? The problem was never a lack of courage. It’s that nobody can see clearly enough to move with confidence. This webinar shows how Velorum’s automatic AS-IS Discovery builds that picture straight from the real stack, in hours. Risk-free. No guesswork.
The hidden cost of manual discovery
It shows up in every migration, every audit, every time a new vendor walks in the door. It never shows up in a budget.
Someone spends weeks mapping libraries by hand, while nobody is quite sure which version is actually running where. A bank with more than 70 core applications needs to move them, one by one, into containers. The engineering is manageable. The hard part is not having a map to start from, and without automatic AS-IS Discovery, that map gets drawn by hand. Then a new regulation lands, and there’s no quick way to see what it touches.
The information was never missing. It was just never visible. Documentation falls out of sync with what’s actually running. What everyone “knows” lives in a few people’s heads instead of somewhere the whole team can reach. Dependencies between services and databases go untracked, quietly, until one of them breaks something important. This is exactly where most teams reach for an IT asset discovery software, hoping for a clean inventory. But an inventory is only step one: what they actually need is a context layer, not just a list of what’s there, but a clear picture of how everything connects.
What the session covered
Xavi Reig walked through why most technology stacks end up this way, with knowledge scattered across a dozen places instead of living in one, and what that costs a team trying to move forward. He framed it as three simple questions any organization should be able to answer, right now:
- How long does the team spend rebuilding context before real work even starts?
- How many different places does the documentation live in, and is any of it complete?
- If an outside vendor had to be brought up to speed on a critical system tomorrow, how long would that actually take?
The number that got the most reactions
$33K–$55K. That’s what technical debt costs, per engineer, per year, before a single incident and before it starts compounding. Deloitte puts 21–40% of total IT spending toward simply keeping that debt in check, and the figure climbs higher in older organizations. CAST looked at over 10 billion lines of code in 2025 and found 61 billion days of repair work sitting there, unresolved, worldwide.
None of this is a knowledge problem. The knowledge already exists, somewhere in the systems. It’s a visibility problem: nobody can see how it all fits together. That’s why any automated software documentation migration effort starts with visibility, not code.
How Velorum addresses automated software documentation
The second half of the session, Xavi Reig showed how Velorum builds that context layer automatically, straight from how the systems actually work today. No workshops, no manual effort, no waiting on someone’s memory.
This session’s featured module, Knowledge Documentation, is what automated software documentation should look like in practice: technical and functional documentation pulled straight from the real systems, and kept current without anyone updating it by hand. Most asset discovery tools stop at a snapshot, a static list that’s already a little out of date by the time anyone reads it. Automatic AS-IS Discovery works differently. The context layer keeps mapping, continuously, so the picture never goes stale. If it’s in the code, it’s in the documentation. That means new hires get up to speed faster, audits stop being dreaded, and hidden dependencies show up before they cause an incident, not after.
And the business case for an automated software documentation migration approach holds up at scale: €500,000 a year in savings for every 50 developers.
Next in the series: W3 · October — Moving to a new data platform? Fabric, Snowflake, Databricks. Know what you’re taking with you, first.
Want to see the full session?
This article covers the highlights. The full session includes a live demo and the Q&A with attendees. Request the full recording here.
