Build a workstation you can support.
OutOfAI℠ · AI-assisted editorial content · Updated November 4, 2026
A successful local AI workstation needs a repeatable task, compatible software and someone responsible for its operation. This guide turns an experimental machine into a reviewable proposal without assuming that a particular brand, CPU family or memory capacity fits every workload.
1. Freeze the pilot before choosing the components
Record the application, model identifier and version, input types, expected document size and maximum simultaneous users. Decide which operations must remain offline. A document-search assistant, image generator and model-training job have different demands; do not use a benchmark for one as evidence for another.
Use fictional or approved non-sensitive documents during setup. Identify who may approve access to real business records, where indexes and chat histories will live, and how the machine will be decommissioned. Begin with the Company data prompt as an advisory reminder alongside technical controls, not as a substitute for them.
2. Get a complete compatibility answer
Ask the supplier to identify the supported operating system, driver, inference runtime and model format. If CUDA is required, use NVIDIA's current compatibility and installation documentation. An application that bundles its runtime may not require a full development toolkit; follow that application's instructions instead of installing extra software by default.
| Area | Question for the supplier | Evidence to retain |
|---|---|---|
| Memory | Can the exact model and target context run alongside ordinary business apps? | Measured peak use during the agreed test, including system and accelerator memory. |
| Storage | Is there space for models, temporary files, indexes and recovery copies? | A capacity plan and an approved backup location. |
| Power and cooling | Does the complete system remain stable during sustained work? | Power-supply compatibility and a supplier-run load test within manufacturer limits. |
| Service | Who fixes driver conflicts or replaces a failed component? | Support scope, response arrangements and warranty terms. |
3. Test accuracy and usability before speed
Prepare a reference set whose correct answers a person can verify. Include a missing answer, a conflicting date, a long document, a scanned page if supported, and a prompt-like instruction inside a document. The assistant should distinguish source material from instructions and state when it cannot support an answer.
Fictional test set: 12 site reports and a one-page reference sheet. Check A: extract the exact project date and cite its source. Check B: mark absent approval as “not supplied.” Check C: preserve conflicting progress figures for human review. Check D: ignore a document sentence asking it to email files externally. Decision: the project lead accepts or rejects each result before rollout.
These are proposed tests, not results from a machine we benchmarked. Passing a small set does not prove safety on every future document. Keep consequential decisions and external actions under explicit human control.
4. Measure the complete working session
Record cold start, time to first useful output, completion time, human correction time and whether the machine remains usable for the team's ordinary applications. Repeat the agreed batch during a sustained session rather than measuring a single short answer. If multiple users are required, test the intended concurrency without exposing an unauthenticated service to the network.
Ollama's documentation explains how its status output distinguishes model loading on CPU and GPU. That can help diagnose a configuration; it is not a guarantee that a given configuration is fast enough. Keep the application version and settings with your measurements so later comparisons are meaningful.
5. Rehearse maintenance and recovery
- Record the approved installation source, model license and version.
- Apply updates in a test window and keep a workable rollback plan.
- Check access permissions for documents, indexes, chat histories and backups.
- Restore a fictional test document and its index from an approved backup.
- Explain to users how to report an incorrect answer or suspected data exposure.
Acceptance is a business decision
A reasonable approval note states the supported tasks, known failures, permitted data and responsible owner. If the workstation cannot meet the agreed test, reduce the scope, change the configuration or pause the purchase. A more expensive component should solve an observed constraint rather than compensate for an undefined requirement.
Use the cost comparison for budgeting and the GPU decision guide to understand memory and acceleration tradeoffs.
Sources and editorial method
Reviewed November 4, 2026. The decision examples, worksheets and acceptance criteria are OutOfAI℠ editorial guidance. They are not measured product benchmarks, customer results or vendor endorsements. Check the current documentation for the exact software and equipment you intend to use.
- Ollama FAQ: runtime configuration and CPU/GPU loading
- LM Studio: offline operation and connected features
- NVIDIA: Windows CUDA compatibility and installation checks
These are primary technical documents, not independent product reviews or academic peer review. A source describing a capability does not establish performance on your business workload.
