01
From documents to connections
Why a collection of texts is not yet an explicit model of enterprise knowledge.
Keynote / Knowledge Architecture
Knowledge unfolds its value in the connections.
What knowledge graphs can do for enterprise AI, where Neo4j fits into the architecture, and when a graph actually makes more sense than other approaches.
45–60 minGerman / EnglishFee from €6,500 plus VAT and travel
Who it’s for
Who this keynote is for.
For technology leaders, architects, and teams in knowledge management and AI product development.
What your audience takes away.
- A clear picture of entities, relationships and context in enterprise knowledge.
- Orientation on graphs, vector search and how they can be combined.
- Criteria for deciding whether a knowledge graph fits your problem.
Content framework
Three perspectives on the topic.
We tailor the focus and technical depth to your question.
02
Graphs in the AI system
How relationships can support retrieval, and the role data quality and modeling play.
03
A sensible starting point
Start with a clear question and consider model, maintenance and value together.
How I work
How relationships sharpen context.
Retrieval in action
Explore the workflow with curated, fictional sample data, fully local and without a live LLM.
- 1Classify
- 2Retrieve sources
- 3Combine
- 4Answer
The example answer is ready.
01 / Classification
Knowledge question · retrieval architecture · conceptual
02 / Retrieve sources in parallel
Vector search
Matching text passagesExample text on semantic search and context-based answers.
Knowledge graph
Entities & relationshipsDocument → product → version → responsible team.
Problem-solution graph
Linked solution pathsNot needed for this question
Structured data
Versions & statusNot needed for this question
03 / Synthesis
Combine relevant results and make the limits of the answer visible.
04 / Answer with sources
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.
- Vector search
- Knowledge graph
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
Frequently asked questions.
How long is a keynote?
The keynote format runs 45–60 minutes. Alternatives within the offering are a 20-minute talk, a 90-minute deep dive with Q&A, or a panel by arrangement.
What does the keynote cost?
Fee from €6,500 plus VAT and travel. International €8,500–12,000 plus VAT. All fees plus VAT.
In which languages can you give the talk?
I speak fluent English. All offerings and intro calls are available in German and English.
Can the keynote be delivered remotely?
Yes. Keynotes are available on-site and remotely; just mention your preferred setting in your inquiry.
How technical is the talk?
The focus depends on the audience. Leadership teams get a strategic perspective; technical teams can go deeper into retrieval, graphs and agentic workflows.
Do we need Neo4j or LangGraph in-house?
No. The talks explain architectural principles. Neo4j and LangGraph serve as concrete examples; you do not need to use these tools already.
What do you need for an inquiry?
Helpful details are your preferred date, venue or setting, audience and size, topic, and the language you want. Availability is checked case by case.
Your next step
Agree on date and focus.
The talk can be designed as a strategic introduction or with a stronger focus on architecture and Neo4j.
Tell me about your audience or team, your question and a preferred date. On that basis, we clarify format and scope.
See the workshop on this topic