Skip to content
Amygdal

RAG development that gives grounded, cited answers

Retrieval-augmented generation lets a language model answer from your knowledge — contracts, manuals, tickets, BIM models, clinical guidelines — instead of from memory. The hard part is not the demo; it is retrieval quality, permissions and knowing when the answer is wrong. That is the part we engineer.

What we deliver

Typical use cases

  • Internal knowledge assistants for policies, processes and wikis
  • Customer support answers grounded in product documentation
  • Contract, tender and compliance document review
  • Natural-language questions over BIM and engineering data
  • Clinical guideline and protocol lookup for care teams

Technology we use

  • OpenAI
  • Ollama
  • Python
  • PostgreSQL
  • Elasticsearch
  • Weaviate

How we work

  1. 01

    Discover

    We learn the business, the users and the constraints, and agree what success looks like.

  2. 02

    Prove

    We test the riskiest assumption first — a prototype or AI proof of concept — before scaling the team.

  3. 03

    Build

    Short iterations, working software every two weeks and demos you can click through.

  4. 04

    Run

    Launch, monitoring and continued development — or a clean handover to your team.

Related work

Frequently asked questions

What is RAG development?

RAG development is building systems where a language model first retrieves relevant passages from your own data and then answers using them. It keeps answers current and traceable without retraining a model.

Which vector database do you use?

It depends on scale and your stack. PostgreSQL with pgvector covers many projects; Elasticsearch, OpenSearch or Weaviate suit larger or search-heavy ones. We pick what you can operate.

How do you stop hallucinations?

You reduce them rather than eliminate them: better retrieval, answers constrained to cited sources, refusal when evidence is missing, and an evaluation set that catches regressions before users do.

Can RAG respect our document permissions?

Yes. We carry permissions from the source systems into the index and filter at query time, so the model never sees content the user cannot access.

Further reading

Let's talk about your project

Send us a short description and we will come back with questions, a rough plan and a team.

Email us