First conversation
About an hour. We understand the pressure, who decides, and what access is realistic.
Discovery, step by step
Follow a real-world Discovery from the first conversation to the final recommendation. Choose a situation, change the access level, and open the documents you would receive at the end.
Meet Musterwerk
Musterwerk builds drive components for machine builders across Europe. Business is good, but the software that runs it grew one decision at a time: a customized ERP, a planning tool written for them in 2009, a customer portal on a rented server, and hundreds of spreadsheets that hold it all together. We use Musterwerk to show how Discovery works without exposing any real customer's systems.
Choose a situation
Each situation follows the same method and ends differently, because the recommendation follows the evidence.
A custom tool runs production planning. The external developer who built it retires in four months. Nobody else has ever changed it.
The customer portal runs on a rented server whose operating system loses security updates this year. A key customer's audit asks for a remediation plan.
Offers are calculated across Excel macros, Google Sheets, and the ERP. Prices disagree, the backlog is stuck, and management wants to know whether AI can help.
The journey
About an hour. We understand the pressure, who decides, and what access is realistic.
Agreement, NDA, access tier, and a readiness check that protects your systems.
Interviews, inspection, and analysis. Your team's time is concentrated in a few short sessions.
Inventory, handbook, assessment, roadmap, and project definition, every statement labelled with its evidence.
Managed services, modernization, a new product, or a clear reason not to proceed.
The outputs become the starting point of the engagement, or your own team's plan.
Access tiers
The access tier sets how deep each output goes, not whether you receive it. In the tour, switch tiers to see how findings and confidence change.
Interviews, the documentation you supply, demonstrations, and limited non-invasive review.
We describe the system as it is reported to us. Anything we could not check is marked Inferred or Unverified, and we make no claim of technical completeness.
Approved read-only access to named repositories, configuration, build and deployment setup, or infrastructure views.
Findings are validated against the sources we inspected, within the named scope.
Access to agreed systems and environments with controlled tests and confirmation from the people who run them. Production logs or business records only when each is separately authorized.
Findings are validated including runtime behaviour, within scope. Tier C is scoped and quoted separately.
What you receive
Written so that your own team, or any partner, can work from them.
Every system in the agreed scope, with its owner, purpose, dependencies, and the source of each fact.
How the system is built, released, and operated, its dependencies, known risks, and knowledge gaps.
What we examined, what we found, how serious each finding is and why, what we could not examine, and the controls we recommend.
Prioritized outcomes, options, dependencies, and the decisions you will need to make. No promised dates.
For the recommended next step: scope, team, schedule, acceptance checks, your responsibilities, commercial basis, risks, and open decisions.
After Discovery
The recommendation follows the evidence. You decide what to do with it.
The system should keep running, and someone accountable needs to operate it and make small, controlled changes.
A specific part of the system needs to change: an upgrade, a refactor, a new platform, or a selective replacement.
The evidence shows a new system or a new capability is the better answer than changing the old one.
Sometimes the right answer is to change nothing yet, or to do the work yourselves. That is a valid outcome, and you keep the outputs.
The terms
The first step
Three short answers are enough to begin. We reply with a first conversation to confirm the scope.
Start with Discovery