The core ideaA useful chatbot is a grounded chatbot
The single thing that separates an AI chatbot worth having from one that damages trust is grounding. A generic assistant answers from the model's general training and will state things about your prices, policies, or products with total confidence and no basis. In a customer-facing setting that is not a quirk, it is a liability.
We build assistants that retrieve from your real data using retrieval-augmented generation, so every answer is anchored to your actual content. The model handles language; your data decides the facts. That is the difference between a helpful assistant and an expensive way to give wrong answers.
It is also why the choice of model matters less than most people assume. A strong model grounded in good data beats a stronger model guessing every time.
What it can beSupport, internal knowledge, or a product feature
AI chatbots earn their place in a few clear shapes: customer-facing support that answers from your real documentation, internal assistants that let a team query scattered knowledge in plain language, and in-product features that make a large catalogue or dataset searchable conversationally.
We help you decide which of these is actually worth building, and which is a distraction. The strongest use cases share a trait: a real body of data the assistant can be grounded in, and a genuine cost to people not getting quick, accurate answers from it.
The buildProduction stack, fixed price, owned outright
We build on a modern production stack with a proper retrieval layer, deployed properly, using leading models including Claude. It is the same foundation we build our own products on, chosen because it is genuinely good rather than because it is cheap or trendy.
A focused chatbot grounded in your data is from £30,000, fixed. Assistants that pull from several data sources, plug into your systems and complete tasks typically land between £45,000 and £75,000. We agree the price and scope before building, and model inference is passed through at cost.
You own your data and the custom deliverables agreed in your contract. Reusable components and third-party software retain their licences. The proposal specifies any retained IP, licensing, hosting and exit terms before work starts.