I will build a production rag pipeline over your business knowledge

G
granqpint
G
granqpint
Ehsan

About this gig

RAG demos are easy. RAG that survives real questions is not.

I build retrieval pipelines that hold up when a real user asks something awkward: hybrid retrieval (vector plus keyword), a reranking stage, chunking designed around your document shape rather than a fixed token count, and an evaluation set so you can prove accuracy instead of hoping for it.

What you get:

- Ingestion for your real sources: PDFs, docs, sheets, websites, database tables, support tickets

- Cleaning and one canonical document representation, the step most pipelines skip

- Hybrid retrieval plus cross-encoder reranking, tuned against your own questions

- A golden question set with scored results, so a regression is visible before your users find it

- Grounded generation with citations back to the source chunk

- Deployed as an API you own, or straight into your existing app

I run this on a production multi-tenant system, including the unglamorous parts: re-indexing when content changes, cost per query, latency budgets and failover lanes.

Tell me what your documents are and what people need to ask them.

Get to know Ehsan

Ehsan

AI Agent and RAG Engineer

  • FromIndia
  • Member sinceJun 2024
  • Avg. response time1 hour
  • Languages

    English
I build AI agents that answer from your business, not from guesswork. My focus is retrieval - RAG: getting your catalogue, docs and policies into a pipeline the agent can be held to, so it cites real sources and escalates what it cannot ground. I run a multi-tenant agent platform in production, so I work on the unglamorous parts daily: re-indexing, evals, cost per query, human handoff. Typical work: WhatsApp and website support agents, internal knowledge assistants, custom tool-using agents, and audits of RAG systems that fail in production. I say so when an agent is the wrong tool.