Business process automation that ends the waiting between teams.
When a process crosses several departments and tools, its delays sit in the handoffs. We map the process as it really runs, automate it step by step without stopping the business, and leave people in charge of the exceptions. Each step is measured before and after, so you see what changed.
The process today
- An order crosses sales, stock and accounting by email
- The same data typed into three tools
- Nobody knows where a request is stuck
- Exceptions handled from memory
- Month-end spent catching up
Once automated
- Each handoff starts the next step on its own
- Data entered once, at the source
- Every request has a status anyone can check
- Exceptions reach a named person, with context
- Month-end starts from clean data
Processes worth automating from end to end.
Four processes that cross several teams, and a real case built one step at a time. The client of the real case is anonymized; sector details are shared in a meeting.
Order to cash
BeforeThe order arrives by email, gets keyed into the ERP, delivery is booked by phone and the invoice goes out at month-end.
AfterThe order is read and created, delivery booked, the invoice issued on shipment and the payment chased on its due date.
Purchase to pay
BeforeRequests by email, approvals in the corridor, supplier invoices matched by hand.
AfterRequests follow an approval path by amount, orders go out, and invoices are matched with the order and the receipt.
Customer onboarding
BeforeThe contract is signed, then a week of forms, accounts and emails passes before the customer can start.
AfterThe signature creates the accounts, sends the welcome email, issues the first invoice and books the kickoff.
Requests and claims
BeforeClaims come in through five channels and wait for someone to sort them.
AfterEach claim is read, classified, completed with the order data and routed, with a deadline everyone can see.
Real case: an operation tooled one wave at a time
BeforeA seasonal business run on paper diaries, shared Excel files and cash, with crews to coordinate across fifteen outings a day.
AfterA booking module first, then online payment, team planning and fleet tracking with maintenance cycles. Each wave added a tool without breaking what worked. Ten years on, the whole operation runs through these tools, and the business absorbed its growth without hiring at every step.
What is business process automation?
Business process automation runs a whole process, such as order to cash or supplier onboarding, through connected software instead of emails and retyping. Each step starts when the previous one ends, data is entered once, and people handle the approvals and exceptions. Task automation speeds up a single step; process automation also removes the waiting between steps.
Automating one task at a time often moves the bottleneck instead of removing it. The invoice gets created faster, then waits three days for someone to send it. Looking at the whole process first shows where the time actually goes: in the handoffs between teams, in the rework after an error, in the requests nobody owns.
The tools follow from that map. A workflow engine such as n8n connects the systems that have an API. An AI step reads what arrives as free text or scans. A small custom screen fills the gap when no existing tool fits, as in the real case on this page. Older systems without an API may need screen robots (RPA), and we say so when they are the only way in.
How a process gets automated without stopping the business.
Week 1
Walk the process
We follow real cases through every team, time each handoff and list the exceptions. You get a process map, the steps to automate first and a fixed price.
Weeks 2 to 4
Automate the first stretch
The steps with the most waiting time go first. Each one runs beside the manual process until your team trusts it.
Weeks 5 to 8
Extend and connect
The next steps join the flow, exceptions get their own path, and a status view shows where each case stands.
After launch
Measure and choose the next one
We compare cycle time and errors with the starting point, then pick the next process with you.
Workflow tool, RPA, custom code or ERP module: how to automate a process?
Four ways to automate the same process, compared on what matters once it runs.
| Criterion | Workflow tool (n8n, Make) | RPA (screen robots) | Custom code or app | ERP module |
|---|---|---|---|---|
| Works best when | Your systems have APIs | An old system has no API | No tool fits the process | The whole process lives in the ERP |
| What makes it break | An API change | A screen change | Little on its own, with upkeep | Upgrades that change the setup |
| Messy input (emails, scans) | Handled with an AI step | Handled poorly | Handled with an AI step | Rarely handled |
| Who can maintain it | A technical person trained on the tool | RPA specialists | Developers | The ERP integrator |
| Tool cost follows | Runs or steps per month | Robots and licenses | Hosting only | The ERP contract |
| How we use it | Our default choice | Last resort, said plainly | For the missing piece | When you already own it |
Why two process automation projects rarely cost the same.
The price depends on the process itself. You receive it in writing, fixed, once the process is mapped and before any build starts. It depends mostly on the points below.
Read the custom software cost guide, with market ranges- 01The number of teams and systems the process crosses.
- 02Systems without an API, which take more work or screen robots.
- 03The share of free text and documents, and so of AI steps.
- 04How many exceptions the process has, and who decides them.
- 05The status view and reporting you want on top.
Process automation: the questions buyers ask us
Which process should we automate first?
The one that runs often, crosses several teams and makes customers wait. Order to cash and supplier invoices are frequent first choices. During the free assessment, we rank your candidates on volume, waiting time and risk, and we tell you when a process is too rare to be worth automating.
Do we have to change our software?
Rarely. Automation connects the tools you already use through their APIs. When a system has none, we look at exports, email or screen robots. A new tool only comes in when nothing you own fits the process, and then it stays small.
What happens to the people who did these tasks?
They stop retyping and chasing, and spend their time on the exceptions, the customers and the decisions the workflow sends them. We involve them from the first week: they know where the process really breaks, and they approve each step before it goes live.
How do you handle exceptions?
Each type of exception has a named owner. The case arrives with its context and a deadline, and the decision is logged. When the same exception keeps coming back, we turn it into a rule, so the pile of cases needing a person gets smaller over time.
Is business process automation the same as RPA?
RPA is one technique among several. Its robots click through screens as a person would, and they break when a screen changes. Process automation connects systems directly through their APIs wherever possible, and reads free text and documents with AI. We keep RPA for old systems with no other way in.
How do we know it worked?
We measure the process before we start: cycle time, handoffs, errors, cases stuck. The same measures are taken after launch, on the same kind of cases, and you receive the comparison in writing.
Your process stays in your hands.
Security and dataMapped with the people who run it.
The map comes from real cases and from the teams who handle them, and they approve it.
Rolled out step by step.
Each step runs beside the manual process until it proves itself. Nothing is switched off overnight.
Documented and owned by you.
Workflows, accounts and documentation are in your company’s name, with an alert on every failure.
Data kept where you decide.
In the EU, in your own cloud or on your servers, depending on the tools chosen.
Measured before and after.
The same indicators, on the same kind of cases, handed over in writing.
In the same family
Also in automation
- AI automation The whole automation practice, rules and AI.
- n8n agency The workflow engine we use most for processes.
- Make and Zapier When your processes already run on these tools.
- n8n vs Zapier vs Make Choose the engine before the process.
- RPA vs AI agents Which steps a robot keeps, and which an agent takes.
- ROI calculator Put a figure on the hours a process costs you.
Where will your team win back its time first?
Tell us which process it is and where it waits. Within one business day, we reply with the steps we would automate first and a time for your free 30-minute assessment.