01Name the outcome
02Bound the first workflow
03Review before expanding
Explanatory diagram. A conceptual reading aid, not benchmark or ROI data. See sources checked for the factual guidance used in this article.

Preparing for an AI setup means more than making a computer available. The technician needs an agreed task, compatible equipment and an approved way to get necessary access. You need a backup, clear handling arrangements and a way to recognize a successful handoff. This guide helps you assemble that information before booking a visit or shipping a device.

1. Describe the outcome before the equipment

Write down the workflow you want to demonstrate at completion. For example: “Use approved sample documents to prepare an internal summary that our coordinator can review.” Identify who will use it, whether it needs internet access and which applications it depends on.

Hypothetical example: Cedar Desk Demo wants a shared office computer configured for drafting summaries from fictional meeting notes. It does not need access to payroll, customer mailboxes or the owner’s personal account. That narrower scope changes which permissions, software and tests are necessary. It also gives the customer a concrete completion check.

2. Build a device and account inventory

Record the device model, operating system, available storage and required peripherals. Tell the provider whether the device belongs to the business, is leased or is managed by an employer or IT company. Managed devices may require an administrator’s involvement. Do not remove management controls to make a setup easier.

List the software and accounts the workflow needs, along with the person authorized to approve access. Keep passwords, recovery codes and private keys out of the inventory. Send serial numbers or other job-specific identifiers only through an agreed private intake route when needed, never in a public website form or catalog.

3. Verify the backup you will rely on

Before changes, identify which files and application data matter. Confirm that the backup covers them and that someone can recover a representative file. Record the last successful backup and who holds any recovery material. Keep that material under your control.

Apple’s service-preparation guidance emphasizes making a backup because service can require erasing or replacing a startup disk. Its repair-specific instructions are not blanket instructions for an AI configuration job. Follow steps appropriate to your exact device and agreed work; do not erase a device or disable protections just because a generic checklist mentions them. Apple service preparation.

For Windows, match the backup method to the account and business environment. Microsoft’s consumer Windows Backup guide says work or school accounts do not work with that app. Ask your IT owner about the organization’s approved backup method rather than moving business files to a personal account. Microsoft Windows Backup.

4. Agree on access without handing over secrets

Ask what the technician needs to read, install or change. Plan for the account owner to complete sign-in and multifactor authentication where possible. If a temporary support account is appropriate, agree on its permissions, lifetime and removal. Some configuration cannot be finished unattended; identify that dependency before sending the device away.

Do not place passwords on shipping labels, in the box or in ordinary email. Device setup also does not imply permission for permanent remote access, stored credentials or ongoing monitoring. Those require a separate, explicit arrangement. Ask where any demonstration data will go if the workflow uses a cloud model or connected service.

5. Prepare for an on-site visit

Confirm the location, contact person, appointment arrangements, workspace and power. Identify who can approve software installation and network access during the visit. Make sure the relevant decision-maker can participate in the handoff.

Agree in writing on the work included, travel arrangements and anything the customer must supply. Avoid putting shared Wi-Fi passwords or administrative credentials in calendar descriptions. If guest access is suitable, have the authorized network owner arrange it. Keep unrelated files and applications out of the demonstration where practical.

6. Prepare for mail-in handling

Do not ship until compatibility, intake instructions and the destination are confirmed. Ask how the provider identifies your device, records its condition and restricts access while it is held. Keep a private record of the device’s condition and the accessories included.

Confirm packaging instructions, carrier requirements, shipping charges, insurance, responsibility for damage, return-address verification and what happens if work cannot proceed. Follow the carrier’s applicable device and battery rules rather than guessing. Do not assume a reference price includes shipping or a particular turnaround. Ask for the arrangements for your specific job.

7. Use a completion checklist

At handoff, run the agreed sample workflow together. Check the output and the behavior when information is missing. Ask for a record of relevant configuration changes, operating instructions, recurring costs and the support route. Identify any remaining work clearly.

Before closing the job, confirm:

  • The agreed demonstration works on the intended device
  • Your team knows how to start, stop and recover the workflow
  • Temporary access is removed or has an explicitly approved end date
  • You know which providers process the workflow’s information
  • Future updates and support responsibilities are understood

InstallAI’s on-site and mail-in services need compatibility and scope confirmed for each job. Bring this checklist and your workflow goal to the setup conversation. Wait for approved intake arrangements before shipping equipment or sharing access.

Sources checked