# What to automate first: 12 business processes ranked by risk, not hype

> Rank a first automation by frequency, sameness, the cost of a miss and whether someone can catch a bad result. Twelve SME processes, in a suggested order.

Source: https://www.fyadvisers.com/blog/what-to-automate-first-small-business/  
Author: Fiona Wang, FYAdvisers  
Published: 2026-11-08  
Last updated: 2026-11-08

The most annoying task is rarely the right first automation. Annoyance is a feeling. A first workflow needs a task that happens often, follows the same steps, and can be checked before a bad result reaches a customer or a bank.

Public threads show owners asking this in plain language. One r/smallbusiness post is titled “What automations should I look into?” The opening post’s body was not available when this was checked, so the discussion was not read in full. Search excerpts of comments suggested starting with work done by hand more than three times a week, and automating the most expensive task rather than the most annoying one. Those comments are unverified. They are a useful prompt, not a finding about Singapore businesses. A separate poster, who described themselves as owning a small marketing agency with four other people, asked how people actually work out what can be streamlined. That status was not checked.

This page is an editorial order for a small team. It is not a survey and it does not claim hours saved. Where a process already has its own guide on this site, the link is the detailed design. This list only decides sequence.

## Score the candidate before you name a tool

Use four questions. Give each 0, 1 or 2. Do this on paper with the person who does the work, not with a vendor’s menu.

| Question | 0 | 1 | 2 |
|---|---|---|---|
| Frequency | A few times a year | Most weeks | Most days |
| Sameness | The steps change with the person you ask | The happy path is stable; exceptions are common | The same steps, including the usual exceptions |
| Cost of a miss | A nuisance | Rework inside the team | Money, a customer promise, or access to a system |
| Catchability | The output goes out before anyone looks | Someone might notice later | A named person sees the output before it matters |

Add the scores. A high total is not an instruction to remove people. It is an instruction to look. Catchability is the question that should break ties. A process with a high cost of a miss and a low catchability score is a bad first build: you would be automating the blast radius before you have a habit of checking.

Two commenters in that first thread, visible only as excerpts, split “often” from “expensive”. Both belong in the score. Frequency without a costly miss is a convenience. A costly miss that nobody can see is a risk. Start where the miss is internal and visible.

## Twelve processes, in a suggested order

The order is a recommendation for a typical small trading, services or operations team. Your score can reorder it. Do not treat the numbers as a maturity model.

### 1. Turn a form or enquiry into a task, with a duplicate check

A website form or a shared mailbox drops a name, a need and a phone number into a queue the right person already watches. The workflow files the record and flags a likely duplicate. It does not reply with a price. This stays internal, so a bad record is caught by the person who would have typed it anyway. [Speed to lead](/services/speed-to-lead/) is the service conversation about response time. This list does not redesign lead routing.

It breaks when the form fields do not match what the team actually needs, so people keep a second notebook. Fix the fields before you add a second destination.

### 2. File attachments from a shared inbox

Invoices, orders and certificates arrive as PDFs. A workflow can put a file in a restricted folder and open a queue item, while leaving uncertain documents for a person. The design, including the rule that text inside a PDF is not an instruction, is in [email attachment routing](/blog/email-attachment-document-routing-automation/).

It breaks when the connector can read every mailbox in the company. Limit it to one address.

### 3. Remind the team about dates you already track

Licence renewals, insurance, domain names, scheduled maintenance, filing dates that already live in a calendar or a sheet. A reminder to a named person is low risk. A reminder to a customer is a later item on this list.

It breaks when the date in the sheet is wrong. The automation will faithfully nag you about a fiction. Clean the list once, then remind.

### 4. Route expense claims, and stop before payment

Collect the receipt, stamp a claim id, flag a missing file or a duplicate, and send the claim to a manager who is not the claimant. Do not let the workflow decide tax treatment or pay the employee. The states and the duplicate-receipt test are in [expense claim approval](/blog/expense-claim-approval-automation-singapore/).

It breaks when a clearer photo of the same receipt creates a second payable claim. The id has to survive the new file.

### 5. Approve a purchase request before anyone emails a supplier

A requisition, an authority check, a versioned order, then a receipt. Releasing the order is allowed only after approval. Paying the invoice is not part of this step. See [purchase order approval](/blog/purchase-order-approval-workflow-singapore/).

It breaks when people can still send the supplier a PDF from a laptop. The workflow is then a parallel story, not a control.

### 6. Approve a supplier invoice, and do not pay it

Match the bill to the order and the receipt where you have one. Hold mismatches. Record who approved which version. Posting to accounting can follow. A payment run is a separate authority. [Invoice approval](/blog/invoice-approval-workflow-automation-singapore/) covers matching, InvoiceNow as a different duty, and GST record-keeping. This ranking only says: do this after internal filing works, and before you automate money leaving the account.

It breaks when the second copy of the same invoice, forwarded by a colleague, becomes a second bill.

### 7. Hand a new joiner from HR to IT with a checklist

An authorised HR record creates tasks. The manager confirms a role template. IT prepares access and leaves it disabled until the start date is still true. Identity documents stay in the HR system. [Employee onboarding](/blog/employee-onboarding-workflow-automation-singapore/) is the design. It is not a claim about the Employment Act.

It breaks when the trigger is a forwarded CV rather than the HR record, or when a withdrawn start date leaves an account enabled.

### 8. Assemble a weekly report from exports you already trust

Pull figures that already exist in accounting, the mailbox or the job system into one page for a Monday meeting. A person still reads it. The value is that nobody retypes twelve cells. The risk is low because the meeting is the check.

It breaks when the export is stale and the meeting treats it as live. Show the timestamp of each source on the page.

### 9. Draft overdue reminders only after internal workflows are trusted

