Make Pricing and Credits Explained for Consulting Firms

Make's subscription price is only half the calculation

Make connects applications through automated workflows called scenarios. A scenario might take a website enquiry, create a contact and opportunity in a CRM, open a project folder and notify the responsible consultant.

Make sells two related things: a plan, which determines the available features and controls, and an allocation of credits, which pays for activity. A firm can need a higher plan for governance while consuming few credits. Another firm can be comfortable with Core's features but require a larger allowance because it processes thousands of records.

What is a Make credit?

A module is one step in a Make scenario. An operation occurs when a module checks or processes data. For most standard modules, one operation consumes one credit. Reading a CRM record, adding a spreadsheet row and sending an email are separate actions.

Credits and operations are not safe to treat as universal synonyms. Make adopted credits as its billing unit in 2025 so that some AI and resource-intensive features could be charged differently. Its current pricing page says most actions consume one credit, while some advanced features use more. For example, it currently lists the Make Code app at two credits per second of code execution on eligible plans.

Before adding AI extraction, web search, code execution or an agent to a workflow, check the product's in-app credit estimate and the current credit documentation ↗. The workflow diagram alone may no longer reveal the bill.

How a simple workflow consumes credits

Consider a hypothetical consulting firm automating new enquiries:

1. Receive a website enquiry.
2. Create or update the CRM contact.
3. Create an opportunity.
4. Add a follow-up task.
5. Send an acknowledgement email.

If every step runs once and uses one credit, one enquiry consumes about five credits. At 120 enquiries a month:

120 enquiries × 5 credits = 600 credits per month

That estimate changes if the scenario searches for duplicates, branches by service line, creates folders, retries failed steps or processes attachments.

Volume matters as much as module count. Make calls each separately processed unit of data a bundle. If a trigger retrieves 20 records, later modules may execute 20 times each. That multiplying effect is why a five-module scenario does not necessarily cost five credits per run.

Current Make plans

When verified on 19 September 2026, Make's US-dollar pricing page showed the following entry prices at 10,000 monthly credits. Annual figures are monthly equivalents paid under an annual commitment. Regional prices, currencies, taxes and checkout terms can differ.

Make advertises savings of 15% or more for annual billing. Recheck the final amount and renewal terms on the official pricing page ↗ before purchasing.

Free: prove the workflow

Free includes 1,000 credits a month, up to two active scenarios and a 15-minute minimum interval for scheduled runs. Make currently lists a five-minute maximum scenario execution time, 5 MB maximum file size and seven days of execution-log storage.

That is enough to learn the interface and test a small process. A firm should not stay on Free merely because average usage fits beneath 1,000 credits: a missed lead or delayed client process can matter more than the allowance.

Core: the sensible starting point for many firms

Core starts at 10,000 monthly credits, permits unlimited active scenarios and allows scheduling down to one-minute intervals. It also increases the maximum execution time to 40 minutes, the maximum file size to 100 MB and execution-log storage to 30 days.

For a small firm with one automation owner, Core is usually the first paid tier to assess for lead routing, project setup, deadline reminders, approved system synchronisation and recurring internal reports.

Pro: an operational-control upgrade

Pro adds priority execution, custom variables and full-text execution-log search, and raises the maximum file size to 250 MB. The business case is stronger when several scenarios share centrally maintained values, troubleshooting speed matters or larger files must move through Make.

A two-person consultancy running three straightforward scenarios may not need Pro. A firm relying on automation for onboarding and recurring reporting could value the extra operating controls even at the same credit volume.

Teams: buy it for coordination and permissions

Teams adds team roles and shareable scenario templates, with a current maximum file size of 500 MB. It becomes relevant when several employees or external specialists maintain workflows. The aim is to reduce dependence on shared credentials, undocumented copies and informal access arrangements.

Enterprise: governance drives the decision

