The short answer
A small business should usually automate a process that is repeated frequently, follows reasonably clear rules, uses structured information and currently consumes measurable time. It should also be low enough in risk that the team can test and learn safely.
New enquiries arrive through a website or marketplace, someone copies the details into another system, sends a similar acknowledgement, assigns an owner and sets a reminder. The work is frequent, predictable and easy to verify.
Use the five-part priority test
1. Frequency
Daily or weekly work creates more opportunity than something performed twice a year. Count how often the full process occurs, not only its most visible task.
2. Time and friction
Include chasing, checking, correcting and re-entering information. A five-minute task may be expensive if fifty people repeat it; a two-hour task may be unimportant if it happens rarely.
3. Rule clarity
The best early candidates have decisions that can be explained: if information is complete, move it forward; if it is missing, request it; if a deadline passes, escalate it. Processes driven mainly by judgement need stronger human control.
4. Data readiness
Automation is easier when inputs are consistent and accessible. If crucial information arrives as vague messages, handwritten notes or changing spreadsheets, improve collection before automating downstream work.
5. Risk and reversibility
Begin where mistakes can be detected and corrected. High-stakes decisions, sensitive personal data and customer-facing commitments require more controls, testing and oversight.
Good first automation examples
| Process | Why it can work | Keep human control over |
|---|---|---|
| Lead acknowledgement and assignment | Frequent, time-sensitive and rules-based | Qualification and sales conversation |
| Appointment reminders | Predictable timing and clear message templates | Complex rescheduling or vulnerable customers |
| Document collection | Known requirements and repetitive chasing | Judging whether unusual evidence is acceptable |
| Recurring internal reports | Data comes from defined sources on a schedule | Interpretation and business decisions |
| Customer review requests | Triggered by a completed service or handover | Complaints and unresolved cases |
What not to automate first
- A process nobody can explain consistently.
- Work that is already rare or inexpensive.
- A broken process whose unnecessary steps should be removed.
- High-risk decisions without clear ownership and safeguards.
- A workflow that changes every week because the business model is unsettled.
In these cases, process mapping or a stronger SOP may need to come first.
A practical first-project sequence
- Choose one clearly bounded workflow.
- Measure its frequency, time, errors and delays.
- Map the real steps, including exceptions.
- Remove unnecessary work before adding technology.
- Define the result and the human controls.
- Test with a small group, then compare outcomes.
- Document ownership and maintenance before scaling.
If you are still choosing between several candidates, use the Veliq automation audit checklist or estimate the opportunity with our free ROI calculator.