Make automations that keep running.

Make is great for connecting tools quickly. I've built Make scenarios for more than sixty clients, and I've also seen what happens when you end up with fifty scenarios only one person understands. So I build with error handling, monitoring and documentation, and I tell you when something is better off as code.

60+ clients on MakeMonitoring on every scenarion8n and code when that fits better
What I build

What I connect Make to.

Connecting your tools

CRM, forms, email, invoicing, Airtable, Slack: data moving between them without anyone copying it.

Error handling

Scenarios that retry, report and stop cleanly instead of failing in silence.

Audit of existing scenarios

I go through what you have, document it, remove what's dead and fix what's fragile.

AI steps

OpenAI or Claude inside a scenario to sort mail, summarise, extract data or draft replies, with a human check where needed.

Moving to code

Scenarios that have become too heavy or too expensive moved to a small service, with the same result.

These are the most common starting points. Every integration is built around how you work.

Built before

What I've built so far.

Built forIT Installs · Juweelwinkel · LiteZilla · Wilderful · CAI Academy · Happy Wellness Group · Lyfto · Onwise · Einvigi · Hilden & Kaira · Subsidie Advies Nederland

How I work

How a project runs.

A conversation first

We go through how the work runs today and what the integration has to do. Every company does this differently, so I don't start from a template.

A fixed, one-time price

You get one price for the build. No monthly licence for something that only needs looking at when a system changes.

I build it and keep it running

I build it, host it if you want me to, and keep an eye on it. The code is yours, so you're never locked in.

Your data

How your data stays safe.

Only what's neededThe integration only gets access to the data it needs for the job, and read-only access where that's enough.

Keys stay out of sightAPI keys and tokens live in an encrypted server environment, never in a spreadsheet or a shared document.

Hosted in the EUI run integrations on servers in the EU unless you prefer your own environment.

Not used to train AIWhere AI is involved, I use the business APIs of OpenAI or Anthropic. Your data is not used to train their models.

Questions

What people ask about Make.

Make or n8n?

Make is quicker to set up and easier for your team to read. n8n can be self-hosted, which helps with costs and data location. I use both and advise per situation.

Can you take over scenarios someone else built?

Yes. I start with an audit, so we know what runs, what it depends on and what can go.

Who keeps an eye on it?

I set up alerts, so failures come to me or to you, whichever you prefer.

Do I pay a monthly fee?

No subscription to me. You pay once for the build. If a system changes its API later, or you want something extra, I'll quote that separately. Hosting is usually a few euros a month, at cost.

Who owns the integration?

You do. The code is yours, and so are the accounts it runs on if you want that. You can hand it to another developer at any time.

What if something breaks?

I add monitoring to every integration, so I usually see a failed run before you do. When something does stop, I fix it quickly.

Related

Often connected together.

Want Make connected to your other systems?

Tell me what runs where today and what should happen automatically. I'll tell you what's possible, how I'd build it and what it costs.

Book an intro call
© 2026 QuikCode · software for better operations