Short answer

Make is our usual default for small and mid-market builds. A large connector library, a visual canvas your operations manager can follow, and per-credit pricing that is very cheap at low volume. We build on it when nobody on your side wants to run infrastructure, when non-technical people need to read and modify the workflows, and when volume is moderate and reasonably predictable.

We do not build on it when you are running hundreds of thousands of credits a month, when workflows need to sit in Git with review and rollback, or when the job is transforming 50,000 rows, which is work for a script. Under roughly 10,000 credits a month the cost is not a decision factor; above roughly 100,000, model it against self-hosted n8n properly.

What it is, and where it sits

Make is a visual workflow platform. You build scenarios on a canvas: a trigger module, then modules that fetch, filter, transform and write. It sits between your systems and moves work between them.

It is the tool we reach for first for a typical SMB build, because it hits the balance most businesses need: enough power for real logic, enough legibility that your operations manager can open a scenario and understand what it does.

What we build in it

Lead capture, routing and CRM sync, the most common Make build
Client onboarding sequences spanning five or six systems from one trigger
Order-to-invoice flows between operational systems and Xero or QuickBooks
Document generation and e-signature routing
Scheduled reporting assembled from multiple sources
Approval chains with timers, escalation and audit trail

How it is priced

Priced per credit (Make's name, since 2025, for what it used to call operations). Your bill scales directly with how much work the automation does.

Model	What you pay for	Best when
Per credit	One credit is roughly one module doing one thing once, so an eight-step scenario running 500 times a month consumes about 4,000 credits.	Volume is moderate and predictable. Under roughly 10,000 credits a month the cost is small enough not to be a decision factor.
Per credit, AI modules	More than one credit per operation, so AI steps consume the allowance faster than ordinary modules.	Counted separately when you estimate, rather than averaged in with the rest.

Estimate your monthly credits before committing: steps per scenario × runs per month, summed across scenarios. High-frequency, low-complexity workflows dominate this number: an email triage flow running 2,000 times a month costs more than an impressive 20-step reporting flow running weekly.

Above roughly 100,000 credits a month, model it against self-hosted n8n properly.

When to choose it, and when to think twice

Choose it when

Think twice when

Nobody on your side wants to run infrastructure. The single biggest factor, and a legitimate reason on its own.

Cost at high volumePer-credit pricing is unforgiving once you are running hundreds of thousands of credits a month.

You need broad connector coverage without writing custom HTTP calls, and mature error-handling routes and rollback behavior without building them.

Version control is weakScenario history exists but it is not Git. For teams with engineering discipline this is a real drawback.

Non-technical people need to read and eventually modify the workflows.

Complex logic gets visually unwieldyPast about thirty modules with several branches, the canvas becomes hard to reason about.

Volume is moderate and reasonably predictable.

Heavy data processing is the wrong fitTransforming 50,000 rows is a job for a script, not a visual platform.

No commercial relationship

We hold no reseller agreement with this vendor, take no affiliate commission, and do not resell licenses. You buy your own subscription directly. It is the only arrangement under which our recommendation means anything.

What we build in Make.com

What it is, and where it sits

What we build in it

How it is priced

When to choose it, and when to think twice

Want the cost model run on your numbers?