What it costs now, under a different name
Integromat pricing,
under its new name
There is no Integromat price list anymore, and that is the first thing worth knowing. Integromat became Make in February 2022, and the plan structure was rebuilt around one number: operations. If you are comparing what you used to pay against what you pay now, that change is usually the whole explanation.
Want to know what this costs in your shop?
I will work out your three biggest time sinks, in hours and dollars. Free, in writing, within 72 hours.
No newsletter, no sequence. You keep the analysis either way.
Tim Muenzel
builds and runs the systems himself
What an operation is, and why it decides your bill
Every module that runs consumes an operation. A scenario with eight modules that fires once uses eight, not one. Iterators multiply that: a scenario that loops over fifty rows and does three things with each is not three operations, it is well over a hundred. This is why two companies on the same plan can have wildly different bills, and why the honest question is never what the plan costs but how many operations your actual work consumes.
Where the model works in your favour
For low-frequency work it is genuinely cheap, cheaper per unit than the better-known alternative, and you are not paying for capacity you do not use. A nightly sync, a form handler, a notification chain: these consume very few operations and the subscription is close to free relative to what it saves. Anyone who tells you to build custom software for that is selling you something you do not need.
Where it turns against you
The problem is not the rate, it is the coupling. Operations scale with your business rather than with your usage of the tool, so growth increases the bill without increasing what the automation does for you. A scenario that touches every order costs twice as much when you sell twice as much, forever, and none of that spend accumulates into anything you own. That is the point at which the arithmetic changes, and it arrives quietly.
The comparison to actually run
Not the monthly rate against a competitor, but the three-year total against the alternative of owning the process. Take your current plan, multiply by thirty-six, add what you expect the volume to do, and put a fixed build cost next to it. For most scenarios the subscription still wins that comparison, and it should. For the two or three processes your business genuinely runs on, it usually does not, and those are the only ones worth moving.
The three-year view
A scenario that processes every order, roughly 40,000 operations a month, on a mid-tier plan:
| Monthly, at that volume | roughly $100 to $200 depending on plan and add-ons |
|---|---|
| Over three years | roughly $3,600 to $7,200, and it continues |
| If your volume doubles | the bill roughly doubles, because operations do |
| Built once instead | from $6,900 fixed scope, then nothing to rent |
| What the build also buys | tests, monitoring that reports failures, code anyone can maintain |
| Where the subscription wins | below roughly 5,000 operations a month, clearly |
Prices in this table are orders of magnitude, not quotes; Make changes plans and so does everyone else. The shape is the point: one column stops growing after year one and the other does not.
Common questions, answered straight
Is there still an Integromat price list?
No. Integromat was renamed to Make in February 2022 and pricing is published under that name. Old Integromat plans were migrated rather than continued.
Why is my bill higher than it used to be?
Usually because operations are counted differently than the old plan counted them, and because scenarios that loop over rows consume far more than people expect. Check a single scenario run and count the modules that actually executed.
How do I reduce operations without rebuilding?
Filter earlier, so modules downstream never run. Batch where you currently loop. Remove modules that only exist for logging. That is real optimisation work and it often halves a bill, which is a better first step than any migration.
At what point is building cheaper?
As a rough line: when the annual subscription for one process passes roughly a third of a fixed build price, and that process is not going away. Below that, stay. The free teardown puts your actual numbers into that comparison.
Do you sell Make optimisation?
No. I do not build or optimise in Make. That is what makes the advice above worth reading: the three suggestions in the previous answer cost me a client and cost you nothing.
Related reading
Bill growing faster than the value?
Free systems teardown: which of your scenarios are worth optimising, which are worth leaving alone, and which single one would be cheaper to own. In writing, within 72 hours, no obligation.
Get your free systems teardown