Prepare for a company-specific pilot.

Explain what arrives, what your team does next and what a useful result looks like. You do not need to share private files in the first consultation.

Pilot duration, sample coverage, cost and support are agreed for the task. There is no universal 30-day schedule or fixed number of files that proves every workflow.

For a scoped pilot, choose representative inputs and an approved template. Include relevant variations and decide how exceptions will be tested.

Confirm the sharing channel, permissions, model services and retention arrangements before transferring company data. A desktop interface does not by itself mean that processing stays on the device.

Review the result with the team that will use it. Agree what must be corrected, what remains unsupported and what the pilot must demonstrate before continued use.

If those checks are met, plan the desktop setup, configured tasks, instructions and support. Any system connection or external action needs its own agreed scope.

Representative files selected for the agreed task.

An approved output template and review owner.

Explicit data handling, success criteria and handover scope.