These preliminary GHT planning ranges describe a purchase-based deployment. They are estimates for the stated scope, not manufacturer quotes, fixed offers or guaranteed delivery dates. A workload review and written proposal establish the actual price.
Timeframes start when the scope is approved, hardware is available, data access is authorized and usable samples are supplied. Procurement lead times and delayed client review extend the calendar. Allowances exclude tax, travel, recurring support/software/cloud costs, major data cleanup, electrical/cooling changes and separately designed high availability. Hosted options replace some hardware purchases with recurring infrastructure charges and require their own quote.
Private AI pilot
One approved document source, one defined workflow and a small evaluation group.
Hardware approachCompact local AI system, such as an NVIDIA DGX Spark, or a qualified GPU workstation. Selection follows a model and workload test.
Acceptance checkAnswer representative questions with sources, reject restricted documents, measure response time and record the pilot decision.
Explore package details ↗Department AI deployment
Several agreed sources, identity integration, permission-aware retrieval and one department workflow.
Hardware approachConfigured professional GPU workstation, including Lenovo ThinkStation options, plus backup and power protection as scoped.
Acceptance checkVerify user permissions, citation quality, simultaneous requests, content refresh, recovery and administrator handover.
Explore package details ↗Integrated company AI
Multiple departments or business-system integrations with stronger operating and recovery requirements.
Hardware approachValidated multi-GPU server architecture, including Lenovo ThinkSystem candidates. Power, cooling, storage and networking are designed together.
Acceptance checkTest each integration, approval boundaries, load, recovery and the agreed operational monitoring. High availability is a separately scoped design.
Explore package details ↗Optional fine-tuning phase
Allow an additional $10,000–$35,000 in implementation and 3–6 weeks for a bounded task with usable approved examples and held-out evaluation. Suitable existing compute may be reused; additional training compute is quoted separately.
We recommend this phase only after a baseline test demonstrates a problem that training can reasonably address.