The wrong passage reaches the model
Chunking ignores document structure, keyword search is missing, and nothing reranks. No prompt fixes missing evidence.
I build retrieval systems that cite sources, refuse when the evidence is weak, and pass a measurable evaluation — in 14 days.
Three failure modes account for most RAG projects that never make it to production.
Chunking ignores document structure, keyword search is missing, and nothing reranks. No prompt fixes missing evidence.
Without a golden question set and retrieval metrics, quality is judged by vibes. Degradation goes unnoticed until users complain.
In legal, compliance, and finance, an unsupported answer is a liability. The system must cite — and refuse when it can't.
Fixed scope. Measurable acceptance test. You own the code and the evaluation.
Document audit, retrieval requirements, and the questions your system must answer correctly. We define "done" before writing code.
Parsing, metadata-aware chunking, embeddings, and a vector index. Structure preserved (act, section, page) so retrieval can filter.
Hybrid search (dense + keyword), reranking, and metadata filters. Measured with recall@k and MRR, not intuition.
Prompt design, citation mapping, and refusal behavior when evidence is weak. No unsupported claims.
A golden set your team can re-run. Retrieval hit rate, faithfulness, latency, and cost per query — in one report.
Dockerized FastAPI service, docs, and a recorded walkthrough. You can run it without me.
A domain-specific assistant that answers questions over statutes and case law with citations. Built on a fine-tuned Mistral-7B and a hybrid retrieval pipeline, with refusal behavior for unsupported questions.
A dependency-free evaluation harness for retrieval pipelines. Measure recall@k, precision@k, MRR, and nDCG on your own corpus — before and after every change.
python -m rag_eval.cli --corpus data/corpus.jsonl --queries data/queries.jsonl
Every engagement begins with a paid, fixed-scope audit so we both know what "working" means.
3 days · credited toward the build
14 days · fixed scope
Fine-tuning sprints ($1,500+) and monthly retainers ($1,500+/mo) available after the audit.
No, and you should be suspicious of anyone who does. I guarantee a measured system: we define the evaluation set together and you see exactly where it fails before scaling it.
That's common, and it's usually an evaluation problem. Nobody defined what "correct" meant, so retrieval degradation went unnoticed. The audit rebuilds the eval set from your real questions and shows whether it's fixable in a week or needs a redesign.
For public information, you can. The moment the answer must come from your private documents, with citations, and without hallucinating, you need retrieval you control.
A sample of real documents, the questions your team actually asks, and one technical contact. Everything else I handle.
Yes. Send yours over; work starts after it's signed.
I'll tell you why it's happening and what I'd test first — whether we work together or not. No pitch deck.