A reminder is customer-facing. It is safe only when the balance is read again before send, disputed invoices are on hold, and a person releases the first versions. [Overdue invoice reminders](/blog/overdue-invoice-reminder-workflow-singapore/) is the design. It sits this far down because a wrong chase damages a relationship you cannot patch with a retry.

It breaks when the morning’s list is treated as the afternoon’s balance.

### 10. Hand an accepted client to the delivery team

After the engagement is accepted, track documents, open a workspace that client cannot see into another client’s files, and keep “received” distinct from “verified”. [Client onboarding](/blog/client-onboarding-workflow-professional-services/) starts at acceptance, not at the first sales email.

It breaks when the first uploaded file marks the project as ready.

### 11. Suggest a reorder, and let a buyer decide

A low on-hand quantity is not a purchase. Available stock, reservations and inbound orders belong in the suggestion. One open request per item and location. [Inventory reorder approval](/blog/inventory-reorder-approval-workflow/) keeps the commercial decision with a person.

It breaks when a second alert creates a second order while the first purchase is already on the water.

### 12. Bank details and payments last, and with a person in the middle

Changing a supplier’s account number, releasing a payment, or emailing customers new bank instructions are last because the cost of a miss is money and the catch, if you remove it, is gone. Verification uses a contact you already hold, not the phone number in the email that asked for the change. [Supplier bank-detail changes](/blog/supplier-onboarding-bank-detail-change-workflow/) is the control. Do not start a company’s automation programme here.

## What should fall off the list

Drop a candidate when three people describe different steps, when every case is “it depends”, or when the first version needs five systems and a historical cleanup. Those are not moral failures. They are [processes that are not ready](/blog/when-not-to-automate-a-process/). Also drop one-off judgement: a quote with unusual terms, a complaint, a discount that is really a favour. The [human-approval ladder](/blog/human-approval-in-automated-workflows/) is where those stay.

If the score says “build” and you do not know whether to do it yourself, hire a freelancer or hire an operator, that is a different decision. Use [DIY, freelancer, agency or an ops hire](/blog/diy-freelancer-agency-or-ops-hire-automation/) after you have named the process, not before.

## A week of notes beats a tool trial

The agency owner’s question was how people figure this out. A practical answer is a one-week log kept by the people who do the work. Do not ask them to estimate. Ask them to mark each repeated task as it happens.

| Day | Task | Times today | Same steps as last time? (Y/N) | What a miss would cost | Who would notice, and when? |
|---|---|---|---|---|---|
| Mon | | | | | |
| Tue | | | | | |

At the end of the week, score only the tasks that appeared at least three times, using the table above. Bring the winner to a [pilot](/blog/workflow-automation-pilot-scope-acceptance-checklist/), which is a statement of work for one process, not a tour of platforms.

If you want a structured look before you buy anything, IMDA’s [CTO-as-a-Service](https://www.imda.gov.sg/CTOaaS) page describes a self-assessment of digital readiness, recommendations, and access to digital consultants for advisory and project management. What is free, and who operates it, changes. Read the live page. A self-assessment is not a grant and not a build.

## Illustrative scenario

Illustrative scenario, not a client and not a result. A six-person trading firm lists three candidates after the week’s log.

| Candidate | Frequency | Sameness | Cost of a miss | Catchability | Total |
|---|---|---|---|---|---|
| Log a website enquiry into the shared sheet, flag duplicates | 2 | 2 | 1 | 2 | 7 |
| Route a supplier invoice to the buyer with the purchase order attached | 2 | 2 | 2 | 2 | 8 |
| Email a customer a quote from the price list as soon as they ask | 2 | 1 | 2 | 0 | 5 |

The quote looks valuable because it is slow and customers wait. It scores last because a wrong price or a wrong term leaves the building before anyone reads it. The firm starts with invoice routing, where the buyer still approves, and leaves quotes on the [draft-and-approve](/blog/human-approval-in-automated-workflows/) side of the line. No time saving is assumed. The only decision is which miss they can still see.

## Limits of this order

The twelve items are common, not complete. A clinic, a site contractor and a recruiter will reorder them. The scores are a conversation aid. They are not a risk model and they have no validated weights. Thread comments used above are excerpts or titles, not a census of owners, and almost all of them are from outside Singapore.

If the candidate is a model rather than a workflow, the hiring note is [how to choose an AI consultant](/blog/how-to-choose-ai-consultant-singapore/) and the rules-versus-model split is [RPA versus AI](/blog/rpa-vs-ai-automation-singapore/).

If you want a second opinion on the top of your own log, describe that one process. You can use the workflow service or WhatsApp +65 9071 3976 ([chat](https://wa.me/6590713976)).

## Frequently asked questions

### Should I automate customer emails first?

Usually no. A wrong internal reminder is recoverable. A wrong email to a customer, especially one that states a price or a promise, is not. File, route and remind internally first. Send customer messages only after a person still approves the draft, which is covered in the human-approval guide.

### How many automations should I run at once?

One, until that one is trusted. There is no sourced number of automations an SME should own. A second workflow started before the first has an owner, a test and a way to see failure tends to become a second thing nobody watches.

### Do I need AI for a first automation?

No. Rules are enough when the steps are the same each time. An AI step is useful later for messy inputs, such as reading a free-text email, and its output should be checked. The comparison of agents and workflows is a separate guide.

### Is there free help in Singapore to decide what to automate?

IMDA describes CTO-as-a-Service as a self-assessment of digital readiness, with recommendations and access to digital consultants for advisory and project management. Terms change. Use IMDA’s CTOaaS page rather than a saved brochure, and do not treat a self-assessment as a funded project.

### What if nothing on the list scores well?

Do not automate yet. Write the process down, name an owner and fix the input. The guide on when not to automate is the next step, not a tool trial.
