n8n vs Make vs Zapier for client work: which to build on

Most "n8n vs Make vs Zapier" articles are written for a company choosing a tool for itself. You have a different problem. You are building for someone else, you will hand it over, and when it breaks in six months, the client will call you, not the vendor.

That changes the answer. Raw power matters less than four things: who pays for the tool, whose account the workflows live in, whether the licence lets you run it the way you planned, and whether the client can survive without you.

Quick definitions before we start. Zapier and Make are cloud automation platforms you rent by usage. n8n is a workflow tool you can rent as n8n Cloud or run yourself for free as the Community Edition, under a "fair code" licence called the Sustainable Use License. A handover is the moment the client takes ownership of what you built.

Which tool is best for client work? The short answer

Zapier is the easiest to hand over, Make is the best value for visual, mid-complexity flows, and n8n is the cheapest at high volume and the most flexible for custom logic. Pick by the client, not by your own preference.

A top comment in a ranking r/n8n comparison thread sums up the trade: n8n's biggest advantage is price, but for a system that cannot stop or a big client, Zapier or Make "could be better. Because if something happens, you have at least a support. On n8n you are on your own."

How do Zapier, Make and n8n charge, and what does it mean for your quote?

They count usage in three different units, and that decides which one is cheap for a given client. Zapier counts tasks (each successful action step), Make counts credits (most module actions), and n8n counts executions (one full run of a workflow).

Sources: Zapier pricing, Make pricing and n8n pricing, all checked October 31, 2026. Make's page states a single scenario run can use anywhere from 2 to thousands of credits, so always estimate from a test run.

A worked example (our illustration, not a quote)

Say a client's lead flow has a trigger plus 4 action steps and runs 2,000 times a month.

1. Zapier: the trigger is free, so 4 tasks per run times 2,000 runs is 8,000 tasks a month. That is well past the 2,000 task Pro tier listed at $49/mo billed yearly, so you would price a higher tier.
2. Make: roughly 4 to 5 credits per run, so 8,000 to 10,000 credits a month, well beyond the free plan's 1,000.
3. n8n Cloud: 2,000 executions, which fits inside Starter's 2,500 at €20/mo billed yearly.

The pattern holds generally: the more steps and runs a workflow has, the more n8n's per-execution billing pulls ahead. For a 3 step flow that runs 200 times a month, the difference is small and ease of handover should win.

Whose account should the client's automation live in?

Build in an account the client owns and pays for, and add yourself as a collaborator. That keeps the workflows, the app connections and the bill in their name, which protects both of you.

If the automation runs in your account, you quietly become a hosting company: you carry the subscription, you own their credentials, and if you part ways, the workflows leave with you. In the shared VPS thread on r/n8n, one of the most upvoted replies was simply: "I just have the clients setup n8n on cloud and pay for it."

How this looks per tool:

• Zapier: client opens Pro or Team; Team adds shared app connections so teammates do not swap passwords or API keys.
• Make: client opens the account and invites you to their organization.
• n8n: client opens n8n Cloud, or you install the Community Edition on a server in the client's name.

Tip: Put tool costs in your proposal as a line the client pays directly. Your fee covers the build and the care plan, not their software bill.

Can you host n8n for clients on your own server?

Not as a shared service clients log into. The n8n Sustainable Use License says you may use or modify the software "only for your own internal business purposes or for non-commercial or personal use," and may only distribute it to others free of charge for non-commercial purposes (licence text on GitHub).

There is a grey zone. In an n8n community thread, a consultant relayed a help center answer saying there is no limit on clients served from one Cloud instance "as long as clients do not interact with your n8n instance." Reselling access, white-labelling or giving clients the editor is not allowed.

Reddit is less relaxed. On a post about running 6+ paying clients on one VPS, replies included "You are violating the license. Each client needs to be on their own server" and "This is a TOS violation and a serious security risk," because one compromised credential could expose every client.

