Technical Debt Mitigator
Reduce technical risk, extend system lifetime and enable modernization — without unnecessary rewrites. 35+ years of software engineering experience across legacy systems, architecture, Delphi and .NET modernization. I don't build your system. I take your side as an independent architect — I work out what you actually have (even without documentation), surface the risks, and make sure what your vendor builds doesn't come back to bite you a few years down the line.
Technical Debt Mitigation→ Legacy Systems→ Architecture→ Delphi→ .NET Modernization
The core problem
The question is whether they're saying that because they verified it — or because they're inside the problem and can't see it. An independent assessment doesn't depend on what the people who built the system think about it. It works from what's actually in the source code, the data, and production behaviour.
The question nobody asks out loud
Without an assessment, you pay nothing — until the risk actually materializes. And then it doesn't arrive gradually. It arrives all at once, at the worst possible moment.
Without documented knowledge, losing one person turns into weeks or months of reconstructing know-how — often in the middle of live operations, not at a calm moment.
The longer a system grows on a closed platform, the more expensive it becomes to leave — the exit cost doesn't fall over time, it rises.
Technical debt doesn't add up linearly — new features get built on the old foundation, and every year of delay makes the eventual modernization cost more than solving it earlier would have.
An architectural problem that surfaces during an acquisition, an audit, or peak operations always costs more and moves faster to fix than one caught calmly in advance.
For comparison: a fixed-price development audit costs CZK 19,900 and is delivered within five business days. A month's delay on a key project or an emergency fix for an unforeseen risk typically costs an order of magnitude more.
What I offer
This isn't an hourly rate for anything. It's a validated methodology for assessing risk and architecture — with a clear, repeatable process and a written deliverable the company keeps using regardless of who performed the audit.
01
A business-critical system running on Delphi (or another aging stack) that nobody wants to rewrite and fewer people every year know how to maintain? I combine architectural judgment, Delphi knowledge and modern C#/.NET to keep it an asset, not a liability.
About legacy systems & Delphi →02
Not entirely sure what your system actually does and why? Documentation missing or out of sync with reality? I reconstruct the architecture directly from the source code, configuration and runtime behaviour — documentation isn't a prerequisite.
How the audit works →03
Having software built and have no way to judge whether the vendor is building to plan and with sound decisions? I stand on your side and watch the load-bearing walls — the data model, module boundaries, contracts.
About construction oversight →04
You don't need to employ an architect — but you do need one within reach when a decision is made that can't be undone two years later, or when debt keeps accumulating with nobody accountable. Senior capacity on a monthly retainer — no hiring, no hunting for a consultant every single time.
About Technical Debt Mitigator → Not sure if you need one? 6 questions →05
Data scattered across ERP, CRM, your online store and other systems, and nobody's sure which version is correct? I design and build the connections between systems — federated across sources, via API or batch — without adding yet another black box.
About system integration →06
Not sure where the team is really losing time or where the risk sits? A fast diagnosis of your process and development management for a fixed CZK 19,900 — no monthly commitment, delivered within five days.
About the development audit →07
Software designed only for today gets rewritten from scratch a few years later. I work by the principle that the model and the implementation stay separate — the technology can be swapped out without destroying the whole system.
What that means in practice →Who I help
"I'm not sure our system is designed to last."
Architecture assessment →"I need an independent person to assess our vendor."
IT construction oversight →"We're taking over an old system with no decent documentation for what we actually bought."
Architecture reconstruction →"We have data in five systems and each one says something different."
System integration →"We're preparing a new system and want independent architectural oversight over it."
Discuss the scope →"We're a software company and need a senior architect for a specific problem."
Write to me →"We're building embedded devices and writing configuration UI for each type costs us too much."
UniSetup R&D program →Philosophy
It should still be maintainable and extensible in ten or twenty years. That means separating the model from the implementation, minimizing vendor lock-in, keeping decisions traceable after the fact, and building architectural boundaries that survive a change of technology or people. The contract is the truth — the screen, the report, the API and the AI agent are just its projections.
Track record
2010 →
The d.process platform deployed at the Liberec Region Authority, still running in public administration today.
2009
Design of a document repository for CzechPOINT — a standalone project outside d.process.
3×
A language and virtual machine of my own — from a bytecode interpreter in 1997 to today's Atra language.
Independence
Alongside the audit practice, I also develop my own technologies long-term (d.process, ATRUST, UNISETUP). When assessing your system, I recommend solutions independently of what I develop myself — the audit practice and my own products are deliberately kept separate on this site.
Browse the technology portfolio →From the field
Illustrative, anonymized scenarios based on recurring risk patterns the audit uncovers.
Bus factor 1
A monthly close depending on one analyst and their personal spreadsheet macros — with no backup of the know-how.
Vendor lock-in
A core workflow built on one vendor's low-code platform — exporting data or logic is practically impossible.
Undocumented legacy
A critical ERP from the 90s with no current documentation — the last in-house expert is retiring.
Partnership
Nobody buys the best architecture if they never hear about it. I'm looking for an independent partner with their own network of B2B contacts who can open doors I can't reach on my own. I explain the technology, you run the sales — purely on a success fee, with no fixed commitments.
Partnership terms →