Make.com for Operations: A Lead-Routing Build, Costed
November 11, 2026 · PanaceaLogics Team
In August, Make stopped billing by “operations” and started billing by credits. For most scenarios nothing changed in practice: most actions still cost one credit each. But the switch is a good prompt to do something few teams ever do, which is to work out what a scenario costs before it goes live rather than after the first invoice.
This piece does that for one common build, and uses it to show where Make fits best.
Where Make fits
Make is a visual integration platform. You build a scenario as a chain of modules on a canvas, each module talking to an app, with routers and filters to send data down different branches. Its strength is that the logic is visible. An operations manager who has never written code can open a scenario, follow the lines and understand what happens to a record.
That makes it a strong fit for operations teams in small and mid-sized businesses whose work runs across a mix of everyday software: a CRM, a spreadsheet, a project tool, a chat app, an email platform. It is less suited to very high volumes of near-identical records, long-running processes, or anything that needs to stay inside your own network.
Pricing, from Make’s pricing page this November: a free plan with 1,000 credits a month, then Core at $9 a month, Pro at $16 and Teams at $29, each billed annually at the 10,000-credit level, with more credits available on a slider. Credits run out at the end of the month on monthly plans.
The build: routing inbound leads
A services business gets around 600 enquiries a month through a website form. Today someone copies each one into the CRM, works out who should own it, and posts it in a team channel. It takes a few minutes each, and the slow part is the minutes before anyone looks.
The scenario that replaces it looks like this:
- A webhook receives the form submission the moment it is sent.
- A search checks the CRM for an existing contact with that email.
- A router splits new contacts from returning ones.
- Create or update the contact in the CRM.
- Create a deal, assigned by region and service.
- Post a message in the right team channel, with a link to the deal.
- Send a confirmation email to the enquirer.
Counting the credits
Each module that performs an action uses a credit. The router is free, and so are error-handling modules.
| Step | Credits per lead |
|---|---|
| Webhook receives the form | 1 |
| Search CRM for the contact | 1 |
| Router | 0 |
| Create or update contact | 1 |
| Create deal | 1 |
| Post team message | 1 |
| Send confirmation email | 1 |
| Per lead | 6 |
Six hundred leads at six credits each is 3,600 credits a month, comfortably inside Core’s 10,000. For a few dollars a month, the business has removed a repetitive job and cut the time to first response from hours to under a minute.
That is the honest headline about Make: for a well-built scenario at modest volume, the platform cost is close to trivial. The cost to watch is not the typical lead. It is three design choices that quietly multiply the count.
Three settings that multiply the bill
Checking for new data on a schedule
Many apps do not send webhooks, so a scenario has to ask them every so often whether anything new has arrived. Each check reads data, and reading data uses a credit, whether or not there was anything new.
A scenario that checks every minute does that 43,200 times in a 30-day month. That alone is more than four times Core’s allowance, before a single lead is processed. Checking every 15 minutes brings it down to 2,880.
Where an app offers a webhook, use it. Where it does not, ask how fresh the data really needs to be. Most leads do not need routing within the minute; within fifteen is usually fine.
Looping over items
An iterator splits one record into many: the line items on an order, the attachments on an email, the rows in a file. Every module after the iterator then runs once per item.
If each enquiry carried a list of twelve services the customer ticked, and the scenario created a record for each, the three modules after the iterator would cost 36 credits per lead instead of 3. The scenario looks the same size on the canvas. The bill is several times larger.
Before adding an iterator, check whether the destination can accept the whole list in one call. Many can, and an aggregator can bundle items back into one before writing.
Adding an AI step
It is now common to add a model call that classifies the enquiry, scores it or drafts a reply. Make notes that some features using its built-in AI provider can use more than one credit per action. Run the scenario against a sample of real leads and read the actual credit count from the history before assuming.
What happens when credits run out
This is the part most teams discover by accident. When credits are exhausted, scenarios stop. Incoming webhooks are queued, but only up to a limit tied to your plan, which Make sets at 667 queued items for every 10,000 credits licensed. Beyond that, submissions can be lost.
For a lead-routing scenario that is a real business risk, not a technical one. Two safeguards are worth setting up on day one: turn on automatic purchase of extra credits if your plan allows it, and set an alert well before the allowance runs low.
Signs you have outgrown Make
Make covers a lot of ground, but a few signals suggest a different tool would serve better.
The credit count is dominated by loops over large volumes of near-identical records. A workflow engine billed per run rather than per step, such as n8n, often costs a fraction as much for that shape of work.
The process must stay inside your own network, for data protection or contractual reasons. Make is a hosted service.
The logic has grown beyond what a canvas makes clear. When a scenario needs custom code in several places, the visual layer starts hiding complexity rather than revealing it. At that point a small, properly tested service is easier to own.
And if most of your work already lives in Microsoft 365, Power Automate may be the more natural home. We have written about when Power Automate is not enough as well.
The short version
Make is at its best when the process is easy to draw, runs across several everyday apps, and the people who own it want to see it. Count the credits per run before you build, prefer webhooks to scheduled checks, keep iterators to the places they are truly needed, and decide in advance what happens when the allowance runs out.
Prices and credit rules from Make’s pricing page, November 2026. The lead-routing example is illustrative.
If you are weighing Make against n8n or GoHighLevel, our side-by-side comparison prices the same workload on all three. And if you want a second pair of eyes on a scenario’s design or its bill, get in touch.