Make.com consultant cost in 2026, with a rate card and n8n math

Rates for this work are published almost nowhere, which is why most people searching for what a Make.com consultant cost looks like end up on a freelance marketplace comparing a $20 an hour profile against a $200 an hour one with no way to tell what separates them. We build and rescue Make scenarios, we publish our own prices, and we have quoted enough of these jobs to know where the bands sit. Below is the rate card, the fixed prices a scenario build lands at, and the arithmetic that decides whether the work belongs on Make in the first place.

Make.com consultant cost by the hour and by the day

Four bands cover almost every quote you will be shown.

Who you are hiring	Hourly	Day rate
Marketplace generalist, offshore, Make listed among ten other tools on the profile	$20 to $50	$150 to $400
Independent specialist, US or UK, Make is the main thing they do	$85 to $150	$650 to $1,100
Certified Make partner or a small automation agency	$150 to $250	$1,000 to $1,900
Consultancy with a delivery team and an account manager	$250 to $400	$2,000 and up

UK day rates for senior automation contractors run £550 to £1,500, which is what we found reading twenty published agency price lists in August 2026 for our survey of AI automation agency pricing. Make specialists sit in that same band as general automation contractors, because the skill being paid for is systems thinking, and the canvas is the easy part.

The second band is where most successful projects come from. Below it you are usually paying someone to learn Make on your scenario, and the discount evaporates the first time a router branch silently drops records for a fortnight before anyone notices. Above it you are buying process and paperwork, which is worth real money if you have a procurement department and close to nothing if you do not.

We charge $150 an hour on the rare occasions we bill hourly at all, for the reasons in hourly versus fixed price for AI work.

What a scenario build costs when the price is fixed

Most Make work should be quoted fixed, because the scope is knowable before anyone opens the canvas. These are the bands we quote in and the bands we see on other published price lists.

Work	Fixed price
Single scenario, 5 to 12 modules, connectors that already exist	$350 to $1,500
Scenario with branching, an error handler and a data store	$1,500 to $4,000
Multi-scenario system spanning four or five business systems	$4,000 to $15,000
Rescue of an inherited scenario nobody documented	$250 to $2,500
Monthly care: monitoring, a fix window, small changes	$500 to $4,000 a month

A single-scenario price under about $300 is a template being installed on your account, and buying one is fine as long as you know that is what you bought. The expensive end of the table is expensive for reasons that have nothing to do with module count, which is the last section of this post.

Make bills operations, n8n bills executions

Most quotes never mention this, and it decides the five-year cost of the system far more than the build price does.

Make charges per operation. One module firing once is one operation, so a scenario with twenty modules that runs a single time consumes twenty operations, and a filter that discards a record still spends everything it spent getting there. Step count and run count multiply together.

Self-hosted n8n charges nothing per run. You pay for a VPS, typically $20 to $40 a month, and a workflow with two nodes costs exactly what a workflow with sixty nodes costs. n8n Cloud does meter, and it meters executions: one workflow run counts once whether it touches three nodes or eighty.

The two platforms are therefore pricing different quantities. Make prices the width of your scenario. n8n prices how often it fires, and self-hosted n8n stops pricing even that.

Run the same 20-step scenario on both platforms

Take one scenario with twenty modules, the shape that pulls a form submission, enriches it, branches on company size, writes to a CRM, writes to a sheet, posts to Slack and sends two emails. This is what the platform bill does as volume climbs. Make figures are the published Core and Pro tiers plus operation bundles as of August 2026, and the n8n column is a VPS with backups.

Runs a month	Make operations	Make plan cost	n8n executions	n8n self-hosted
500	10,000	$10 to $18	500	$25
2,000	40,000	$40 to $70	2,000	$25
10,000	200,000	$300 to $700	10,000	$40
50,000	1,000,000	$1,200 and up	50,000	$80

At 500 runs a month the argument is not worth having, and anyone pushing you toward a migration at that volume is selling. At 10,000 runs a month the identical logic costs somewhere near $500 on Make and near $40 on n8n, a gap of roughly $5,500 a year. That gap compounds.

Build cost moves the other way. A connector-heavy scenario is genuinely faster to assemble on Make, so the same job often quotes 10 to 25% lower there, and n8n adds a one-time hosting and hardening cost of $800 to $2,500 covering the server, backups, queue mode where the volume needs it, and the update routine somebody has to own. Put those together on the 10,000 run example and n8n repays its setup premium in five to eight months, then keeps repaying it every month after.

Below a few thousand runs a month it never repays, and we tell clients that when they ask us to migrate them for the sake of it.

One limitation on the table above: Make stops publishing prices past its Teams tier, so the bottom two rows come from client invoices we have seen rather than a price list, and you should treat them as indicative.

When Make earns its premium

Make is the right answer more often than that cost table suggests, because the platform line is one of four meters in a monthly automation bill and rarely the biggest, which is the argument in the running costs nobody mentions.

• Nobody at your company will ever own a server. Self-hosted n8n needs an owner with engineering discipline. That owner can be a vendor, and the role can be paid for, but it cannot sit empty.
• Volume is under a few thousand runs a month and likely to stay there, so the operations bill stays inside the noise of your software spend.
• You depend on a connector Make maintains and n8n does not, against an API unpleasant enough that rebuilding it on raw HTTP would cost more than years of Make fees.
• Somebody non-technical needs to open the canvas and understand roughly what is happening, which Make does better than any competing tool, n8n included.

Set against that, Make's weak versioning remains a genuine problem. There is still no clean way to answer what changed in a scenario last Tuesday and who changed it, which is an unpleasant property for something that runs your invoicing, and it is the single reason our Make rescues take longer to diagnose than our n8n ones. We line all three main platforms up in Zapier versus Make versus n8n.

My opinion, stated plainly: paying Make's operation pricing for a wide scenario firing tens of thousands of times a month is renting convenience at roughly ten times what owning it costs, and plenty of companies should keep renting, right up until the day they hire someone technical.

Four things that move a quote more than the platform does

1. Scope on paper. A quote worth reading names the scenarios, the systems each one touches, the edge cases handled, the edge cases excluded, and the test that decides whether the thing is finished.
2. Hardening. Error handlers on every route, a retry policy, a store for records that failed so they can be replayed, and an alert that reaches a person who is awake. This roughly doubles the effort over a happy path, it is the largest hidden difference between two quotes for the same scenario on any platform, and skipping it is the same pattern that produces an n8n workflow that keeps failing in production.
3. Account ownership. Some consultants build on their own Make organisation and rent the result back to you at a lower sticker price. Ask whose name is on the subscription before you pay a deposit.
4. The month after handover. Warranty, hourly, or silence. Ours is a 30-day bug warranty, and the wider choice between a retainer and a phone number is in agency versus freelancer versus in-house.

We quote Make scenario builds fixed, $3,000 to $15,000 for multi-scenario systems and less for single ones, half up front and half on delivery, with the Make subscription in your name and the operations bill visible to you every month. If you want the platform question settled before anyone builds anything, our build service page covers how we scope it.