AI automation for your business: start with these 5 processes

To start with AI automation in your business, you need one process that takes up time every week, not a strategy document. Adoption is underway. According to Eurostat data, about a third of businesses with ten or more employees used at least one AI technology in 2025: 34.5 percent in Belgium and 33.2 percent in the Netherlands. A year earlier, it was about a quarter. For a small or midsize business in Belgium and the Netherlands, the first hurdle is often practical. Which business process should you automate first, and what should you keep in your own hands?

Dark interface with glowing blue lines connecting gear, cloud, and document icons in a workflow
From manual steps to automated workflows.

This article covers five processes that are common candidates for a first pilot: the weekly report, product descriptions, document review, follow-ups and reminders, and CRM updates. You will also see how to set up each pilot and where people stay in control. We will not promise time savings nobody has measured. Those only count once you can measure them yourself.

AI automation: which process should you choose first?

Start with a process that comes back every week, has a clear input and result, and involves a lot of copying or searching. Pick one such process. If you test five processes at the same time, each gets too little attention. Give that one process a pilot of its own for a few weeks. We explain why in our article on starting with one frustrating workflow. Frequent and predictable is a better starting point than rare and exciting.

The best candidates:

  • come back every week or month

  • have a clear scope, with defined input and a defined result

  • involve a lot of copying, pasting, or searching

  • need context that exists only inside your business

Starting small is not a lack of ambition. Gartner predicts that more than 40 percent of agentic AI projects will be canceled by the end of 2027. The reasons it gives are rising costs, unclear business value, and inadequate risk controls. "Most agentic AI projects right now are early stage experiments or proof of concepts that are mostly driven by hype and are often misapplied," said Anushree Verma, Senior Director Analyst at Gartner.

Avoid starting with tasks that rarely occur, tasks where every exception needs a judgment call, and anything that needs a human signature by law. A rare task that demands a lot of judgment can create more discussion than value. Consider it only after an initial pilot has shown that people and the agent can work together reliably in your business.

These five processes are common candidates for a first pilot across different industries. Here is what they look like as manual work and with an AI agent:

ProcessManual workWith an AI agent

Weekly report

Open three sources, copy the numbers, and format the report

The agent retrieves data and prepares a draft

Product descriptions

Write, review, and publish each description

The agent edits a draft in your tone of voice

Document review

Read and check every document in full

The agent summarizes and flags discrepancies

Follow-ups and reminders

Track deadlines and send reminders manually

The agent sends them on time, after approval

Updating your CRM

Retype information one field at a time

The agent fills in missing fields

Automating business processes with AI: the 5 processes in practice

A table shows what changes, but not how to get started. Here is how to set up a pilot for each process, including the points where a person decides.

  1. 01

    The weekly report

    The same sources, the same numbers, every Monday. An agent retrieves the data, builds the report in your template, and flags values that differ from the previous week. You check the flagged items and send it. Keep the pilot small: one report, one source, and four weeks alongside your existing process before expanding. At Voltti, this is how it works with our own search data. Our Hermes installation reads the Search Console numbers through read-only access. The agent lines them up by page and suggests which pages need attention first. People set the goals and review the work.

  2. 02

    Product descriptions and copy

    The agent writes a draft in the tone of your existing copy and suggests improvements to structure and wording. At first, you review every piece yourself. Only after that works consistently do you give the agent more room. Publishing permissions are agreed separately. In Voltti's own CMS, the agent sometimes publishes directly. We review the result afterward and make corrections where needed.

  3. 03

    Document review

    Checking contracts, quotes, and invoices for discrepancies takes care, and few people enjoy it. The agent reads each document, summarizes it, and flags unusual amounts, dates, or clauses. A person decides what to do with each flag; the agent supplies the list. To see how an agent also finds answers in your own documents, read search internal knowledge with an AI agent.

  4. 04

    Follow-ups and reminders

    Quotes waiting for a reply, overdue invoices, and customers expecting an answer. The agent monitors deadlines and prepares a reminder at the right time. You approve the tone in advance, then the agent sends messages under the agreed rules. Each message is logged so you can review it afterward.

  5. 05

    Keeping your CRM up to date

    Retyping information from emails and forms into a CRM is repetitive work. The agent extracts names, companies, and status changes from the source and fills in missing fields. Each change goes into the log so you can see what the agent changed and reverse it if necessary. Our article on connecting AI to your CRM and CMS explains which integrations make sense.

