Which process should an SME automate first?

Which process to automate first

Process automation in an SME starts with one workflow, not a tool list. Automate first the job that returns every week in the same shape, hurts one person, has a recognisable end, and whose inputs already sit in email, a PDF, or a system you use. The Monday report pasted together from five exports is a candidate. The conversation with an unhappy customer is not.

ChatGPT is already open in a lot of offices. Copilot may be too. The report is still built by hand. If a vendor pitches an «agent» on top of those chat tools, read what an AI agent is before you treat it as automation. Before you add licences, sort with four questions. That takes a quarter of an hour and costs nothing.

Four questions before a tool comes in

BDO noted in 2026 that large companies already build AI into their value chain, while many SMEs stay on individual apps. Their advice: a few concrete cases, owned by management, not treated as an IT side topic. In practice that is one workflow that survives these four questions.

• Does it repeat on a weekly or daily rhythm?
• Does it hurt in time, errors, or a single owner?
• Can you say the start and the end in one sentence?
• Is the input already in email, a PDF, or a system you use?

Does it repeat?

Count how often the process happens in a normal month. Daily or weekly is a candidate. Twice a quarter is usually a project, even when it hurts this week.

Write down three things: who does it, on which weekday, and what happens if that person is ill or on holiday. If the answer is “then we wait”, you have frequency and a single point of failure.

Five Excel exports every Monday: that repeats. Switching the till system once: that does not.

Does it hurt?

Pain is time, an error, or a person without whom nothing moves. Ninety minutes every Monday until the numbers add up. Three follow-up questions a week because the wrong column landed in the sheet. The office manager who is the only one who knows which file counts.

You do not need a stopwatch study. If the process regularly waits until it becomes urgent, it hurts. If nobody wants to do it and it is still mandatory, it hurts. If a typo knocks over an invoice or a report, it hurts.

“We could make this nicer someday” is not enough. That is discomfort. A bottleneck looks different: it blocks the next person.

Does it have a clear end?

An email with a PDF arrives, and the relevant fields land in bexio or Abacus. A quote goes out, and seven days later a follow-up draft is ready, or the status is dead. You can say in one sentence when the process is finished.

Calming a difficult customer has no such end. Turning the proposal until it “feels right” does not either. Neither does “make the numbers look coherent for management” when the question in the room changes every week.

Without an end you are trying to automate judgement. That fails before anyone has picked a tool.

Is the data already there?

Email, PDF, spreadsheet, folder, bexio, Abacus, Microsoft 365. The input has to exist somewhere already. You do not need a new collecting point. You need a source you can point at: this comes in, that should go out.

The adesso GenAI Impact Report 2026 for Switzerland names data quality and missing processes as the most common blockers, 32 percent each, not the model. That is adesso’s measurement, not ours, but it matches office life. If the Excel columns change name every week, the PDFs live in the inbox one week and on a stick the next, and nobody will say which version counts, the process is missing. A different model will not fix that. If three answers are yes and the data is shaky, tidy up first. A tool on a workflow with no stable source only freezes the mess.

If those files hold personal data, the filing place matters too. A free chatbot account is the wrong place for them. What the revised Swiss Data Protection Act asks for in practice is set out by the FDPIC. This is not legal advice.

You can run this sort internally in fifteen minutes. Each person in management, operations or the office names one process that grates and holds the four questions up against it. What gets four yes answers and has an owner is your first workflow. The rest waits. How to analyse the workflow you picked: process analysis for SMEs.

What you should not automate first

One-off projects are the wrong start. The office move, the new website, the data clean-up before year-end accounts: once that is done, nobody touches it again. There is no repetition.

Highly individual advice does not belong at the front either. The conversation where you walk a client through their numbers. The exception you make on purpose. The phone call that holds the relationship. A template is often enough.

The same goes for the chaotic process with no owner. If three people are “sort of responsible” and the files live in four folders, you will automate the mess. First name a person who owns the process, then run the four questions again.

Two neighbouring questions often arrive in the same breath. If the whole team needs the same rules and tools, that is a workshop, not a single workflow, and it is covered by AI in Business. If you want to test a product idea, that is different work, and the Process Check does not scope an MVP.

Starting ten things at once feels like a plan. A week later, nobody in the office uses any of them.

What it costs

The four questions cost nothing internally. If you want to narrow down to one workflow with us in 60 minutes, that is the Process Check: a flat CHF 99. The fee is credited in full if you later book an implementation package. If the session takes place and no concrete case comes out of it, you get the money back.

The packages are guide prices, confirmed in the check, not a quote from this page. Small is two to three days and CHF 3,200–4,800. Medium, Large and Max are larger. After go-live, token fees stay with you and hosting is a guide figure of CHF 50–150 a month, cancellable. If you already know that several workflows, or AI inside your own product, are the job, AI implementation is the closer fit. The check stays the small start for a single piece of work.

The tool comes after the process

Only once the process is clear is the tool question honest. Sometimes a Copilot licence in Microsoft 365 is enough. The pain sits in drafting, summarising and sketching, and the work already lives in Word, Outlook or Excel. Then the next step is not a build. You use the licence where the process already lives, with a clear rule about which data must not go into the chat.

Sometimes the process is the hand-over between systems: source A into system B, same shape every week. Copilot inside a document does not change the transfer. Then you need a built workflow, and you choose the tool after the four questions, not after a vendor pitch.

You do not need a feature list of integration platforms here. Leave bexio or Abacus in place even when a gap sits next to them. Name the gap and keep the software you already have. Replacing the accounting software, or the fiduciary, is not a first step.

A made-up example: five exports, or the customer

• If five exports are due every Monday

  Someone pulls them from three tools, pastes them into Excel, deletes rows, checks totals, and sends the file to two people. Just under an hour, longer when something is wrong. On holiday, the report waits. It repeats, it hurts, it has an end, and the data already sits in the tools. That is a candidate.

• If a customer is unhappy

  The tone is sharp, the complaint may or may not be fair, and someone from management has to hold the conversation. It is different every time. What counts is judgement. That is not a first case.

• If the Monday report sounds familiar

  Two siblings often sit next to it: invoices that stall beside the accounting software, and quotes that die in the inbox. The same four questions, a different weekday.

The same filter in 60 minutes

If you have already sorted internally and one candidate is clear, bring it. If three processes all hurt, bring all three. In the session we narrow them down to one.

The result: a short description (what, who, how often) and an indication of package size. No tool sale in the session. What the check covers, and what it does not, is on the Process Check page.