Reference architectureKnowledge system

Answer engine over internal documents

01 — The problem
The answer exists — in a policy PDF, a past thread, a spreadsheet nobody owns. Finding it takes longer than the task, so people guess, and the guesses differ.
02 — What we built
Documents are chunked, embedded and indexed with their source and recency preserved. Retrieval is tuned and evaluated against real questions, and every answer cites the document it came from so it can be checked.
03 — What changed
Staff get a cited answer in seconds, and the cases where the system does not know are visible instead of invented.

Technology

Built with

  • Vector database
  • Embeddings
  • Reranking
  • Citations
  • Evaluation set
Related

Nearby work.

All work
  • Associated companyKnowledge system

    Answer engine over 6.9M tax passages

    A production answer engine we built and run for tax and accounting questions, searching about 6.9 million indexed passages.

    • Qdrant
    • Embeddings
    • Reranking
    • Hybrid search
  • Reference architectureAI agent

    Inbound qualification system

    Sales opens a ranked, enriched list instead of an inbox, and every enquiry is answered — including the ones that used to fall through.

    • LLM agent
    • CRM API
    • Enrichment
    • Queue
  • Reference architectureDocument automation

    Document-to-ledger pipeline

    The routine majority posts without a human. Finance spends its time on genuine exceptions instead of on data entry.

    • Vision + OCR
    • Extraction
    • Rules engine
    • Accounting API

Have a problem shaped like this one?

Tell us what the process looks like today, and we'll show you what the built version does differently.