SolutionsPricingWorkshopsBlogNewsAboutLet's Talk

Business Automation Workshop: Preparation and Success Guide

How to prepare and run a business automation workshop that delivers results. What to prepare in advance, how to choose the first process, and what happens after.

AutomushPublished 10 min read

A business automation workshop is a focused working session where the business selects one process, builds it with automation tools, and sees it running by the end of the day. It is not a lecture or strategic planning – it is hands-on building, with real data and real systems, so the business leaves with something that works.

We run workshops like this with businesses that want to start with automation but do not know where to begin, or have already tried on their own and got stuck. The workshop focuses on one process that repeats often, takes time, and involves manual copying of data between systems.

Why run a business automation workshop instead of just starting to build?

A business automation workshop forces the business to choose one process and finish it on the same day. Without this, most attempts to start with automation end halfway – you start building something, discover you are missing access to a system, move to a different process, and after two weeks nothing works.

In a workshop there is a fixed schedule, a clear goal, and someone leading the build. The business arrives prepared with access and data, we build the process in real time, and by the end of the day there is an automation running. This is not a prototype – it is something the business can leave switched on and use the next morning.

The workshop also exposes where the real problems are. Sometimes you discover that the process you chose depends on a field that does not exist in the CRM, or that the data arrives in a format that changes every time. Instead of discovering this after two weeks of working alone, you discover it in the workshop and solve it on the same day or decide to move to a different process.

What do you need to prepare before the workshop?

Before a business automation workshop, the business needs to choose one process and prepare access to the systems involved in it. If the workshop is about an automation that moves leads from a form to a sheet and sends a WhatsApp message, you need admin access to the form, access to the sheet, and an approved WhatsApp Cloud API account.

The process you choose should be something that repeats at least a few times a week, is currently done manually, and can be described in three or four simple sentences. “When a new lead arrives, we copy it to a sheet, send them a welcome message on WhatsApp, and update the status to ‘new’” – that is a suitable process. “We want to improve the customer experience” – that is not.

You also need to prepare a real example of the data. If it is a form, you need to know what the response that arrives from it looks like. If it is a sheet, you need to know which columns hold the name, phone, and status. In the workshop we do not build on assumptions – we build on the data that actually flows through the systems.

If the business works with a CRM or other management system, you need to confirm that API access or an integration is available. If not, you can work with Google Sheets as an intermediate layer – it is not ideal for the long term, but it is enough to build the first process and see it working.

Which process should you choose first?

The first process in a business automation workshop should be something that repeats often, takes measurable time, and involves at most three systems. If you choose something too complex, the workshop turns into a project, and by the end of the day nothing works.

Good processes for a first workshop:

  • Moving leads from a form or WhatsApp to a sheet or CRM, with automatic sending of a confirmation message
  • Updating a lead status in the CRM when a reply arrives on WhatsApp
  • Sending an automatic reminder to leads who have not replied within 48 hours
  • Issuing an invoice through Morning (Green Invoice) when a deal is marked “closed” in the CRM
  • Sending a daily report to WhatsApp with the number of new and open leads

Each of these processes can be built in a half-day workshop, tested with real data, and left running. After the first process works, you can build the second and third – but not in the same workshop.

Process type How long to build Suitable for first workshop?
Moving leads between two systems 2–3 hours Yes, ideal
Sending automatic messages based on conditions 2–4 hours Yes
Automatic invoice issuing 3–4 hours Yes, if API is ready
AI agent managing a full conversation 8–12 hours No, too complex for first workshop
Integration with legacy system without API Depends on system No, requires additional development

How do you build the process in practice during the workshop?

In a business automation workshop we build the process in n8n, which is an automation platform that lets you connect different systems without writing code. Every process consists of three parts: a trigger that starts the process (for example, a new lead in a form), actions that process the data (copying to a sheet, checking a condition, formatting a message), and a final action that outputs the result (sending a message, updating a record).

The build starts with the trigger. If the process starts when a new lead arrives from a form, we build a webhook that receives the data from the form. If the process starts when a lead replies on WhatsApp, we build a trigger that listens for incoming messages through the WhatsApp Cloud API. We test that the trigger works by sending real data and checking that it arrives in n8n.

After that we build the intermediate steps. If we need to copy the lead to a sheet, we add a node that connects to Google Sheets and inserts a new row with the correct fields. If we need to check a condition (for example, “if the lead is from a certain area”), we add an IF node that splits the flow. Each step is tested before moving to the next – we do not build the entire process and then discover that step two did not work.

At the end we add the final action – sending a message on WhatsApp, updating a status in the CRM, or issuing an invoice. We test the full process with real data from start to finish, and if everything works – the process stays switched on.

Throughout the build we add error handling. If the WhatsApp API does not respond, the process should not get stuck – it should retry or send an alert. If a field is missing in the data, the process needs to know what to do. This is not “nice to have” – it is the difference between a process that works for two weeks and a process that works for a year.