Enterprise adds capabilities including custom functions, enterprise app integrations, overage protection, advanced security and higher support. A small firm does not need Enterprise simply because it serves large clients. The relevant triggers are concrete requirements such as single sign-on, formal security review, specific enterprise applications or contractual support expectations.

Three credit traps to understand

1. Scheduled checks can consume credits without producing output

A scenario that checks an inbox every 15 minutes can run 2,880 times in a 30-day month. Whether each empty check is billable depends on the trigger and how it executes, so inspect Make's history rather than assuming. Where an application supports a webhook - a notification that starts the scenario only when an event arrives - it can avoid unnecessary polling.

2. Bundles multiply downstream actions

Assume one trigger retrieves 20 new records and four downstream modules run for every record:

1 trigger operation + (20 records × 4 actions) = 81 operations

For standard one-credit actions, that is approximately 81 credits. Add one downstream module and usage rises by about 20 credits, not one. Make says routers and its dedicated error-handler modules do not consume credits, while actions that read, search, create, update, transform or aggregate data generally can.

3. AI can create two separate bills

When a scenario uses a connected external AI provider, Make can charge credits for the module activity while the model provider separately charges for token usage. With Make-supplied AI services, Make may use dynamic credit consumption based on the model, tokens or another usage factor.

Before approving an AI workflow, record which provider supplies the model, how Make calculates credits for that module, who pays for tokens and how much prompt or document size can vary.

What happens when credits run out?

Make says scenarios stop when the purchased credits are exhausted. It sends usage notifications at 75% and 90%. Incoming webhooks may queue within the account's storage allowance, while polling scenarios can search from the last successful run after service resumes.

Paid customers can upgrade or purchase extra credits. Make's pricing FAQ currently says extra credits may be available in 1,000- or 10,000-credit bundles, while automatic purchasing uses 10,000-credit blocks on Core, Pro and Teams. The exact price is defined by the subscription, so check the account's current terms instead of assuming a universal overage rate.

Annual credit flexibility also differs by tier. Make's current plan table associates 12-month credit expiry with annual Pro and Teams plans; the general FAQ says monthly credits expire at the end of the monthly term. Confirm the terms attached to the exact plan rather than treating all annual subscriptions alike.

Which plan should a consulting firm choose?

1. Build one representative workflow on Free.
2. Run realistic sample volumes - not one test record.
3. Review consumption by scenario and module.
4. Project normal and peak monthly usage.
5. Add a buffer for retries, growth and unusual batches.
6. Choose the lowest tier that supplies both the capacity and controls required.
7. Review the estimate after the first full billing cycle.

As a planning assumption - not a Make rule - using roughly 70–80% of the allowance in a normal month leaves room for variation without paying indefinitely for excessive spare capacity.

Choose Core when one owner needs dependable standard automations. Assess Pro when priority, troubleshooting or centrally reusable values matter. Move to Teams when permissions and shared development have become operational requirements.

Who should not buy Make yet?

• The underlying process changes every week.
• Staff do not agree which system contains the authoritative record.
• The applications lack workable integrations or APIs.
• No one owns monitoring and error resolution.
• Volume is so low that a manual checklist is clearer and safer.
• Client or regulatory requirements prohibit the proposed data flow.
• The team expects “no-code” to mean “no maintenance.”

Automation makes a stable process faster. It does not resolve unclear ownership or poor-quality data.

The conclusion

Make's entry prices are accessible, but its real cost is driven by workflow architecture and volume. Firms must consider how often scenarios run, how many bundles they process, how many downstream modules execute and whether AI introduces dynamic usage.

For many small professional-services firms, the most defensible route is Free for a controlled pilot followed by Core for live use. Pro and Teams should be purchased for specific operating controls - not because they sound more professional.

The important question is not, “How many automations can we build for $9?” It is, “How many actions will our actual workflows perform, and what happens when one fails?”

For a step-by-step calculation method, continue with How Many Make Credits Will Your Automation Actually Use?

If you are still choosing a platform, compare Make, Zapier and n8n for professional-services firms.