Make Pricing Explained: Every Tier, the Credit Model & Your Real Cost

TL;DR — Make starts free and Core is just $9/mo, but the sticker price is the least interesting number here. Every paid plan includes the same 10,000 credits — you pay more for features, not more volume — and your real bill is driven by how your scenarios burn credits (polling, loops and AI are the culprits). Here's every tier billed both ways, exactly how credits are consumed, and the traps that turn a "$9" plan into something bigger.

Every tier, billed monthly and annually

*Make advertises 15%+ off for annual billing;^[1] the annual column is that discount applied and rounded — exact annual rates shift, so confirm the live figure on Make's pricing page before you commit.

Look down the "credits" column and the single most important fact about Make pricing jumps out: Core, Pro and Teams all include the same 10,000 credits.^[1] You are not buying more automation volume as you climb the tiers — you're buying features. Pro adds priority execution, custom variables and searchable logs; Teams adds collaboration — multi-user access, roles and shared templates. If you're a solo builder who never needs those, there is no pricing reason to leave Core, no matter how much you automate. That alone corrects the most common misreading of Make's pricing.

How Make actually bills: credits, not seats

Make doesn't charge per user — it charges for work done, metered in credits since August 2025.^[1] The base rule is simple: one module execution costs one credit — adding a Google Sheet row, fetching a Gmail message, posting to Slack are one credit each.^[2] Two categories cost more, and they're exactly where budgets slip:

• AI modules consume credits by token usage, so a heavy prompt or a multi-step agent run costs far more than a plain action.^[2]
• Make Code (custom JavaScript or Python) runs at two credits per second of execution time.^[2]

Because billing tracks work and not headcount, your cost scales with automation volume — which is genuinely great news for growing teams (add colleagues for free) but means the question that matters isn't "which tier looks cheap?" It's "how many credits will my scenarios actually burn?"

The credit traps that blow up a "$9" plan

This is where aggregating what real users hit — not the marketing page — earns its keep. Three patterns quietly consume credits faster than anyone expects:

Polling triggers run even when nothing happens. A scenario that polls every 5 minutes fires ~8,640 times a month just checking for new data — whether or not there's anything there — and each check is a credit.^[2] That single design choice can eat most of a Core allowance before you've done any real work. The fix is free and dramatic: use webhook/instant triggers instead of polling wherever the app supports them, and the overhead disappears.

Iterators multiply. Loop over a list and every item runs every downstream module. A single order with 12 line items pushed through 4 modules is 48 credits for one order, not 4.^[2] At a few hundred orders a month that's the difference between comfortable and out of credits.

Failed steps retry — and retries cost credits.^[2] A flaky integration that retries silently is burning budget while you're not looking, which is why error handling isn't just good hygiene, it's cost control.

None of these are hidden fees — they're consequences of how the meter works. But nobody tells you on the pricing page, and they're the real reason a nominally cheap plan can surprise you.

When 10,000 credits isn't enough: packs and top-ups

Since every paid tier ships with the same 10,000 credits, scaling volume doesn't mean climbing tiers — it means buying credit packs. Make sells extra credits in bundles (commonly 10,000 at a time) and Core, Pro and Teams can auto-purchase them so scenarios don't stall mid-month.^[3] The catch worth pricing in: add-on credits run at roughly a 25% higher per-credit rate than your plan's base allowance,^[3] so heavy, sustained volume is cheaper to plan for than to top up reactively. And note a billing subtlety: on annual Teams/Enterprise plans, credits are allocated as a 12-month pool that expires after the year rather than resetting monthly^[3] — great for uneven workloads, but don't leave a chunk unused in month eleven.

Use the slider to see where your monthly volume lands against the free (1,000) and paid-base (10,000) credit lines, and roughly how many packs a heavier workload adds. It's guidance, not a quote — model your real scenarios, then confirm against Make's live pricing.

A worked example: what a real setup actually costs

Numbers make this concrete. Picture a small e-commerce team on Core ($9/mo) running two automations. The first is a lead-capture flow on a webhook trigger — it fires only when a form is submitted, so at a few hundred submissions a month it barely touches the allowance. The second is an order-processing flow that loops over line items: at an average of 12 items through 4 modules, that's ~48 credits per order.^[2] Process 300 orders a month and you're at roughly 14,400 credits on that flow alone — already past Core's 10,000, so this team needs one credit pack on top of the $9 base, not a tier upgrade.

Now watch the same team make one mistake: building that order flow on a 5-minute polling trigger instead of a webhook. That adds ~8,640 credits a month of pure overhead^[2] — checks that mostly find nothing — nearly doubling their consumption for zero benefit. Same automations, same plan; the design decision, not the pricing page, is what moved the bill. That's the whole game with Make: your tier sets the floor, but your scenario design sets the meter.

Cost at scale — the real TCO

Think of Make's total cost in two layers. The platform fee is small and flat: most serious teams live on Core or Pro ($9–16/mo), and it barely moves as you add people. The variable layer is credits, and it scales with how much automation you run — this is the part to forecast, using the traps above.

That two-layer shape is the whole financial argument for Make. Per-task tools get punishing exactly when you succeed — every extra task costs more, forever. Make's platform fee stays put while your usage grows, and disciplined scenario design (webhooks over polling, filters early, right-sized models on AI steps) keeps the variable layer flat too. For teams with real volume, that's why the migration stories in the reviews almost always run toward Make from something pricier — and why the same teams warn you, in the same breath, to respect the credit meter.

Keeping your bill predictable

Because cost is usage-driven, a little discipline keeps it boringly steady. Size one tier's credit headroom above your estimate for the first month — over-provisioning is far cheaper than a revenue-critical flow running dry. Watch consumption in week one, not at renewal, when a runaway scenario is cheap to catch. Prefer webhooks to polling and filter right after the trigger so you never burn credits on test records, duplicates or empty checks. And match the model to the task on AI steps — a lighter model for routine classification, a premium one only for customer-facing work. For the AI side specifically, with a live credit-load estimator, the Make AI Playbook picks up where this leaves off.

Which tier is right for you

Start on Free to learn and prove one workflow — it's a real tier, not a trial. Move to Core ($9/mo) the moment you want more than two scenarios or faster execution; it's where most teams settle and, because credits don't change above it, often where they stay. Choose Pro ($16/mo) only if you specifically need priority execution or searchable logs, and Teams ($29/mo) when you need collaboration — multiple users, roles, shared templates. Enterprise is about governance and support, not features you'll click. The rule of thumb: pick your tier by the features you need and your credit pack by the volume you run — they're two separate decisions, and conflating them is what leads to overpaying.

For whether Make is the right platform at all — how it scores, who it's for, where it frustrates — see our Make review.