Software engineering from Vienna • Digitalization, AI agents, web & apps

Technical consulting

Technical audit before buying software or a shop

Buying software or a shop changes not only functions but also data responsibility, operational risks and further development. A technical audit makes visible what is being taken over and which assumptions must be checked before a decision.

Understand architecture and code

Structure, dependencies, extension points, testability and the path from a change to the production version are reviewed. What matters is whether the existing architecture can actually support the announced roadmap.

For shops, the catalogue, search, cart, checkout, stock logic and key integrations are added. Critical business processes should not be judged on the basis of screenshots alone.

Review data and interfaces

An audit clarifies who owns the data, how it can be exported and which systems are leading for customers, orders, products and documents. Data quality and historical special cases are particularly relevant for a later migration.

Interfaces are examined for documentation, authentication, rate limits, error behaviour and dependencies. An undocumented integration can shape operation more than a visible front-end feature.

Assess licences, security and operation

This includes patch processes, permissions, secrets, logging, backups, restoration and known vulnerabilities. Licences also need to be checked, including GPL and other copyleft obligations, commercial licences and their transferability.

GDPR, data processing agreements, the storage and deletion concept, production access and change approvals must be traceable. Technical debt belongs in the assessment as a separate risk item.

Turn findings into decisions

The findings are prioritised by impact and likelihood. In addition, assumptions, missing evidence and necessary measures should be explicitly documented before a takeover.

This creates a sound basis for negotiation, integration planning and operating decisions. An audit is not meant to prevent the purchase across the board but to make the actual obligations transparent.

Facing a similar problem?

We analyse your starting point and show you a pragmatic next step.

Book an initial consultation