Discovery, step by step

See what Discovery looks like before you commit.

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.

DISCOVERY10 business days. A fixed price for Tier A or B. Five written outputs and one recommendation.You keep the outputs, whatever you decide next.

Meet Musterwerk

An example company you may recognise

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.

IndustryDrive components and gearboxes for machine builders
LocationBaden-Württemberg, one plant, one warehouse
People140 employees, family-owned, second generation
IT teamHead of IT and one administrator; no in-house developers
ERPAuftragsPlanerCustomer portalNightly syncEDI linkShop-floor dataFile serverDocument archiveQuality systemHR and payrollDrive and SheetsExcel workbooksShared mailboxes
Core business systemCustom-built softwareCloud serviceSpreadsheets and documentsIntegration

Choose a situation

Which situation sounds like yours?

Each situation follows the same method and ends differently, because the recommendation follows the evidence.

The journey

Six steps from a first call to a clear decision

01

First conversation

About an hour. We understand the pressure, who decides, and what access is realistic.

02

Before we start

Agreement, NDA, access tier, and a readiness check that protects your systems.

03

Ten business days

Interviews, inspection, and analysis. Your team's time is concentrated in a few short sessions.

04

Five outputs

Inventory, handbook, assessment, roadmap, and project definition, every statement labelled with its evidence.

05

One recommendation

Managed services, modernization, a new product, or a clear reason not to proceed.

06

The next step, if you want it

The outputs become the starting point of the engagement, or your own team's plan.

Access tiers

You decide how much access to grant

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.

TIER A

Context-led

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.

TIER B

Read-only technical inspection

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.

TIER C

Broader validated inspection

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

Five outputs you can act on

Written so that your own team, or any partner, can work from them.

See the examples
01

System inventory

Every system in the agreed scope, with its owner, purpose, dependencies, and the source of each fact.

02

Systems handbook

How the system is built, released, and operated, its dependencies, known risks, and knowledge gaps.

03

Technical assessment

What we examined, what we found, how serious each finding is and why, what we could not examine, and the controls we recommend.

04

Outcome roadmap

Prioritized outcomes, options, dependencies, and the decisions you will need to make. No promised dates.

05

Project definition

For the recommended next step: scope, team, schedule, acceptance checks, your responsibilities, commercial basis, risks, and open decisions.

After Discovery

Four ways a Discovery can end

The recommendation follows the evidence. You decide what to do with it.

01

Application Managed Services

The system should keep running, and someone accountable needs to operate it and make small, controlled changes.

02

Modernization

A specific part of the system needs to change: an upgrade, a refactor, a new platform, or a selective replacement.

03

New product development

The evidence shows a new system or a new capability is the better answer than changing the old one.

04

A clear recommendation not to proceed

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

Agreed in writing before we start

Duration
10 business days, starting with a readiness check: access works, the right people are available, and the scope is clear.
Price
A fixed price for access Tier A or B, agreed in writing before we start. Tier C is scoped and quoted separately.
You receive
Five written outputs: system inventory, systems handbook, technical assessment, outcome roadmap, and a project definition for the recommended next step.
Then
One recommendation, with the evidence behind it. Continuing with us is optional, and you keep the outputs either way.

The first step

Start by understanding your system.

Three short answers are enough to begin. We reply with a first conversation to confirm the scope.

Start with Discovery