Compare situations

Same method. Different evidence. Different answers.

Three situations at the same company, side by side. The recommendation follows what Discovery finds, not what was expected at the start.

Side by side

From trigger to next step

SITUATION 1

The one person who knows the system is leaving

Trigger
A custom tool runs production planning. The external developer who built it retires in four months. Nobody else has ever changed it.
Access
Tier B, read-only technical inspection
Key findings
  • The tool can only be built on one laptop
  • Scheduling rules exist only in code
Recommendation
Application Managed Services
First step after Discovery
Transition and stabilization: Joint sessions with Mr Brandt, company-owned build, first release by our team, restore test, monitoring of the ERP interface.
Take this tour
SITUATION 2

An audit finding and an end-of-life deadline

Trigger
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.
Access
Tier B, read-only technical inspection
Key findings
  • Server operating system near end of support
  • Administrative access open to the internet
  • Customer passwords stored with an outdated method
Recommendation
Modernization
First step after Discovery
Risk map and baseline: The findings become the risk map. We record today's behaviour, including the sync's failures, so each change can be measured.
Take this tour
SITUATION 3

Spreadsheets, silos, and a wish for AI

Trigger
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.
Access
Tier A, context-led
Key findings
  • Prices exist in three places, and they disagree
  • Surcharge rules live in macros only two people understand
Recommendation
Modernization
First step after Discovery
Inspection: Read-only access to the ERP price data and the macros; every Inferred finding is checked.
Take this tour