Business process automation

Business process automation

The hours lost in a company rarely go into the actual work: they go into moving information from a form into a spreadsheet, from the spreadsheet into an email and into the calendar. Process automation removes that path.

What it solves

  • The same data, entered three times, in three places.
  • A forgotten step only shows up at the client, and the fix stays unseen.
  • Where things stand and "how it's done" live in one person: if they're away, it stops.
  • Every new client brings hours of admin.

What you get

  • The process map, documented and yours
  • Automations on top of your existing apps
  • An instant notification on every failure
  • Changes to the process, included in the subscription

How it's built

  1. 01

    We map the real process

    Not the one in the job description, but the one that actually happens. It usually turns out there are two or three parallel processes, not one.

  2. 02

    We pick the points worth automating

    A step that takes two minutes but happens forty times a week takes priority over one that takes an hour and happens once a month.

  3. 03

    We build and connect

    The system connects to your existing apps via API or webhook. We don't change the tools you work with unless one of them is genuinely getting in the way.

  4. 04

    We run in parallel, then hand over

    At first, the automation runs alongside the manual process, so any differences are visible. Only once there are none does the manual version stop.

When it doesn't fit you

  • The process changes with every client, for real reasons: then you don't have a process, you have a craft.
  • The step that would be automated happens twice a month. It costs more to build than to do.
  • Nobody knows who does what. A system laid on top of the tangle only speeds it up.

If one of these cases comes up on the call, we tell you then, not after you sign.

The price depends on how many apps get connected and whether they have an API, on how many exceptions the process has, and on who holds it right now. See the packages →

Want a figure now? Pick the modules in the configurator and see the price on the spot.

Questions · Process automation

Do I have to change the apps I use?

Generally, no. We build on what you already have: calendar, email, spreadsheets, CRM, invoicing software. We only suggest a change when a tool genuinely blocks the automation, and we tell you exactly why.

How long until I see the first result?

The first automated workflow usually goes live within 2 to 4 weeks of the 30-minute call, depending on complexity. The rest is added one piece at a time, so we never have to stop the business to install something.

What happens if my process changes six months from now?

Changes are included in the monthly subscription. A system that can't change becomes an obstacle, not a help: that's why we don't just sell an installation and leave.

What happens if the automation gets something wrong?

You get a notification on every failure, saying exactly what broke. That's the practical difference from a bad manual process: there, the mistake is discovered by the client; here, you know the minute it happens. Nothing runs silently.

Do I become dependent on you?

The process map and the documentation stay with you, in a form a person can read. If you work with someone else tomorrow, they have somewhere to start. We don't hold your process hostage in a format only we understand.

I only have three employees. Is it too early?

It depends on how many times a week the step repeats, not on how many of you there are. A three-person business handling forty requests a week has more to gain than a fifteen-person one handling five. On the call, we count repetitions, not employees.

We build with
  • n8n
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • Node.js
  • Supabase
  • PostgreSQL
  • Anthropic
  • Google Cloud
  • Meta
  • Telegram
  • Resend