- What is search relevance consulting?
- Helping a team improve how well its search, retrieval and ranking systems match results to what users want. That covers how queries are understood, how results are retrieved and ordered, how fast they return, and how quality is measured.
- Do you work on RAG and AI assistants as well as classic search?
- The same questions apply: what the user means, what gets retrieved, and how you measure quality. We look at the retrieval layer that feeds the answer, because a generated answer can only be as good as what was retrieved.
- How does an engagement start?
- With a 30-minute conversation. If it fits, the usual first step is a two-week Architecture Sprint, which ends with a roadmap, a working proof of concept and a go/no-go recommendation.
- Which search and retrieval technologies do you work with?
- We have worked with Elasticsearch, Lucene, two-tower retrieval models and RAG pipelines, in prior roles and in consulting work. We choose the approach that fits your data and latency budget, and we assess what you already run before recommending changes.
- Do we need to replace our current search system?
- Not necessarily. The Architecture Sprint starts by assessing what you have, including a data audit and readiness assessment, and ends with a recommendation on what to change and what to keep.
- How do you measure whether relevance improved?
- With offline metrics, online experiments and human review, chosen to match what users value in your product. Accuracy alone is rarely the right measure, so defining the metric that tracks user satisfaction is part of the work.
- Who owns the work?
- You do. You receive the complete codebase, trained models and documentation, with zero lock-in. See How We Work for details.