01
Describe search from the user’s perspective
Collect typical questions, hard cases and useful answers; phrase expectations so they can be tested.
Workshop / Search & Retrieval
We translate your search problem into concrete questions and comparison criteria. The result is a well-founded architectural approach: Where is lexical search enough? Where does semantic context help? Which relationships would need to be explicit for a graph?
Who it’s for
For search, data and AI teams as well as business owners with a concrete search or retrieval task.
Content framework
We tailor the focus and technical depth to your question.
01
Collect typical questions, hard cases and useful answers; phrase expectations so they can be tested.
02
Examine which terms, meanings or relationships an answer requires and which data is available for it.
03
Narrow down candidates, define quality checks and sensibly scope the next technical experiment.

If possible, bring typical search queries and approved sample content. Whether a hands-on search comparison is part of the workshop depends on your data and existing infrastructure.
The listed deliverables define the intended scope of work. Scope and technical exercises are set out in the proposal before the workshop.
How I work
This simplified example shows how sources and follow-up questions narrow down an answer. It is not a search benchmark and not a performance comparison of BM25, vector and graph search. We assess the right approach based on your questions and data.
Explore the workflow with curated, fictional sample data, fully local and without a live LLM.
The example answer is ready.
Knowledge question · retrieval architecture · conceptual
02 / Retrieve sources in parallel
Example text on semantic search and context-based answers.
Document → product → version → responsible team.
Not needed for this question
Not needed for this question
Combine relevant results and make the limits of the answer visible.
Vector search can find passages with similar content. A knowledge graph adds explicit relationships, for example between document, product and version. That can help narrow down the right context. The benefit depends on modeling and data quality; a graph does not guarantee a correct answer.
What would this look like with your documents? In the Machine-Readability Check, we examine your knowledge foundation and the next steps.
Request a workshop proposal →Before you inquire
1 day from €6,500 / 2 days from €12,500 plus VAT. All fees plus VAT. The exact scope of work is set out in the proposal.
Depending on the topic, you get a use case canvas with a roadmap, a first graph model with a validation brief, or a state diagram with evaluation cases and a prototype scope. Each topic page lists its deliverables.
Both formats are possible. Working mode, technical requirements and scope are tailored to your team.
For the Machine-Readability Check, the setup is the head of IT plus two to three business unit leads. All other topic workshops are designed for up to eight participants.
No. We can start with a narrowly scoped domain, existing documents or a specific process. The starting point depends on where you are today.
These tools are not required for conceptual work. Whether a hands-on technical exercise makes sense, and what access it needs, is clarified in advance.
Please do not send confidential documents with your first inquiry. Access, suitable examples and any required non-disclosure agreement are settled before we start working together.
Yes. I speak fluent English. All offerings and intro calls are available in German and English.

Your next step
If possible, bring typical search queries and approved sample content. Whether a hands-on search comparison is part of the workshop depends on your data and existing infrastructure.
Tell me about your audience or team, your question and a preferred date. On that basis, we clarify format and scope.
See the keynote on this topic