€300 a month, cancel any month
Automation is not a project you finish. Things break, formats change, somebody renames a folder. This is the arrangement for keeping it working — and for getting a little more of it every month.
Why a subscription rather than a project
Most automation work we see fails the same way: somebody built something clever, it ran for eight months, then a supplier changed their invoice layout and nobody owned the problem. The script is not the hard part. Keeping it alive is.
So instead of selling you a project and walking away, we stay on the hook for what we built, and we keep adding to it in small pieces you can actually absorb.
Who it is for
This works best when there is already something to look after — usually after a proof of concept, sometimes after inheriting automations somebody else built.
- You have more than one thing worth automating — a queue of small annoyances rather than one big project.
- You want it to keep working — without opening a new project, getting a quote and waiting, every time something shifts.
- You would rather spend a little every month — than a lot once a year.
What €300 a month covers
- One new small automation each month — you choose which. If you skip a month, we will happily do something bigger the next one.
- Monitoring — we watch the things we built and notice failures before you do.
- Upkeep and fixes — when an integration changes, a format shifts or a credential expires, that is on us, not on your team.
- A 30-minute review each month — what ran, what broke, what is worth doing next.
- Cancel any month — no notice period, no clawback. What we built keeps running.
What it does not cover
It is a fair-sized monthly slot, not an unlimited one, and pretending otherwise would just end in an awkward conversation.
- Larger automations — anything beyond the monthly slot is quoted separately, and always before we start it.
- New products — if the answer is an application rather than an automation, that is a custom build, typically €12,000–25,000.
- Someone else's systems — we can take over automations we did not build, after a look at them. Sometimes the honest answer is that rebuilding is cheaper than adopting.
Practical questions
What counts as one "small" automation?
Roughly a day or two of work: a report that assembles itself, a form that files itself, a notification that reaches the right person, a handover between two systems that currently happens by copy-paste. If what you want is bigger, we will say so and price it before doing anything.
What if nothing breaks in a month?
Then you get the new automation and a short review, and we have a quiet month. That is the deal working as intended, not you overpaying.
Can we pause instead of cancelling?
Yes. Monitoring stops while paused, and the automations keep running — they just have nobody watching them.
What tools do you build on?
Whatever fits and whatever you can live with: n8n, Make, Python, or straight into the system you already pay for. We will tell you which parts create a dependency on us, because some do.
Do we need the proof of concept first?
No. If you already know what you want automated, we can start here.
Bring your list
Twenty minutes, your three most annoying manual jobs, and we will tell you whether the monthly slot covers them.