What Make is good at
Make, previously Integromat, runs automation scenarios in the cloud on a visual canvas. Among the platforms listed on marketing and business automation services, it is the one that best balances capability against how much your team can follow, which is why it survives handover better than most.
- Branching you can see. Routers split a scenario into paths with their own filters, so “if the enquiry is from Australia and mentions a mortgage, do this instead” is visible on the canvas rather than buried in settings.
- Working with lists. Iterators and aggregators handle a set of records properly: process each order line, then bundle them back into one document. This is where simpler tools stop being enough.
- Operation-based pricing that generally works out cheaper than per-task pricing for multi-step scenarios, though the exact comparison depends on volume and should be modelled rather than assumed.
- Error handling as a first-class feature. Directives for retry, break and resume mean a failed run can be repaired rather than lost.
- A broad connector library plus a generic HTTP module for anything missing, including local services with an API.
What Make is bad at
- Getting complicated quickly. The same flexibility that makes it powerful lets scenarios sprawl into something nobody wants to touch. Discipline about sub-scenarios and naming is the difference, and it is a build decision rather than a platform feature.
- Operation counting. Costs are easy to underestimate, because every module run counts. A scenario that polls frequently can consume the plan faster than expected, so the design has to favour webhooks over polling.
- Data residency. It is a hosted service, so where customer data may be processed is decided by their terms rather than by you. For work that must stay on your own infrastructure, self-hosted n8n is the alternative.
- Very simple two-step jobs, where the extra capability just adds concepts a small team does not need.
What I build on Make
- Lead routing with real conditions: source, service, language, location and value deciding the owner and the follow-up, as on lead generation automation.
- Order and fulfilment scenarios for stores, including per-line-item processing and courier updates, described on eCommerce automation.
- Document generation and filing from templates, with bundles of records aggregated into one PDF.
- CRM synchronisation between two systems, with conflict rules rather than a blind overwrite.
- Scheduled data collection into Sheets for automated reports and dashboards.
- Messaging workflows that connect forms, WhatsApp and the CRM without a developer in the loop for every change.
When I would pick something else
| Situation | Better choice |
|---|---|
| Data must stay on your own servers | n8n, self-hosted |
| Very high execution volume | n8n, on cost |
| A non-technical team wants to build their own | Zapier |
| The work is really CRM workflow | HubSpot |
| Everything happens inside Google Workspace | Apps Script |
How a build runs
- Map the scenario on paper, including every branch and what happens when a step fails. Make rewards this because routers built as an afterthought are what turn a scenario into a maze.
- Design for operations cost. Webhooks instead of polling where possible, filters early so modules do not run needlessly, and an estimate of monthly operations before the build starts.
- Build in a separate scenario with test data, including the awkward cases: empty fields, duplicates, Nepali text and records that arrive twice.
- Add error handlers to every route, with alerting to a person and a store of failed records that can be reprocessed.
- Go live and watch the operations counter for a fortnight against the estimate, adjusting the design if it is running hot.
- Hand over with a blueprint export, naming conventions, documentation and training.
What you receive
- Scenarios in your own Make account, with a blueprint export you can import elsewhere.
- Connections and credentials in your name, documented, with the renewal points noted.
- Error handling and a failed-record store on every production route.
- An operations estimate and a note of which design choices keep the cost down.
- Plain-language documentation, handover training and optional month-to-month maintenance.
Pricing
Build cost is quoted per scenario and complexity, as a fixed project price with optional monthly maintenance. Make’s own subscription is paid by you, in your name, on their published plans, and I take no commission on it. I will tell you honestly when a cheaper platform would do the same job.
Next step
Tell me the process, the systems involved and roughly how many times a day it would run. I will come back within four business hours with whether Make is the right platform, an operations estimate and a fixed price.