Field notesAI, Security

Why your business intelligence belongs on a local LLM

1 min read

Language models can now answer questions about your own operation. Few businesses ask where that data goes when they do.

For a retail group the answer is a commercial risk. For a hospital or a law practice it can be a regulatory one.

It happened one browser tab at a time

Paste a sales report, a contract or a patient summary into a hosted AI tool and it travels to a third party’s servers, where it may be retained, logged or reviewed. Most organisations never decided this on purpose.

A local model keeps the boundary

It runs on hardware you control, in your office or in a private cloud account in your name, and answers from your ERP, hospital system or documents without sending them anywhere else. For summarising, drafting and searching, open-weight models have closed much of the gap with hosted ones.

Before asking which model is smartest, ask which model you are allowed to show your data to.

When local is right, and when it isn’t

Go local for regulated data (patient records, legal case files, personal data covered by the GDPR or India’s DPDP Act), for commercially sensitive data, and for high, predictable volume, where per-request fees add up month after month.

Don’t when the data isn’t sensitive, the volume is low, or the task needs the strongest reasoning available. Then a hosted tool with a business-grade data agreement is cheaper and good enough, and we will say so.

Start with the boundary, not the model

What the system may read, who may ask it questions, what gets logged. Then a model sized to the hardware and the task, tested against questions your team already knows the answers to.

Seen this in your own operation?

Book a free audit

Next field note

Cutting over without cutting offJanuary 9, 2026 · 1 min read