Make pricing at a glance
Every tier includes unlimited scenarios and the full app library. What you buy is operations per month, plus faster scheduling intervals as you move up.
- Free: 1,000 operations/month, 15-minute minimum interval
- Core: from about $9/month — 10,000 operations, 1-minute intervals
- Pro: from about $16/month — 10,000 operations plus custom variables and priority execution
- Teams: from about $29/month — shared scenarios, roles and team templates
- Enterprise: custom pricing with SSO and dedicated support
- Operation bundles scale up within each tier, so the monthly price rises with volume
What an operation actually is
One operation is one module doing one thing with one piece of data. This is the definition that trips people up: a scenario run is not one operation, it is one operation per module per item processed.
- Every module that executes consumes one operation, including the trigger
- Process 50 rows through a 4-module scenario and you spend roughly 200 operations
- Filters that block an item still cost the operation that evaluated it
- Routers themselves are free, but each branch's modules bill normally
- Errors that reach a module still consume the operation
What burns operations fastest
Three patterns account for most surprise bills. Fixing them is usually cheaper than upgrading a plan.
- Polling triggers on short intervals — a 1-minute check runs 43,200 times a month
- Iterators splitting arrays, where every item becomes its own module run
- Search modules that return many records before a filter narrows them
- Fix: switch pollers to webhooks wherever the app supports them
- Fix: filter as early as possible, ideally in the trigger's own query
How to estimate your monthly operations
Work it out per scenario, then add them up. The formula is simple and far more accurate than guessing from the number of automations you run.
- Operations = runs per month x modules per run x items per run
- Example: a 6-module order sync firing 500 times a month is about 3,000 operations
- Add roughly 20% headroom for reruns, testing and error retries
- Make shows per-scenario operation usage, so refine the estimate after a week live
- Size the plan to that total, not to the number of scenarios you have built
Make vs Zapier on real cost
Make is usually cheaper, but the gap depends on workflow shape rather than volume alone. Zapier charges per step; Make charges per module per item.
- Simple 2-step workflows: the two are close in price
- Multi-step workflows with routers and logic: Make is dramatically cheaper
- Workflows processing large arrays: Make's per-item billing narrows the gap
- Make's entry paid tier starts around $9 against Zapier's roughly $20
- Pabbly is cheaper again if you only need successful actions billed
Which Make plan to pick
The jump from Free to Core is really about scheduling, not volume — the 15-minute floor on Free is what most people hit first.
- Learning Make or running one hourly scenario: Free
- Anything that needs to react within a minute: Core
- Complex scenarios with custom variables and priority execution: Pro
- Multiple people editing shared scenarios: Teams