Implementing AI in your business: from pilot to everyday use

A pilot usually follows five steps:

  1. Choose one process together.

  2. Decide which steps are fixed and which need flexibility.

  3. Connect only the systems the process needs.

  4. Test in a bounded environment.

  5. Roll out only after explicit approval.

Predictable, repetitive steps can use a fixed script. Work that differs each time needs a flexible agent that can adapt. We explain the distinction in our article on automating recurring tasks.

Measure before you start. Write down how much time the process takes each week and how often someone has to fix a mistake. Track the same two numbers during the pilot. At the end, for example after four weeks, compare them. That comparison, not a vendor's estimate, tells you whether to expand.

Looking for outside funding for a first project? Our overview of public grants and support for AI lists the official programs in Belgium and the Netherlands.

Here is how we work ourselves: content work at Voltti starts with a ticket that our own Hermes installation picks up. The agent reads the task, carries it out, and records the verification. It edits directly in our CMS and sometimes publishes; we review the work afterward and correct it where needed. For pilots at businesses in Belgium and the Netherlands, we agree those boundaries in advance. The agent does the work, while people remain responsible for goals, claims, and publishing rules. For a step-by-step account of a pilot, see our approach page.

What goes wrong in a first AI automation pilot?

A first pilot usually stalls on four points: too many processes at once, no baseline, too much access, and review without an owner. Each one has a simple fix.

Testing several processes at once. None of them gets enough attention, and you cannot tell which change made the difference. Pick one process to automate first.

Skipping the baseline. Without the numbers from before the pilot, nobody can say whether it helped. Write them down in the first week.

Giving the agent more access than the process needs. Connect only the systems and permissions the task uses. Our page on security and privacy shows how we limit access per connection.

Leaving the review without an owner. If nobody is responsible for checking flagged items, they pile up. Name one person before the pilot starts. That person also keeps the team informed about what the agent does.

Start next week with one process, rather than next quarter with a plan for ten. Not sure which to choose? Our services for AI automation for businesses have their own page. If you first want to understand what an agent can do, start with our introduction to AI agents.

For more specific examples, see how an AI agent prepares quotes and SEO with an AI agent.

Portrait of Seppe Gadeyne

Seppe Gadeyne is a developer and the owner of Voltti. He sets up AI agents for companies in Belgium and the Netherlands.

Updated on

Frequently asked questions

01Do I need to automate all my processes?

No. Start with one process that takes up time every week and run it as a pilot for a few weeks. Once the pilot shows that it works, and you have the numbers to back that up, you can add a second process. Expanding step by step keeps each change easy to check.

02Which software can I connect?

Software with an API, or sources Hermes can read directly, may be suitable: a CRM, CMS, project management tool, or document source. We assess whether each integration is useful and safe, including its permissions and limitations. The agent only gets access to the systems and data the chosen process needs.

03How long does it take to automate a process?

A pilot usually takes 2 to 4 weeks, from the first conversation to the evaluation. Simple steps with one source go faster. Integrations with several systems, or steps that need approval rules, take longer. During the pilot, the agent works alongside your current process, so you can compare the numbers from before and during the pilot.

04What if the automation goes wrong?

Hermes asks for confirmation before high-risk actions. Testing is intended to catch errors before rollout, and logging lets you check what happened afterward. Testing will not catch every error, so a person keeps reviewing the output during the pilot. Changes in a system like a CRM can be traced in the log and reversed.

05What does AI automation cost?

That depends on the process, the integrations, and which steps are fixed or flexible. Voltti therefore provides a custom quote after a pilot discussion; we do not use a standard monthly rate. In that discussion, we look at one concrete process first, so the quote matches the work you want to automate.

Which process do you want to automate?

Discuss your pilot