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
- Python
Each item says what it actually is — a client system, a live system we built and run, or an architecture we build repeatedly — so nothing here can be read as more than it is.
How to read this page
A client is named only where that client has approved it in writing. Where you see no name, there is no name to see — not a redaction. Figures are measurements we can show you the method for, and there are none we cannot.
Longer case studies, with the engineering written out and — where we have one — a walkthrough of the build.
A production answer engine we built and run for tax and accounting questions, searching about 6.9 million indexed passages.
Open any of them for the problem, what we built, the engineering decisions worth defending, and what changed as a result.
Sales opens a ranked, enriched list instead of an inbox, and every enquiry is answered — including the ones that used to fall through.
The routine majority posts without a human. Finance spends its time on genuine exceptions instead of on data entry.
Staff get a cited answer in seconds, and the cases where the system does not know are visible instead of invented.
One source of truth with roles, history and reporting — and a system the business owns and can extend.
What these are built from
We introduce references directly, on request, once a project is serious enough that it's a fair use of their time. That is a more useful signal than a testimonial we wrote ourselves.
Tell us, and we'll walk you through what the version built for you would look like.