−20%

20% off all services

Skip to content

We value your privacy

We use necessary cookies to keep the site working and, if you agree, Google Analytics to see which pages are useful. You can change your choice at any time at the bottom of the page. Cookie Policy

Automation

Repetitive work – hands-free.

We hand repetitive processes over to n8n – or to Make, when that is more practical or you already use it. A failure never goes unnoticed: retries, an alert and a log.

PriceBased on scopeBased on scope

(01)

How it works

  • 01

    Retries

    3 automatic retries; with growing intervals where appropriate.

  • 02

    Failure alerts

    A failed workflow never passes silently – you know about it straight away.

  • 03

    Execution log

    Kept, so you can see what ran, when and with which data.

  • 04

    Critical process monitoring

    The most important processes are watched continuously.

  • 05

    Response by plan

    Response – according to your maintenance plan; without a plan, incidents are separate work.

  • 06

    In writing, upfront

    Scope and price – in the proposal, before any work starts. Final prices – VAT not applicable.

(02)

How we work

  1. 1

    Conversation

    We clarify the goal and what you already have. For a system we take over – a technical audit.

  2. 2

    Proposal

    Price, scope and timeline – in writing, before any work starts.

  3. 3

    Build

    Design and code in one team. Later you edit the content yourself.

  4. 4

    Launch

    Basic SEO, analytics and a speed check. After launch – a 6-month warranty.

(03)

Frequently asked

How much does automation cost?

Based on scope: the price depends on the number of processes and how many systems take part in them. After a conversation we put the price, scope and timeline in a proposal.

What happens when a workflow fails?

It is retried up to 3 times, with growing intervals where appropriate. If it still fails, an alert is sent and the execution log keeps a record of what happened.

We already use Make. Do we have to switch to n8n?

Not necessarily. n8n is our main tool, but we use Make when that is more practical or you already use it.

Who fixes it when something breaks?

Response is according to your maintenance plan. Without a plan, incidents are handled as separate work.

(04)

Tools

Our main tool is n8n. We use Make when that is more practical or you already use it.

  • n8n
  • Make

Maintaining your automations

Incident response – according to your maintenance plan. Plans from €149/mo.Incident response – according to your maintenance plan. Plans from €119/mo. −20%

Maintenance plans

Get a free
purchase-journey review.

We look at where visitors drop off on the way to a purchase or an enquiry and tell you what we would fix first. The review is free – no commitment.

What do you need?

Get a free review

We reply within 1 business day.