Europe 2026
How to Leverage Domain Expertise — Chris Lovejoy, Notius Labs
Overview
This talk argues that building successful vertical AI products is fundamentally an organizational challenge, not solely a technical one. The core thesis is that effectively integrating domain expertise into AI development processes is more critical than the sophistication of the AI models themselves. The speaker proposes a framework for structuring organizations around domain experts, enabling them to contribute at different levels, from direct input to system design, ultimately leading to more differentiated and effective AI products.
Who should watch
- AI Engineers
- Product Managers
- Builders of vertical AI products
- Those struggling with the last-mile problem in AI product development
- Organizations aiming to bake domain expertise into their AI systems
Key takeaways
- Winning in vertical AI is an organizational problem, requiring a system for incorporating domain insights.
- Domain experts can be leveraged in three primary roles: Oracle (directly embedding expertise), Evaluator (defining and measuring quality), and Architect (designing self-improving systems).
- The choice of role depends on whether performance is objectively measurable and if manual iteration is sufficiently fast.
- Starting as an Oracle is common, with potential evolution to Evaluator or Architect as the product and organization scale.
- Key mistakes include not hiring domain experts, hiring the wrong type, or not integrating them effectively into the organization.
- A principal domain expert should be appointed early, with clear accountability for AI quality and decision-making.
- Domain experts need ownership and should be involved in key decisions to help build differentiated products.
- Hiring for breadth of skills, including domain expertise and adjacent technical or analytical skills, is crucial.
Notable quotes
*Winning in vertical AI is an organizational problem.*
*The system for incorporating domain insights is more important than the sophistication of your models.*
Unofficial community note. Prefer the recording for nuance.