Isle Client Environment Provisioning (Onboarding)

Isle Client Environment Provisioning (Onboarding)

1. 01

   Create the client's Isle account and open the environment configuration screen

   Provision one managed desktop environment per client engagement. The $29/month Tier 1 plan covers a single-environment workflow, so a second concurrent client means a second plan or a move to Custom enterprise pricing via contact sales.

2. 02

   Select the application target: KiCad for electronics work or FreeCAD for 3D engineering

   Isle only wraps these two applications today. If the client's deliverable is schematic capture, PCB layout, or Gerber output, choose KiCad. For parametric modeling or STEP/IGES/STL export, choose FreeCAD. Do not promise managed desktop support for any other professional software.

3. 03

   Validate API access and SDK integration against the agency's agent stack

   Isle is framework-agnostic, so the agent framework the agency already runs does not need to change. Confirm the connection before the client kickoff call, not during it.

4. 04

   Configure application health monitoring and set the alert threshold for the client's environment

   Health checks are what separate a managed Isle deployment from a raw desktop install. Decide who on the delivery team receives a failure alert and within what window they respond.

5. 05

   Define the artifact checkpoint cadence for the client's repeatable design operation

   Pick the operation first (for example automated PCB layout review or part placement), then set checkpoints around its natural completion points. Checkpoints are the recovery mechanism when an agent produces a bad artifact.

6. 06

   Test checkpoint restoration and environment containment with a deliberately failed agent run

   Run the agent into a known error, restore from the last checkpoint, and confirm the environment returns to a clean state. Do this before the client sees the workflow, because recovery controls are the main thing the retainer is paying for.

7. 07

   Hand off the environment to the client with a written runbook covering checkpoints, monitoring alerts, and escalation

   The runbook should state which design operations the agent owns, which ones stay with the client's engineers, and what triggers a rollback. This document is what justifies the managed service tier at renewal.