Check first, then build.
AI projects rarely fail because of the model. They fail because of data, interfaces, or a task nobody made measurable. That is why every project starts with a check on real data and ends with a system measured against criteria agreed beforehand.
From use case to running system
- 01
Check
In the Readiness Check we examine the use case on your real data: state of the data, interfaces, deployment path, measurability. It ends with a written verdict — build or don’t. A reasoned “don’t build this” is a legitimate result.
- 02
Build
We build in weekly steps, each with working software. What “done” means is fixed beforehand: thresholds on a frozen test dataset. The evaluation runs before acceptance and as a regression test after every change.
- 03
Hand over
We put the system into operation on your infrastructure and hand over source code, documentation and reproducible deployment into your repositories. You run it yourself afterwards, or we keep looking after it.
A report you can base a budget decision on
A document with six chapters that management can read and IT can recalculate.
“Done” is a measurement, not a feeling
An AI system does not return the same answer every time. So before the build we agree not on an output but on a threshold over a frozen test dataset. A criteria sheet can look like this:
test_dataset: size: 200 reference questions from the department state: frozen before project start criteria: source_correct: >= 90 % # answer names the right source answer_without_evidence: 0 # rather “not found” than guessed access_rights_violated: 0 response_time_p95: <= 4 s measurement: before acceptance and after every update
The values are an example. Criteria and thresholds are set together for each project.
Questions about a project?
Lukas Friedrich answers questions about how we work personally.