RAG Chatbot on Custom Knowledge Base
A retrieval-augmented chatbot that finds the relevant passages by vector search and answers from them, citing the source document.
A short, evidence-led assessment of your processes and data, ending in a ranked list of options, including the ones where AI is not the right answer.
Indicative starting price: $4,999 (USD). Final price depends on scope.
A pilot is narrow and has a decision at the end of each stage. We stop if the stage's exit criterion is not met.
Collect a slice of your real data, clean it and set aside examples to test against.
Build the smallest approach that could work, and test it on the held-back examples.
Run it on live work with a person checking the output, especially uncertain cases.
Track accuracy, collect corrected cases and decide whether to extend, retrain or stop.
Each phase has an input from you and a written output from us. Building the pilot itself is a separate engagement.
| Phase | What happens | You provide | You receive |
|---|---|---|---|
| Step 1Review | Listen to where time and money go. List candidate processes and check what data exists behind each. | A few hours with process owners; examples of the data. | A candidate list with notes on data readiness. |
| Step 2Score and shortlist | Score each candidate on impact, effort, data readiness and risk, including privacy. | Input on business priorities. | A ranked shortlist, including options where AI is not the answer. |
| Step 3Recommend | Choose a first pilot and define the measure that will decide whether it worked. | Agreement on the success measure. | A written recommendation. |
| Step 4Plan the pilot | Scope a narrow pilot on a slice of your data with a person reviewing the output. | Confirmation of the data slice and reviewer. | A pilot plan with go/no-go criteria. |
Anonymised client projects. Client names are withheld because of confidentiality; the project page explains each one.
A retrieval-augmented chatbot that finds the relevant passages by vector search and answers from them, citing the source document.
Practical articles from the engineers on this topic.
Forget the headline-grabbing demos. The changes that are reaching ordinary businesses this year are narrower, cheaper and less glamorous than the coverage suggests. Here is what looks durable, …
Yes. We have built OCR-based extraction pipelines that validate fields against business rules, send mismatches to a person for review and keep an audit trail.
No. The assessment itself shows what is ready and what is not. We start from one measurable problem and a slice of your data.
With a fixed set of real questions, including ones that have no answer in your documents. We score retrieval and answers separately and agree a pass threshold before launch.
No. Where a rule, a report or a simple automation does the job, we say so. AI is used where it earns its place.
A narrow use case running on a slice of your real data, with a person reviewing the output, so you can judge accuracy before committing further.
The 'starting at' figure is indicative. After a short discovery conversation we share a written scope and an estimate based on what the project actually involves.
This is agreed in writing before work starts. Our default is that you own what we build for you, and that your data stays in systems you control.
Tell us which processes cost the most time. We will give you an honest view of where AI will and will not help.