Automating business processes: a guide for small and medium-sized businesses

What does process automation mean in everyday work?

An enquiry arrives by email. Someone reads it, finds the contact in the CRM, copies details into a spreadsheet and creates a task. Each application works. Connecting them is still manual work.

Automation connects these steps. It recognises a defined input, checks the required information and performs authorised actions. When an exception occurs, it stops or refers the case to the responsible person. Simply storing a document digitally is not yet an automated process.

Which tasks can be automated?

• Capture enquiries, match them to a contact and identify missing information.
• Read information from known document types and check it before importing it.
• Send approvals to the responsible person and remind them of pending decisions.
• Synchronise customer data or status changes between CRM, ERP and other applications.

Good candidates recur, have similar inputs and lead to an identifiable result. Ask about the last difficult case too: missing information and unusual workflows reveal where manual review is still needed.

When is preparation more important than automation?

If the goal is unclear or nobody can decide which data is authoritative, clarify that first. Rare one-off tasks, constantly changing workflows and errors that are difficult to correct also argue against immediate implementation.

Sometimes a better template, a required form field or a clear responsibility is enough to start with. I consider these options rather than automatically proposing new software.

Workflow, integration, custom software or AI?

These components can be combined. I might use n8n for the workflow and add a custom interface for handling tasks. What matters is what the task requires and what your existing systems reliably support.

How do you choose the first process?

Compare frequency, manual effort, data quality and known exceptions. Also check whether the required access is authorised and available. The largest theoretical time saving is not always the best starting point.

My Process Score helps you discuss eight prerequisites of a specific workflow. It is a practical guide, not a scientifically validated assessment. Missing access or serious error consequences take priority over a high overall score.

What does a usable workflow need?

A case needs an identifiable status. That includes intake, checks, any approvals and the confirmed result. The labels in the example mean: RAW for intake, RULE for defined rules, AI for a possible AI step and HUMAN for a human decision.

Before actions that change data, I establish what happens on a retry. Reading a file twice is usually less serious than sending a proposal twice. If confirmation is missing, the workflow must not simply report success.

When does AI help, and when are rules enough?

Required fields, calculations and unambiguous matching usually need no AI. They follow known rules. AI can be useful when a step needs to interpret differently worded messages or read information from varying document layouts.

I keep these tasks limited and plan how their results will be checked. A correctly formatted record can still contain incorrect information. Where there is uncertainty or a binding decision, a responsible person remains part of the workflow.

What do concrete solutions look like?

• Enquiry to proposal: find contact details, prepare a draft and obtain approval before sending.
• Document to CRM: read information, check it and match it to an unambiguous record.
• Approval and follow-up: manage responsibilities, deadlines and reminders in a visible workflow.

These examples describe possible solutions, not completed client projects or measured savings. Which parts fit your business depends on your data, rules and applications.

What does implementation cost?

A reliable quote needs a defined scope. I review the systems involved, the data and the exceptions. We then agree the deliverables, cost and schedule. A fixed figure without that groundwork would not be useful.

In addition to development, licences, hosting and support may incur costs. Your own time for questions, access and acceptance also belongs in the plan. These items should be clear before commissioning the work.

How much work does the process take today?

Record the number of cases, the manual minutes per case and the internal hourly cost. The calculator uses these to estimate current effort. It does not predict how much of that work will actually disappear.

A financial assessment must account for remaining approvals, exceptions and operating costs. Time freed up is not automatically a cash saving either. It may, for example, be used to handle work more carefully.

Which exceptions need to be considered?

• An enquiry or file arrives twice.
• A target system is temporarily unavailable.
• Required details are missing or inconsistent.
• An approval refers to a version that has since changed.
• The responsible person is absent or access has expired.

For these cases, we establish when the workflow stops, retries or creates a task for review. Someone also needs to be responsible for handling those tasks. An error log alone does not solve the problem.

What needs to be clarified about data and access?

Before implementation, I establish where data goes, which providers are involved and which permissions are needed. Storage, deletion and responsibilities are included. I do not need customer data, passwords or confidential documents for an initial enquiry.

If personal data is processed, the specific operational and legal requirements need to be reviewed. A server location alone does not answer every question about privacy and permitted processing.

How does an automation project work?

1. Review the task: document the current workflow, data, systems and open questions.
2. Define the scope: agree the result, boundaries, costs and acceptance criteria.
3. Implement: develop rules, connections and any required interfaces.
4. Check: test typical cases, exceptions and, where agreed, a limited pilot.
5. Hand over: explain operation, documentation and responsibility for running the solution.

Timing and sequence depend on the project. Missing access and external approvals are real dependencies that I identify before the start. Support after handover is agreed separately.

What makes a good first project?

Choose part of a process that is useful on its own. A prepared proposal draft can already help while review and sending deliberately remain manual. This lets you assess the implementation against a manageable result.

What can you prepare for an initial enquiry?

• What starts the workflow, and when is it complete?
• Which applications and people are involved?
• How often does the case occur, and what is done manually?
• Which exceptions or questions occur regularly?
• What should change after the improvement?

A few sentences are enough to start. I review with you what information is still missing and whether a sensible scope can be defined.