Case Studies › Knowledge Search

Internal Knowledge Search

How a 150-person accounting firm gave every employee a research assistant that never phones home.

Solstice Financial | 150 staff, 400+ clients | Mac Studio M3 Ultra 512GB

The firm

Solstice Financial is an accounting and advisory firm with 150 staff across two offices. They advise 400+ clients on tax, audit, corporate finance, and advisory work.

Their internal knowledge is vast — 15 years of engagement files, tax research notes, client histories, precedent documents, internal policies, and regulatory briefings. It's all stored on a shared drive and in their document management system.

Nobody can find anything.

The problem

When a junior accountant needs to know:

...they have three options:

  1. Search the shared drive. Type keywords into Windows search. Get 400 results, most of which are irrelevant. Open five documents. Find what they need in the third one, 25 minutes later. Or don't find it at all.
  2. Ask a senior colleague. The senior colleague spends 10 minutes explaining something they've explained six times before. The junior accountant takes notes. The notes get lost.
  3. Google it. Get generic guidance that doesn't reflect the firm's specific experience or client base. Risk acting on outdated information.

The real problem isn't search — it's that the firm's collective knowledge is locked in documents that humans can't efficiently navigate.

And there's a new complication: the firm's partners have said no to using ChatGPT or similar tools for internal research. Not because they're anti-AI — because client financial data, tax strategies, and advisory work product can't go through a third-party API. The ICO would have questions. The clients would have concerns. The professional indemnity insurers would have opinions.

The cost:

What Foundry does

Foundry runs on a Mac Studio in the firm's server cupboard (it doesn't need a rack — it sits on a shelf). It's plugged into the firm's network and has read access to the document management system.

It reads everything, understands it, and answers questions — locally.

Here's what that means in practice:

  1. Foundry indexes the firm's document collection — every engagement file, research note, policy document, and precedent. Not by keywords. By meaning. It understands that a document about "capital allowances for solar panels" is relevant when someone asks about "renewable energy tax relief."
  2. When someone asks a question, Foundry searches the indexed content, finds the most relevant passages, and writes a clear answer in plain English — with citations to the specific documents and page numbers it drew from.
  3. Nothing leaves the building. The question is processed on the Mac Studio. The answer is generated on the Mac Studio. The documents stay on the firm's network. No API calls, no cloud processing, no third-party seeing client data.
  4. It learns the firm's vocabulary. When someone asks about "the Henderson matter," Foundry knows that refers to the 2024 acquisition advisory engagement for Henderson Dental Group. It picks up the firm's internal language over time.

What it looks like day to day

Tuesday, 10:15 AM

A junior accountant, Priya, is working on an R&D tax credit claim for a software company. She's never done one before.

She types into the Foundry search bar: "R&D tax credits for software development — have we done this before?"

Foundry responds in 3 seconds:

Yes. The firm has handled 7 R&D tax credit claims for software companies since 2022.

Most relevant: The 2024 claim for BrightStream Ltd (engagement file 2024-0341) involved similar circumstances — a SaaS company claiming for backend algorithm development. The senior on that engagement was Michael Chen. Key precedent: HMRC accepted that server optimisation algorithms qualified, but frontend UI work did not.

Internal guidance note: "R&D Tax Credits — Software Sector" (April 2024, Policy Team)

Relevant documents:
- BrightStream R&D claim summary (2024-0341, p. 12-18)
- HMRC correspondence — BrightStream (2024-0341, p. 31-34)
- Internal R&D software sector guidance (Research Notes, April 2024)

Priya reads the BrightStream summary, finds the exact approach the firm used, and adapts it for her client. She books a 15-minute call with Michael Chen to confirm her approach rather than a 2-hour "start from scratch" meeting.

Wednesday, 2:30 PM

A manager is reviewing a file and needs to check the firm's policy on independence for audit clients who also request advisory services.

He searches: "Independence rules for audit clients requesting advisory work"

Foundry responds:

The firm's independence policy (last updated January 2026, document POL-014) states that advisory services for active audit clients require pre-approval from the engagement partner and the ethics partner. The key restrictions are:

1. No advisory work that involves originating data the audit team will test
2. No management decision-making roles
3. Fee cap: advisory fees must not exceed 15% of audit fees for that client

Precedent: This was tested in the 2023 Marlow Industries engagement, where the ethics partner approved a tax advisory engagement subject to the fee cap (see engagement file 2023-0287, p. 8).

He reads the policy, checks the precedent, and writes his response to the client. Ten minutes instead of an hour of searching and calling.

The numbers

MetricBeforeAfterChange
Time to find internal information25-45 min30 sec - 3 min90% reduction
Senior time answering repeat questions5-10 hrs/week1-2 hrs/week80% reduction
New staff onboarding to independent work4-6 months2-3 months40-50% faster
Duplicate research effortFrequentRareNear eliminated
Consistency of adviceVariable (depends who you ask)Consistent (grounded in firm's own precedents)Standardised
Data sent to cloud providersAll questions via ChatGPT (when used)NoneFully local
Monthly AI API cost£600-900 (OpenAI, when used)£0£7,200-10,800/year saved

Annual impact: 8,000+ hours of professional time recovered across the firm. At an average charge-out rate of £150/hour, even recovering 10% of that for billable work is £120,000/year.

Foundry cost: £999 setup + £99/month = £2,187 first year. Plus the Mac Studio if not already owned (~£5,500-6,500 for an M3 Ultra with adequate RAM).

What stayed cloud

What moved local: the AI that reads firm documents and answers questions. That's the part that was either impossible (can't use cloud AI on client data) or painfully slow (keyword search through 15 years of files).

What it doesn't do

What the team says

"I used to spend half my morning looking for a precedent file. Now I ask Foundry, get the answer, and I'm working on the actual problem in under a minute." Priya, junior accountant (6 months qualified)
"The real surprise was onboarding. New joiners are useful in week two instead of month three because they can actually find how we do things here." Senior manager
"We banned ChatGPT for client-related research in 2025. We lost nothing — Foundry does it better because it knows our firm's experience, not just the internet's." Partner, risk and compliance

Is this right for your firm?

This setup works for:

Not a fit if you:

Want to see it search your own documents? Book a Foundry Fit Review →

Technical details

Hardware
Mac Studio M3 Ultra, 512GB unified memory (for large document collections; smaller collections work on 128GB+)
Model
Qwen3 (30B or 235B MoE depending on collection size) via MLX or llama.cpp
Embedding model
nomic-embed-text-v1.5 for semantic document indexing
Pipeline
Document ingestion → embedding generation → semantic index → query → retrieval → answer generation with citations
Index size
~1GB per 10,000 documents (varies by document length)
Query latency
2-5 seconds for typical queries against 50,000+ documents
No-cloud posture
All indexing, retrieval, and answer generation performed locally. No outbound API calls.
Citation accuracy
Every claim in an answer links to a specific document and page/section. If no source is found, Foundry states "no relevant document found" rather than guessing.
Observability
llm_stats dashboard showing index health, query volume, response times, and model status
Access control
Respects existing folder/file permissions. Users only see results from documents they have access to.

← Back to all case studies | Next: Code Review →