The clean options:

1. One n8n Cloud account per client, paid by the client.
2. Community Edition on the client's own server, which they own and you maintain under a care plan.
3. A commercial licence from n8n if you truly want a multi-client platform. Ask license@n8n.io in writing.

What breaks when you self-host n8n for several clients?

Shared servers fail in ways a single client never sees: one client's workload takes down another's, and the error alerts die with the server. The r/n8n thread on running 6+ clients on one VPS is a list of these.

• Out of memory kills. One commenter warned that a huge file or JSON array can spike RAM until Linux kills the container, and then "your built-in n8n error workflow will not fire because the container is already dead." Their fix was an external watchdog that pings Slack.
• Noisy neighbours. Another spent a week chasing dropped webhooks for one client, caused by a different client's 2 minute polling loop, until they switched to queue mode.
• Lost encryption keys and changed webhook URLs, called "classics that everyone learns the hard way."
• Cost surprises. In the ranking r/n8n comparison thread, one builder said a self-hosted client project's "server + licensing costs ended up way higher than Zapier's enterprise plan," and valued Zapier's predictable bill.

If you self-host anyway, keep one instance per client, back up the encryption key, and monitor from outside the server.

Handover and maintenance: which tool can the client live with?

The tool the client's staff can read is the one that survives. A top reply on an r/automation thread about handovers to small businesses put it as: "The best automation is the one people can actually keep using without calling someone every week."

The same thread had a 30 year small business owner calling Make's interface hard for non-developers and saying automations break when Word, QuickBooks or Outlook update. Another builder said "Make is fine for small business if someone builds it for them... n8n is probably too much." So whichever tool you pick, plan for breakage:

• Log every run to a simple sheet with time and status, as one commenter in the shared VPS thread recommends, so you can see when something silently stopped.
• Add error alerts that reach you before the client notices.
• Write a one page handover note: what each workflow does, which accounts it uses, how to pause it.
• Sell a monthly care plan, because apps change and flows will need fixing.

The AI Automation pack has a pre-handover test list and a care plan menu you can copy, built from these same threads.

How to choose a tool for a specific client

Answer five questions in order, and the tool usually picks itself.

1. Who will touch it after handover? No one technical: Zapier or Make. An IT person: n8n is on the table.
2. How many runs and steps? Estimate monthly runs times action steps. Thousands of tasks a month on long flows points to n8n.
3. Any data rules? Health, legal or finance data that must stay in house points to self-hosted n8n on the client's server.
4. Which apps? Check each tool's integration list for every app. A missing connector means custom HTTP calls, which non-technical clients cannot maintain.
5. What can you support? Only promise uptime on a stack you can debug at short notice.

Mistakes freelancers make when picking a platform

Most problems come from choosing the tool you like, not the one the client can own.

• Running clients in your own account. You end up paying their bills and holding their data.
• Shared self-hosted n8n for everyone. Licence risk plus one failure taking down all clients.
• Quoting before a test run. Make credits and Zapier tasks vary by workflow; build a prototype, read the usage, then quote.
• No monitoring after launch. Silent failures are how retainers end.
• Free detailed scoping. A detailed free plan is easy for a client to hand to someone cheaper; charge for scoping.

For the selling side, pricing and first clients, see how to start an AI automation agency with no experience.

Where to go from here

1. Open free accounts on Make and Zapier and a trial of n8n Cloud, and build the same 4 step flow in each.
2. Note the usage each run consumed, so you can quote with real numbers.
3. Pick a default tool for your niche, and keep one alternative for high volume clients.
4. Write your standard terms: client owns the account, you are a collaborator, care plan is separate.
5. Make three proof projects and start pitching.

The AI Automation pack adds the full lessons, proposal templates, the hours saved pricing calculator and the handover checklists for $19, and all 16 Money Printer packs are $39. Results depend on your niche, skills and consistency, and nothing here is an income promise.