02Service
RAG & custom AI chatbots
Chatbots and assistants that answer from your own documents, show where each answer came from, and say so when they don't know.
The short answer
Updated
RAG (retrieval-augmented generation) is how a chatbot answers from your own content. It searches your documents first, then the model answers using only what it found, with a link to the source. I build RAG chatbots for support, sales and internal teams, usually in 3 to 6 weeks for $6k to $20k.
- Typical budget
- $6k to $20k
- Timeline
- 3 to 6 weeks to production
- How it's quoted
- You get a fixed quote after the first call. Model, vector database and hosting costs are separate.
A chatbot that knows your business, and admits when it doesn't.
Most chatbot complaints come down to two things. It made something up, or it couldn't find an answer that was sitting in a PDF the whole time. Both are search problems, not model problems.
So most of the work goes into the unglamorous layer: cleaning and splitting your documents, searching them well, checking who's allowed to see what, and testing answers against the questions people actually ask. The model is the easy part.
A good fit if
- Your support team answers the same fifty questions every week
- Your docs, policies or contracts are spread across drives and tools
- You tried a chatbot plugin and it made things up
- Different people should get different answers, based on their access
What you get
- 01
Content that stays current
Your PDFs, docs, help centre, tickets or database, parsed, split and indexed, then re-synced when they change.
- 02
Search that finds the right passage
Keyword and vector search together, with a reranker, tuned on your real questions instead of left on defaults.
- 03
Answers with sources
Every answer links to the passage it came from. If nothing relevant turns up, it says so and hands over to a person.
- 04
A test set and a dashboard
Real questions with known good answers, re-run before every change, plus a view of what people ask and where it struggles.
How a project runs
Week 1
Audit
What content exists, who can see what, and the questions people ask most.
Weeks 2 to 3
Index and prototype
Your content indexed and a working chatbot, tried by a few people on your team.
Weeks 4 to 6
Production
Sign-in, permissions, the chat widget or integration, monitoring and launch.
Ongoing
Improve
Fix the questions it misses and tune the search, each change checked against the test set.
- OpenAI
- Claude
- Embeddings
- pgvector
- Pinecone
- Qdrant
- Hybrid search
- Rerankers
- LlamaIndex
- LangChain
- Document parsing
- Next.js
- Python
Related work
- File 002AI agentsIn beta
Altrun
An AI assistant that turns incoming signals into scheduled actions- Role
- Founder, engineer
- Year
- 2026
- Stack
- LLM tool calling, Agentic workflows, Telegram Bot API
- File 004Customer messagingLive
Name withheld under NDA
Name withheld under NDA- Role
- Lead engineer
- Year
- 2024
- Stack
- WhatsApp Business API, Node.js, React
Questions people ask
What is RAG, in plain terms?
The chatbot looks things up before it answers. It searches your content for the relevant passages, hands only those to the model, and the model writes the answer from them, with a link to the source.
Should we use RAG or fine-tuning?
For answering from your own content, RAG almost every time. It stays current when documents change, shows its sources and costs far less. Fine-tuning is for teaching a style or a narrow task, not facts.
Where can the chatbot live?
On your website, inside your app, in Slack or Teams, on WhatsApp, or behind an API that your own product calls.
How do you stop it making things up?
It only answers from the passages it found, it cites them, and it's tested on questions where the right answer is "I don't know". Those tests run before every release.
How much does a RAG chatbot cost?
Usually $6k to $20k to build. One clean source, like a help centre, sits at the low end. Several sources, per-user permissions or scanned documents push it up. Running costs are usually a small monthly bill for the model and the vector database.
How long does it take?
3 to 6 weeks to production. You can try a prototype on your own content after about two weeks.
What do you need from us to start?
Access to the content it should answer from, a list of the questions people ask most, and someone who can tell whether an answer is right.
Further reading
Related services
Contact
Tell me what you're trying to fix.
I read every message myself and usually reply the same day. A rough idea is enough to start.
Or send a short briefHours
Your hours work for me.
San Francisco
--:--
New York
--:--
London
--:--
Berlin
--:--
Dubai
--:--
Singapore
--:--
Sydney
--:--
Surat
--:--
Me
I keep flexible hours and move my day to overlap with yours, whether that's a morning standup in New York or a late release in Sydney.