The Credit System Changed Everything (Most Teams Missed It)
In August 2025, Make fundamentally changed how it bills customers. The shift from operation-based to credit-based pricing looked minor on paper. In reality, it changed how workflows consume monthly budgets. Teams didn’t notice until invoices arrived with shock.
The old system: 10-step workflow = 10 operations per run. Simple math. The new system: 10 steps still cost credits, but now triggers cost credits too. Filters cost credits. Routers cost credits. A workflow checking email every minute for new submissions runs 43,200 credit checks monthly before any actual action happens. Add filtering, CRM lookup, and notifications, and a simple lead capture scenario burns 50,000+ credits from a plan budgeted for 10,000.
This is why the Core plan at $29/month (10,000 credits) feels suffocating for any real business work. Teams upgrading to Pro at $99/month do so not for features, but for breathing room. The gap between plans isn’t features. It’s the ceiling on actual credit consumption when workflows run 24/7.
How Credits Actually Drain (And Where Most Teams Go Wrong)
Every module action counts as one credit. Google Sheet row addition: one credit. Gmail fetch: one credit. Filter routing data: one credit. Trigger checking email every 5 minutes: one credit per check. This granular counting is where consumption spirals.
Teams build workflows that look simple on the canvas. They set execution intervals to “check every minute” because it feels responsive. That’s 43,200 monthly checks on a single workflow. Five workflows with the same interval: 216,000 monthly credits burned just on trigger checks, before any actual processing happens. On Core plan, you’ve used your entire monthly budget on trigger checks alone.
A lead capture workflow illustrates the problem perfectly. Form submission (1 credit) triggers filters to check for spam (1 credit), looks up contact in Pipedrive (1 credit), creates deal (1 credit), sends Slack notification (1 credit). That’s 5 credits per form. Multiply by 500 daily forms: 2,500 credits daily, or 75,000 monthly. Core plan: $29 for 10,000 credits. You’d need Pro plan within the first week of operation.
Three Mistakes Draining Credits Fastest
First: execution intervals set too aggressively. Checking email every minute when every 15 minutes works fine wastes 86,400 monthly checks per workflow. Five workflows at this interval: you’ve burned 432,000 credits on checks that could have been every 15 minutes.
Second: running expensive operations on every record. A scenario that calls an API on every form submission, even ones it shouldn’t process, wastes credits on operations that fail. Routers and filters cost credits but cost less than running full workflow steps on data that won’t process.
Third: unbounded loops and iterators. A loop processing 1,000 records runs 1,000 iterations plus every action inside each loop. A 10-step loop becomes 10,000 credits burned. On Core plan, that’s your entire monthly budget on one scenario.
The Make Pricing Plans That Actually Scale
Free: 1,000 credits monthly. Sandbox only. Real businesses hit this limit in days.
Core: $29/month, roughly 10,000 credits, 1-minute execution intervals. Covers freelancers running 2-3 simple workflows and small agencies starting automation. The moment you scale to lead capture + CRM sync + invoicing across multiple clients, you’re budget-constrained.
Pro: $99/month, roughly 8 million credits (check current Make pricing table), unlimited active scenarios, priority support. This is where SMBs should start if serious about automation. The $70/month jump looks steep until you realize Core plan doesn’t have headroom to run multiple workflows without constant optimization.
Teams running 50,000+ monthly operations often consider n8n self-hosted ($30/month unlimited operations), but that trades managed infrastructure for server maintenance responsibility.
Monitoring Before Budget Blows
Make’s usage dashboard is your early warning system. Check it weekly, not monthly. Teams discovering budget trouble on day 25 have no time to optimize. Weekly checks catch runaway workflows on day 8, leaving 20 days to fix them.
If average weekly consumption exceeds 20% of monthly quota, you’re trending toward shortfall. Hit 50% by day 15 and you need immediate optimization. Use automation audits to find and disable workflows not delivering ROI.
Rollover feature (new in 2026): unused credits carry forward one month. Most teams ignore this. If December volume drops, dial back execution intervals in November, bank credits, and spend them in January when volume spikes. This small lever saves $50-100/month for seasonal businesses.
The AI Integration That Complicates Costs
Make lets you connect custom AI providers (Claude, GPT) starting at Core plan. This adds complexity. A 10,000-token Claude API call isn’t the same cost as a local filter step. Most teams don’t budget AI token costs inside Make scenarios.
If building Claude integrations for content generation or analysis, budget aggressively. One daily content generation workflow can blow quarterly budget if token consumption isn’t tracked. Solution: batch AI tasks, run once, store output, reuse. One 2,000-token call daily costs far less than 50 small calls across individual records.
Make vs. Zapier: Should You Switch?
Zapier charges based on tasks (actions taken). Make charges based on credits (all steps). For equivalent workflows, Make is 3-5x cheaper. A team running 20,000 operations monthly spends $200+ on Zapier but only $30 on Make Core.
But cost isn’t everything. Zapier’s simplicity (you don’t architect credit consumption) appeals to non-technical teams. Make’s complexity requires discipline around workflow design. Pick Make if your team can architect efficiently. Pick Zapier if you value simplicity over cost.
Hybrid approach: use Make for complex, high-volume workflows and Zapier for simple one-offs. Management overhead costs $10-15/month in lost productivity, but can save $50-100 total if workflows split cleanly between simple and complex.
Is Automation Worth Building At All?
Before optimizing Make spend, ask if the workflow saves more time than maintenance costs. A lead intake scenario saving 3 hours weekly pays for Pro plan ($99/month) in one month. Most workflows don’t hit that bar immediately.
Map time savings before committing. If workflow saves less than 30 minutes weekly, maintenance burden (monitoring, fixing broken integrations, updating when APIs change) outweighs benefit. Automation pays when you’re drowning in manual work, not optimizing an already-lean process.
Start with highest-friction tasks: lead capture to CRM, invoice generation to accounting, form submissions to email. These typically save 5-10 hours monthly and pay for themselves immediately. Use those savings to fund more complex automations later.
