From six hours to seconds. Enterprise RAG for a leading international US tax advisory firm.
Their advisors lived inside a document retrieval problem — FATCA, FBAR, treaty law, and multi-jurisdictional guidance scattered across shared drives, a legacy DMS, and email archives. Sphere built a jurisdiction-aware enterprise RAG system that solved it in five weeks.
If you only read one box.
A leading international US tax advisory firm — serving American expatriates and corporations from its European headquarters across offices in Europe, Asia, and the Middle East — was drowning in its own knowledge. Regulatory publications, client case archives, advisory memos, IRS guidance, and treaty documents lived in a fragmented ecosystem of shared drives, a legacy document management system, and email.
The fix wasn't a better folder structure. Sphere built a production enterprise RAG system: a custom ingestion pipeline, hybrid vector + keyword retrieval with jurisdiction-aware metadata filtering, rigorous pre-production evaluation benchmarks, role-based access control, and a tamper-evident audit trail — designed in, not bolted on.
The result: document research that took advisors an average of six hours per engagement now takes seconds, retrieval accuracy improved by 66%, and the whole system reached production in five weeks.
Same advisors. Same knowledge base. A completely different working day.
An advisor needs the current treatment of a foreign trust reporting question spanning two jurisdictions.
Keyword search across a legacy DMS, shared drives, and old email threads. Cross-checking IRS guidance against treaty documents by hand. Average: six hours per engagement.
One natural-language query. Hybrid retrieval surfaces the governing guidance, prior memos, and relevant precedent — with citations — in seconds.
A junior advisor takes on a complex cross-border engagement type they've never handled.
Institutional knowledge lives in senior partners' heads and 15 years of unindexed engagement files. Junior staff escalate, wait, or reinvent the research.
Junior advisors query the same institutional knowledge as senior partners — scoped by role-based access control, so client-specific records never leak across engagement teams.
A regulator or professional review later asks how an AI-assisted research conclusion was reached.
Generic AI tools produce answers with no provenance. In a regulated advisory environment, an uncited answer is an unusable answer.
Every query, retrieval event, and generated response is logged in a tamper-evident audit trail — source documents, cited chunks, and synthesis, all on the record.
The firm's most valuable asset was also its least accessible.
The client is a leading US tax advisory practice for Americans abroad. Their team of CPAs and IRS Enrolled Agents guides clients — from individual expatriates to multinational corporations — through the most complex intersections of US federal tax law, local tax rules in their operating jurisdictions, and international treaty obligations. Every engagement touches FATCA, FBAR, Form 5471, FIRPTA, bilateral estate tax treaties, streamlined filing procedures, and a dense web of IRS guidance that changes regularly across multiple jurisdictions.
As the firm expanded from its European headquarters into additional financial centers across Europe, Asia, and the Middle East, so did the volume and complexity of the knowledge it needed to manage. Regulatory publications, client case archives, internal advisory memos, IRS announcements, OECD treaty documents, regional tax guidance, and prior engagement records had accumulated across a fragmented ecosystem of shared drives, a legacy document management system, and email archives.
The cost was concrete: advisors spent an average of six hours per engagement on document research alone — time billed against margins, not against insight.
Discovery first. Architecture second. No stack proposed before the failure modes were understood.
Sphere began with a structured discovery process rather than immediately proposing a technology stack. Understanding the specific failure modes of the firm's existing retrieval workflows — and the compliance sensitivity of the data involved — was a prerequisite to designing a system that would actually work in a regulated professional services environment.
- Knowledge source mapping.Sphere inventoried every repository in the firm's ecosystem: IRS publications and revenue rulings, OECD treaty documentation, regional tax guidance, internal advisory memos, client case archives, engagement letters, and research from prior matters — mapping sensitivity and access requirements for each source type.
- Custom ingestion pipeline. Domain-optimized chunking and multi-jurisdiction document classification, tuned to how tax guidance is actually structured and cited.
- Hybrid retrieval architecture. Vector + keyword search fused with semantic reranking and jurisdiction-aware metadata filtering, so a query about one jurisdiction never surfaces guidance governing another.
- Role-based access control from the architecture stage. Advisors retrieve only within their authorization scope; client-specific records never surface in cross-advisor queries.
- Tamper-evident audit trail.Every query, retrieval event, and generated response logged — source documents, cited chunks, and synthesis — giving the firm's leadership full visibility and an evidentiary record for any engagement subject to later professional review.
No interface shipped before the retrieval benchmarks passed.
Before deploying any interface, Sphere ran structured RAG evaluation benchmarks across four dimensions: retrieval precision, retrieval recall, answer faithfulness (whether the generated response was grounded in the retrieved documents), and answer relevancy(whether the response actually addressed the advisor's query).
Each milestone carried a quantitative pass/fail threshold before the build progressed. The result of that discipline: retrieval accuracy improved by 66%over the firm's previous keyword-based search — measured, not asserted — and the system went from kickoff to production in five weeks.
The impact of collapsing per-engagement research from six hours to seconds compounds rapidly across a professional services firm. Advisors take on more engagements without added headcount. Junior advisors access the same depth of institutional knowledge as senior partners. And the firm's multi-market expansion runs on a knowledge base that travels with the business — not expertise that stays at headquarters.
“Sphere deployed a production-ready RAG pipeline in five weeks. Document retrieval accuracy improved by 66% compared to our previous keyword-based search. Most strikingly, the time our advisors spend on document research dropped from an average of six hours per engagement to seconds. Sphere understood that responsible AI means the governance layer is designed in — not added later.”
Managing Partner, international US tax advisory firmName and firm withheld at the client's request · quote verified by Sphere
Capabilities delivered
Enterprise RAG in regulated professional services
Why is the client anonymized in this case study?
What is enterprise RAG, and how is it different from keyword search?
How long does it take to deploy a production-ready enterprise RAG system?
Can enterprise RAG be deployed securely for compliance-sensitive client data?
How was the “six hours to seconds” result measured?
Can Sphere build something similar for our firm?
Your firm's knowledge should answer in seconds, not hours.
Sphere will scope the ingestion pipeline, retrieval architecture, governance layer, and evaluation plan for your knowledge base — and show you exactly how the build runs — in 30 minutes.