ARQIL / Practical field note · General planning guidance
“Automate the business” is too broad to be a useful starting brief. Choose one repeated task with a clear beginning, an understandable outcome, and exceptions you can describe.
Look for a bounded process
Enquiry routing, copying approved information, preparing a weekly internal summary, or drafting a standard reply can be easier to evaluate than a system asked to make open-ended business decisions.
Map what happens today
Write the current steps, which tools hold the information, who checks the output, and where errors occur. Include time spent correcting mistakes, not just time spent doing the routine.
Test access before promising a connection
A platform may need a paid plan, an API, account permissions, or explicit consent to process data. Confirm those conditions before assuming two systems can exchange information.
Keep a person in the important steps
If an output can affect a customer, money, sensitive information, or an important decision, define review and escalation rules. AI-generated text can be incorrect. A useful draft is different from an authorized answer.
Calculate the whole cost
Consider setup, subscriptions, API usage, maintenance, monitoring, human review, and failure recovery. Time freed for other work is not automatically a cash saving.
Start small enough to verify
Use test records, compare expected and actual behavior, and simulate a failed connection. Decide who receives an error alert and how to continue manually. Expand only after the narrow workflow behaves reliably.