Make.com Pricing Breakdown 2026: Plans, Credits, Costs & Which to Choose
Imagine your agency lands a client needing 47 workflows connected across Shopify, Slack, and their custom CRM. You prototype everything in Make.com during week one. Week four, the invoice hits: $40 over budget. A webhook misfired. A scenario looped on errors. Nobody caught it. This make.com pricing breakdown gives you the post-credits-switch numbers you actually need: calculator formulas, real workflow costs, and ROI projections against Zapier, so you scope projects profitably from day one. For agency-specific implementation tactics, see our automation for marketing agencies guide: automation for marketing agencies; for more details, see our guide on zapier pricing worth it.
Overview of Make.com Pricing Plans in 2026
Make.com is a no-code automation platform that lets users build visual scenarios to move data, trigger actions, and process information across thousands of tools. As of 2026, Make officially replaced the older "operations" metric with a credits-based pricing model. That change (which rolled out in August 2025) fundamentally shifts how you forecast monthly spend. The current lineup includes Free, Core, Pro, Teams, and Enterprise plans. Each tier sets different credit thresholds, scheduling intervals, and feature access.
| Plan | Monthly Billing | Annual Billing | Base Credits/Mo | Key Limit |
|---|---|---|---|---|
| Free | $0 | $0 | 1,000 | 2 active scenarios max, 15-min intervals |
| Core | $12/mo | ~$10.59/mo | 10,000 | 1-min intervals, unlimited active scenarios |
| Pro | $21/mo | ~$18.82/mo | 10,000 | Priority execution, custom variables |
| Teams | $38/mo | ~$29/mo | 10,000 | Multi-user, team roles, shared templates |
| Enterprise | Custom | Custom | Custom | SSO, audit logs, 24/7 support, overage protection |
Annual billing saves roughly 15% across all paid tiers. If you're committing to Make for a client retainer, annual is almost always worth it unless your contract is shorter than six months.
Because the system now measures usage in credits, and different actions carry different weights, understanding these tiers is the first step toward building a sustainable automation infrastructure. For a deeper look at how Make stacks up against alternatives, see make.com vs zapier vs n8n.
The Free Plan: Ideal for Testing, Not Production
If you're just starting to experiment with automation, the Free plan is a reasonable entry point. According to Make's own pricing page, this plan includes 1,000 credits per month and caps you at 2 active scenarios. Scenarios on the Free tier run no more often than every 15 minutes.
You can build and test to see how modules interact. But there are strict limitations. Most real-world workflows exceed 1,000 credits quickly, and the 2-scenario cap means you can't build even a modest multi-workflow stack. Use the Free plan to validate credit consumption math before any client commitment. Don't use it for anything that matters.
Core Plan: Scaling Your Automations
The Core plan is the standard starting point for most small businesses and early-stage operators. At $10.59/month billed annually (or $12/month month-to-month), it delivers a real jump in capacity.
What changes on Core:
- 10,000 base credits per month, scalable up to 300,000 credits/month via add-ons
- 1-minute scheduling intervals (down from 15 minutes on Free)
- Unlimited active scenarios
- Make API access for connecting custom systems
- Custom functions and data stores for more complex logic
For more details, see our guide on zapier pricing plans comparison 2026.
The jump from Free to Core is where most agencies should land their clients early. The 1-minute scheduling interval alone changes what's possible. When you calculate value, look at cost per credit. A well-architected Core plan workflow typically costs $0.001 per credit. That's cheap enough that the math almost always beats hiring someone to do it manually.
One caveat: if you're running code-heavy scenarios with the Make Code App (billed at 2 credits per second of execution), a $10.59/month plan can evaporate faster than expected. Test your execution time before committing to a credit tier.
Pro Plan: Power Features for High-Volume Workflows
The Pro plan costs $18.82/month billed annually ($21/month month-to-month) and shares the same 10,000 base credits as Core. The difference isn't volume by default: it's execution quality and tooling.
| Feature | Pro Plan |
|---|---|
| Monthly Price | $18.82/mo (annual) / $21/mo (monthly) |
| Base Monthly Credits | 10,000 (scalable to 8M/mo with add-ons) |
| Advanced Tools | Priority execution, custom variables, full-text log search |
| Key Advantages | Faster execution for time-sensitive workflows, deeper debugging |
Priority execution means Pro scenarios jump the queue when Make's infrastructure is under load. For client workflows where a 2-minute delay in a Slack notification is acceptable, Core is fine. For anything where timing matters, Pro pays for itself.
Pro users also get full-text execution log search, which sounds minor until you're debugging a scenario that fired 847 times overnight. Webhooks matter here too: they let your scenarios trigger instantly from an external event instead of polling, which prevents wasted credits and ensures automations only run when necessary. Comparing Pro to Core, the ROI usually comes from time saved on debugging and execution reliability, not raw credit volume. For teams building AI-driven automations or agent-based architectures, see our article on ai-agents-for-business: ai-agents-for-business.
Teams Plan: Multi-User Collaboration
The Teams plan runs $29/month billed annually ($38/month month-to-month). It's not about more credits: it's about organizational control.
What Teams adds over Pro:
- Multi-user access with defined roles and permissions
- Shared scenario templates across the team
- Analytics dashboard for usage monitoring
- Team management controls
If you're running an agency with multiple builders touching the same client account, Teams is worth it. The shared templates alone save hours when you're spinning up similar workflows across clients. However, if you're a solo operator or a founder doing this in-house, Pro covers everything you need.
Enterprise Plan: Custom Solutions for Large Organizations
The Enterprise plan operates on custom pricing tied to your volume and organizational requirements. According to Make's pricing page, it includes 24/7 support and overage protection, so critical workflows don't stop during traffic spikes.
Standard features include Single Sign-On (SSO), detailed audit logs, custom functions, and access to enterprise app integrations. This plan is for teams managing complex, multi-departmental automations where downtime carries real financial risk. If your organization prefers to outsource design and maintenance, consider partnering with an ai automation agency for implementation and governance: ai automation agency.
Understanding Credits vs Operations: What Actually Changed
The shift from operations to credits happened in August 2025, and it changed the math. Previously, most actions counted as a single operation regardless of complexity. Credits work differently: consumption varies by action type, and different modules carry different "weights."
Key examples from Make's documentation:
- Standard module action (e.g., add a Google Sheets row): 1 credit
- Make Code App execution: 2 credits per second of runtime
- Data transfers: scale at 5 GB per 10,000 monthly credits
A heavy, code-intensive script burns credits much faster than a simple data transfer. This is why the plan tier matters less than workflow architecture. Efficient scheduling and proper error handling are direct levers for controlling your monthly bill, not just best practices.
One thing that surprised many users: the credit multiplier for Code App execution. If your scenario runs a 10-second custom code block, that's 20 credits per execution. Run that 500 times a month and you've spent 10,000 credits on one step alone.
Billing, Discounts, and Cost Calculators
Make.com's annual billing discount sits at roughly 15% across all paid tiers. For agencies building client retainers, committing annually on your Make subscription and baking that into the retainer price is cleaner than managing monthly fluctuations.
For budgeting, use this formula:
Monthly credit estimate = Triggers per day x Modules per scenario x 30
Then add a multiplier for any Code App usage: seconds of execution per run x 2 x monthly run count.
Extra credits are available if you exceed your plan limits. Per the November 2025 changes to Make's pricing structure, both automatic and manual additional credit purchases cost 25% more than the credits included in your base plan. Manual purchases come in multiples of 1,000 credits, giving you a way to scale without immediately jumping to a higher tier. That 25% premium adds up fast if you're chronically over budget; it's usually cheaper to upgrade the plan than to keep buying overage credits.
Which Plan Should You Choose?
Selecting the right plan comes down to three variables: scenario count, polling frequency, and team size.
| Use Case | Recommended Plan | Why |
|---|---|---|
| Solo testing / learning | Free | 2 scenarios, 1,000 credits covers most experiments |
| Solo operator, simple workflows | Core annual | $10.59/mo covers most single-founder stacks |
| Agency, client workflows | Core or Pro | Pro if timing or debugging matters; Core if not |
| Multiple builders, shared account | Teams | Role controls and shared templates justify the price |
| Enterprise compliance requirements | Enterprise | SSO and audit logs are non-negotiable at this scale |
For a deeper comparison, check out make.com vs zapier vs n8n 2026.
Use the Free plan to build your first scenario, then run the estimator to see if you'll exceed the 1,000-credit limit. If you consistently hit that cap, upgrade to Core. The $10.59/month fee will cost you less than the time you waste on manual workarounds.
Common Mistakes and Pitfalls to Avoid
The most common mistake is polling instead of using webhooks. If your automation checks for new emails every minute, it consumes credits every minute regardless of whether a new email arrived. Webhooks fire only when an event actually happens. Switching a polling trigger to a webhook can cut credit consumption by 80% or more on high-frequency scenarios.
The second pitfall is ignoring error handling. If a scenario fails and keeps retrying without an error handler, it burns through credits in minutes. Every scenario needs a stop condition or an error path. No exceptions.
A less obvious one: leaving Code App steps in production without measuring their execution time first. A 3-second block feels fast. But at 2 credits per second, running 1,000 times a month costs 6,000 credits on that step alone. Profile your code steps before deploying to any paid tier.
Choosing the Right Make.com Plan for Your Business
Credit-based billing rewards technical discipline. Agencies that architect lean, with webhooks over polling, native modules over custom code, and error handlers over blind retries, deliver client value at margins competitors can't match. Those who ignore the math eat surprise overages that kill project profitability.
This make.com pricing breakdown gave you the current 2026 structure, accurate plan prices, the calculator formulas, and the real cost drivers to scope accurately. Your next step: audit one active client scenario. Count modules, measure execution time, apply the multipliers. Compare projected against actual spend. That gap is your optimization roadmap and your competitive advantage. Start with a Free plan test; the credit consumption data will validate your estimates before any client commitment.
FAQ
Q: What are the Make.com pricing plans in 2026? Make.com uses a credits-based pricing model. Plans are Free ($0, 1,000 credits/month), Core ($10.59/mo annual, 10,000 credits), Pro ($18.82/mo annual, 10,000 credits), Teams ($29/mo annual, 10,000 credits), and Enterprise (custom pricing, custom credits).
Q: How much does Make.com cost per month? Core costs $10.59/month billed annually or $12/month month-to-month. Pro costs $18.82/month billed annually or $21/month month-to-month. Teams costs $29/month annually or $38/month monthly. Enterprise is custom.
Q: What changed when Make switched from operations to credits? Make replaced the "operations" metric with credits in August 2025. The key difference: credits are weighted by action complexity. Standard module steps still cost 1 credit, but the Make Code App charges 2 credits per second of execution time. This means code-heavy workflows cost significantly more than they did under the old operations model.
Q: What's the difference between Make.com credits and operations? Make replaced the legacy 'operations' metric with a credits system. Usage is now measured in credits, which bill different actions based on complexity. For example, the Make Code App uses 2 credits per 1 second of execution, while a standard module action costs 1 credit.
Q: Is Make.com's free plan enough for real workflows? The Free plan includes 1,000 credits per month and caps you at 2 active scenarios, with a 15-minute minimum interval between runs. It works for testing and learning, but most production workflows exceed these limits fast.
Q: How do I calculate Make.com pricing for my usage? Use the formula: Triggers per day x Modules per scenario x 30 days. For Code App steps, add: seconds of execution x 2 x monthly run count. Because billing is credit-based, use webhooks to reduce unnecessary polling and keep your estimate accurate.
Q: How does Make.com pricing compare to Zapier? What is cheaper? Zapier charges only for successful task executions. Make historically charged for both polls and actions, which made it expensive for polling-heavy workflows. With the credits model, Make's cost depends heavily on architecture. Webhook-driven workflows on Make are often cheaper than Zapier for the same output. Polling-heavy workflows can run higher. See our zapier-vs-make-comparison article for a side-by-side breakdown: zapier-vs-make-comparison.
Q: What are alternatives to Make.com? Common alternatives include Zapier and n8n. When comparing, look at how each platform counts usage (tasks vs. credits vs. executions) and the number of available integrations. n8n is worth considering if you're comfortable self-hosting and want zero per-execution costs at scale.