Local AI and enterprise evidence
Where does the work actually run?
For an agreed local workflow, the model and its working data can run on your organisation’s approved infrastructure. Start with a simple question: where does the recording, document or drawing go from the moment a person hands it over?
Trace one recording
A client call may originate on a phone platform. For local after-call processing, the authorised recording reaches the agreed intake. The model prepares its transcript and draft on the approved system. The adviser checks the source.
Filing or sending anything uses only the integrations and permissions agreed for that step. Map the phone platform, copies, backups, support access and official record separately.
When the internet goes off
A prepared installation can continue the part it already has the local model, tools, records, access and power to complete. That does not make a disconnected supplier reply or an external CRM available. We identify what completes, what queues and who authorises an exception.
What do we pay for?
There is no external model-provider fee per token for the agreed, fully local processing. The system still needs capacity: hardware or a lease, licences where applicable, storage, electricity, support and maintenance.
Agree the expected workload, peak, term and exclusions in rand. If demand exceeds that capacity, queue the work or approve an expansion.
Who owns what?
Write down which equipment, configurations and commissioned outputs you own; which model or software rights are licensed; who can export or restore records; and what happens when the agreement ends. A local installation does not transfer every publisher’s IP.
What if a model changes?
A pinned local release can continue on the approved version without automatically adopting a provider’s newest model. Define who may update it, which tests must pass and how the previous release can be restored.
Evidence for IT, risk and procurement
Ask us to walk one authorised job from its source to its accepted output. Check the permissions and destinations, retention, approved operator access, recovery and deletion. Include any stage outside the local boundary in the same review.
Local control can support your privacy obligations under South Africa’s Protection of Personal Information Act (POPIA); an installation location alone does not establish legal compliance.
Useful handout · No registration required
One-workflow pilot brief (text version)
Use these seven questions internally before a scoping call. Do not put sensitive client records into a public form.
- Which repeated job, what starts it, who is waiting?
- Which document types and internal systems may be used, and who may authorise access?
- What result would you accept? Name a draft, output and exception.
- What role must review it? What better use could they make of the time?
- What must continue offline and what can wait for an external connection?
- How many jobs, at what peak, what term, what staff time and rand costs will you compare?
- What new evidence or change would prove the result, and who can say pass, hold or fail?