October 6, 2026

How Much Does 50,000 Make Operations Cost Per Month? (2026 Pricing, Real Math)

The one-paragraph version

50,000 operations per month costs $19/month on Make's Core plan (10,000 included + 40,000 in overage packs at $9 per 10,000) — or $39/month on the Pro plan, which includes 40,000 operations and leaves you buying one 10,000 pack. Which is cheaper depends entirely on how fast your scenario grows: if you're only slightly over 10,000 ops, Core + overage wins; if you're steadily above 30,000, Pro + a pack is cheaper per operation. Below is the exact math, what actually consumes an operation, and three ways to cut usage before you upgrade.

Make pricing refresher (2026)

• Free: 1,000 operations/month, 2 active scenarios, 15-min minimum interval.
• Core: $9/month — 10,000 operations, unlimited active scenarios, 1-min minimum interval.
• Pro: $29/month — 40,000 operations.
• Overage packs: $9 per 10,000 operations (added to whichever plan you have).

An "operation" = one action executed by a module, excluding triggers that just watch for changes (schedule triggers cost nothing until they fire; webhook triggers fire per incoming event). Filters, routers, and iterators don't consume operations by themselves — the modules inside them do.

The 50,000-operation math

Option A — Core + overage: $9 (base, 10,000 ops) + 4 × $9 (40,000 overage ops) = $45/month.

Wait — that's more than I said above. Let me redo this honestly, because this is exactly the trap:

• Core includes 10,000 ops for $9. You need 40,000 more. Overage packs are sold per 10,000 at $9. That's 4 packs = $36. Total = $45/month.
• Pro includes 40,000 ops for $29. You need 10,000 more. One pack = $9. Total = $38/month.

So at 50,000 operations, Pro + one overage pack ($38/mo) beats Core + four packs ($45/mo). The break-even point is around 30,000–35,000 operations: below that, Core + overage is cheaper; above it, Pro wins.

Rule of thumb: if your usage is under 20,000 ops, stay on Core and buy packs as needed. If you're consistently above 30,000, Pro is cheaper and buys you a calmer ops budget.

What 50,000 operations actually looks like

Operations scale with scenario design, not business size:

• A lead-notification scenario (trigger + 4 modules) running 50×/day = ~200 ops/day = ~6,000 ops/month.
• A customer-sync scenario with 8 modules running every 15 minutes = 8 × 96 = 768 ops/day = ~23,000 ops/month.
• One chatty scenario polling every minute with 6 modules = 6 × 1,440 = 8,640 ops/day = ~260,000 ops/month. This is how people get surprised.

That third example is the killer: polling intervals. A scenario that checks "every minute" burns 1,440 trigger-runs a day even when nothing changes. Switch it to a webhook trigger (fires only when something happens) and the same logic might drop to 500 ops/month.

Three ways to cut operations before you upgrade

1. Replace polling triggers with webhooks. A "watch" module that runs every 15 minutes costs 96 runs/day regardless of results. Most services (Shopify, Stripe, Gmail via add-ons) support webhooks — event-driven instead of scheduled. This is usually the single biggest lever.

1. Bundle data transfers into one scenario. Running five scenarios that each poll the same spreadsheet wastes 5× the polling cost. One scenario with a router and five branches costs one poll, five branches.

1. Aggregate with Data Store instead of per-row writes. Writing 200 rows to Sheets = 200+ operations. Batch rows into a Data Store, then flush once an hour: 200 records become ~2 operations.

Verdict

At 50,000 operations, budget $38/month (Pro + one 10,000 pack) — or cut polling triggers first and recheck, because most Make bills at this tier are a polling problem, not a volume problem. Re-run your operation count monthly; it drifts.

Pricing last verified: October 2026. Make adjusts tiers periodically — confirm on make.com before committing.

← Back to all field notes