What happens after the workshop?

After a business automation workshop, the process we built continues to run, and the business sees it working with real data. It usually takes a few days to get used to the process happening on its own, and a few more days to understand what else can be done.

The first process does not solve all the business’s problems – it solves one problem, but it proves that automation works and that more can be built. Most businesses that run a first workshop come back after a month or two to build the second process, and then the third. After three or four processes, the business already knows what it needs and how to prioritize.

Some businesses continue building on their own after the workshop, and some move to managed automation where we are responsible for maintenance, fixes, and additions. Both paths work – it depends on whether the business has someone internal who can manage it or not.

What matters is that the first process does not remain alone. One automation saves time, but three or four automations change how the business operates. The workshop is the starting point, not the end point.

How do you measure if the workshop succeeded?

A business automation workshop succeeded if by the end of the day there is a process that works, the business knows how to run it and check it, and the process continues running the week after. This is not “did we learn something” – it is “is there something that works”.

The first measure is technical: does the process run successfully with real data? If we built an automation that moves leads from a form to a sheet, does a lead that enters after the workshop arrive in the sheet within a minute? If yes – the process works. If not – something broke, and it needs to be fixed before continuing.

The second measure is operational: does the process save measurable time? If the manual process took five minutes per lead, and now it happens automatically, and ten leads enter every day – that is 50 minutes a day, or four hours a week. This is not precise ROI, but it is enough to decide whether to build the second process.

The third measure is whether the business continues using the process after two weeks. If the process is switched off after a week, something did not work – maybe it broke and was not fixed, maybe it did not fit how the business actually operates, or maybe we chose the wrong process. If the process is still running after a month – the workshop succeeded.

Can you run a workshop yourself without external guidance?

You can run a business automation workshop yourself if you have someone in the business who knows automation tools like n8n or Make, and who has time to focus on it for a full day. The workshop does not require programming knowledge, but it does require understanding how systems talk to each other, and how to handle a situation where something does not work.

The advantage of a workshop with external guidance is that we have already solved the common problems. If the webhook is not receiving data, we know where to check. If the WhatsApp API returns an error, we know if it is a permissions issue or a message format issue. If you build alone, each problem like this can stop the workshop for an hour or more.

If you decide to build alone, it is important to start with a very simple process – moving data from point A to point B, without complex logic. After that works, you can add conditions, checks, and additional actions. But if you start with a process that involves five systems and three conditional decisions, the chance that the workshop will end without a working process is high.

How does the workshop fit into a broader automation strategy?

A business automation workshop is an entry point, not a complete plan. It builds one process that works, but it does not plan all the automations the business will need in the coming year. The broader planning happens after the workshop, when the business already knows what can be done and what cannot.

After the first process works, you can sit down and map the rest of the processes that repeat in the business. Where else is there manual copying of data? Where else does someone wait for a response from one system to update another system? Where else are messages sent manually that could be sent automatically? Each of these processes is a candidate for the next automation.

The order in which you build the processes matters. Usually it is best to start with the processes that repeat the most often and are simplest to build, and only then move to more complex processes. If you build in this order, each process saves time immediately, and the business sees results throughout the journey – not just at the end.

Some businesses reach a point where they want to build an AI agent that manages full conversations with customers, or a complex integration between four or five systems. That is no longer a workshop – it is a project that takes weeks. But the workshop is what proves it is possible and that it is worth the investment.

Frequently asked questions

How long does a business automation workshop take?

A typical workshop takes between four and six hours, depending on the complexity of the process you choose. By the end of the workshop there is one process that works and runs with real data. If the process is more complex or involves a system that requires additional setup, the workshop can last a full day.

What happens if the process does not work by the end of the workshop?

If by the end of the workshop the process does not work, we do not leave it halfway. Either we identify the problem and solve it on the same day, or we decide to move to a different process that can be finished. The goal of the workshop is to leave with something that works, not with a task list. If there is a technical issue that cannot be solved on the same day – for example, missing API access that takes a week to approve – we summarize what needs to be done and schedule a continuation after the access is ready.

Do you need technical knowledge to participate in the workshop?

You do not need programming or development knowledge to participate in a business automation workshop. What you do need is familiarity with the systems the business works with – knowing where the data sits, what a typical record looks like, and which processes repeat. We handle the technical part of the build, and the business provides the business understanding and access to systems.

How much does it cost to run a business automation workshop?

The cost of the workshop depends on the length, the complexity of the process, and the number of systems involved. A typical half-day workshop that builds one process costs less than a day of developer work, and the process that is built continues working after that with no additional cost. If the business continues working with us on additional processes, the first workshop is sometimes included in a broader framework.

Interested?managed automation service

From the newsroom

All news

Which of your processes could run on its own?

A free 30-minute discovery call, no commitment. We map your processes together and tell you honestly whether and how automation can help.

Try a call with agent now