Pilot kickoff checklist
Use this checklist before your first pilot training session. Pilots are organization deployments (Business and Enterprise), not the Individual plan.
Access
- Confirm the tenant URL users should bookmark.
- Invite the first cohort from Admin → Members. See Add users and members.
- Confirm at least two admins can access Admin.
- Confirm SSO or login-code behavior with a test user.
- Decide where users should ask questions during the pilot.
Data
- Pick the first project, folder, or document set.
- Confirm source-system permissions are correct.
- Sync or upload the training files.
- Confirm important files are indexed before training.
- Avoid syncing broad root folders unless that scope is intentional.
Workflows
- Pick one or two workflows to demo.
- Test each workflow on a small sample.
- Make sure requested files have clear names.
- Keep draft workflows private until they are ready.
- Decide who can edit shared workflows during the pilot.
Spend and reporting
- Set the pilot or organization spend cap.
- Decide whether to set per-user caps.
- Tell users that large files and broad workflows cost more.
- Review Admin -> Analytics after the first training.
- Export usage data if you need to analyze spend in a spreadsheet.
Feedback loop
- Ask users to use thumbs-down on bad responses.
- Ask users to include URLs and screenshots for bugs.
- Review high-value and high-cost runs with power users.
- Update workflow instructions after the first few real runs.