Make consulting for SMBs.
An order comes in via a form and has to reach the CRM, accounting and the right team — depending on what it says. Branching flows like that can be modelled clearly in Make, without a server of your own. We build the scenarios, keep an eye on usage and look after them day to day.
What we do with Make
Consulting & concept
First the question of whether Make is the right tool or whether n8n or Zapier fits better. Then: which processes are worth automating and in what order.
Building scenarios
We build the scenarios in the visual editor, with routers, filters and error routes, test them with real data and document what happens where.
Usage & cost
Make bills by usage. A clumsily built scenario that polls empty every minute costs money for nothing. We build so that only what needs to run actually runs.
Operations & monitoring
A scenario that fails silently at night is worse than none. We set up error handling and notifications and step in when something gets stuck.
Connecting your systems
CRM, ERP, mailbox, shop, accounting. Where Make has a ready-made module we use it — where it does not, we connect via the HTTP module, webhook or API.
Handover & migration
On request we train your people until they maintain their own scenarios. And if volume or data protection eventually point to n8n, we move the flows there.
What Make is particularly good at
Make, formerly Integromat, shows a flow as a chain of modules on a canvas. Branches, loops over lists and data transformations are visible there instead of having to be imagined. That keeps scenarios understandable for people who did not build them.
The price for that is usage-based billing. Every step of a run counts. At a few hundred runs a month that barely matters, at tens of thousands it does. So we work out the usage beforehand and tell you at what point a self-run n8n pays off.
And honesty requires this too: Make is a cloud service. Your data runs through the provider's servers. For many flows that is unproblematic; for staff, patient or client data you need to look more closely. We do that with you before the first scenario goes live.
Common questions about Make
Make or n8n?
Make is quicker to get going: no server, a very clear visual editor and a large library of ready-made modules. n8n is the better fit when data must stay on infrastructure you control, when volumes are high enough that usage-based pricing hurts, or when you need a lot of custom code. We compare the three tools on our workflow automation page.
Make or Zapier?
Zapier has the larger app catalogue and is the easiest start for simple, linear chains. Make shows its strength as soon as a flow branches, loops over lists or transforms data in detail — and it tends to be cheaper at medium volume. For many businesses both would work; then the tools you already use decide.
Where is our data processed with Make?
Make is a cloud service, so your data runs through the provider's infrastructure. When an organisation is created, a hosting region is chosen; we check with you which region your account uses and whether that suits your data. A workflow that calls further services also sends data to wherever those services run.
Who owns the Make account?
You do. We set up the organisation in your name or work in your existing one. That way scenarios, connections and billing stay with you, even if you ever stop working with us.
What does Make cost?
Make bills by consumption, in tiers with a monthly allowance. What that means for you depends on how often your scenarios run and how many steps they have. We estimate the usage before building and design the scenarios so the allowance is not burned on empty runs.
Related services
These service areas are often used together:
Which process eats the most time at your place?
Name one. In the first call we tell you whether automating it is worth it and with which tool — even when the answer is no.
