Desk research checked 27 August 2026 against Make’s official public pricing and help pages. This guide is educational information, not personal testing, financial advice, a quote or a promise of savings. Prices, allowances and features can change.
The short version
Make charges for a plan and credit allowance, not simply for the number of workflows you create. A scenario can consume several credits each time it runs because its modules may each perform one or more operations. Some AI and advanced features use credits dynamically, so a neat module count is not always a reliable cost forecast. Start with a representative workflow, inspect its recorded credit use and model a busy month before choosing a tier.
For a UK buyer, the figures displayed in US dollars are only a starting point. The sterling amount charged can be affected by the checkout currency, card or payment-provider exchange rate, foreign-transaction charges and applicable VAT or other tax. Check the final renewal amount and tax treatment at Make’s checkout rather than converting the headline figure once and treating it as fixed.
Plan snapshot
When this guide was researched, Make’s official pricing page showed these US-dollar examples for 10,000 credits per month. They are a dated snapshot, not a UK quote:
- Free: $0, with up to 1,000 credits each month, two active scenarios and a 15-minute minimum interval between scheduled runs.
- Core: $12 a month on the monthly 10,000-credit view. The pricing page lists unlimited active scenarios, one-minute scheduling and Make API access among the additions to Free.
- Pro: $21 a month on the monthly 10,000-credit view. Listed additions include priority scenario execution, custom variables and full-text execution-log search.
- Teams: $38 a month on the monthly 10,000-credit view. Listed additions include teams, team roles and shared scenario templates.
- Enterprise: custom pricing, with additional governance, security, support and scale features.
The credit selector matters as much as the plan name: increasing the allowance changes the price. Make also displays discounted annual billing, which involves annual commitment or prepayment. Re-open the pricing page, select the required credit volume and billing frequency, and check the current full annual amount rather than relying on an old monthly equivalent.
Monthly versus annual: do not compare the labels alone
A monthly subscription has a one-month billing cycle and a monthly credit allocation. An annual subscription is paid for the whole year in advance; the “per month” amount shown on the annual pricing view is therefore an equivalent rate, not necessarily a monthly payment. Make explains the billing cycles in its monthly and annual subscriptions guide.
The way credits are released also differs by annual plan. Make’s help page says Pro and Teams can receive an annual package of credits for flexible use over the billing year, while Core keeps monthly allocated credits even with annual billing. This distinction can matter for seasonal businesses: a yearly Pro or Teams pool may absorb a busy period differently from a Core allowance that resets each month.
- Monthly may suit uncertainty: the commitment is shorter, but the displayed rate can be higher.
- Annual may lower the headline rate: it also means paying the yearly amount upfront and accepting a longer commitment.
- Expiry still matters: do not assume unused credits roll over indefinitely. Make says credits expire at the end of the applicable term or reset period.
- Changing plan is not neutral: review Make’s current upgrade, downgrade, renewal and cancellation rules before switching billing cycle or tier.
What one credit means
Make’s credits documentation separates operations from credits. An operation records a module’s activity; credits are the billing unit. For most non-AI apps, the default fixed rate is one operation to one credit. For example, a module that uploads one file normally uses one credit for that upload, regardless of file size, unless Make labels the module with another rate.
One scenario run is not the same as one credit. Each module that executes can use credits, and a trigger can produce multiple bundles for later modules to process. Iterators, repeated bundles, branches that actually execute, retries, polling and error-recovery paths can all change consumption. A scenario that looks small on the canvas can therefore use many credits at volume.
Dynamic and AI credit use
Some AI and advanced modules use dynamic rather than fixed credits. Make says the amount can depend on tokens, file size, pages processed or run time. Longer prompts and responses, larger files and repeated AI calls can therefore consume more credits than a simple one-credit-per-module estimate. Look for Make’s usage tag on the exact module and check its feature documentation.
The connection method can also change who bills you. If a third-party AI module requires your own OpenAI, Anthropic or similar connection, Make says you pay Make credits for the operation and the AI provider separately for token use. Make’s built-in AI features and modules with an automatic provider connection can instead charge Make credits dynamically for tokens and other usage factors. Include both bills in a cost comparison where an external provider account is involved.
AI conversion rates and available models can change. Avoid building a long-term budget from one short prompt or a copied token-to-credit figure. Record several representative runs, including the longest realistic input and output, then add headroom.
Extra credits and the overspend risk
If a paid plan runs short, Make says you can upgrade or buy extra credits. Its extra-credits guide states that manually purchased and automatically purchased extras carry a 25% additional cost compared with credits included in the plan.
Auto-purchasing can keep scenarios running, but it is not a fixed spending cap. Make says it purchases extras in 10,000-credit units when the plan allowance is exhausted and can repeat the purchase, up to a cycle limit linked to the subscription allowance. A loop, unexpected data spike or runaway AI process could therefore trigger more than one charge before somebody intervenes.
Extra credits are also time-limited. On monthly billing they expire at the end of the current billing cycle. On annual billing they can remain until the end of the billing year, but Make documents an important exception: annual Core still resets monthly, so its extra credits expire at the monthly reset. Extra credits add data-transfer allowance but do not raise every other plan limit.
- Leave auto-purchasing off until an owner has agreed the business case and monitoring process.
- If continuity requires it, restrict who can enable it and document the maximum possible charge under the current plan.
- Set internal alerts below the plan limit and review credit use by scenario, not just at organisation level.
- Investigate unusual growth immediately: duplicated bundles, loops, retries, polling frequency and AI input size are common places to look.
- If extras are needed repeatedly, compare the full cost with a larger allowance rather than treating the 25% premium as normal.
Plan limitations that can change the real cost
Credits are not the only constraint. Make’s plan table varies limits and features including active scenarios, scheduling interval, data transfer, data-store capacity, incomplete-execution storage, webhook queue size, execution-log retention, API access, priority execution, collaboration and governance. Buying extra credits does not automatically unlock a higher plan’s features or raise every parameter.
- Free-plan constraints: 1,000 monthly credits, two active scenarios and 15-minute scheduled intervals may be enough to learn, but not to represent a time-sensitive live process.
- Storage and retention: short log retention or limited incomplete-execution storage can affect investigation and recovery.
- Data transfer: file-heavy workflows can meet a non-credit allowance before they use all purchased credits.
- Scheduling and queues: frequency and webhook queue limits matter when demand arrives in bursts.
- Team controls: unlimited scenarios do not mean every collaboration, role, SSO or governance feature is included.
- Connected-service costs: Make’s fee does not include every third-party API, AI, email, messaging or storage charge.
A practical way to choose an allowance
- Map one real workflow. List the trigger, modules, branches, expected bundles, polling schedule, retry paths and AI calls.
- Use safe sample data. Run representative cases without sensitive or consequential live records.
- Measure rather than guess. Use Make’s execution and credit views to record normal, large and failed runs.
- Model volume. Apply the measured use to an ordinary month and a realistic peak month, including growth and retries.
- Add all costs. Include the Make plan, possible extras, separate AI/API bills, VAT, currency conversion and payment fees.
- Check non-credit limits. Confirm scheduling, transfer, storage, log retention, queues, roles and support for the selected tier.
- Choose a response to exhaustion. Decide whether scenarios should pause, the plan should be upgraded or controlled extra-credit purchasing is justified.
- Review after launch. Assign an owner to watch failures and spend, sample outputs and revisit the model when data volume or scenario design changes.
For the wider suitability, security and operational checks, read the practical Make evaluation guide, the Make versus Latenode comparison and the platform-neutral automation checklist.
Affiliate disclosure
The button below is a Make affiliate link. If you register through it and later make an eligible subscription payment, UK Digital Tools Research may receive a commission, at no extra charge because of the link. This commercial relationship does not prove that Make is suitable or good value for your business. Compare the current plan, limits and total UK cost before deciding.
No discount, saving, service outcome or uninterrupted automation is promised. Extra-credit purchases may be excluded from affiliate commission under Make’s programme terms; that does not change what you pay.