The Digital Architecture Check: What Must Be Clear Before Any Tool or AI Decision

Before a company buys a new tool or starts a migration, it should know what it currently has. That sounds obvious. It rarely is. In most mid-sized businesses, no complete overview of the software landscape exists.

A tool stack assessment closes this gap. It is a time-bounded project with a concrete deliverable.

What gets delivered

At the end of an assessment, a document answers three questions:

1. Which tools are actually in use?
2. Where does which data live, and who maintains it?
3. Which three to five weaknesses generate the largest friction losses?

Plus a prioritised recommendation: what to address first, what can wait, what should not be touched.

The document is typically 15 to 25 pages. It is not meant for the drawer – it is a working document for management discussions. It contains no advertising for specific vendors. It contains recommendations that are independent of what would be easiest to sell.

What the process looks like

An assessment is deliberately compact. The effort on the client side remains manageable because the work is based on existing material, focused conversations and clear decisions.

Phase 1: Inventory. A complete audit of all tools in use. Licences, accounts, data. Who has access, who is the administrator. This is the least spectacular phase and simultaneously the most important. Software regularly surfaces here that management had forgotten existed.

Phase 2: Process walkthrough. Three to five core business processes are traced end-to-end – from lead to invoice, from goods receipt to stock entry, from employee onboarding to first login. What happens in which system, where does data break, where is it entered twice, where do employees complain.

Phase 3: Analysis. Consolidation of findings. What are structural problems, what are isolated cases. Which investments would address which pain points.

Phase 4: Presentation. Results are discussed with management in person, not sent by email. First the situation is explained, then decisions and priorities are set.

What an assessment is not

It is not a technical deep-dive on individual systems. Nobody checks whether the Exchange server is correctly configured or whether the backup strategy is properly documented. Such audits are valuable, but they are not part of this format.

It is also not a software recommendation. The output is not: “You should implement Microsoft 365.” It is: “Your current mail stack causes 35 percent of support tickets. A move to a cloud-based solution would address these issues. Three options are realistic; one is recommended – the selection belongs in a separate step.”

The difference sounds minor but is significant. An assessment conducted to sell a predetermined solution is not consulting – it is a sales process in academic clothing.

What it costs

The price bracket for a tool stack assessment is deliberate. High enough that only companies with genuine interest in change will enquire. Low enough that the barrier remains surmountable. The specific fee is agreed per engagement before work begins.

For companies in Austria, there are funding pathways that can cover a significant portion of the costs. Which ones apply in a given case is clarified in advance.

What comes next

After the assessment, there are three paths:

1. The company implements the recommendations using its own resources.
2. The company assigns individual projects from the list to specialised service providers.
3. The company arranges ongoing support, in which I coordinate the implementation.

None of the three paths is implied in the assessment fee. The decision is made after delivery. That is the purpose of the format: first see what is happening, then decide.