Process design
Before connecting anything, we map how it's done today and how it should be done. Automating a messy process just makes it messy faster.
We connect your ERP, your email and the rest of your software so data moves from one system to another on its own. Every workflow is documented and raises an alert when it fails.
An order arrives by email and someone types it into the ERP. An invoice is downloaded from one portal and uploaded to another. It's work that adds nothing, and where one slip ends in an error.
Setting up an automation takes an afternoon. Keeping it working a year from now is another matter: someone has to find out when it stops, and it can't depend on whoever built it.
We work with n8n and Make, and we use them every day in our own operations.
Before connecting anything, we map how it's done today and how it should be done. Automating a messy process just makes it messy faster.
Make when it makes sense to start quickly with no server to maintain. n8n when you want the workflows and the data to run on a server of yours or ours.
Odoo, Microsoft 365, Google Workspace and any software with an API. We write down which account each connection uses and with what permissions.
Classifying an email or pulling the data out of an invoice are just more steps. AI comes in where something needs reading. Everything else is still a fixed rule.
Every run is logged. If a workflow fails or is switched off, the alert goes to a channel someone actually watches, with the steps to restart it.
Software changes and credentials expire. We review the workflows and adapt them when one of your systems is updated.
A free one-hour session to find the tasks that keep repeating and choose which one to start with.
Which workflow gets built, which systems it touches and what happens when something fails. All in writing and at a fixed price.
In a test environment and with the awkward cases: the order with no reference, the duplicate invoice, the attachment that never arrives.
The workflow runs for a few days in parallel with the manual process, until both give exactly the same result.
It's left with the alerts switched on and the documentation handed over, plus a periodic review on our side.
One agent keeps the accounts up to date inside Odoo, another coordinates projects and another answers with what the company already knows.
A phone and WhatsApp assistant that answers questions, books appointments and hands over to a person. Under way, in phases.
An AI assistant that runs on a group-owned machine, with cloud models, skills for each company and a private area for each person.
Agents connected to your ERP, support desk and email that answer with your data and leave actions ready for you to review.
Your email, documents and ERP searchable in natural language, with answers that cite their source.
Rules of use, approved tools and training so your team uses AI without exposing data.
ERP and CRM with Odoo: implementation, custom development, hosting and support from a single team.
Make is a cloud service: you get started quickly and there's nothing to maintain. n8n can be installed on your own server, so the data doesn't pass through a third party. It depends on the volume and on how sensitive the data is.
The ones done the same way every time: orders that come in by email, supplier invoices, periodic reports, due-date reminders, adding and removing users. Anything that needs judgement stays with a person, with the information already gathered.
The alert comes in and we fix it. That's why every workflow has logging and alerts from day one, and why we offer maintenance.
Yes. We review them, document what each one does and which credentials it uses, and tell you which to keep and which to rebuild.
No. An automation always follows the same steps. An agent decides which steps to take based on what you ask it. For a fixed process, an automation costs less and is more predictable.
Tell us how it's done today. In an hour you'll know whether it can be automated and what it would take.