Pre-visit plan
Workflow, devices, network assumptions, authorized contact, service area, and exclusions.
On-site AI setup
Configure the workflow with the people and hardware involved.
Share the location, device details, and business task. Availability, access, travel, compatibility, and the exact work are confirmed before a visit is scheduled.
What the visit can include
Installation, testing, training, and a clean handoff.
The customer remains in control of credentials and consequential settings. No ongoing remote access is implied by an on-site setup.
Approved changes
Install and configure only what the written scope and action-time approvals allow.
Acceptance tests
Exercise normal, missing-information, denial, recovery, and revocation cases.
Team handoff
Demonstrate the workflow, show approval points, document changes, and remove temporary access.
Reference price
$3,000 is a starting point, not a complete travel quote.
The final quote must confirm currency, taxes, service territory, appointment window, device count, workflow scope, hardware, travel, lodging, meals, support, cancellation, and warranty terms.
1
The customer enters passwords and completes MFACredentials do not belong in the public planner, chat, email, or handoff notes.
2
Security changes receive action-time approvalThe plan does not silently authorize firewall, account, OS, or identity changes.
3
Ongoing access is separateRemote support, monitoring, or maintenance requires its own explicit scope.
Visit outcome
Working acceptance caseDemonstrated against agreed test data
Configuration recordWhat changed, what did not, and how to pause it
Team ownershipNamed owner, approval path, runbook, and next review