Choose a pilot worth running

Find a specific bottleneckCopy Anchor Link

Ask your team which repeated task consumes time and has a recognizable good result. Avoid starting with “automate operations.” Break it down into a job someone can demonstrate.

Examples include preparing a weekly report, classifying incoming requests, drafting follow-ups, or extracting information from a standard document.

Write the pilot briefCopy Anchor Link

Capture these details before building:

• The job and why it matters.
• The person responsible for the result.
• The current process and its source systems.
• The input the AI employee can use.
• The output a person will review.
• Actions the AI employee must not take.
• The KPI and evidence that would justify expanding the pilot.

Do not invent a target just to finish the brief. Use a baseline measured from your own work.

Start with enough informationCopy Anchor Link

You can pilot a single workflow without sharing company runway, full revenue, or all customer records. Use the minimum material needed to test the job, with permission from the people responsible for it.

Include difficult casesCopy Anchor Link

Test incomplete records, ambiguous requests, conflicting instructions, and cases that need escalation. A pilot made only of easy examples cannot establish whether the process is dependable.

Next: set up the workflow →