Aitsa resources · Practical guidance
Do you need AI, automation, or a better process?
You may not need AI. Clear, predictable work often suits ordinary automation. Unclear responsibilities need a better process. Consider AI when varied text or documents need interpretation, and decide how the result will be checked.
Aitsa practical guide
Choose what the work needs.
Start with the problem, the inputs and the consequence of getting it wrong. A tool should follow that decision.
One workflow can combine clearer responsibilities, fixed rules, AI assistance and human approval. These are complementary choices, not a ladder towards removing people.
| What is happening? | Start with | Business example | What to check |
|---|---|---|---|
| People disagree about who does what, or what 'done' means. | Improve the process first | Give a completed-job handover a clear owner and finish point. | Agree the steps and exceptions before choosing software. |
| The inputs and rules are predictable. | Use ordinary automation | Flag an empty PO field or remind the owner of an approaching review date. | Test missing data, duplicates, retries and a manual fallback. |
| Useful information arrives as varied text or documents. | Consider AI assistance | Suggest fields from a customer email or draft a summary from approved notes. | Check against the source; route uncertain or consequential outputs to a person. |
| The action needs authority, context or carries significant consequences. | Keep a person responsible | Approve a quote, resolve a disputed quantity or accept a safety decision. | Keep the decision with the authorised person. AI can prepare information. |
AI can sit inside an automated workflow. Clear rules can still fail, and fluent AI output can still be wrong. Choose the controls as carefully as the tool.
Discuss what would help your business →Three starting points to assess
For an engineering workshop, an assistant could turn a customer email into a draft quote request using an approved template. A salesperson still checks the specifications, price and commitments.
For a contractor, document extraction could suggest expiry dates and missing fields for a reviewer. For a processing business, a reporting assistant could assemble approved updates into a draft report. These are examples to assess, not installed products or demonstrated customer outcomes.
Check the answer against the source.
Keep the original email, document or approved record next to the AI suggestion. Check names, job references, dates, quantities, amounts and conditions that may have been omitted. Leave unclear fields unresolved and route them to a person.
Try varied and unfamiliar examples, not just the example used to prepare the prompt. Include conflicting dates, missing information and a document from the wrong job. A fluent answer or a high confidence claim is not proof that the result is correct.
Count the time spent reviewing, correcting and handling failures. Keep consequential decisions with an authorised person and agree what happens when the tool or connection is unavailable.
Set a clear data boundary
For a first demonstration, use synthetic or approved non-sensitive examples. Name the tools and accounts staff may use, and the information they may enter. Do not treat a paid subscription as permission to upload every document.
OpenAI states that its business products and API do not use business data for model training by default. That is one provider control, not a conclusion about your whole workflow. Assess the relevant contract, retention, access, connected apps and cross-border arrangements.
OpenAI: business data privacy and DPA availabilityBuild a cost case from your own numbers
Count software seats, model usage, integrations, hosting, monitoring, staff review and ongoing maintenance. Use current supplier quotes rather than assuming a fixed rand price.
For an illustrative draft-quote test, compare the time from request to reviewed quote before and after the pilot. Include corrections and failed attempts. If drafting becomes faster but checking takes longer, the net saving may be small. Agree beforehand what evidence would justify expanding, revising or stopping.
Put the decision into a real workflow.
Use the Before you automate worksheet to map one process, name its owner and choose a bounded test. The fictional fabrication-shop example shows a useful first workflow that does not need AI.
Use the worksheet and worked process mapEquip the team as well as the workflow
A short practice exercise can reveal whether the immediate need is clearer instructions, staff training or a system integration. Ask a team member to use the proposed approach on an unfamiliar example and explain how they checked the result.
Aitsa offers separately scoped leadership training, employee workshops, corporate AI roadmaps and implementation. The initial conversation is free; paid work, outputs and terms are agreed in a proposal.
Explore employee AI trainingPut the guide to work
Want help with your own workflow?
Tell us what keeps getting stuck. Start a conversation about the people, process and result you want to improve.
- A free initial conversation.
- Detailed investigation and implementation are scoped and quoted separately.
- The worksheet stays free to download.
Prefer email? Email Willem.
Enquiry saved
Thank you. Your workflow is a useful place to start.
Aitsa has saved your request and contact details. Keep the reference below if you need to follow up.
Your reference:
Get the worksheetThe initial conversation is free. Any further work is agreed separately.
Sources and further reading
Prepared by Aitsa Integration. Updated 13 September 2026. These primary sources support the guidance; requirements and provider terms can change.
A useful place to start
More room for the work that moves you forward.
Bring a workflow to improve, a team that needs practical AI skills, or a decision about where to begin. Let’s find a useful next step.
Start a conversationA free first conversation. No commitment to a project.