Automate a task first when it is repeated often, follows clear rules and has an owner who can handle exceptions. A good first automation usually removes predictable administrative work without making an important business decision on someone’s behalf.
Start by observing the process. If staff disagree about what should happen, writing an automation may simply reproduce that disagreement faster.
List the work before shopping for tools
Ask the team which tasks they repeat, what information they copy and where work waits for a handover. Examples might include recording enquiries, sending an acknowledgement, preparing a routine report or reminding staff about an internal deadline.
For each candidate, record how often it happens, roughly how long it takes and the errors or delays it creates. Estimates are enough for an initial discussion if you label them. Measure the most promising task before committing to a larger build.
Use a simple decision screen
| Question | A promising first candidate | A reason to investigate further |
|---|---|---|
| Are the rules stable? | Staff follow the same agreed steps | Each case needs a new interpretation |
| Is the input reliable? | Required information arrives consistently | Missing or contradictory information is common |
| Can errors be detected? | Logs and checks reveal a failure | A mistake could remain hidden |
| Can someone take over? | An owner can review exceptions | No one is responsible after setup |
| Is the benefit meaningful? | Repeated effort or delay is reduced | Maintenance may exceed the work saved |
This is a planning screen, not a numerical claim that one task will deliver a particular return. Use it to narrow the candidates and choose a pilot.
A good first example: enquiry intake
A hypothetical service business receives website enquiries and manually copies each one into a shared record. A first automation could record the submission, assign its category and notify the responsible person.
It could send a factual acknowledgement saying the request has been received. Staff would still assess the scope, price and suitability before making a commitment. The acknowledgement should not promise availability or accept a contract automatically.
This is an illustrative workflow. It is not a claim that a named client has implemented it or achieved measured time savings.
My web application and integration support can help assess that kind of process alongside a broader digital strategy review.
Write the manual process first
Describe the trigger, required information, normal steps and expected output. Identify what happens when a field is missing, a duplicate arrives or a service is unavailable.
If the process is currently unreliable, simplify it before automating. You may discover that a clearer form, one shared record or a defined staff responsibility solves much of the problem without a complex integration.
Agree what the automation may do and what requires review. Internal reminders and record creation often have different consequences from sending quotations, approving refunds or publishing customer communications.
Check access and information needs
List the accounts and data the workflow needs. Use appropriate business accounts and the narrow access required for the task. Keep credentials out of general documents and ensure the organisation can manage access when staff change.
Do not copy customer information into additional services simply because a tool makes it easy. Define the purpose, access and retention arrangements. Where an automated message is sent, confirm that its content and timing fit the customer’s expectations and your communication arrangements.
Run a small pilot
- Choose one process and name its owner.
- Record the current effort, delay and error types.
- Define the normal result and exceptions.
- Test with representative, non-sensitive sample data.
- Pilot a limited scope with monitoring.
- Compare results and decide whether to expand.
Check for duplicates and repeated triggers. If the same enquiry is received twice, the workflow should not create an uncontrolled chain of messages or assignments. Agree how staff pause the automation and continue manually.
Include maintenance in the value calculation
Automations can fail when passwords, forms, integrations or provider features change. Someone needs to review errors, renew services and update the workflow.
Compare effort saved with setup, subscription and maintenance costs. Do not promise an exact saving based only on an estimated task duration. Observe the pilot and include time spent handling exceptions.
A modest automation that works reliably and remains understandable can be more useful than a broad system nobody can maintain.
Frequently asked questions
Should every automation use AI?
No. Clear rules may be served by a straightforward form, integration or scheduled process. Use AI where its role is useful and its output can be checked appropriately.
What if the task happens only occasionally?
Assess the effort and consequence of mistakes. A rarely used automation may cost more to maintain than a clear manual procedure.
When should we expand?
After the pilot works, the owner can handle exceptions and the observed benefit justifies the next stage. Expand one defined part at a time.
Bring one repetitive task to the discussion
Examples of the current inputs, steps and exceptions are enough to begin assessing whether automation is the right next move.
Discuss your next step
If you would like help applying this to your organisation, share a short description of your situation and the decision you need to make.





